Процесс updater завершился с ошибкой 1 ошибка при установке zip файла twrp
Mounting /system and /vendor read-write
Checking enviroment
Xposed version: 86
Placing files
gzip: short write
Updater process ended with ERROR: 1 Error installing zip file'/external_sd/xposed-v86-sdk21-arm64.zip'
Updating partition details.
. done
The text was updated successfully, but these errors were encountered:
How to Fix TWRP Error 1
So here’s how the entire process will be carried out. First off, we will be flashing the stock boot.img file onto your device. This will remove the root from your device (if you are already rooted). Once that is done, we will take this stock boot.img file, patch it via Magisk, and flash it via Fastboot Commands. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
ulefonebt2 commented Aug 9, 2016
i try format sd, system, wipe, cache. all
reinstall only the moderate rom and appears the same ERROR
any idea to solve??
thank you for reply
rovo89 commented Aug 10, 2016
Please post the TWRP log, it might contain information about the space situation.
About Chief Editor
Sadique Hassan
A technical geek by birth, he always has a keen interest in the Android platform right since the birth of the HTC Dream. The open-source environment always seems to intrigue him with the plethora of options available at his fingertips. “MBA by profession, blogger by choice!”
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
pekkle_hksar
Senior Member
madbat99
Senior Member
Matthewwwww1998
Member
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
murph187
Senior Member
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
techblaze
New member
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Sushanthn94
New member
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
magicstep
New member
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
yousef96875096340963068
New member
hariturbo
New member
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
damansilla
Member
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
atomspop
New member
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Freed0m_
Member
bajpay3296
Member
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
I had flashed new version on firmware but forgot to update TWRP recovery that is why I was getting this error. I updated TWRP recovery. also flashed boot.img image then I was able to fix this issue.
samyxy
New member
PendiukG
New member
I was having the same issue. After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation. I don't know if this was the correct approach, but after many tries this is what worked for me
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Sent from my Mi A1 using XDA Labs
KafkaG
Senior Member
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
KafkaG
Senior Member
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
but I have to extract it from the firmware of lineageos I installed or from the original one of stock? and how do I extract it?
KafkaG
Senior Member
yorkberliner
Senior Member
please be patient. DLoad and extract with 7zip the firmware from here. Extract the firmware again. Now you have the original boot.img from MIUI.
In Fastboot flash the boot.img with "fastboot flash boot boot.img".
tanapak1
Senior Member
If above method won't work, re-download the rom file, this seems corrupt.
Next time try to fresh flash the rom instead of ota, some ota are broken and would have some issue like this.
KafkaG
Senior Member
If above method won't work, re-download the rom file, this seems corrupt.
Next time try to fresh flash the rom instead of ota, some ota are broken and would have some issue like this.
KafkaG
Senior Member
please be patient. DLoad and extract with 7zip the firmware from here. Extract the firmware again. Now you have the original boot.img from MIUI.
In Fastboot flash the boot.img with "fastboot flash boot boot.img".
which of those rom? the first one, 8.1 almost destroyed the system (with the boot.img) and I had to put the boot.img back from the twrp backup, so which link is right?
Edit: I think, indeed, I'm sure I need the boot.img of the rom that I have or lineage, but I do not know how to extract it from the zip.
yorkberliner
Senior Member
okay. I think the best way is you flash first the original Firmware from here with Xiaomi Flash Tool. DLoad and install on your PC. DLoad and read this Site.
Now you have the original Firmware installed. Go to settings, about the Phone, Buildnumber. Tab 7 times on it and than go to the Developer. Open OEM and US-Debugging. Reboot into Fastboot. In ADB/Fastboot write "fastboot devices" and your device must recogniced. Than write "fastboot oem unlock". After this you get a reboot to system. Now look again iin settings, devoloper if oem and usb-debugging on. Reboot in fastboot your Phone. Now write again "fastboot devices". Is everythink okay than write "fastboot boot recovery-3.2.1-2-oreo.img". Now you have twrp installed. In twrp flash the twrp-recoveryinstaller-3.2.1-2-oreo.zip. After this you can flash your favoryte Custom Rom. Good Luck :good:
KafkaG
Senior Member
okay. I think the best way is you flash first the original Firmware from here with Xiaomi Flash Tool. DLoad and install on your PC. DLoad and read this Site.
Now you have the original Firmware installed. Go to settings, about the Phone, Buildnumber. Tab 7 times on it and than go to the Developer. Open OEM and US-Debugging. Reboot into Fastboot. In ADB/Fastboot write "fastboot devices" and your device must recogniced. Than write "fastboot oem unlock". After this you get a reboot to system. Now look again iin settings, devoloper if oem and usb-debugging on. Reboot in fastboot your Phone. Now write again "fastboot devices". Is everythink okay than write "fastboot boot recovery-3.2.1-2-oreo.img". Now you have twrp installed. In twrp flash the twrp-recoveryinstaller-3.2.1-2-oreo.zip. After this you can flash your favoryte Custom Rom. Good Luck :good:
Alex, и так версия 3 ,более новую версию не могу найти на сайтах в формате zip.А так макс версия для моего аппарата 3.2.1 по-моему
Александр Новиков ответил Насте
когда ты уже прошьешь
Настя, скопировать во внутреннюю память, далее зайдите в TWRP->установка->установка IMG->Выбираете ядро->раздел boot
Иван, может подскажешь?последнюю версию twrp можно скачать только в формате .img,для установки через тврп новой версии тврп файл должен в формате .zip,дак как его тогда установить?
ulefonebt2 commented Aug 10, 2016
when i install exposed.zip appears the error and after the smartphone go in loop on ulefone logo.
now i reflash the rom.. this is the log now
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP 3.0.2-1 on Wed Aug 10 20:51:12 2016
(pid 173)
BOARD_HAS_NO_REAL_SDCARD := true
TW_NO_REBOOT_BOOTLOADER := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/msm_dwc3/f9200000.dwc3/gadget/lun0/file' does not exist, USB storage mode disabled
TW_HAS_DOWNLOAD_MODE := true
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/devices/mdp.0/qcom,mdss_fb_primary.190/leds/lcd-backlight/brightness
I:Specified brightness file '/sys/devices/mdp.0/qcom,mdss_fb_primary.190/leds/lcd-backlight/brightness' not found.
I:Find_File: Error opening '/sys/class/backlight'
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 162
I:LANG: en
Starting the UI. setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (1080 x 1920)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 162
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution.
I:Loading resources.
I:Loading variables.
I:Loading mouse cursor.
I:Loading pages.
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/boot'
I:Processing '/logo'
I:Processing '/nvram'
I:Processing '/recovery'
I:Processing '/lk'
I:Processing '/proinfo'
I:Processing '/protect_f'
I:Processing '/protect_s'
I:Processing '/system'
I:Processing '/system_image'
I:Processing '/cache'
I:Processing '/data'
I:Unhandled fstab information: 'backup=1;wipeingui;wipeduringfactoryreset', 65, line: '/data ext4 /dev/block/platform/mtk-msdc.0/by-name/userdata backup=1;wipeingui;wipeduringfactoryreset
'
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Processing '/external_sd'
I:Processing '/usbotg'
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/0123456789ABCDEF'
I:Settings storage is '/data/media/0'
I:Decrypt adopted storage starting
I:PageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
Updating partition details.
I:Data backup size is 849MB, free: 11865MB.
I:Unable to mount '/usbotg'
I:Actual block device: '', current file system: 'auto'
. done
I:Unmounting main partitions.
Partition Logs:
/boot | /dev/block/mmcblk0p7 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: Boot
Storage_Name: Boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/logo | /dev/block/mmcblk0p11 | Size: 8MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: Logo
Storage_Name: Logo
Backup_Path: /logo
Backup_Name: logo
Backup_Display_Name: Logo
Storage_Path: /logo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/nvram | /dev/block/mmcblk0p2 | Size: 5MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: Nvram
Storage_Name: Nvram
Backup_Path: /nvram
Backup_Name: nvram
Backup_Display_Name: Nvram
Storage_Path: /nvram
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p8 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: Recovery
Storage_Name: Recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/lk | /dev/block/mmcblk0p6 | Size: 0MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p6
Display_Name: Uboot
Storage_Name: Uboot
Backup_Path: /lk
Backup_Name: lk
Backup_Display_Name: Uboot
Storage_Path: /lk
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/proinfo | /dev/block/mmcblk0p1 | Size: 3MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: Proinfo
Storage_Name: Proinfo
Backup_Path: /proinfo
Backup_Name: proinfo
Backup_Display_Name: Proinfo
Storage_Path: /proinfo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/protect_f | /dev/block/mmcblk0p3 | Size: 4MB Used: 0MB Free: 4MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Has_SubPartition IsPresent
Primary_Block_Device: /dev/block/mmcblk0p3
Display_Name: Protect
Storage_Name: Protect
Backup_Path: /protect_f
Backup_Name: protect_f
Backup_Display_Name: Protect
Storage_Path: /protect_f
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/protect_s | /dev/block/mmcblk0p4 | Size: 4MB Used: 0MB Free: 4MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /protect_f
Primary_Block_Device: /dev/block/mmcblk0p4
Display_Name: protect_s
Storage_Name: protect_s
Backup_Path: /protect_s
Backup_Name: protect_s
Backup_Display_Name: protect_s
Storage_Path: /protect_s
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/system | /dev/block/mmcblk0p16 | Size: 1518MB Used: 1498MB Free: 20MB Backup Size: 1498MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p16
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/system_image | /dev/block/mmcblk0p16 | Size: 1568MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p16
Display_Name: System
Storage_Name: System
Backup_Path: /system_image
Backup_Name: system_image
Backup_Display_Name: System
Storage_Path: /system_image
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/cache | /dev/block/mmcblk0p17 | Size: 106MB Used: 0MB Free: 106MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p17
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/data | /dev/block/mmcblk0p18 | Size: 12751MB Used: 849MB Free: 11865MB Backup Size: 849MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p18
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537
/external_sd | /dev/block/mmcblk1p1 | Size: 30605MB Used: 14453MB Free: 16152MB Backup Size: 14453MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: External SD-card
Storage_Name: External SD-card
Backup_Path: /external_sd
Backup_Name: external_sd
Backup_Display_Name: External SD-card
Storage_Path: /external_sd
Current_File_System: vfat
Fstab_File_System: auto
Backup_Method: files
MTP_Storage_ID: 65538
/usbotg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: USB-OTG
Storage_Name: USB-OTG
Backup_Path: /usbotg
Backup_Name: usbotg
Backup_Display_Name: USB-OTG
Storage_Path: /usbotg
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
MTP_Storage_ID: 65539
In this guide, we will show you the steps to fix TWRP Error 1 on any Android device. When it comes to stepping into custom development, there are a plethora of tweaks and customizations that tech enthusiasts prefer. And replacing the device’s stock recovery with a custom one is right there at the top. But why do users install a custom recovery when there’s already an in-built recovery present? Well, the reason is that the stock recovery isn’t built to support any custom tweaks whatsoever.
At the very most, you could wipe off the data, reboot your device to Fastboot, or in some instances, perform the ADB sideload functionality. But that’s it. You cannot flash ZIP or IMG files, erase data partition, create and restore a backup of various device partitions, etc. Hence the need for a custom recovery becomes all the more important. And as of now, TWRP is the sole recovery ruling the charts. While there are others as well, but they are build using the TWRP’s source code.
However, this recovery isn’t free from its fair share of issues. For example, you might get TWRP Error 7 while flashing custom ROMs or TWRP Error 20 after flashing GApps. Then there are instances of users facing TWRP Error 70 due to insufficient storage in the System partition. And now, there have been numerous complaints from users getting bugged with the TWRP Error 1. If you are also facing this issue, then fret not. This guide will list out two different methods to fix this TWRP Error 1 once and for all. Follow along.
Table of Contents
ulefonebt2 commented Aug 9, 2016
i try format sd, system, wipe, cache. all
reinstall only the moderate rom and appears the same ERROR
any idea to solve??
thank you for reply
STEP 3: Patch Stock Boot.img via Magisk
In this section, we will be patching the stock boot.img file via Magisk. This will give us the magisk_patched.img file which will then be flashed onto your device. So follow the below steps to carry out this task. Make sure that the stock boot.img file is transferred to your device. [Having trouble on your Android 11 device? Check out this guide: Fix Magisk patched boot.img issue while Rooting Android 11]
- First and foremost, install the Magisk Manager app on your device.
- Then launch it and tap on the Install button situated next to Magisk.
- From the Method section, choose Select and Patch a file.
- Browse to the extracted boot.img file and select it.
- Then tap on the Let’s Go option situated at the top right.
- Magisk will now load the boot.img file and will patch it accordingly. Once that is done, you would get the Download Complete message.
- The patched boot image file will be saved in Internal Storage > Downloads. The name of the file will be magisk_patched.img. We will now use this file to fix the TWRP Error 1. Follow along.
STEP 4: Flash Patched Boot.img via TWRP
Finally, you just need to flash this patched boot.img file to your device. Again, there are two different approaches for the same, but since TWRP is the easier method than compared with Fastboot Commands, we will be using this method only. Make sure that you have the magisk_patched.img on your device:
- First off, boot your device to TWRP Recovery.
- Then go to the Install section and tap on the Install Image button situated at the bottom right.
- Browse to the magisk_patched.img file and select it.
- Then select the Boot partition from the menu and perform a right swipe to flash it.
- Once done, you may now reboot your device to the ‘rooted OS’ by going to Reboot > System.
That’s it. The process stands complete. With this, we conclude the guide on how to fix TWRP Error 1. If you still have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.
STEP 1: Download Stock Boot IMG
First and foremost, you will need the stock boot.img file corresponding to the firmware version installed on your device. You could check the current firmware build number from the About Phone section. Once you have verified the same, download the corresponding firmware file (stock or custom ROM whichever is currently installed).
Now if you are having a Pixel device, then you could easily extract the firmware via WinZIP or WinRAR. But that isn’t the case with other devices. In the case of OnePlus, the partition image files are placed inside payload.bin. Whereas Oppo and Realme have their files inside the OZIP package, so you would need standalone tools for this purpose. In this scenario, you may refer to our detailed guide linked below:
Once you have got hold of the stock boot.img file, proceed to the next step to fix the TWRP Error 1.
The Reason for TWRP Error 1
The reason for this issue is due to the corrupt boot.img file. Well, we aren’t talking about the stock boot image file, rather it’s the patched boot img file that we use for rooting purposes. For the unawares, there exist two different methods to root any device. In the first one, you could directly flash the Magisk ZIP Installer file via TWRP and your device stands rooted. The next method requires getting the stock boot.img file, patching it via Magisk and then flashing it via Fastboot commands.
However, there is an important point worth keeping in mind. You will have to use the same boot.img file from the firmware that corresponds to the current firmware installed on your device. Any mismatch in the version would lead to a conflicting situation and could lead to a few issues, one of which is TWRP Error 1. So how could this be rectified? Well, you would have to patch and flash the correct boot.img file and it will fix the TWRP Error 1. Here are all the required instructions for the same.
STEP 2: Flash Stock Boot.img file via TWRP
The next step in the guide to fix the TWRP Error 1 requires you to install the stock boot.img file onto your device. While we could do so via Fastboot Commands, but since TWRP is already installed, let’s take this approach only. Do keep in mind that if your device is rooted, then it will be unrooted on flashing the stock boot.img (don’t worry we will re-root it later on as well).
- To begin with, transfer the stock boot.img file to your device.
- Then boot your device to TWRP, either via hardware key combinations or by using the adb reboot recovery command.
- Now go to the Install section and tap on the Install Image button situated at the bottom right.
- Navigate to the stock boot.img file and select it.
- Then select Boot from the partition selection screen and perform a right swipe to flash it.
- Once done, go to Reboot and select System. Your device will be booted to the OS. Now move over to the next step to fix the TWRP Error 1.
Читайте также: