Hello!
Mi Blu Pure XL is dead, No OS installed.
I tried to install the system image with fastboot, but I have the following errors.
The recovery and Boot was installed OK.
[[email protected] BLU]# fastboot flash recovery BLU_RECOVERY_0.img
target reported max download size of 134217728 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.933s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.573s
Errors:
[[email protected] BLU]# fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected] BLU]# fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: unknown command)
finished. total time: 0.002s
[[email protected] BLU]# fastboot flash system BLU_SYSTEM_0.img
target reported max download size of 134217728 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
Please Help me!!! :crying:
Any Help!????
Any Help!????
This phone has a semi unlocked bootloader. You can only flash BOOT and RECOVERY. For the rest the need to use SP Flash Tool.
Error
Error with SP Flash Tool:
BROM Exception! ( BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)
I see that I need flash preloader firts. But i dont have preloader.bin
Someone could share ?
Thanks to all!!
I found everything needed in the following message
http://forum.xda-developers.com/pure-xl/general/blu-development-t3213354/post65349290#post65349290
Thanks to all! Today I am the happiest man in the world .
So it's my first time ever trying to root a phone and i can't install TWRP on my phone (Mate 10 Lite). My phone has both OEM unlocked and USB debugging on. I'm using ADB to install it.
That's what i get when i type in "fastboot flash recovery twrp.img" to the command window:
target reported max download size of 471859200 bytes
sending 'recovery' (25170 KB)...
OKAY [ 0.629s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.636s
twrp file I'm using: https://forum.xda-developers.com/ma...s-recoveries--other-development/twrp-t3737747
and the tutorial I followed: https://www.xda-developers.com/how-to-install-twrp/
It's my first time ever doing something like this so please be understanding.
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Why not try installing TWRP via magisk?? Its easier that way
/\ agree /\
:angel:
lawrence_craig said:
Hey guys,
I recently flashed HAVOC OS on my 1+7 Pro.
I got to TWRP by using the boot command, however now I cannot boot to TWRP. When using the command:
Code:
fastboot flash recovery twrp.img
I get the following error:
Code:
sending 'recovery' (31440 KB)...
OKAY [ 0.697s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.733s
Then when I try:
Code:
fastboot boot twrp.img
I get the following error:
Code:
downloading 'boot.img'...
OKAY [ 0.698s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.728s
Is anyone able to help?
Click to expand...
Click to collapse
Make sure you are using the latest TWRP img.
Never flash recovery. Always boot recovery and then install TWRP zip. Have you not read the instructions?
As others mentioned, easier way to recover TWRP is to flash a magisk patch boot.img and flash TWRP zip in magisk.
Thanks for the tips guys, all sorted!
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?
EDIT : THIS ERROR ONLY HAPPENS ON WINDOWS. GO TO THE TELEGRAM GROUP IN THE BOTTOM LINK AND INSTALL PIZZAG'S MINT LINUX. AS IT HAS ADB AND FASTBOOT DRIVERS BAKED IN. ROMS FLASH FLAWLESSLY ON LINUX. IF YOU HAVE ANY PROBLEMS CONTACT THE DEVS VIA TELEGRAM.
C\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash boot boot.img
1031shadow said:
Sending 'boot_a' (98304 KB) OKAY [ 3.350s]
Writing 'boot_a' OKAY [ 1.409s]
Finished. Total time: 4.808s
ADD HERE fastboot reboot fastboot then it should reboot to twrp fast boot then the super.img will flash correctly
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash super super.img
Sending sparse 'super' 1/5 (774340 KB) OKAY [ 26.719s]
Writing 'super' OKAY [ 0.049s]
Sending sparse 'super' 2/5 (784673 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase metadata
Erasing 'metadata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Flashing Should Be Finished
Device Flashing Should Be Finished
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Should Be Rebooting To Android
Device Should Be Rebooting To Android
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO PRESS ENTER TO EXIT
PRESS ENTER TO EXIT
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>PAUSE
IF ANYONE HAS AN ERROR LIKE THE ONE ABOVE . WHERE EVERYTHING FLASHES
BUT SUPER.IMG or system a.img
edit the script and make this change
RIGHT CLICK THE SCRIPT THEN EDIT GO TO THE LINE AFTER
FASTBOOT FLASH BOOT BOOT.IMG AND ADD THIS fastboot reboot fastboot IT SHOULD LOOK LIKE THIS:
fastboot flash boot_a boot.img
ECHO
ECHO
fastboot reboot fastboot
ECHO
ECHO
SLEEP 2
fastboot flash system_a system.img
this fixes super.img (no link FAILED (Write to device failed (no link))
and system A.img (FAILED (Write to device failed (no link))
ALSO YOU SHOULD INSTALL SYSTEM WIDE ADB AND DOWNLOAD GOOGLES PLATFORM
(ON WINDOWS AND LINUX IF NOT ALREADY INSTALLED)
TOOLS AFTER INSTALL. GO TO THE ROOT OF YOUR HARD DRIVE IN THE ADB FLODER AND REPLACE THE ALL THE FILES THERE FOR THE ONES IN THE PLATFORM TOOLS YOU DOWNLOADED FROM GOOGLE. IF YOU HAVE A RYZEN CPU DOWNLOAD AND INSTALL THE FIXES FOR FASTBOOT
for system wide adb https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
credit goes to
Snoop05 for system wide adb
The new telegram account has several moto devices unified in one group they also have a chat room where other users and the actual devs will respond to your inquiries or you can message them directly on telegram.
Another thing is windows is trash if you want the best compatibility with the ROM flasher he provides you can install his mint Linux with adb and fastboot installed also has dump and build tool for those who like his ROMs .
the above error only happens in Windows I've tested on Linux and it works without having to edit the script
all credit goes to
A-Team @pizzaG
https://t.me/A_Team_Digital_Solutions
Thank you. !
Much appreciated on the links and detailed info.
1031shadow said:
FOR ANYONE WHO HAS THIS ERROR GO TO THE BOTTOM OF THE PAGE FOR FIX
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 3.350s]
Writing 'boot_a' OKAY [ 1.409s]
Finished. Total time: 4.808s
ADD HERE fastboot reboot fastboot then it should reboot to twrp fast boot then the super.img will flash correctly
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot flash super super.img
Sending sparse 'super' 1/5 (774340 KB) OKAY [ 26.719s]
Writing 'super' OKAY [ 0.049s]
Sending sparse 'super' 2/5 (784673 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot erase metadata
Erasing 'metadata' OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Flashing Should Be Finished
Device Flashing Should Be Finished
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO Device Should Be Rebooting To Android
Device Should Be Rebooting To Android
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO
ECHO is on.
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>ECHO PRESS ENTER TO EXIT
PRESS ENTER TO EXIT
C:\Users\dali\Downloads\KomodoOS_A12_Custom_GSI-Moto_G_Stylus_5G_2022_XT2215-4-v0.01>PAUSE
IF ANYONE HAS AN ERROR LIKE THE ONE ABOVE . WHERE EVERYTHING FLASHES
BUT SUPER.IMG or system a.img
edit the script and make this change
RIGHT CLICK THE SCRIPT THEN EDIT GO TO THE LINE AFTER
FASTBOOT FLASH BOOT BOOT.IMG AND ADD THIS fastboot reboot fastboot IT SHOULD LOOK LIKE THIS:
fastboot flash boot_a boot.img
ECHO
ECHO
fastboot reboot fastboot
ECHO
ECHO
SLEEP 2
fastboot flash system_a system.img
this fixes super.img (no link FAILED (Write to device failed (no link))
and system A.img (FAILED (Write to device failed (no link))
i contacted the developer for a fix but no reply so i fixed it myself i love these roms but very little help from the comunity so i did it myself ive been rooting for 12 years now so not a noob but not a dev
ALSO YOU SHOULD INSTALL SYSTEM WIDE ADB AND DOWNLOAD GOOGLES PLATFORM TOOLS AFTER INSTALL. GO TO THE ROOT OF YOUR HARD DRIVE IN THE ADB FLODER AND REPLACE THE ALL THE FILES THERE FOR THE ONES IN THE PLATFORM TOOLS YOU DOWNLOADED FROM GOOGLE. IF YOU HAVE A RYZEN CPU DOWNLOAD AND INSTALL THE FIXES FOR FASTBOOT
for system wide adb https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
credit goes to
Snoop05 for system wide adb
i also wanted to add i really appreciate the developers for this rom for even taking time to develop roms and root for this device i will be posting the links for their telegram to download custom gsi and custom stock roms it was almost impossible to find as of writing
all credit goes to
A-Team @pizzaG https://t.me/ATeamReleases
Click to expand...
Click to collapse
ATeamReleases is not found on Telegram right now.
Your right I'ma edit with new links
403 forbidden
https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/