Hi all,
I've been running CM 13 successfully on my Xiaomi Mi5 for a while, and decided to upgrade to LineageOS 14.1. I figured it would be simple, d/l gemini weekly build, opengapps, wipe, flash through recovery.
However, when I attempt to install, I get the following error:
Error: Checkingthe TZZ version ..... assert failed: gemini_verify_trustzone("TZ.BF.4.0.1-77307) == 1
I've wiped everything (except for internal storage), so I didn't think I had to use the experimental migration version.
Any suggestions? (I'm currently downloading the 1.4Gb of Miui8 to see if reflashing back to miui then back again works)
Update:
I flashed reflashed miui, and although it wouldn't boot (no OS found), I could successfully flash LineageOS afterwards!
cangurob said:
Update:
I flashed reflashed miui, and although it wouldn't boot (no OS found), I could successfully flash LineageOS afterwards!
Click to expand...
Click to collapse
I had a similar issue with my oneplus 3. I wound up reflashing stock, reformatting to exf4, and wiping and I was able to install correctly. Glad you are up and running.
Related
SOO, I may have broken my find 7a, I was running on DU 8.2 with LVM, decided it was time to switch the the DU lolipop build, so I did everything right, backed up all my apps, did a TWRP backup. DU loli doesn't support LVM, so I flashed the remove LVM zip, rebooted recovery, tried to install DU loli and it failed, restarted recovery, tried it again and it failed, decided I would try the remove LVM zip once more and flash loli again, no go. So then I decide that I'm not brave enough for lolipop and flash the Setup LVM zip and try to restore my backup, it fails on restoring data (over and over, even on my older backups). This isn't good, because I need my phone, so I download 2 more roms, DU 8.2 and Nameless lolipop, They install in probably under a second, but then don't boot with or without LVM. So then I decide that maybe If I flash Remove lvm, Wipe everything, then use Coldbirds method twice (unsplit then split) that might reset everything. That didn't work, neither did flashing nameless with coldbirds unified, I've been trying everything I can think of, and I'm at my wits end, I don't know what I'm on coldbirds wise, it's probably my 8 or 9th time using that tool today. I have fastboot working, and recovery working (Used twrp 2.8.0.1, 2.7.1.0 entropy, 2.x.x.x coldbirds). Is there a way to just reset everything back to stock? All my partitions and such? Would flashing Oppo recovery and a color OS rom do that? Is there anything else I can try? Thanks for any responses or advice
-e
hi,
today, i tried to update my op3 from lineageos 14.1-201703202 to the new lineage-14.1-20170309 with twrp. but i when flashing, i get error 7.
i already had the same issue the last time and could solve the issue with first flashing oxygen 4.0.3.
i guess when i flashed oxygen 40.3, i got the newest firmware and modem (and still have it, of course). why do i get this "error 7" again?
i thought it was because of the "false" twrp (i have 3.0.4-1) and then i made the big mistake to update twrp to 3.1.0.0. this version of twrp wiped my phone. thanks good, i had a one day old full nandroid backup to restore phone including going back to twrp 3.4.0-1.
but what should i do to get the newest lineageos flashed?
i am a absolute beginner and dont have deeper knowledge, but i am already a little bit angry that everytime i want to flash an lineageos update, i get into trouble. is this normal with oneplus3 and lineage? what am i doing wrong?
thanks a lot for your help.
best regards,
flotsch1
I have a similar issue with LineageOS updates.. I flashed LineageOS14.1-20170208 nightly on my Oneplus 3 with twrp-3.0.4-1, however I cannot upgrade to newer nightly releases. For some reason they always fail to install, it actually boots on recovery mode but installation using twrp quickly fails and I cannot even see the exact error it throws. Any ideas?
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
jim262 said:
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
Click to expand...
Click to collapse
It isn't, it is a check for firmware... Could be that lineage is using OB12 firmware now..
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309.
But there's new fw/modem here https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Install latest and flash new lineage. No error 7 here!
kebeil said:
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309. But theres no new fw/modem ... https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Click to expand...
Click to collapse
The fix is mentioned in the official weekly lineageos thread. basically you need to factory reset, flash the zip file attached in the thread and then flash the latest lineageos nightly/weekly image, followed by wiping dalvik and cache. It worked for me anyway, although everything got wiped so I had to restore my apps from backup (I use titanium backup).
flashing the betafirmware was the solution for error 7, but please see my other tread explaing my gapps-problems after successful lineagos update.
Here is how you fix error 7 in TWRP. You simply edit the first Two lines in the updated script by deleting them. https://youtu.be/XkwSO_I9GfE
Hello,
Since I got my XT1635-02 in April I have tried to use LineageOS and/ or AOKP. The problem is, when I flash either, I get an endless bootloop.
When I got the phone I:
Unlocked the bootloader
Flashed TWRP - the latest 3.1.1-0
Flashed Lineage ROM
I don't use Gapps - or I'd rather not - but at this stage I have flashed the Pico package
Then flash su-addon.
I've tried different combinations; only flashing LineageOS/AOKP but got the same result.
Stock images work fine for me. I even got to the point where I had to write a little bash script to flash all of the components in the correct order for the RETUS Nougat image.
Last month, by some fluke I got LineageOS to boot. However, I have no idea what I did differently, it just seemed to work that one time. However, I have been living off of that install for about 3 weeks and the OTAs even worked perfectly.
Today I got bored and decided to flash AOKP.
Booted in to TWRP
Wiped Dalvik, Sys, Data, Cache
Flash AOKP
Reboot
Bootloop.
Is there something wrong with my phone or is there something wrong with my process?
Any suggestions welcome. Thank you.
I remember​ that problem with Razr. Some custom roms were booting fine, some bootlooping.
The first workaround was to flash working one then without reboot flash desired one.
Later we figured out that wiping/formating partitions was the problem. Bootlooping rom couldn't read the file system. Solution was to not wipe or to wipe to the correct file system.
Sent from my XT1635-02 using Tapatalk
I think you may be on to something because I had flashed LineageOS after flashing the stock Nougat image. Still, would like a surefire way to just run a ROM. I've never had this issue on any other device.
I had it on Razr and just started to happen after one CM nightly build. Turned out that devs changed FS.
I rooted my phone yesterday fine and made a backup of my oxygen OS (original rom).
I am definitely successfully unlocked and rooted, and TWRP newest version is running.
I have tried so much to get a new rom running correctly I have tried both resurrection remix official and unofficial:
https://forum.xda-developers.com/on...evelopment/op3-3t-resurrection-remix-t3754941
I have also tried official paranoid android, but every time it starts up I get two issues the first is the error saying "android.media has stopped" the more serious being the fact that no matter which rom I flash it always begins force restarting over and over again, I get into the OS fine, have a scroll around and around every 2 mins or so it just force reboots, then it comes back and is fine for 2 mins then same again.
It has happened with the official and unofficial versions of resurrection remix and also happens exactly the same with paranoid android. I have no idea what else to try at this point.
The process I have been using for flashing is this:
1. Boot into TWRP recovery
2. Wipe everything but internal storage.
3. Install my rom.
4. Reboot.
5. Starts up successfully and then falls back into the standard boot loop and the android.media error.
I have also tried it with GAPPS which was throwing some setup wizard has stopped error, so for now I am just attempting to get an actual rom running without constantly restarting.
Any help is massively appreciated, I am tech savvy, hence why this is annoying me even more.
Thanks,
Kieran
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
jeffrey268 said:
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
Click to expand...
Click to collapse
My backup is the original oxygen and this restores fine and works fine just as soon as I try to flash a new rom it just keeps restarting every few minutes, I dont really know what else to try.
Also to add I sometimes see this issue when I attempt to flash certain roms..... 'assert failed: op3.verify_modem("2017-11-16") == 1'
Use the recommended firmware by the rom. Also you can't flash most roms without Gapps.
1. Flash proper firmware
2. Flash the rom
3. Flash Gapps or something similar.
4. Flash any additional kernel (optional).
5. Flash SuperSU or Magisk.
The assert failed littery tells you that you use using the wrong modem // firmware.
my first question which custom Rom you installed every Rom developer say it is stable but only few has been stable as rock . i tried everything but settled with AICP Rom. and then try to use GAPP as ARM64 android 8.1
u have first install Rom and then GAPP then magisk or Superuser anything which u refer
https://forum.xda-developers.com/on...e-development/wip-official-aicp-13-0-t3713637
this is the Rom which i use it . .they are stable and also update it weekly thrice ..
if u like it you can install this ROM
Lineage 16.0 now available from here
https://download.lineageos.org/crackling:laugh:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
upd: yes, my bad, for me 15.1 also doesn't work, so it is on my side.
upd: I did this to fix it: https://forum.xda-developers.com/showpost.php?p=66158015&postcount=2) as I understand I downgraded fastboot to be cynogen, from los
ilya_m said:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
Click to expand...
Click to collapse
You may have to sideload it if coming from 15.1
ilya_m said:
for me it does not boot. just boots to bootloader... (just wrote here as I don't see the rom thread)
Click to expand...
Click to collapse
Are you using the nougat bootloader? Try downgrading to any of the COS13 firmwares then flashing.
FWIW though this is a bug with LOS since beroid's crDroid works fine with the newer bootloader. Same with his TWRP (this bug does exist in OrangeFox Recovery which suggests it's a software thing).
Works, but I'd stay to 15.1
The ROM works fine for me. Everything, the camera, talks work fine. But I don't know if it's just me but my phone runs pretty slow on the new ROM, without any of my apps installed.
I've installed it on my Swift which has TWRP 3.3.1 with no issues.
The issue started when I wanted to install OpenGapps pico. I get error 70, saying I have no space.
I've tried a lot of things I've found online, including wiping everything (full wipe, including any and all partitions, /data, /system, and everything else), resizing the /system partition (still only 1511MB).
I've searched this Swift sub-forum, and have not found a solution. Is my search failing me?
I still get error 70 when I try to install OpenGapps, saying there's not enough space.
Anything else I can try?
romanboy said:
I've installed it on my Swift which has TWRP 3.3.1 with no issues.
The issue started when I wanted to install OpenGapps pico. I get error 70, saying I have no space.
I've tried a lot of things I've found online, including wiping everything (full wipe, including any and all partitions, /data, /system, and everything else), resizing the /system partition (still only 1511MB).
I've searched this Swift sub-forum, and have not found a solution. Is my search failing me?
I still get error 70 when I try to install OpenGapps, saying there's not enough space.
Anything else I can try?
Click to expand...
Click to collapse
Are you installing the GApps in TWRP immediately after the LOS Installation, prior to booting into LOS?
Have you tried the nano instead the pico?
I followed the instructions at https://wiki.lineageos.org/devices/crackling/install using twrp 3.2.3 as instructed. I used MindThe Gapps 9.0 as I saw somewhere (as romanboy above found) that standard Gapps gives error 70 (not enough space) even for nano version. Swift boots into LOS 16 after some time but it keeps displaying popup about Pixel Setup keeps stopping: I can only show App Info (with Force Stop option) or Close app: either case results in popup appearing again. I've asked the author of the above wiki (on reddit #LineageOS) but no reply.
I started again by installing cm13.2 then used twrp 3.2.3 to install LineageOS16.0 followed by OpenGapps 9 pico. All now Ok.. So MindTheGapps 9.0 is no good.
Camera not working, flashed with latest TWRP.
Official Rom
LaneyUK said:
Camera not working, flashed with latest TWRP.
Click to expand...
Click to collapse
There is now an official lineage Rom
https://download.lineageos.org/crackling