Develop Bugs

Problem with installing Lineage 14.1 made by surdu_petru

First of all thank Surdu for making both CM13 and this CM14 rom.
I'm having a bit of problem with installation.
Model number is HUAWEI RIO-TL00
I am running the CM13 made by surdu_petru, 13.0-20160502-UNOFFICIAL-rio. I was able to get that installed relatively easily and it runs just smooth and fine.
I have updated the TWRP to the version listed by Surdu in the Lineage OS thread and performed factory reset before attempting to install,
but I got an error 7
the version I'm attempting to install is "lineage-14.1-20170115-UNOFFICIAL-rio"
the error messages are
comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3..0.C3-00022
assert failed: rio.verify_trustzone("TZ.BF.3.0.C3-00025") = "1"
Installing zip file '/external_sd/lineage-14.1-20170115-UNOFFICIAL-rio.zip'
checking for MD5 file...
skipping MD5 check: no MD5 file found
Updater process ended with ERROR:7
Error installing zip file '/external_sd/lineage-14.1-20170115-UNOFFICIAL-rio.zip'
I noticed that something on my phone definitely doesn't match with the updater script.
Removing the assert lines in the updater script will allow TWRP to install, but I cannot get past the Cyanogenmod robot face, it keeps flickering after a second.
Any suggestion on what to do is appreciated, thanks.

1. try to flash the lastest version of TWRP. surdu_petru had mentioned that in the post.
2. I experienced the same issue of looping Cyanogenmod face flickering, after force reboot. all fixed.

Oneplus 3 bricked tried multiple methods, please help

So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance

EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?

tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.

EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.

tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.

EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos

Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..

You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.

hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM

Stuck installing ROM on Mi A2 Lite (daisy) - ERROR 1, ERROR 7

Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...

mothzart said:
Hi,
I am "building" (first had to fix the LCD etc.) a de-googled DAISY. I managed to unlock the bootloader, install TWRP, and root the original OS (Android One 10).
The problems started when I tried to install a custom ROM (at first Havoc, but other gave the same results). Just as instructed (YT, other pages, here...) I:
- formatted via TWRP
- REBOOT to TWRP
- wipe all except SD
- install ROM from zip
...and at this point I came across an error message
Error applying update: 7 (Error code: : kInstallDeviceOpenError)
Updater process ended with ERROR: 1
Many solutions suggest flashing boot.img from the ROM package, but (WHY?!?) all ROM's ((Havos, crDroid etc.) for daisy have no such file, although other devices have boot.img in their package.
I'm pretty much clueless... :/
Help, and thanks in advance...
Click to expand...
Click to collapse
Error 1 usually means wrong install package or wrong TWRP.
Are you using TWRP by offain?

[SOLVED]
The whole problem was that TWRP was wrong (not even offain as far as I remember). But I got a HUUUUGE amount of help (MANY THANX!!!!) from opal06 (main maintainer for crDroid on daisy) on Telegram channel dedicated to crDroid on daisy.
So If anyone hase similar problems - go to Telegram group - they will help you!
After flashing right (modified) TWRP versions, evrthng went fine, although I got to admit it was pretty complicated for [unlock + TWRP + custom rom + root] combo. On lavender it was much easier
cya all, good luck!

EDIT: Solved. Fail to flash Stock ROM on OP5T

EDIT: Solved.
I followed this tutorial: https://forum.xda-developers.com/t/...d-q-10-0-ota-for-oneplus-5t-dumpling.3709265/
I removed the compatibility.zip on my pc using 7zip and then loaded the file on the phone while it was on recovery mode (twrp). The installation went fine.
---
I was following this tutorial: https://forums.oneplus.com/threads/...bootloader-easiest-step-by-step-guide.733862/
But, when i go to flash the downloaded OTA Rom, TWRP throws a lot of red errors:
Zip Treble compatibility error!
Invalid zip file format!
Error installing zip file <pathname>
Now I got a phone with no ROM, only TWRP on it... and not sure how to progress from here.
I tried with two OOS versions:
OnePlus5TOxygen_43_OTA_048_all_1904191530_f1dedf62ffb14bff.zip
OnePlus5TOxygen_43_OTA_069_all_2010292144_76910d123e3940e5.zip <-- this seems to be the last one on OnePlus website.
Any suggestions to fix this?

LineageOS img.xz file and TWRP?

Hello guys. So, i want to install an unofficial lineage os to my Xiaomi redmi 6 (cereus). But th problem is the custom rom file format is img.xz and it's not detected by the TWRP recovery. I've tried to extract the img.xz into a img file. And it actually detected with the TWRP, so i tried to install it and locate the rom to System Image. It's tecnically got the rom image installed succesfully, but when i tried to boot it up, it's just got to the xiaomi logo and then it's just restarted repeatedly to the xiaomi logo again and again. So at this point, I don't know what can i do?
Note : Gapps and magisk installed without any issues because they're zip files. So i don't think the problem is in the magisk or Gapps.
Device : Xiaomi Redmi 6 ( Cereus )
TWRP Version : 3.6.2_9.0
Lineage OS ROM : Lineage OS Unofficial cereus (a64 and ab rom ) ( I got it from Andy Yan's Personal Builds SourceForge ).

NarenTheNoobFlasher said:
Hello guys. So, i want to install an unofficial lineage os to my Xiaomi redmi 6 (cereus). But th problem is the custom rom file format is img.xz and it's not detected by the TWRP recovery. I've tried to extract the img.xz into a img file. And it actually detected with the TWRP, so i tried to install it and locate the rom to System Image. It's tecnically got the rom image installed succesfully, but when i tried to boot it up, it's just got to the xiaomi logo and then it's just restarted repeatedly to the xiaomi logo again and again. So at this point, I don't know what can i do?
Note : Gapps and magisk installed without any issues because they're zip files. So i don't think the problem is in the magisk or Gapps.
Device : Xiaomi Redmi 6 ( Cereus )
TWRP Version : 3.6.2_9.0
Lineage OS ROM : Lineage OS Unofficial cereus (a64 and ab rom ) ( I got it from Andy Yan's Personal Builds SourceForge ).
Click to expand...
Click to collapse
Its Feb 2023 and I've just done EXACTLY the same thing trying to put lineageOS 20 onto a Galaxy TAB A 8..0 LTE. Hope I find a solution as my device is resting in download mode just to stop it from looping/buzzing.