Having trouble updating from RR to stock pie. Cant update bootlader

Having trouble updating from RR to stock pie. Cant update bootlader - Google Pixel 2 Questions & Answers

So Ive been running the last verions of RR and decided I wanted to update to stock pie on my Pixel 2. Proving way more difficult then I thought.
On a mac with the latest platform tools.
Flash-all does not work, as it gives these errors:
Code:
./flash-all.sh
./flash-all.sh: line 18: fastboot: command not found
./flash-all.sh: line 19: fastboot: command not found
./flash-all.sh: line 21: fastboot: command not found
./flash-all.sh: line 22: fastboot: command not found
./flash-all.sh: line 24: fastboot: command not found
Then I tried to run each line individually, which sorta works. But trying to update the bootloader results in this error:
Code:
./fastboot flash bootloader bootloader-walleye-mw8998-002.0075.02.img
Sending 'bootloader_a' (38696 KB) OKAY [ 1.002s]
Writing 'bootloader_a' (bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: 'Command Flash Error')
Finished. Total time: 1.008s
Any idea what's going on or how to resolve this?

Have you updated your ADB tools?

Related

Rooting?

Over the past few years, my need to root my phone has diminished because Google and Samsung have added most things I needed from root...
Are there still reason to root this device? Any cool things we are missing out on without root?

There is no way to root this device. Bootloader is locked ?

Just Google "root Huawei p40 pro" and there are several links to unlock it
https://myphoneupdate.com/unlock-bootloader-huawei-p40-pro/

RedSkyRoad said:
Just Google "root Huawei p40 pro" and there are several links to unlock it
Click to expand...
Click to collapse
There is no way to root and unlock P40 Pro bootloader, all the links online are auto-generated spam advertising products such as KingRoot.
If you don't believe, check Huawei official forums. There are thousands of people asking Huawei for unlock codes and they all get the same reply.

Unlock Bootloader script - By SkyEmie_'
(Please enable USB DEBBUG and OEM UNLOCK if the device isn't appear..)
/!\ All data will be erased /!\
Press any key to detect device..
List of devices attached
K5J0220313014947 device
Type IMEI digit :860996043157062
Press any key to reboot your device..
Press any key when your device is ready.. (This may take time, depending on your cpu/serial port)
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
(bootloader) Necessary to disable Phone finder
FAILED (remote: 'Command not allowed')
---------- Post added at 01:15 PM ---------- Previous post was at 01:14 PM ----------
i tried to disable find my phone but it reactive automatically i tried everything from disconnecting huawei id diasbling developper mode adminstrator etc wtf with this huawei ****

ahh pity.
was about to buy this phone. buy i can't live with so many ads anymore. especially now manufacturers are sending them to homescreens lock screens notifications etc.
i assume we still need root to install most of the adaway adblock plus and minmingaurd and similar best apps?
---------- Post added at 06:37 PM ---------- Previous post was at 06:32 PM ----------
RedSkyRoad said:
Just Google "root Huawei p40 pro" and there are several links to unlock it
https://myphoneupdate.com/unlock-bootloader-huawei-p40-pro/
Click to expand...
Click to collapse
according to other members this doesn't work. have you actually used it?

articoceanic said:
ahh pity.
was about to buy this phone. buy i can't live with so many ads anymore. especially now manufacturers are sending them to homescreens lock screens notifications etc.
i assume we still need root to install most of the adaway adblock plus and minmingaurd and similar best apps?
Click to expand...
Click to collapse
What ads? I don't have any ads on my phone

RedSkyRoad said:
What ads? I don't have any ads on my phone
Click to expand...
Click to collapse
all android phones have ads. either in browser or apps. on pc u can install adblockers in your browsers. but on android phone it is harder.
you need root access to install adblockers. as google makes its money from ads.
now some manufacturers are moving towards showing ads in home and lock screen and notification panels etc. like how some Samsung tvs show ads in the home menu etc.
so adblocking is a priority for me in whatever tech i buy, tv phone pc etc.

articoceanic said:
all android phones have ads. either in browser or apps. on pc u can install adblockers in your browsers. but on android phone it is harder.
you need root access to install adblockers. as google makes its money from ads.
now some manufacturers are moving towards showing ads in home and lock screen and notification panels etc. like how some Samsung tvs show ads in the home menu etc.
so adblocking is a priority for me in whatever tech i buy, tv phone pc etc.
Click to expand...
Click to collapse
It is perfectly possible to block ads without root.
I use a vpn based open source app called Blokada, available on F-Droid... https://f-droid.org/en/packages/org.blokada.alarm/
Other similar apps are available.
While it's not quite as effective as the host file based ad blockers that require root, such as adaway, it's still very good, with plenty of lists to download, and I see very few ads on my phone.

Or an ad blocking dns address like dns.adguard.com

articoceanic said:
all android phones have ads. either in browser or apps. on pc u can install adblockers in your browsers. but on android phone it is harder.
you need root access to install adblockers. as google makes its money from ads.
now some manufacturers are moving towards showing ads in home and lock screen and notification panels etc. like how some Samsung tvs show ads in the home menu etc.
so adblocking is a priority for me in whatever tech i buy, tv phone pc etc.
Click to expand...
Click to collapse
I support the devs and buy the apps. Browsers can be blocked with addons

Pixel 2 bricked? Only boots to bootloader

Hi all, i have a Pixel 2 64gb unlocked bootloader and recently tried to flash stock factory image android 11 but somehow it went wrong and now being stuck on bootloader only, it wont boot to elsewhere except bootloader.
Before I begin this, it was on Android 12 Pixel Experience custom rom.
i had no issue with the ADB or Fastboot drivers but it just seem doesn't work even updating everything.
below is the result i get when trying to fastboot factory image
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
fastboot: error: Failed to identify current slot
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
getvar:version-baseband FAILED (remote: 'unknown command')
getvar:serialno FAILED (remote: 'GetVar Variable Not found')
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (remote: 'unknown command')
Checking 'product' FAILED
Could not getvar for 'product' (remote: 'GetVar Variable Not found')
fastboot: error: requirements not met!
Press any key to exit...
I have tried many ways to recover it but does not work still. In device manager, it shows up as android bootloader surface so it shall work.
Another thing here is I try to boot a temporary twrp to it but it wont flash and will stuck at sending "Recovery"...
Let me know if anyone here could help, thanks a lot.

FB not flashing one these

hi
its op8 os12 when ever i try FB os12 rom to flash i always get bootload and not flashing these files only
even device is in FBD mode
Code:
Writing 'my_bigball_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
E:\IN2011_11_C.21_202205172355>fastboot flash my_carrier_b my_carrier.img
Sending 'my_carrier_b' (340 KB) OKAY [ 0.000s]
Writing 'my_carrier_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
E:\IN2011_11_C.21_202205172355>fastboot flash my_company_b my_company.img
Sending 'my_company_b' (328 KB) OKAY [ 0.016s]
Writing 'my_company_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
E:\IN2011_11_C.21_202205172355>fastboot flash my_engineering_b my_engineering.img
Sending 'my_engineering_b' (328 KB) OKAY [ 0.016s]
Writing 'my_engineering_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Oneplus 8 IN2017 Error while flashing Global rom.

I got this error while flashing global rom in oneplus 8 In2017. Please assist me.
I unlocked the bootloader and just press flash-all file in Global rom file and now my phone is stuck in Fastmode and this error occurs in windows 11 pc. SDK tools are up-to-date, fastboot version is 33.03 I just downloaded them from their official site.
I also tried:
fastboot flashing unlock
fastboot flashing unlock_critical
but it said ,Device Already: Unlocked
Please help me otherwise I'll lost my device.
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.117s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\khateeb\Desktop\G-Rom Flash Oneplus 8 5G\10.5.12-GLOBAL-OnePlus8Oxygen_15.O.21_OTA_021_all_2008080054_906daa239-FASTBOOT/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Sending 'boot_a' (98304 KB) OKAY [ 3.290s]
Writing 'boot_a' OKAY [ 0.518s]
Finished. Total time: 3.871s
Sending 'dtbo' (8192 KB) OKAY [ 0.276s]
Writing 'dtbo' OKAY [ 0.025s]
Finished. Total time: 0.350s
Sending 'modem_a' (524288 KB) OKAY [ 17.560s]
Writing 'modem_a' OKAY [ 2.063s]
Finished. Total time: 19.678s
Sending 'recovery' (102400 KB) OKAY [ 3.386s]
Writing 'recovery' OKAY [ 0.337s]
Finished. Total time: 3.767s
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.059s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.008s]
Finished. Total time: 0.075s
current-slot: a
Finished. Total time: 0.010s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1996 KB) OKAY [ 0.070s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.009s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'bluetooth' (460 KB) OKAY [ 0.022s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.018s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'devcfg' (48 KB) OKAY [ 0.004s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.117s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'featenabler' (88 KB) OKAY [ 0.011s]
Writing 'featenabler' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'hyp' (436 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.009s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'keymaster' (248 KB) OKAY [ 0.018s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'logo' (7784 KB) OKAY [ 0.233s]
Writing 'logo' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'mdm_oem_stanvbk' (3776 KB) OKAY [ 0.118s]
Writing 'mdm_oem_stanvbk' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'multiimgoem' (16 KB) OKAY [ 0.012s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'odm' (960 KB) OKAY [ 0.032s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'opproduct' (48828 KB) OKAY [ 1.580s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'qupfw' (56 KB) OKAY [ 0.010s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'spunvm' (348 KB) OKAY [ 0.013s]
Writing 'spunvm' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3236 KB) OKAY [ 0.120s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl' (3392 KB) OKAY [ 0.116s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl_config' (96 KB) OKAY [ 0.007s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed

Khateeb2110 said:
I got this error while flashing global rom in oneplus 8 In2017. Please assist me.
I unlocked the bootloader and just press flash-all file in Global rom file and now my phone is stuck in Fastmode and this error occurs in windows 11 pc. SDK tools are up-to-date, fastboot version is 33.03 I just downloaded them from their official site.
Click to expand...
Click to collapse
You are a candidate for the MSM Tool to revert back to stock.
-- Did you follow this guide to alleviate the pain of converting to Global?

rodken said:
You are a candidate for the MSM Tool to revert back to stock.
-- Did you follow this guide to alleviate the pain of converting to Global?
Click to expand...
Click to collapse
Yes similar procedure , I got bootloader unlock token from oneplus site.
then I just unlocked the bootloader and run flash-all file in Global rom folder. Then I got this error.
then I tried :
fastboot flashing unlock
fastboot flashing unlock_critical
It said that device is unlocked but still facing this error.
I think that error is from this command:
fastboot reboot fastboot
I got this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
after that no more commands are able to run properly.

Khateeb2110 said:
I think that error is from this command:
fastboot reboot fastboot
I got this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
after that no more commands are able to run properly.
Click to expand...
Click to collapse
Try to avoid using the flash-all bat file. Run each command separately and switch slots to see if you hit paydirt.

rodken said:
Try to avoid using the flash-all bat file. Run each command separately and switch slots to see if you hit paydirt.
Click to expand...
Click to collapse
what do you mean by switching slots?

Khateeb2110 said:
what do you mean by switching slots?
Click to expand...
Click to collapse
How to manually switch the active slot - link.

rodken said:
How to manually switch the active slot - link.
Click to expand...
Click to collapse
Thankyou so much bro that error got solved but now getting a new error:
Writing 'product' FAILED (remote: 'No such file or directory')
i rechecked the file name also tried by dragg in drop but still not working.

Khateeb2110 said:
Thankyou so much bro that error got solved but now getting a new error:
Writing 'product' FAILED (remote: 'No such file or directory')
i rechecked the file name also tried by dragg in drop but still not working.
Click to expand...
Click to collapse
In some cases, you might need a high-end USC-C cable or reinstall your ADB drivers from a different source.

rodken said:
In some cases, you might need a high-end USC-C cable or reinstall your ADB drivers from a different source.
Click to expand...
Click to collapse
I'm using original cable of oneplus 8 and also downloaded sdk tools from official android site and also tried from some other sites. but still getting this error at last step of flashing rom.

Khateeb2110 said:
I'm using original cable of oneplus 8 and also downloaded sdk tools from official android site and also tried from some other sites. but still getting this error at last step of flashing rom.
Click to expand...
Click to collapse
Is there a reason as to why you haven't skipped the last step to see if the device will boot?

Ye
rodken said:
Is there a reason as to why you haven't skipped the last step to see if the device will
Click to expand...
Click to collapse
Yeah! I tried once but it goes to Qualcomm CrashDump Mode.

Khateeb2110 said:
Ye
Yeah! I tried once but it goes to Qualcomm CrashDump Mode.
Click to expand...
Click to collapse
It's clearly the ROM that you are flashing.
-- Are you in FastbootD mode when flashing?

rodken said:
It's clearly the ROM that you are flashing.
-- Are you in FastbootD mode when flashing?
Click to expand...
Click to collapse
Yes when I run:
fastboot reboot fastboot
My phone reboots and open in fastbootd mode. and fastbootd is written on the top of phone. so i'm sure about that.
I also tried by installing Indian version. but it also got the same error.
All the files got flashed successfully. but at the end the :
fastboot flash product product.img
is not working properly.

Khateeb2110 said:
All the files got flashed successfully. but at the end the :
fastboot flash product product.img
is not working properly.
Click to expand...
Click to collapse
Indication points to the fact that the ROM is somewhat corrupted.
Have you tried to run the commands in Fastboot mode and not FastbootD mode?

When I tried this in fast boot it said "no such partition". but when i flash in fastbootd mode it said "no such file or directory".

Khateeb2110 said:
When I tried this in fast boot it said "no such partition". but when i flash in fastbootd mode it said "no such file or directory".
Click to expand...
Click to collapse
Wondering if the flash-all file within in the Global ROM folder corrupted a file or two.

So you are saying that the files are corrupted???

Khateeb2110 said:
So you are saying that the files are corrupted???
Click to expand...
Click to collapse
Just the file that is seeming to be a problem child in 'writing'.
-- Bear in mind that not all ROMs are created equal regarding stability even after downloading it and flashing it.
-- Have you seen this thread as of yet?

rodken said:
Just the file that is seeming to be a problem child in 'writing'.
-- Bear in mind that not all ROMs are created equal regarding stability even after downloading it and flashing it.
-- Have you seen this thread as of yet?
Click to expand...
Click to collapse
I tried by changing Rom file global and indian but both are showing same error.
Brother Now I switched the slot and used the latest global rom. All files are flashed successfully but phone is not booting, when I turn on the phone it opens in fastboot mode. Any solution.

Khateeb2110 said:
Brother Now I switched the slot and used the latest global rom. All files are flashed successfully but phone is not booting, when I turn on the phone it opens in fastboot mode. Any solution.
Click to expand...
Click to collapse
Have you tried to redownload the ROM and try again?

Flashing is not allowed for Critical Partitions

Hello guys!
Today I unlocked my old oneplus 6 phone,I wanted to flash google rom,so I execute
Bash:
adb reboot bootloader
and run flash script inside google android images.
Bash:
└─$ ./flash-all.sh
Sending 'bootloader' (4620 KB) OKAY [ 0.154s]
Writing 'bootloader' FAILED (remote: 'Flashing is not allowed for Critical Partitions
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.051s
I have no idea why this happpened,so I searched on google but got nothing.
And I've tried
Bash:
└─$ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
Since I am new to these kinds of topics,any advice would be appreciated.

did you already set fastboot flashing unlock ?
makesure your adb / platform-tools is the latest too

Database Info

welcome