Hi, I´m trying to recovery my Huawei G740, and I have from the other Huawei G740 all files to recovery my phone (boot.img/recovery.img/system.img/userdata.img/cache.img and custom.img, but when I put all together with fastboot the phone don´t work, It try to start after that restart itself and come inside recovery mode, any suggestion or advice to make this work guys.Thank you.
I:\Android\sdk\platform-tools>fastboot devices
96ee49a fastboot
I:\Android\sdk\platform-tools>fastboot flash cache cache.img
sending 'cache' (196608 KB)...
OKAY [ 12.415s]
writing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 12.421s
I:\Android\sdk\platform-tools>fastboot flash cust cust.img
sending 'cust' (262144 KB)...
OKAY [ 16.512s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 16.517s
I:\Android\sdk\platform-tools> fastboot flash boot boot.img
sending 'boot' (12288 KB)...
OKAY [ 0.773s]
writing 'boot'...
OKAY [ 0.608s]
finished. total time: 1.382s
I:\Android\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)...
OKAY [ 1.029s]
writing 'recovery'...
OKAY [ 1.023s]
finished. total time: 2.053s
I:\Android\sdk\platform-tools>fastboot flash userdata userdata.img
sending 'userdata' (460449 KB)...
OKAY [ 28.798s]
writing 'userdata'...
OKAY [ 22.669s]
finished. total time: 51.469s
I:\Android\sdk\platform-tools>fastboot flash system system.img
sending 'system' (445101 KB)...
OKAY [ 27.826s]
writing 'system'...
OKAY [ 21.810s]
finished. total time: 49.636s
I:\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.005s
Long time Droid Pro user who now has got a hold of a Droid RAZR XT912. I am trying to get it completely back to stock in order to flash it over to Pageplus. It IS a VZW XT912 was rooted and had safestrap 3.11 installed and I was running CM10.2 Spyder (very slick ROM). Anyhow I want to zero the phone back to stock and I don't have access to a windows machine that can RSD Lite back to stock so I am trying to use the Matt L Groff Batarang Droid RAZR script which is an amazing piece of work. So I put the XT912 into AP Fastboot and run the program in Linux and it does all the flash magic but it will not write the preinstall img or recovery img files...everything else works fine and the phone reboots into the radio programming screen and then reboots to a fresh install WITH superuser ROOT still intact. I did not install OTA Voodoo rootkeeper or any other root retention apk. Any ideas using the Linux script to flash the phone back to completely non rooted stock?
I tried to search all the message boards and threads but I can't find a specific solution....thank you for you time if anyone has any ideas? I downloaded the script twice and checked the MD5sums.
thanks in advance.
here is the script string
sending 'mbm' (512 KB)...
OKAY [ 0.039s]
writing 'mbm'...
OKAY [ 0.526s]
finished. total time: 0.565s
rebooting into bootloader...
OKAY [ 0.147s]
finished. total time: 0.147s
Press any key when the screen flashes back on.
sending 'mbmloader' (42 KB)...
OKAY [ 0.011s]
writing 'mbmloader'...
OKAY [ 0.292s]
finished. total time: 0.303s
sending 'mbm' (512 KB)...
OKAY [ 0.162s]
writing 'mbm'...
OKAY [ 0.582s]
finished. total time: 0.744s
rebooting into bootloader...
OKAY [ 0.154s]
finished. total time: 0.154s
Press any key when the screen flashes back on.
erasing 'cache'...
OKAY [ 0.040s]
finished. total time: 0.040s
sending 'logo.bin' (854 KB)...
OKAY [ 0.060s]
writing 'logo.bin'...
OKAY [ 0.286s]
finished. total time: 0.345s
sending 'devtree' (512 KB)...
OKAY [ 0.170s]
writing 'devtree'...
OKAY [ 0.514s]
finished. total time: 0.684s
error: cannot load 'system.img'
sending 'boot' (8192 KB)...
OKAY [ 0.512s]
writing 'boot'...
OKAY [ 0.885s]
finished. total time: 1.397s
sending 'recovery' (9216 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 1.421s]
finished. total time: 1.993s
error: cannot load 'preinstall.img'
sending 'radio' (21936 KB)...
OKAY [ 1.364s]
writing 'radio'...
OKAY [ 2.788s]
finished. total time: 4.153s
rebooting...
finished. total time: 0.150s
Your device will now reboot and install radio files, then fully boot normally.
hi, I need help.
I have flashed a ROM 5.1.1 XT1527 XT1524 in but did not have the bootloader unlocked, and apparently pedia have now unlocked bootloader and flash a rom whenever I get this:
Flashing GPT and bootloaders ...
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.351s
error: cannot load 'motoboot.img'
Flashing Modem SW ...
sending 'modem' (54616 KB)...
OKAY [ 1.716s]
writing 'modem'...
OKAY [ 3.549s]
finished. total time: 5.265s
Flash AP images ...
sending 'logo' (679 KB)...
OKAY [ 0.020s]
writing 'logo'...
OKAY [ 0.100s]
finished. total time: 0.120s
sending 'boot' (32768 KB)...
OKAY [ 1.040s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.639s
sending 'recovery' (32752 KB)...
OKAY [ 1.031s]
writing 'recovery'...
OKAY [ 2.065s]
finished. total time: 3.096s
sending 'system' (262143 KB)...
OKAY [ 8.220s]
writing 'system'...
Invalid signed image
Preflash validation failed
FAILED (remote failure)
finished. total time: 8.620s
sending 'system' (262141 KB)...
OKAY [ 8.230s]
writing 'system'...
Invalid signed image
Preflash validation failed
FAILED (remote failure)
finished. total time: 8.255s
sending 'system' (262141 KB)...
OKAY [ 8.222s]
writing 'system'...
Invalid signed image
Preflash validation failed
FAILED (remote failure)
finished. total time: 8.271s
Wipe Cache and Data ...
erasing 'userdata'...
OKAY [ 0.521s]
finished. total time: 0.522s
erasing 'cache'...
OKAY [ 0.042s]
finished. total time: 0.042s
What I understand and what I am doing is going back to an earlier or better version Downgrade but I will not let that do not have the bootloader unlocked, and can not unlock it since it does not activate the option in developers "Allow OEM Unlock" that copion not active, and now I'm stuck in fastboot mode and I can not do anything .
This is what I get when trying to unlock the bootloader :
D:\moto e 5.1.1\FlashFirmware 5.0.2 AMXLA>mfastboot devices
TA0930ILHQ fastboot
D:\moto e 5.1.1\FlashFirmware 5.0.2 AMXLA>fastboot oem unlock EOW2SHFPQ5XESUDR5YNX
...
Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s
Now I 've read post on the internet and I have to flash a rom the same cid and this is my cid and so I understand the cid12 is for Latin America and yet does not leave me any flash rom I always generates the same problem
D:\moto e 5.1.1\FlashFirmware 5.0.2 AMXLA>fastboot getvar cid
cid: 0x000C
finished. total time: 0.008s
You can unlock the bootloader without marking the option "Allow OEM Unlock" ?
is that all you can flash rom stock without having the bootloader unlocked, but that leaves no flash ?
what am I doing wrong?
someone could help me revive my cell
hello, me exactly the same way someone could help me please, thank you very much
**************THE PROBLEM***************
Boot into recovery (twrp) - and flash Los 15.1 after formatting internal- then comes the *error 255* .
So I tried it with twrp treble and it flashed without any problems.
After flashing I clicked reboot and it rebooted into twrp again.
No matter how many times I try rebooting from system or twrp it boots into twrp itself. *Tried with many twrps*
But it boots into bootloader and from there I could click start to boot to system!
So I thought I would flash stock ROM (Oreo August) and I did. On rebooting, it went straight to stock recovery and I selected reboot to system and it didn't! It rebooted back to the recovery!
So I rebooted into the bootloader and clicked start and then it boots! And it shows encrypting and reboots to the setup area.
After setting up I rebooted the device ( normal way ) and again I found myself in the stock recovery!!
**************** THE SOLUTION **************
FLASH STOCK NOUGAT ROM (I FLASHED THE NOVEMBER BUILD)
Link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Since I was on Oreo downgrading was not directly applicable.. I flashed TWRP and formatted the phone then booted to bootloader and flashed the stock ROM!
Fastboot commands didn't work exactly ! So I followed this guide to get the servicefile.xml in the ROM zip to create a new .bat file that flashed the phone!
Link: https://youtu.be/njXQYn53SPc
OR
I've made an attachment of the .bat file that you can download and extract.
Bootloader was left unlocked!
OTAs were successful! No issues so far! Flashed November 2017 Fastboot ROM and updated to August 2018 Oreo via OTA!
Cheers People!! Happy Flashing!!
Oh! And as always! No one will take responsibility for your actions! You alone are responsible!! ? #standardprocedure
Hi, u wipe data and factory data in the recovery before installing stock? i had the same problem yesterday and I solved it flashing stock 7.1.1 (NPSS26.118-19-14 - November 2017)
SteveO-RG said:
Hi, u wipe data and factory data in the recovery before installing stock? i had the same problem yesterday and I solved it flashing stock 7.1.1 (NPSS26.118-19-14 - November 2017)
Click to expand...
Click to collapse
Thanks mate! It Worked Well! ??
Cheers!!
I have the same problem. I've tried TWRP 3.2.1_r12 and 3.2.3-0, in both cases the phone reboots to recovery and I have to reboot again to bootloader and from there to the OS. Any way to fix this without going back to stock ROM? It's no big deal, I reboot rarely, but still slightly annoying.
indrekh said:
I have the same problem. I've tried TWRP 3.2.1_r12 and 3.2.3-0, in both cases the phone reboots to recovery and I have to reboot again to bootloader and from there to the OS. Any way to fix this without going back to stock ROM? It's no big deal, I reboot rarely, but still slightly annoying.
Click to expand...
Click to collapse
I honestly tried many times to get it working normally without going back to stock ROM but couldn't!
Sorry bruv! I guess this is the only way! :angel:
the_phantom_97 said:
I honestly tried many times to get it working normally without going back to stock ROM but couldn't!
Sorry bruv! I guess this is the only way! :angel:
Click to expand...
Click to collapse
Bummer. Thanks anyway
DUDE!!!
I had an Issue yesterday while trying to downgrade and i ended having a custom ROM with the fingerprint sensor disabled i dont know why!
But today i followed this thread an solved the problem!!
A lot of thanks my friend! My eternal gratitude!!!
Thanks for this solution, but I still get BAD KEY message and I can't relock bootloader. Any advice to solve this problem? Thx
the_phantom_97 said:
**************THE PROBLEM***************
Boot into recovery (twrp) - and flash Los 15.1 after formatting internal- then comes the *error 255* .
So I tried it with twrp treble and it flashed without any problems.
After flashing I clicked reboot and it rebooted into twrp again.
No matter how many times I try rebooting from system or twrp it boots into twrp itself. *Tried with many twrps*
But it boots into bootloader and from there I could click start to boot to system!
So I thought I would flash stock ROM (Oreo August) and I did. On rebooting, it went straight to stock recovery and I selected reboot to system and it didn't! It rebooted back to the recovery!
So I rebooted into the bootloader and clicked start and then it boots! And it shows encrypting and reboots to the setup area.
After setting up I rebooted the device ( normal way ) and again I found myself in the stock recovery!!
**************** THE SOLUTION **************
FLASH STOCK NOUGAT ROM (I FLASHED THE NOVEMBER BUILD)
Link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Since I was on Oreo downgrading was not directly applicable.. I flashed TWRP and formatted the phone then booted to bootloader and flashed the stock ROM!
Fastboot commands didn't work exactly ! So I followed this guide to get the servicefile.xml in the ROM zip to create a new .bat file that flashed the phone!
Link:
OR
I've made an attachment of the .bat file that you can download and extract.
Bootloader was left unlocked!
OTAs were successful! No issues so far! Flashed November 2017 Fastboot ROM and updated to August 2018 Oreo via OTA!
Cheers People!! Happy Flashing!!
Oh! And as always! No one will take responsibility for your actions! You alone are responsible!! ? #standardprocedure
Click to expand...
Click to collapse
JRapsky said:
Thanks for this solution, but I still get BAD KEY message and I can't relock bootloader. Any advice to solve this problem? Thx
Click to expand...
Click to collapse
That is most probably because you're trying to flash an old firmware wherein your bootloader is already on the newer one! We'll try flashing with this December 2018 firmware linked below but don't use the zip in the thread... It is only for Nougat Firmware!
2018 December Firmware:-
https://androidfilehost.com/?fid=11410963190603890525
Fastboot command zip by @brunorochaa00 :- https://androidfilehost.com/?fid=13356325061477270130
this zip has the fastboot and the commands... Just extract the firmware to the folder where you extract the zip and flash any of the .bat files!!
i ran through all these commands but it still says no OS is installed in TWRP
trying to install custom rom give 255 ERROR'
do these logs look normal?
PS C:\adb> .\2-Instalador-Completo.bat
*************************************************
* Instalador Firmware *
* Moto Z2 Play Albus XT1710 *
* Script by Junior Passos *
*************************************************
"Desligue seu Moto Z2 Play e conecte-o no computador em Modo Fastboot."
"Aviso: Os arquivos no armazenamento interno serao totalmente deletados!"
Press any key to continue . . .
< waiting for device >
max-sparse-size: 268435456
finished. total time: 0.001s
...
OKAY [ 0.002s]
finished. total time: 0.002s
sending 'partition' (45 KB)...
OKAY [ 0.002s]
writing 'partition'...
Validating 'gpt.default.xml'
Security version downgrade
Image primary_gpt failed validation
Preflash validation failed
Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.076s
sending 'bootloader' (5115 KB)...
OKAY [ 0.116s]
writing 'bootloader'...
Validating 'bootloader.default.xml'
Committing 'bootloader.default.xml'
- flashing 'emmc_appsboot.mbn' to 'aboot'
- flashing 'rpm.mbn' to 'rpm'
- flashing 'tz.mbn' to 'tz'
- flashing 'devcfg.mbn' to 'devcfg'
- flashing 'cmnlib.mbn' to 'cmnlib'
- flashing 'cmnlib64.mbn' to 'cmnlib64'
- flashing 'keymaster.mbn' to 'keymaster'
- flashing 'prov.mbn' to 'prov'
- flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.526s]
finished. total time: 0.644s
sending 'modem' (71573 KB)...
OKAY [ 1.612s]
writing 'modem'...
OKAY [ 1.126s]
finished. total time: 2.761s
sending 'fsg' (4020 KB)...
OKAY [ 0.081s]
writing 'fsg'...
OKAY [ 0.126s]
finished. total time: 0.233s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.032s
sending 'dsp' (16384 KB)...
OKAY [ 0.370s]
writing 'dsp'...
OKAY [ 0.295s]
finished. total time: 0.668s
sending 'logo' (2192 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.098s]
finished. total time: 0.164s
sending 'boot' (16384 KB)...
OKAY [ 0.432s]
writing 'boot'...
Image signed with key bad key
OKAY [ 0.392s]
finished. total time: 0.840s
sending 'recovery' (20580 KB)...
OKAY [ 0.522s]
writing 'recovery'...
Image size exeeded partition limits
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.536s
sending 'system' (262141 KB)...
OKAY [ 6.039s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 6.058s
sending 'system' (255657 KB)...
OKAY [ 5.741s]
writing 'system'...
OKAY [ 3.393s]
finished. total time: 9.142s
sending 'system' (243061 KB)...
OKAY [ 5.673s]
writing 'system'...
OKAY [ 3.380s]
finished. total time: 9.058s
sending 'system' (260374 KB)...
OKAY [ 6.039s]
writing 'system'...
OKAY [ 3.955s]
finished. total time: 10.002s
sending 'system' (260395 KB)...
OKAY [ 6.005s]
writing 'system'...
OKAY [ 3.608s]
finished. total time: 9.629s
sending 'system' (242845 KB)...
OKAY [ 5.567s]
writing 'system'...
OKAY [ 3.173s]
finished. total time: 8.753s
sending 'system' (262140 KB)...
OKAY [ 5.994s]
writing 'system'...
OKAY [ 3.402s]
finished. total time: 9.402s
sending 'system' (262141 KB)...
OKAY [ 6.108s]
writing 'system'...
OKAY [ 3.620s]
finished. total time: 9.742s
sending 'system' (262142 KB)...
OKAY [ 5.885s]
writing 'system'...
OKAY [ 3.633s]
finished. total time: 9.531s
sending 'system' (262141 KB)...
OKAY [ 6.044s]
writing 'system'...
OKAY [ 3.412s]
finished. total time: 9.465s
sending 'system' (239056 KB)...
OKAY [ 5.488s]
writing 'system'...
Invalid sparse image data
Failed to flash sparse image
FAILED (remote failure)
finished. total time: 7.494s
sending 'system' (45248 KB)...
OKAY [ 1.018s]
writing 'system'...
Invalid sparse image data
Failed to flash sparse image
FAILED (remote failure)
finished. total time: 1.044s
sending 'oem' (155105 KB)...
OKAY [ 3.549s]
writing 'oem'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 3.562s
erasing 'carrier'...
OKAY [ 0.135s]
finished. total time: 0.150s
erasing 'cache'...
OKAY [ 0.008s]
finished. total time: 0.008s
erasing 'userdata'...
OKAY [ 0.128s]
finished. total time: 0.140s
erasing 'DDR'...
OKAY [ 0.001s]
finished. total time: 0.002s
...
OKAY [ 0.002s]
finished. total time: 0.002s
"Arquivos instalados com sucesso!"
rebooting...
finished. total time: 0.001s
I tried installing custom ROM (viper OS) on my moto z2 play and it showed the same error. Updater process error 255 and after trying two more ROMs my phone is stuck in twrp mode. Why the error: 255 and how to fix it, is it that i can never install a custom ROM or what? and about downgrading it to NOUGAT i'm trying it now. I'll let you know if it works. but can you help me with the error 255!
FIX
Use this command on PC:
fastboot oem fb_mode_clear
https://forum.xda-developers.com/showthread.php?t=2774709&page=5
Works! But i lost my imei...
Hi guys,
Recently after a
fastboot boot twrp-3.3.1-test43-hotdog-unified-mauronofrio.img
Click to expand...
Click to collapse
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Do you want to wipe all the data ( Reccomended )[Y/N]?n
Sending 'boot_b' (98304 KB) OKAY [ 2.785s]
Writing 'boot_b' OKAY [ 0.468s]
Finished. Total time: 3.700s
Sending 'dtbo' (16384 KB) OKAY [ 0.473s]
Writing 'dtbo' OKAY [ 0.043s]
Finished. Total time: 0.621s
Sending 'modem_b' (166356 KB) OKAY [ 4.741s]
Writing 'modem_b' OKAY [ 0.686s]
Finished. Total time: 6.146s
Sending 'reserve' (250136 KB) OKAY [ 7.109s]
Writing 'reserve' FAILED (remote: '(reserve_b)
No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.794s]
Writing 'recovery' OKAY [ 0.353s]
Finished. Total time: 3.314s
Sending 'vbmeta' (8 KB) OKAY [ 0.013s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.039s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.034s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 9.956s
Sending 'abl_b' (1164 KB) OKAY [ 0.036s]
Writing 'abl_b' OKAY [ 0.013s]
Finished. Total time: 0.071s
Sending 'aop_b' (200 KB) OKAY [ 0.006s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'bluetooth_b' (828 KB) OKAY [ 0.025s]
Writing 'bluetooth_b' OKAY [ 0.011s]
Finished. Total time: 0.057s
Sending 'cmnlib_b' (384 KB) OKAY [ 0.012s]
Writing 'cmnlib_b' OKAY [ 0.008s]
Finished. Total time: 0.036s
Sending 'cmnlib64_b' (500 KB) OKAY [ 0.015s]
Writing 'cmnlib64_b' OKAY [ 0.009s]
Finished. Total time: 0.042s
Sending 'devcfg_b' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'dsp_b' (65536 KB) OKAY [ 1.919s]
Writing 'dsp_b' OKAY [ 0.335s]
Finished. Total time: 2.553s
Sending 'hyp_b' (480 KB) OKAY [ 0.015s]
Writing 'hyp_b' OKAY [ 0.007s]
Finished. Total time: 0.041s
Sending 'imagefv_b' (20 KB) OKAY [ 0.001s]
Writing 'imagefv_b' OKAY [ 0.006s]
Finished. Total time: 0.022s
Sending 'keymaster_b' (248 KB) OKAY [ 0.008s]
Writing 'keymaster_b' OKAY [ 0.007s]
Finished. Total time: 0.034s
Sending 'LOGO_b' (6540 KB) OKAY [ 0.195s]
Writing 'LOGO_b' OKAY [ 0.046s]
Finished. Total time: 0.284s
Sending 'multiimgoem_b' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_b' OKAY [ 0.006s]
Finished. Total time: 0.030s
Resizing 'odm_b' OKAY [ 0.006s]
Sending 'odm_b' (912 KB) OKAY [ 0.028s]
Writing 'odm_b' FAILED (Status read failed (T
oo many links))
fastboot: error: Command failed
Sending 'oem_stanvbk' (876 KB) FAILED (Write to device faile
d (No such file or directory))
fastboot: error: Command failed
Sending 'opproduct' (612316 KB) FAILED (Write to device faile
d (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'qupfw' (72 KB) OKAY [ 0.012s]
Writing 'qupfw' OKAY [ 0.003s]
Finished. Total time: 0.042s
Sending 'storsec' (24 KB) OKAY [ 0.007s]
Writing 'storsec' OKAY [ 0.003s]
Finished. Total time: 0.032s
Sending 'tz' (3092 KB) OKAY [ 0.096s]
Writing 'tz' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.011s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.037s
Sending 'xbl' (3120 KB) OKAY [ 0.094s]
Writing 'xbl' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.014s]
Writing 'xbl_config' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 23.363s]
Writing 'system' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 23.425s]
Writing 'vendor' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785428 KB) OKAY [ 23.379s]
Writing 'product' FAILED (remote: 'Partition no
t found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Premere un tasto per continuare . . .
Click to expand...
Click to collapse
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Gorthan said:
Hi guys,
Recently after a
I'm stuck in a bootloop. I would like to specify that I ran the twrp checked if I was able to flash something but I saw that I was not able to flash anything because my phone doesn't have the root I rebooted the phone, and from that moment I cannot run the os at all. I'm able to go to the fastboot and I'm able to run the twrp and the recovery.
I tried to reflash the boot only but without success. At this moment I tried to reinstall all the system 10.0.9 but I received this message:
Unfortunately, all these attempts failed. In the past, I tried the rooting. After the first period, it worked properly but I was not able to re-install magisk boot file as it was not recognized by the magisk app. I don't remember if there were some magisk module.
I don't know if this helps, please assist. If the topic is in the wrong section, please move it.
Thank you in advance for your help.
Click to expand...
Click to collapse
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
thanks so much for your reply.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. Now I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in the Partition B and works properly.
mauronofrio said:
Try to install again the rom, and when the device reboot itself in recovery don't reboot it
Click to expand...
Click to collapse
thanks so much for your reply. I followed your advice and actually helps.
I realized that with the twrp I selected the partition A and I reinstalled the rom again and the system restarted. I'll try to restore the partition B. (But in meantime I'm performing a backup all the data ).
Update: I reinstalled the system in Partition B and works properly.
Update 2: I finally spend a bit of time on the phone and I already rooted. Thanks to @mauronofrio for help.