https://download.lineageos.org/crackling
The First One!
Do we need su for arm or su for arm64?
Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64
What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs
kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite
M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs
AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.
Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"
Can this be installed over the top of cm13.0 nightly?
Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.
M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.
Wifi
Installed tonite smoothly however no wifi - anyone else with this?
Same here, just reported a bug to the bugtracker.
Make a clean install three days ago, all works fine
pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-
Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.
M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.
I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.
ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English
Related
Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks
Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.
Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.
is a ZIP file available for flashing via TWRP?
Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?
seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.
Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.
hello,
(with "this rom" i mean >sultan cm13<. I edited the title, before that it "was can't but sultan cm13", but now i know it doesnt boots any aosp roms)
a few days ago i used this rom as secondary with multirom (primary was freedom 1.10). now today, i wanted to use this rom as my dailydriver rom. i made the normal procedure, making a backup, then wiping the partitions (system, data, cache, dalvik) and after it flashing the rom. on the first try, i did it like i usually do, first the rom, then the gapps and then xposed. then i rebooted, and it was stuck on the 1+ logo screen about 10 mins. then i reflashed it, but just the cm.zip. then i still got stuck.
i tried it with the unofficial and the official twrp recovery. now i did a nandroid restore to the freedomos rom, and it boots normal.
please help me, i really want to use sultans cm13, i really like it!
i don't know why it doesn't work, i mean as a secondary it booted flawless..
btw i'm on the 3.2.7 firmware
(problem exists on all 6.0 aosp roms i tried. Please read further posts)
Did you follow the flashing instructions to the letter? If you did, you would have seen that the CM13 requires a one time flash of the OOS 3.2.6 firmware (linked in the thread).
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
ReNeH99 said:
Yeah sure but it did work with the 3.2.7 firmware on multirom, so i thought i dont have to do this. Well i will try this, and give you feedback then
Thanks
Click to expand...
Click to collapse
BTW, which xposed version did you flash? If it was v86.x then that's the most likely culprit (since the latest patch, v87 works, v86.x causes bootloop).
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
ReNeH99 said:
i just flashed the 3.2.6 firmware, still does not work.
yes i used the v87 xposed, also the second try i only installed the cm.zip, without xposed and gapps, etc.
Click to expand...
Click to collapse
Hmm... strange... TWRP doesn't give any errors either?
Hw4ng3r said:
Hmm... strange... TWRP doesn't give any errors either?
Click to expand...
Click to collapse
nope no errors, all the folders and build.prop, etc is in the /system folder too..
i also redownloaded the rom, md5 hash is right and it doesn't help either
May be a silly question but did you uninstall multirom?
Hw4ng3r said:
May be a silly question but did you uninstall multirom?
Click to expand...
Click to collapse
yep
i gonna try to flash RR 5.7.4, to see what happens then
edit: what i forgot to say, i also reinstalled multirom and the multirom recovery for another try. in the multirom menu the touch doesn't work then, and when the primary rom (cm13 sultan) boots after 5 secs, i just get a black screen, the phone isnt of, just a black screen, i have to press all 3 buttons for a reboot then.
edit2: RR also does not boot
edit3: lol i just reinstalled multirom and it boots as secondary rom. then i copied it to the primary slot, and *bling* it doesn't boot again... i dont get this...
Ok i tried it with multiple AOSP roms and it simply doesn't work. Strange thing is, they work as a secondary rom when i have multirom installed.
Does anybody have a solution for this maybe? I hope someone who knows about this problem can help me i don't want oos anymore i need aosp
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,
a few days ago moved from stock to twrp-3.0.2.2-klte, lineage-14.1-20170125-nightly-klte-signed and open_gapps-arm-7.1-micro-20170125.
So far I'm facing issues with APK installations. I always get the "parsing problem message" during manual installation. The files are not corrupt, I enabled untrusted apps as well as USB-debugging.
I went through some posts. Reinstalled GAPPS (micro and full), wiped everything, reinstalled the whole ROM and even tried last cm-14.1-20161225-NIGHTLY-klte but always get stuck with the same message... there is a problem parsing the package.
UPDATE: Same situation with lineage-14.1-20170131-nightly-klte-signed.
Has someone an idea? Would really appreciate some help. Thanks.
Device: Samsung Galaxy S5 (G900F/ klte)
MDAman said:
Hi,
a few days ago moved from stock to twrp-3.0.2.2-klte, lineage-14.1-20170125-nightly-klte-signed and open_gapps-arm-7.1-micro-20170125.
So far I'm facing issues with APK installations. I always get the "parsing problem message" during manual installation. The files are not corrupt, I enabled untrusted apps as well as USB-debugging.
I went through some posts. Reinstalled GAPPS (micro and full), wiped everything, reinstalled the whole ROM and even tried last cm-14.1-20161225-NIGHTLY-klte but always get stuck with the same message... there is a problem parsing the package.
UPDATE: Same situation with lineage-14.1-20170131-nightly-klte-signed.
Has someone an idea? Would really appreciate some help. Thanks.
Device: Samsung Galaxy S5 (G900F/ klte)
Click to expand...
Click to collapse
How exactly did you "move from stock"? Clean/dirty flash? Use migration build? Details please.
I just installed lineage-14.1-20170131-nightly-klte-signed with open_gapps-arm-7.1-stock-20170131, rebooted, setup all my settings (Declined the restore from previous backup on first start) and went to Play to install all my apps. Rebooted to flash addonsu-arm-signed, then rebooted again and flashed SuperSU-v2.79-201612051815.
All working fine for now on my G900T and I had CM13 prior to this. From TWRP wiped all but the ExternalSD, rebooted to recovery and wiped again all but ExternalSD, then did a Factory Reset and installed LOS. The only thing not working is FolderMount, but I was expecting that until the next update.
Sent from my SM-G900T using Tapatalk
jhedfors said:
How exactly did you "move from stock"? Clean/dirty flash? Use migration build? Details please.
Click to expand...
Click to collapse
I've flashed TWRP using Odin3, booted into recovery, fully wiped stock (sys, data, cache, int sd, etc.) and installed LineageOS rom + GApps.
Reflash again and check md5 of your dowload rom agains the rom provided by lineage website.
This is md5 of the latest rom version 20170131
7305fd079020c0f872148241b437ceaa
md5sums are provided to verify the file download was successful. If you'd like to verify the file has not been tampered with, check its signature instead.
hanzaz said:
Reflash again and check md5 of your dowload rom agains the rom provided by lineage website.
This is md5 of the latest rom version 20170131
7305fd079020c0f872148241b437ceaa
md5sums are provided to verify the file download was successful. If you'd like to verify the file has not been tampered with, check its signature instead.
Click to expand...
Click to collapse
Done that. Still the same error.
Installed lineage-14.1-20170207-nightly-klte-signed (MD5 is fine). APKs still can't be parsed.
First I updated. Afterwards I wiped and tried clean install. No difference.
I have the exact same issue. Moving the apk from external to internal storage solves the problem though. Seems to be a hickup in the binding of the SD memory.
_-M-_ said:
I have the exact same issue. Moving the apk from external to internal storage solves the problem though. Seems to be a hickup in the binding of the SD memory.
Click to expand...
Click to collapse
simple yet elegant.
Thank you very much.
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