Develop Bugs

Install ViperOne_5 on corrupted HTC One M8

I wiped everything on my phone (HTC One M8) and it's empty now! I managed to install TWRP using fastboot, but when I try to install ViperOne_5.0.2, TWRP says "error installing zip file, zip file is corrupt". But the file's MD5 matches the MD5 of file on website. I tried latest version of TWRP and later downgraded to 2.8.7, but result is the same.
I installed boot.img inside ViperOne_5.0.2 using fastboot but still can't install ViperOne. What should I do? What am I missing while installation?
Please help me :crying:
Thank you very much

Solved
My SD card was acting weird. I changed SD card and everything installed correctly.

Can't update firmware through TWRP

Hey all,
I'm having some trouble trying to update firmware packages through TWRP (and any ROM other than xiaomi.eu). I'm trying to flash this rom and I've downloaded both the ROM and the firmware as linked on the page. When I try to flash both through TWRP, the script succeeds but returns a value of 1. I'm assuming that means it failed, shouldn't it return 0 on success?
After flashing I've tried to boot to system, but it loops through the boot animation and a TWRP "Open Recovery Script" screen. Not too sure what that means. I'm running TWRP version 3.2.0-0.
I didn't have any of these problems with my Mi 5. Not too sure what I'm doing wrong. Can anyone guide me in the right direction?
Thanks

JaredG_ said:
Hey all,
I'm having some trouble trying to update firmware packages through TWRP (and any ROM other than xiaomi.eu). I'm trying to flash this rom and I've downloaded both the ROM and the firmware as linked on the page. When I try to flash both through TWRP, the script succeeds but returns a value of 1. I'm assuming that means it failed, shouldn't it return 0 on success?
After flashing I've tried to boot to system, but it loops through the boot animation and a TWRP "Open Recovery Script" screen. Not too sure what that means. I'm running TWRP version 3.2.0-0.
I didn't have any of these problems with my Mi 5. Not too sure what I'm doing wrong. Can anyone guide me in the right direction?
Thanks
Click to expand...
Click to collapse
Did you format data and type yes in TWRP?
For a lot of ROM changes you need to format the whole data partition not just wipe it.

Dobsgw said:
Did you format data and type yes in TWRP?
For a lot of ROM changes you need to format the whole data partition not just wipe it.
Click to expand...
Click to collapse
Yes I have.
I'm not too sure if I'm supposed to be rebooting to system afterwards. It's rebooting into MIUI 9 which sets up the internal storage and lets me copy the firmware updates onto the device through TWRP, but I'm still getting that 'return 1' and boot loop issue.

JaredG_ said:
Yes I have.
I'm not too sure if I'm supposed to be rebooting to system afterwards. It's rebooting into MIUI 9 which sets up the internal storage and lets me copy the firmware updates onto the device through TWRP, but I'm still getting that 'return 1' and boot loop issue.
Click to expand...
Click to collapse
Flash the firmware, then the ROM, then gapps if you use it.
Then format data and reboot.
That should get things working for you.
Then after that if you're flashing the same ROM you wont need to do a format of data you can just wipe it and keep internal storage

Dobsgw said:
Flash the firmware, then the ROM, then gapps if you use it.
Then format data and reboot.
That should get things working for you.
Then after that if you're flashing the same ROM you wont need to do a format of data you can just wipe it and keep internal storage
Click to expand...
Click to collapse
I can't seem to update the firmware. I'm definitely doing something wrong it's never taken me this long on any of my devices.
Trying to flash the Mi 6 Global 7.11.2 firmware gives this log in TWRP:
package_extract_file took 00s
...
SetMetadataFn took 00s
RunProgramFn took 00s
script succeeded: result was [1.000000]
Updating partition details...
...done
Click to expand...
Click to collapse
Then trying to flash the ROM afterwards gives me error 7. Where am I going wrong with the firmware update?
I bet at the end of all this it's going to be just a simple mistake haha :/

JaredG_ said:
I can't seem to update the firmware. I'm definitely doing something wrong it's never taken me this long on any of my devices.
Trying to flash the Mi 6 Global 7.11.2 firmware gives this log in TWRP:
Then trying to flash the ROM afterwards gives me error 7. Where am I going wrong with the firmware update?
I bet at the end of all this it's going to be just a simple mistake haha :/
Click to expand...
Click to collapse
Its not your fault.
Error 7 is common. It means the zip is looking for the device name and getting the wrong one. Probably looking for "Sagit" or something and TWRP is saying "this is a Mi 6"
Scripts follow exact logic haha.
So my recommendation is to copy the RR zip to PC.
Use 7zip to extract just the updater script from the meta-inf file.
Then use notepad++ to delete the very top few lines which are about checking device type.
Then copy it back to the zip and flash it.
It won't check what device it is flashing on and will flash regardless.
That's fine as you know its the correct device.
Seems like the firmware package is flashing fine.
You can also go to the LineageOS 15 thread and download the firmware package I made from the latest miui firmware. Its on the OP by NisseCool.

Dobsgw said:
Its not your fault.
Error 7 is common. It means the zip is looking for the device name and getting the wrong one. Probably looking for "Sagit" or something and TWRP is saying "this is a Mi 6"
Scripts follow exact logic haha.
So my recommendation is to copy the RR zip to PC.
Use 7zip to extract just the updater script from the meta-inf file.
Then use notepad++ to delete the very top few lines which are about checking device type.
Then copy it back to the zip and flash it.
It won't check what device it is flashing on and will flash regardless.
That's fine as you know its the correct device.
Seems like the firmware package is flashing fine.
You can also go to the LineageOS 15 thread and download the firmware package I made from the latest miui firmware. Its on the OP by NisseCool.
Click to expand...
Click to collapse
I'm not convinced that the firmware is flashing correctly. This is the error message from trying to flash the ROM:
Can't install this package on top of incompatible data. Pleas try another package or run a factory reset
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
This was after I flashed the firmware package that you put together from the LineageOS 15.0 thread and after formatting data and rebooting into MIUI. Flashing the firmware gave the same log output as my previous post.
I had a look at the updater script, and it's definitely passing the first assert statements. This is the line with the error message:
HTML:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
This is killing me
EDIT: Disregard my comment about the firmware not updating. I had a look at the firmware update script and from the TWRP log it seems like it is flashing fine.

Fixed.
Firmware was flashing fine. I need to learn to properly read instructions.
I had formatted data through the interface where you need to type 'yes', but I didn't do an advanced wipe and tick data (I swear I had done it already)
Silly mistakes. Learn to read instructions, kids haha
Thank you for your help

JaredG_ said:
Fixed.
Firmware was flashing fine. I need to learn to properly read instructions.
I had formatted data through the interface where you need to type 'yes', but I didn't do an advanced wipe and tick data (I swear I had done it already)
Silly mistakes. Learn to read instructions, kids haha
Thank you for your help
Click to expand...
Click to collapse
That's really strange. Format should do the same as wipe just more effective.
Glad it's all working!

can't install Magisk

tried to replace SuperSU with Magisk via TWRP.
Magisk won't take by itself.
Removed SuperSU. Tried again. Still NG.
"adb reboot recovery" back to TWRP and flashed SuperSU. I have root back, though I don't see SuperSU in the app drawer.
The info to install Magisk leave a bit to be desired.
"install manually" what does that mean?
Remove root (SuperSU) seems to prevent one from installing Magisk, though I did "adb reboot recovery" to get the re-install of SuperSU done.
In the long run, I want to update our other H811 to 20x from 20q. Thats' what started me down this track.
Any input?

Did Magusk Zip Got Trough without any issues in TWRP?
Did you have the magisk App in drawer after flashing Magisk?
Magisk manager is sometimes an older version, so you have to go to magisk manager (app) open ist and click on upgrade or install upgrade.
sometimes my device needed 2installations. one in twrp an another in MAgisk app. but both were v16.0 zip.

no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.

metropical said:
no & no. "updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v16.0.zip'
Tried installing Magisk Manager, which went ok. And then Magisk from that. Error.
"Boot image patched by other programs (SuperSU, perhaps?)
Please restore stock boot image."
So I ran the script that removes SuperSU.
Tried install again from MM.
"Select stock boot image dump in .img or .img.tar format."
No idea where to find that.
Tried this method.
NG. SuperSU doesn't show in app drawer, though it appears to be working as I can reboot recovery from the phone without going into Terminal and adb.
Click to expand...
Click to collapse
You should Always search the TWRP errors you have, that gives you more info.
Error 1 means on your system partition is not enough space anymore, so delete or Freeze some bloatware/apps and it should go trough.
boot.IMG files are containt in KDZ (firmware files).
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.

uweork said:
Maybe you should visit https://******************/
and read trouh installation (with pictures) for better understanding.
Click to expand...
Click to collapse
went and posted in digeridoohan original thread.
https://forum.xda-developers.com/showpost.php?p=76980632&postcount=25580
all is well.. thanks very for the help. and I installed the Xposed module that works with TextAid and MM.
also your link won't doesn't seem to work. I've found that a I've had to use shortened links of late or they don't fire on XDA.

Guys I can't run Magisk on my LG G4 H815 with Nougat v29a. After removing Supersu and flashing magisk 17.1 with twrp, the phone doesn't boot normally. It reboots recovery when I click reboot system. It always reboot recovery. I don't know why.
Do you have any Idea?

Nexus 7 2013 ERROR: 7

Hi, I'm new here. I did some searching and couldn't find any answers regarding my problem exactly. I'm using TWRP to update my Nexus 7 2013 (flo). I have been successful in the past - as recently as yesterday. Something happened along the way and now I only get an error when attempting to flash ROMs.
I have been trying Lineage 16 and 17.1. I did do the repartition, but I get the same error on both ROMs:
Installing zip file '/sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Checking fir Digest file...
Warning: No file_contexts
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file /sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Updating partition details...
...done
I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!

ericdudeus said:
....I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!
Click to expand...
Click to collapse
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:

Thank you! I actually started over - completely wiped the tablet, repartitioned it, flashed the ROM, and Gapps, and it's fully functioning again. It just didn't like something in the process before, I guess.
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse

Hi,
i have too this problem.
I wipe everything, flashed the repartitioning zip and still havoc 3.3 cannot be flashed. What i have to do? thanks

The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!

ericdudeus said:
The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!
Click to expand...
Click to collapse
It's tell me E: eroor creating fstab

k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL

thrilway said:
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL
Click to expand...
Click to collapse
OK, the relevant error is...
Code:
erasing 18342 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,223772,228864,229950,243200]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
It seems your eMMC hardware version is <4.4
But RESTOCK should work.

Thanks, but I'm running a linux desktop, so I can't really run RESTOCK. Is there a guide somewhere to run the commands in RESTOCK manually?

EDIT
I've reviewed your logs. For the custom ROM to work you need repartition. Install sysrepart-max.zip then reboot and now install the ROM. If gapps are needed, use pico.

It worked! Thanks

k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
Thank you so much! It worked perfectly. In the beginning it didn't work, I just reboot the device after wiping system/data/cache/dalvik, then tried again to install the ROM, Now my device has the new ROM working without problem.

Getting error 70 in twrp when installing Opengapps (pico) even BitGapps

Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!

BlackVoltage said:
Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!
Click to expand...
Click to collapse
This is a Nexus 7 forum, not Error 7 forum, lol.
The error indicates a too small 'system' partition and you need to enlarge it. You will find a solution on Nexus 10 'manta' forum.

Ok thanks - I did not see that at first. My fault. Do you know a special Error 7 Nexus 10 Forum? Or am I just right here?
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com

Question Working TWRP but can't install ROM

TWRP 3.7.0_12-0 is installed on slot A and B and remains after rebooting. With ADB I can push files to the sdcard and I can see them under install but I'm not able to install a ROM (error message without any details).
I think something with the partitions isn't ok but I don't know what and how to repair this. In addition to the partitions you can see on the screenshot of the Backup part there are VBMeta System and Super partitions with 0 MB.
Which partitions should be mounted? Only Data is mounted, USB Storage also isn't mounted.

Please post a screenshot of the error message, and say the procedure that you've used, to install TWRP and to try and install the ROM.

I think, I tried everything possible to install again crDroid. So I don't know for sure, which way I installed TWRP (most probably with ADB sideload).
Installing the ROM
- push crDroid.zip /sdcard within TWRP (but not in the sideload modus)
- same with NikGapps an Magisk
- flash crDroid in TWRP
Maybe I didn't see before - today I got the nmessage ERROR: 1
- I'll try to fix this with the help of this article https://www.droidwin.com/fix-twrp-error-1/ but I don't know how to find out the firmware installed in twrp?
Update:
I could install Magisk without problems. Flashing crDroid stops then with: Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError)
Updater process ended with ERROR: 1

gartmann said:
I think, I tried everything possible to install again crDroid. So I don't know for sure, which way I installed TWRP (most probably with ADB sideload).
Installing the ROM
- push crDroid.zip /sdcard within TWRP (but not in the sideload modus)
- same with NikGapps an Magisk
- flash crDroid in TWRP
Maybe I didn't see before - today I got the nmessage ERROR: 1
- I'll try to fix this with the help of this article https://www.droidwin.com/fix-twrp-error-1/ but I don't know how to find out the firmware installed in twrp?
Update:
I could install Magisk without problems. Flashing crDroid stops then with: Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
if you are on A11, use the latest twrp skkk for A11
if you are on A12, use the latest twrp skkk for A12
alioth/poco f3/redmi k40
skkk/TWRP • AKR DL
dl.akr-developers.com