[TWRP][Montana]TWRP for Moto G5s[ARM/ARM64 Support] - Moto G5S ROMs, Kernels, Recoveries, & Other Devel

TWRP For Moto G5s Montana​
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.1-0
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24

Custom Oreo arm64 release????

rssxda said:
Custom Oreo arm64 release????
Click to expand...
Click to collapse
No, first we want a arm32 build.

Can't decrypt/mount my fs with this. Works on Squids TWRP.
Moto G5S XT1794

Can use Treble imagem?

Hello, here is a new version of the twrp arm / arm64.
twrp.fstab file modification
old twrp.fstab
HTML:
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data f2fs /dev/block/bootdevice/by-name/userdata flags=encryptable=/dev/block/bootdevice/by-name/metadata
/keymaster emmc /dev/block/bootdevice/by-name/keymaster
/cache auto /dev/block/bootdevice/by-name/cache
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=backup=1
/oem ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
/persist ext4 /dev/block/bootdevice/by-name/persist flags=fsflags=noatime,nosuid,nodev,barrier=1,noauto_da_alloc;mounttodecrypt
/firmware ext4 /dev/block/bootdevice/by-name/modem flags=fsflags=ro,nosuid,nodev,barrier=0;mounttodecrypt
/misc emmc /dev/block/bootdevice/by-name/misc
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable;fsflags="utf8"
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable;fsflags="utf8"
new twrp.fstab
HTML:
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data f2fs /dev/block/bootdevice/by-name/userdata flags=encryptable=/dev/block/bootdevice/by-name/metadata
/keymaster emmc /dev/block/bootdevice/by-name/keymaster
/cache auto /dev/block/bootdevice/by-name/cache
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery flags=backup=1
/vendor ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="Vendor";backup=1;wipeingui
/persist ext4 /dev/block/bootdevice/by-name/persist flags=fsflags=noatime,nosuid,nodev,barrier=1,noauto_da_alloc;mounttodecrypt
/firmware ext4 /dev/block/bootdevice/by-name/modem flags=fsflags=ro,nosuid,nodev,barrier=0;mounttodecrypt
/misc emmc /dev/block/bootdevice/by-name/misc
/efs1 emmc /dev/block/bootdevice/by-name/modemst1 flags=backup=1;display="EFS"
/efs2 emmc /dev/block/bootdevice/by-name/modemst2 flags=backup=1;subpartitionof=/efs1
/logo emmc /dev/block/bootdevice/by-name/logo flags=display="logo";backup=1;flashimg=1
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD Card";storage;wipeingui;removable;fsflags="utf8"
/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable;fsflags="utf8"
I'm no longer this model for now because I gave it to my wife, if anyone can try it. But it should work properly
link AFH > https://androidfilehost.com/?fid=746163614322269316

Hello,
if I try to boot twrp without flashing it using
Code:
fastboot boot recovery.img
it gets stuck on the twrp splash screen. Do you know why this does not work? Flashing and booting after flashing works perfectly btw, but I'd like to be able to backup my stock recovery for ota updates.

tafiir said:
Hello,
if I try to boot twrp without flashing it using
Code:
fastboot boot recovery.img
it gets stuck on the twrp splash screen. Do you know why this does not work? Flashing and booting after flashing works perfectly btw, but I'd like to be able to backup my stock recovery for ota updates.
Click to expand...
Click to collapse
whay you whant to backup your stok recovery?
you can flash it on the phone any time with fastboot/mfastboot comand's
just remember wich stok rom you used last time and flash the propper recovery from it!
Thankyou!

Hello New twrp 3.2.2-0 > https://androidfilehost.com/?fid=5862345805528040464
https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html

PERGUNTA
Essa versao 3.2.2-0 ela e 32/64 bits

kaique teixeira said:
Essa versao 3.2.2-0 ela e 32/64 bits
Click to expand...
Click to collapse
64bit!

teble
is this procedure for installing treble roms?
can be installed GSI rom on the montana (moto g5s)?

tiagoneo said:
is this procedure for installing treble roms?
can be installed GSI rom on the montana (moto g5s)?
Click to expand...
Click to collapse
Of course not. Treble isn't even here yet
Sent from my Moto G5S using XDA Labs

What is the difference of this version and Squid ?? I've flashed the Squid last week, and I can flash this over the Squid ?

1ZeeN said:
What is the difference of this version and Squid ?? I've flashed the Squid last week, and I can flash this over the Squid ?
Click to expand...
Click to collapse
No encryption support, but installs DU perfectly

will this work for XT1795 model?

going to stock rom instead of twrp
Flashed twrp successfully. But whenever I try to access the recovery the next time, it is going to stock recovery instead of twrp.
If I flash it again, I could access TWRP at that time. But if I reboot to system and try again, stock recovery appears.
what should I do to flash it permenantly?
fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15914 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.378s]
finished. total time: 1.068s

Akshay K yatheendran said:
Flashed twrp successfully. But whenever I try to access the recovery the next time, it is going to stock recovery instead of twrp.
If I flash it again, I could access TWRP at that time. But if I reboot to system and try again, stock recovery appears.
what should I do to flash it permenantly?
fastboot flash recovery twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (15914 KB)...
OKAY [ 0.632s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.378s]
finished. total time: 1.068s
Click to expand...
Click to collapse
Can't you read?
"Image not signed or corrupt" make sure to only use signed and official versions of Twrp!

Some random said:
Can't you read?
"Image not signed or corrupt" make sure to only use signed and official versions of Twrp!
Click to expand...
Click to collapse
It will be shown even on official twrp. You have to disable overwiting recovery by stock system. For example, magisk can handle it

GoldeneyeS2 said:
TWRP For Moto G5s Montana​
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.1-0
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24
Click to expand...
Click to collapse
I need perfect gapps for motog5s montana please help me??

Related

[Q] Chuwi Vi8 recovery mode

I use Chuwi Vi8 Dual Boot edition
Windows side is running but Andorid side is some Errors and not opening
I try to open android Os but opening boatloader and fastboot
I choose Recovery mode from Bootloader then reboot OS and Bootloader screen again
I can use only fastboot and bootloader screen
I upload some pictures opening
first screet Error "EFILINK ERROR [android_image_start_buffer:752] bzImage kernel corrupt
@ Fastboot screen
FASTBOT INIT...
E: installer device ignored
FASTBOOT CMD waiting...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found
Is there someone have any idea about this ?
Help pls
I try Twrp recovery
C:\platform-tools>fastboot devices
BaytrailBB739E56 fastboot
C:\platform-tools>fastboot flash recovery twrp-2.8.6.0-xt1032.img
target reported max download size of 1283254954 bytes
sending 'recovery' (8480 KB)...
OKAY [ 0.988s]
writing 'recovery'...
OKAY [ 0.670s]
finished. total time: 1.658s
aksoft34 said:
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
Click to expand...
Click to collapse
try a different usb otg hub/cable
has the same errors. Bought a different otg hub/cable and worked found installer.cmd /installer medium
even hot swapping before booting to uefi built in shell with singular usb cable worked(swapped usb keyboard to usb drive after enteriing bios but before selecting the uefi shell)
Try my port http://www.needrom.com/download/chuwi-vi8-dualos-cw1506/
I have the same issue. Did you solved it? If yes how? Thx

[RECOVERY] TWRP for Vibe P1 / Turbo

I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2018-04-12
ChangeLog
twrp-3.2.1
Device side:
* fixed encryption fully
TWRP side:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Flashing guide(without fastboot)-
Method#1: this guide for whom got TWRP recovery v3.0.1-0 via QFIL using QPST software or who has @_kyo_ 's TWRP installed
1)load this latest TWRP (v3.1.0-0 or updated version) in sdcard or internal storage
2) boot into existing TWRP recovery
3)click on install tab
4)here from bottom left popup menu, select appropriate storage and from bottom right toggle, switch to INSTALL IMAGE mode(see screenshot)
5)flash latest TWRP v3.1.0-0 as recovery(see screenshot)
6)reboot into new TWRP recovery
Methof#2:Another method is using QPST's qfil option. In this method simply add latest version of twrp >put that into same location where stock(288) twrp existed>than apply same method with updated twrp as you did while qfil-ing stock twrp
Great work @FireLord
THEHARI said:
Flashing guide(without fastboot)-
note- this guide for whom got TWRP recovery v3.0.1-0 via QFIL using QPST software or who has @_kyo_ 's TWRP installed
1)load this latest TWRP v3.1.0-0 in sdcard or internal storage
2) boot into existing TWRP recovery
3)click on install tab
4)here from bottom left popup menu, select appropriate storage and from bottom right toggle, switch to INSTALL IMAGE mode(see screenshot)
5)flash latest TWRP v3.1.0-0 as recovery(see screenshot)
6)reboot into new TWRP recovery
Click to expand...
Click to collapse
confirmed working on my lenovo P1a42
upgraded from TWRP recovery v3.0.1-0 by kyo
so backup & restore fixed i guess ??
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
and did you finished your exams ??
mohamed abd elmoaety said:
so backup & restore fixed i guess ??
---------- Post added at 08:01 PM ---------- Previous post was at 07:58 PM ----------
and did you finished your exams ??
Click to expand...
Click to collapse
yea no bugs. no exams still running
FireLord said:
yea no bugs. no exams still running
Click to expand...
Click to collapse
**** exams anyway
"OOPS!
no mirrors found."
Hi,
I'm trying to use your method to get twrp so I can install custom rom, but I stuck here
E:\dev\Android>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.973s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.425s
Any idea?
Thanks
flash problem
for flash
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (30576 KB)...
OKAY [ 1.112s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.346s
any idea?
Get the bootloader unlocked first
:d
developerx07 said:
Get the bootloader unlocked first
:d
Click to expand...
Click to collapse
I have same issue and bootloader unlocked. What should I have to look at second?
New 3.1.1 twrp is up. check changelog https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
Is flashing via QPST method the same with flashing via fastboot? (Does it have the exact same results?) @FireLord
danthecoolboy said:
Is flashing via QPST method the same with flashing via fastboot? (Does it have the exact same results?) @FireLord
Click to expand...
Click to collapse
Yes, both have same result
Error while flashing recovery
target reported max download size of 268435456 bytes
sending 'recovery' (30594 KB)...
OKAY [ 1.033s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.278s
I have unlocked the bootloader using fastboot oem unlock
Please help
thanks in advance
vibe p1a42
s.kakrecha said:
target reported max download size of 268435456 bytes
sending 'recovery' (30594 KB)...
OKAY [ 1.033s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.278s
I have unlocked the bootloader using fastboot oem unlock
Please help
thanks in advance
Click to expand...
Click to collapse
even I get the exact same error. I have also unlocked the bootloader using fastboot oem unlock-go.
Awesome XDA & Friends.........Thank you
FireLord said:
I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
I was able to install the latest TWRP and I am on AEX ROM on my Vibe P1a42. Thanks to all of you guys in this thread.:good:
FireLord said:
I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
Could you please give me TWRP img for Lenovo Vibe P1a42? I could not install TWRP. getting error 'valid signature and data)'
---------- Post added at 11:52 AM ---------- Previous post was at 11:25 AM ----------
FireLord said:
I've ported TWRP to the vibe p1/ turbo. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on the AndroidFileHost.
Kernel used
XDA:DevDB Information
[RECOVERY] TWRP for Vibe P1 / Turbo, ROM for the Lenovo Vibe P1
Contributors
FireLord
Source Code: https://github.com/omnirom/android_bootable_recovery
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-16
Last Updated 2017-03-16
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (30576 KB)...
OKAY [ 1.112s]
writing 'recovery'...
FAILED (remote: invalid signature and data)
finished. total time: 1.346s

cannot install twrp and stock recovery deleted- help needed please

Need some help please with something that has gone wrong with my first attempt to alter Android. I wanted to install a custom recovery, root the phone and take it from there.
I have a Moto e 1st edition, xt1021, system info given below.
I unlocked the boot loader, installed Minimal ADB Fastboot 1.4.3, downloaded the latest TWRP image 3.3.1.-condor for the Moto e from the TWRP website.
I used flashboot flash recovery initially to install the TWRP image, which failed, but has wiped the stock recovery. I cannot boot into recovery or do a factory reset.
The phone will boot normally. If I try a factory reset, it boots normally. If I boot into recovery, I get the Android image on his back with a red triangle, and “no command”. If I go into system recovery from here, and try both 'update by adb sideload' or 'update from sd card', both fail.
I have tried flashboot boot recovery using a stock recovery, but the phone is stuck on the initial Moto logo.
I have also tried to install an earlier TWRP recovery, 2.7.1-condor and CWM 6.o.4.7 falcon but this has failed to install also.
I have now reached the limit of my abilities – any help much appreciated, but please spell out in words of one syllable if possible.
=========================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb devices
List of devices attached
ZX1B245XHK device
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb shell pm list features
feature:reqGlEsVersion=0x30000
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.camera
feature:android.hardware.camera.any
feature:android.hardware.faketouch
feature:android.hardware.location
feature:android.hardware.location.gps
feature:android.hardware.location.network
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.light
feature:android.hardware.sensor.proximity
feature:android.hardware.telephony
feature:android.hardware.telephony.cdma
feature:android.hardware.telephony.gsm
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.usb.accessory
feature:android.hardware.usb.host
feature:android.hardware.wifi
feature:android.hardware.wifi.direct
feature:android.software.app_widgets
feature:android.software.backup
feature:android.software.connectionservice
feature:android.software.device_admin
feature:android.software.home_screen
feature:android.software.input_methods
feature:android.software.live_wallpaper
feature:android.software.managed_users
feature:android.software.print
feature:android.software.sip
feature:android.software.voice_recognizers
feature:android.software.webview
feature:com.motorola.camera
feature:com.motorola.camera.chalmers
feature:com.motorola.context
feature:com.motorola.hardware.tier.
feature:com.motorola.hardware.wave.0
feature:com.motorola.smartaction2
feature:com.motorola.smartactions2_1.1
feature:com.motorola.software.bodyguard
feature:com.motorola.software.device.condor_umts
feature:com.motorola.software.fmradioservice
feature:com.motorola.software.fmrecording
feature:com.motorola.software.guideme
feature:com.motorola.software.product.condor_tescogb
feature:com.motorola.software.storageoptimizer
feature:com.motorola.software.x_line
==================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb reboot bootloader
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot flash recovery C:
\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\twrp-2.7.2.0-hlte-4.3.img
target reported max download size of 299892736 bytes
sending 'recovery' (10738 KB)...
OKAY [ 0.608s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot boot C:\Users\ME\
Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.499s]
finished. total time: 0.920s
========================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>FASTBOOT GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>

Can't flash system.img in TWRP - E:Cannot flash images to file systems

I am trying to install a custom ROM on a Huawei P Smart FIG-LX1. I have a system.img that i should flash to the system partition.
So when i try to flash the image i have two system partitions:
Ona named "System" and one named "System Image".
If i try flashing it to the "System" partition i get this error:
Code:
[IMAGE FLASH STARTED]
Image to flash: '/external_sd/system.img'
Calculating restore details...
E:Cannot flash images to file systems
If this can help i have wiped the system partition containing the original ROM.
useless double posts
Can't flash system images in fastboot - FAILED (remote: 'sparse flash write failure')
Hi, i am trying to install a system.img to the system partition using fastboot using fastboot flash system C:\Users\user\Desktop\system.img but when i run the command i get this error: Sending sparse 'system' 1/7 (460796 KB) OKAY [...
forum.xda-developers.com
Size of image is larger than the target device in TWRP
Hi, I am trying to flash a system image in TWRP. When i try flashing the system.img to the System Image partiton i get this error: Size of image is larger than target device How can i solve this error? I tried the resize partition option on the...
forum.xda-developers.com

Can't flash system images in fastboot - FAILED (remote: 'sparse flash write failure')

Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
shaon121$ said:
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
Click to expand...
Click to collapse
It still doesn't work as administrator and with the image in the C drive root.
Change your img file and try again..or download again... What is your phone model?
shaon121$ said:
Change your img file and try again..or download again... What is your phone model?
Click to expand...
Click to collapse
I have already tried different images, the phone is a Huawei P Smart FIG-LX1.
useless double posts
Can't flash system.img in TWRP - E:Cannot flash images to file systems
I am trying to install a custom ROM on a Huawei P Smart FIG-LX1. I have a system.img that i should flash to the system partition. So when i try to flash the image i have two system partitions: Ona named "System" and one named "System Image". If...
forum.xda-developers.com
Size of image is larger than the target device in TWRP
Hi, I am trying to flash a system image in TWRP. When i try flashing the system.img to the System Image partiton i get this error: Size of image is larger than target device How can i solve this error? I tried the resize partition option on the...
forum.xda-developers.com
slx23 said:
Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Click to expand...
Click to collapse
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com

Categories

Resources