Does anyone know how to fix Error 7 when trying to flash Lineage with TRWP?
I haven't updated since near the end of CM13 so probably a year ago now.
Does Lineage have all the tweaks of CM?
Thanks
xda163fm said:
Does anyone know how to fix Error 7 when trying to flash Lineage with TRWP?
I haven't updated since near the end of CM13 so probably a year ago now.
Does Lineage have all the tweaks of CM?
Thanks
Click to expand...
Click to collapse
With error 7, you probably need to wipe 'data' with TWRP. You will lose all your data/apps, to my knowledge, it is not possible to 'dirty' flash LOS over CM, a clean new installation is needed with the sacrifice of your data.
Tweaks: at the moment, I don't miss anything from CM that is not in LOS.
Related
Hi Everyone
I have just grabbed the Paranoid .zip for Nexus 9 (Flounder) flashed it via twrp but it stuck in bootloop for about 10 mins. I have restarted the device but still no luck. Any suggestions?.
Thanks
vampire_8_7 said:
Hi Everyone
I have just grabbed the Paranoid .zip for Nexus 9 (Flounder) flashed it via twrp but it stuck in bootloop for about 10 mins. I have restarted the device but still no luck. Any suggestions?.
Thanks
Click to expand...
Click to collapse
You figure it out? I had the same issue.
Marky__Mark said:
You figure it out? I had the same issue.
Click to expand...
Click to collapse
I think I did can't really remember mate, I think it was the kernal I had a custom one and caused the bootloop. Flashed the stock boot image and it did work afterwards. Honesty I ditched it after 2 days running dirty unicorns now, in my opinion it's the best custom rom out there for now, I even flashed it to my N6 running perfectly fine check it out and make sure u don't have xposed install you can have some issues, just check it out and read the thread you'll be fine ????????
vampire_8_7 said:
I think I did can't really remember mate, I think it was the kernal I had a custom one and caused the bootloop. Flashed the stock boot image and it did work afterwards. Honesty I ditched it after 2 days running dirty unicorns now, in my opinion it's the best custom rom out there for now, I even flashed it to my N6 running perfectly fine check it out and make sure u don't have xposed install you can have some issues, just check it out and read the thread you'll be fine ????????
Click to expand...
Click to collapse
Im running PA with xposed and elementalx and its smooth as silk. My issue, I think, is my device was unencrypted and its been so long that I havent used a custom kernel that i forgot about it. I flashed the new AOSPA without elementalx to test out the stock kernel and i think it tried to encrypt. When it took too long for the first boot, i manually rebooted the device and that borked the data so i had to do a factory reset and lose all my data. Pain in the ass, but im diggin this rom.
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
luigymarani said:
Hello, i tried to OTA update my op3 from oficial CM13 nighly to oficial CM14 nighly and it did update.
but when i tried to enter TWRP recovery mode (i want to restore the backup because the new cm version has too many bugs) it wont open twrp, it stays in the op logo for some seconds and then a black screen appears and i have to restart my phone
i tried to reinstall twrp, intall stock recovery but nothing works, please help
Click to expand...
Click to collapse
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
nitros12 said:
If you had searched for your problem, you would have come across this: http://forum.xda-developers.com/oneplus-3/how-to/oos-3-5-2-comunity-build-t3461648/post68691560#post68691560. Reflash it in fastboot and it will work.
Click to expand...
Click to collapse
Thanks a lot! it worked
Hw4ng3r said:
Are you running official TWRP? CM14.1 requires modified TWRP and I believe most people are using version 23 (Credits to @eng.stk) for CM14.1.
Click to expand...
Click to collapse
Oh I didnt know that, thank you
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
DamianSewo said:
Thank you for both asking the question and answering the question. If I had seen this topic earlier I wouldn't have wasted 5 f*cking hours. Thank you!
CM13 nightly to CM14 nightly ruined everything for me. Never doing dirty flash again.
Click to expand...
Click to collapse
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
This is quite funny (obviously not to you and no offense) and sad, but people that have been used CM14.1 for a while have said the same thing for about 2 months now: "people coming to CM14.1 from 13 are in for a mess"
Click to expand...
Click to collapse
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
DamianSewo said:
No offense taken. This is just what happens if you venture using MODs with limited knowledge
But the misery of updating hasn't ended yet. So now I have access to TWRP, and I had done a TWRP nand backup before going to CM14, but I found out this was from the Boot, System, EFS and System Image, but NOT from the 'data'. When I restore everything I have I do get back into CM13, but nothing is working and it's rebooting all the time. Completely useless. I just checked and both my data and sd-card are intact. So I don't understand why I am not just getting back to the state I was before starting the CM14 misery. Is this because files on the 'data' got changed when doing the OTA CM14 nightly?
I also tried first restoring the image and then putting the CM13 nightly that I came from on top of it. Same ****. Also tried other way around, first CM13 nightly from TWRP, and then the image restore ('data' excluded since I didn't have that) on top of it. Also no luck.
Anyone an idea how to get back to my CM13?
By now I have wasted a full working day. I regret ever installing CM14, I just want to get back to the situation yesterday with a working CM13... :crying:
Click to expand...
Click to collapse
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
luigymarani said:
Exactly, when I got my TWRP working again I tried to restore my backup (cm13) but it happened like you said, wouldn't work.
I had to clean flash a new cm13 rom :/
Click to expand...
Click to collapse
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
DamianSewo said:
Why were you unable to use your backup to restore CM13? In my case I didn't have a backup of the data-partition, which I think is the problem. But if you have a complete backup you should be able to get it back right? Isn't that the whole purpose of doing a backup before you update the ROM?
Click to expand...
Click to collapse
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
luigymarani said:
It should have worked, but it didn't. I have no idea why, it was a complete backup and everything in it was working perfectly so idk
Click to expand...
Click to collapse
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
DamianSewo said:
Okay so if you restored a complete backup and still wasn't able to get back to a working CM13 then we probably have exactly the same issue.
It could also be related to the TWRP version we have installed now, maybe the new TWRP is not able to handle CM13. Anyone here to comment on this?
Click to expand...
Click to collapse
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
luigymarani said:
Which TWRP version are you using? I flashed the 3.0.2.1-v23 and it supports cm13, because o already flashed a new cm13 rom and I'm using TWRP normally.
Click to expand...
Click to collapse
I'm also using 3.0.2.1-v23. Trying to find any information that could help me have my CM13 TWRP image working again, but no luck so far
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.
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
Last weekend, I decided to flash a new ROM since the one I have been using is no longer being developed. I flashed a LineageOS nightly build because I used to like Cyanogenmod and heard Lineage is a continuation. I do like the ROM overall, but for some reason it encrypted my phone during install. I did not want it to do this, it just did it without asking me (when I first got my phone, I remember I was having problems with it being encrypted, with my recovery and such).
Is there any way to reinstall LineageOS without it encrypting the phone? If not, how do I decrypt the phone again and get back to basically stock + root? I downloaded the most up-to-date stock 7.1.2 ROM from Google, and was going to just flash that, but it wouldn't let me in TWRP (said the zip was not valid). I also tried rolling back to an older backup (not LineageOS), but the phone never booted.
FYI - I use Linux Mint and have the latest adb/fastboot, and the latest TWRP for Nexus 5x.
Thank you if you can help.
cspctec said:
Last weekend, I decided to flash a new ROM since the one I have been using is no longer being developed. I flashed a LineageOS nightly build because I used to like Cyanogenmod and heard Lineage is a continuation. I do like the ROM overall, but for some reason it encrypted my phone during install. I did not want it to do this, it just did it without asking me (when I first got my phone, I remember I was having problems with it being encrypted, with my recovery and such).
Is there any way to reinstall LineageOS without it encrypting the phone? If not, how do I decrypt the phone again and get back to basically stock + root? I downloaded the most up-to-date stock 7.1.2 ROM from Google, and was going to just flash that, but it wouldn't let me in TWRP (said the zip was not valid). I also tried rolling back to an older backup (not LineageOS), but the phone never booted.
FYI - I use Linux Mint and have the latest adb/fastboot, and the latest TWRP for Nexus 5x.
Thank you if you can help.
Click to expand...
Click to collapse
If you want to flash stock rom you have to flash it via fastboot. The instruction is on the Google download side. But if I remember right you have to wipe everything so make a backup of important data.
If I format my "userdata" with fastboot to get rid of the encryption, do you know if it will delete my ROM backups? I think the encryption is why I'm having trouble going to another ROM from LineageOS. I REALLY wish the ROM would simply ask you before deciding to encrypt the phone. I have no reason to encrypt my phone, and I don't want it encrypted.