yashsingh1/xdaforums huggingface dataset:
[LineageOS Questions & Answers] jhedfors:
... It is not so bad to clean wipe once in a while either :)
[LineageOS Questions & Answers] Nordlenning:
Since I already have lineage-14.1-20170317 installed & get this error trying to update to lineage-14.1-20170324 this seems strange.

What connection is there to the migration build & the signing of new builds & I have sideloaded latest zip update... Hmmm

Just curious..
[LineageOS Questions & Answers] jhedfors:
I wish i could tell you. Maybe it could be helpful if you could attach recovery logs that show the error when attempting to flash. If it is signature verification error, I can only think that a clean flash can fix it. I have seen it suggested before to disable zip verification in TWRP...
[LineageOS Questions & Answers] Nordlenning:
Where can I locate those logs, names? from TWRP , I have disabled zip verification in TWRP to no effect.
[LineageOS Questions & Answers] jhedfors:
Under Advanced menu in TWRP. Select copy logs, and it will place them in the root of your sdcard directory.
[LineageOS Questions & Answers] Nordlenning:
This from recovery.log

|:Set page: 'flash_zip'

I;operation_start: 'Flashing'

Installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170324-nightly-tsubasa-signed.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

minzip: Not a Zip archive (found 0xb919c702)

minzip: Parsing archive 0xb493f5f4 failed

Zip file is corrupt!

Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170324-nightly-tsubasa-signed.zip'

Updating partition details...

**************************

I;operation_start: 'Flashing'

Installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170324-nightly-tsubasa-signed.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

Verifying zip signature...

I:read key e=3 hash=20

I:1 key(s) loaded from /res/keys

E:footer is wrong

I:Zip signature verification failed: 1

Zip signature verification failed!

Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170324-nightly-tsubasa-signed.zip'

Updating partition details...
[LineageOS Questions & Answers] jhedfors:
Yeah, something odd for sure is going on that I am not sure you are going to resolve without clean flash. You could backup, and try to clean flash, and then test if you can flash on top if that. Sorry, I don't have any other suggestion. Something could have gotten corrupted in your data.

Do you have an updated TWRP version?
[LineageOS Questions & Answers] Nordlenning:
Do you have an updated TWRP version?

I'm using TWRP 3.1.0.0

EDIT

Just wiped & formatted my installation & installed Latest LOS with TWRP.

No problems observed. Latest installed & working with root..

So the waiting game begins until next update :)
[LineageOS Questions & Answers] ghano88:
thank you

:) thank you so much
[LineageOS Questions & Answers] IronRoo:
I kept getting zip verification fail on latest builds of LOS13 and LOS14 on Samsung S4 Mini, which I couldn't understand, anyhow it turned out to be TWRP 3.0.3-3 I was using which I had recently updated as well. Previous TWRP ver I used, 3.0.1, worked fine. Anyhow, I updated TWRP to 3.1.0 (which is still a test ver on my S4 Mini) and it flashed the Linage ROM's no problem. What ver of TWRP you on?

Edit: oh now see you are on latest TWRP
[LineageOS Questions & Answers] MaedaKeiji:
Hi there, with this new update will we have to update the gapps too??

I've installed Lineage OS 14.1 on my gf LG G3 and is working fine, updates are appearing but I'm afraid of doing them because of the gapps... :S
[LineageOS Questions & Answers] CristiannL:
Just updated my LG G2 with the version from 2017-04-24 (This is actually my first update on Lineage, I've been running the version from 2017-03-20 until today). It was try and error. After installing update I got a bunch of errors from Google services - the kind of errors that don't go away after a restart - so I've just re-flashed Gapps from Recovery. No more errors and I now have the latest update from Lineage.

Don't forget to back-up ;)
[LineageOS Questions & Answers] Nordlenning:
Some info regarding updating.

I have tested this every possible way by now, & I discovered that it is the internal

installer

that corrupts the file. Today the latest LOS was released 28.xx.xx.xx & I downloaded this update from within LOS. Then I tried to install this from LOS menu using install option. The phone rebooted to TWRP after some time.

Then I checked to see if the update was installed, it was not. I found the update in the download dir. I copied the file to my SD card to be safe & tried to install it using TWRP from my internal & from my SD, neither worked. The signing issue was still there. Wiping cashe/dalvik etc have no effect. It will not install. File is corrupt. SO i downloaded the update file on my lap, & copied it to my SD using my USB cable. First I deleted my internally downloaded update. Then I rebooted to TWRP & tried to install again. NO PROBLEM update installed without problems. we don't need to wipe anything before installing update.

So my conclusion is that the file gets corrupted when trying to install it from the main LOS install procedure.

You must download it again

. I will try to install next update directly from internal using TWRP next time to see if the internally downloaded file is OK.

Los is informing that this updating should be done manually, but not that the file will get corrupted if you don't.

This may help other NOT to corrupt the downloaded file trying to use the internal install procedure.
[LineageOS Questions & Answers] IronRoo:
Thanks for that, it does seem to suggest you may be correct, however I have only ever downloaded manually via the LOS website and then flash manually with TWRP (not started from LOS updater) which was why I thought it was TWRP. Possibly they are two separate issues?
[LineageOS Questions & Answers] zwok985:
Thanks !! :victory:
[LineageOS Questions & Answers] ashussain5:
by dirty flash you mean download the latest nightly, save it to sd card, boot recovery and nstall the .zip right?
[LineageOS Questions & Answers] Nordlenning:
The latest LOS arrived yesterday, & my final test.

This time I just downloaded latest LOS & rebooted my phone to TWRP.

Maneuvered into /data/data/org.lineageos.updater/app_updates/ where the update is downloaded.

Then I installed Latest update from there & encountered NO problems... No wiping cache etc needed.

So don't ever use this internal install after downloading zip. You will run into this signing issue.

This is the first time I encounter install files that gets corrupted/written to. Lessen learned.

Otherwise, LOS works excellent on my sony experia v.
[LineageOS Questions & Answers] IronRoo:
yes, but specifically it means you do not wipe

---------- Post added at 12:55 AM ---------- Previous post was at 12:54 AM ----------

OK, good :highfive:
[LineageOS Questions & Answers] Vectrexer:
THANK YOU!
[LineageOS Questions & Answers] revived_blaze:
I have download the latest update and even got to recovery mode from the update window. But after that i face a issue of corrupted zip file.

I have tried downloading the update thrice but still get the same issue. How to fix this issue?

Here's the recovery log:

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

minzip: Not a Zip archive (found 0x29221e12)

minzip: Parsing archive 0x76dbdfeb38 failed Zip file is corrupt! Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170517-nightly-kenzo-signed.zip' Updating partition details...

I: Data backup size is 4721MB, free: 18065MB.

I:Unable to mount '/usb-otg' I:Actual block device: '', current file system: 'auto' ...done
[LineageOS Questions & Answers] Nordlenning:
You did not read the post above!. You say "got to recovery mode from the update window"

The post say :" So don't ever use this internal install after downloading zip "
[LineageOS Questions & Answers] bintangalexander:
i follow you guide but why to comeback again to twrp after reboot system ?
[LineageOS Questions & Answers] phajkic:
Damn I have the same problem... also when i try to format data i have red error

E: unknown command [log]

E: unknown command [log]

So for now my phone is total dead...

Ok, I solved the problem.

I installed the new version of TWRP, now everything works fine.
[LineageOS Questions & Answers] freddy boy:
Where igofor my SM-G935W8 whit Videotron in Canada

---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------

For the Rom whit LineageOS
[LineageOS Questions & Answers] dantheperson:
Where did you get TWRP 3.1 from? I can't see S4 Mini GT-I9195 listed on TWRP devices page.
[LineageOS Questions & Answers] IronRoo:
it was the tryout version a few weeks ago from here

https://xdaforums.com/showthread.php?t=2678420
[LineageOS Questions & Answers] nesoor1230:
Hi All. When manually updating lineage at nexus 5x by TWRP, should I wipe system beside delvic /cache? To ensure not to duplicate the two system.

Also is it a must to flash the gapps again ?

By another phrasing what is right procedure to install updates that downloaded externally by PC, and by using TWRP. Thanks
[LineageOS Questions & Answers] bhishmar:
Detailed steps for updating LOS 14.1

I also have the same question as "nesoor1230"

Let me elaborate further.

a) What is the exact procedure of updating Lineage-OS 14.1?

b) Should we wipe cache/Dalvik before flashing new LOS-14.1 zip with TWRP?

c) Should we wipe "System" also? (Not required/ Should not do/ Does'nt matter)

d) Should we install Gapps again after flashing LOS-14.1 zip?

e) Does the Gapps has to be the new version (same dated version as new LOS-14.1) ?

f) Instead of using TWRP for flashing above, can we do this with fastboot PC method?

g) Should we wipe cache/Dalvik after install (final step)?

h) Question-(f): Is using fastboot a more reliable method, even though not simple?

I am using MotoG 2015 (osprey)

Can experts here give their comments & experiences?
[LineageOS Questions & Answers] kurtn:
Why don't you use in-rom method settings-about phone-lineageos update?

Last 5 LOS updates for moto e condor worked fine. Up till march I did the same with mokee marshmallow ROM.
[LineageOS Questions & Answers] bhishmar:
Because I read in these & related forums that many faced problems with LOS-built in method, especially in MotoG 2015 osprey. Many were so recommending some manual method.

I want some experts with experience to answer the pointed queries.

Any way thanks for ur 2 cents...
[LineageOS Questions & Answers] kurtn:
Comeon, give the maintainers a chance. They are maintaining a piece of code that should do the work for you. Try it, and if it doesn't, you cann allway do a manual installation. Last time LineageOS update faild for me, I changed to anoher ROM. I've learned: Manual methods are less stable for me, because sometimes I forget sometheing. But if you really whant to:

a) What is the exact procedure of updating Lineage-OS 14.1? Do a backub if you want. Go to TWRP, flash the ROM, wipe cache/Dalvik, Reboot to system.

b) Should we wipe cache/Dalvik before flashing new LOS-14.1 zip with TWRP? Before or after doesn't matter

c) Should we wipe "System" also? (Not required/ Should not do/ Does'nt matter) Never wipe System when you stay with the same ROM. If installation fails, you have no System.

d) Should we install Gapps again after flashing LOS-14.1 zip? No. Gapps makes an entry in System to survive update.

e) Does the Gapps has to be the new version (same dated version as new LOS-14.1) ? The Google apps are updating themselves via Playstore. No need for new gapps.

f) Instead of using TWRP for flashing above, can we do this with fastboot PC method? You can, but I don't recommend. It's a nother source of instability.

g) Should we wipe cache/Dalvik after install (final step)? Before or after doesn't matter
[LineageOS Questions & Answers] bhishmar:
Need to re-install updated-Gapps on Lineage-OS nightly upgrade ?

I have seen many who give such/similar recommendation here regarding re-installing latest Gapps-package, while upgrading to a new nightly LOS rom. Most say not required.

"Ibuprophen" in another thread:

https://xdaforums.com/showpost.php?p=71314165&postcount=3 says it does'nt hurt to flash an updated Gapps, while upgrading to a new ROM nightly.

But let me quote from the official Lineage-OS Wiki site,

regarding upgrading Lineage-OS:-

https://wiki.lineageos.org/upgrading.html

So official LOS site says you MUST re-flash updated-Gapps (means mandatory)

Confusing !! he . Who to believe?

Can experts here comment on this anomaly?
[LineageOS Questions & Answers] kurtn:
Plesse non't confuse updating and upgrading.

Updating is going from one nightly to another.

Upgrading is going from LOS 13.0 to 14.1

This thread is about updating. Your link is upgrading.
[LineageOS Questions & Answers] bhishmar:
Updating vs Upgrading & Gapps

Are you very sure about this. I mean these terms: Updating/Upgrading!

I have seen these two terms used many times loosely, in these very forums to mean the same, & in some posts, it is very difficult to differentiate, from context.

Let me try to find holes in your argument.

Just see the official Lineage-OS Wiki site for "Manually Upgrading LOS". Steps-1 to 10:

https://wiki.lineageos.org/upgrading.html

Did u see anywhere in these detailed steps, Wipe Data/Factory Reset is mentioned?

Answer : No?

Now If you are Upgrading (as per your meaning, say from 13.x to 14.1) Don't you think Wipe Data/Factory Reset is an essential step? I think so.

So does that mean "Upgrading" in the above Official site means: updating 14.1 nightly to next nightly?

Answer: Very much possible.

Now I am not saying I am right & you are wrong! You may still be right.

But with such glaring inconsistencies, in forums & official sites, no wonder a newcomer like me & others are confused.:confused:

I am a newbie here in these forums, but by no means I am a newbie in this field.

Your comments & other expert's are welcome, to untangle this.:)

Thanks
[LineageOS Questions & Answers] kurtn:
[MENTION=5126823]bhishmar[/MENTION]: you are right it's confusing. And you have no reason to trust me or anyone else in this forum. But I think, we both trust the LOS people - we give the highest possible rights to their software on our phones.

In the LOS wiki they talk about version upgrade. It's a feature of LOS to upgrade without factory reset. In other custom androids they simply say "do a clean install if you come from another version or ROM".
[LineageOS Questions & Answers] bhishmar:
Thanks for ur quick acknowledgement.

I tend to agree with ur 1st statement, but disagree with the 2nd (feature) comment.

There are two possibilities:-

A. Maybe the LOS-Wiki is talking about version upgrade [13.x --> 14.1] in the way you meant, but missed to mention the "Factory-Reset" step, possibly implying it ( I am not sure).

Otherwise the only explanation is:

B. They mean "updating' [nightly --> nightly] by the term "upgrading" (only terminology confusion).

Anyway it cannot be a special feature to upgrade without factory reset, as you mentioned above.

Because the only difference between a dirty-flash & a clean-flash in operational sequence, is the absence of factory-wipe in former.

Also there is no confusion in the following statement:-

a) We use clean-flash for [13.x --> 14.1], or even a fresh install from stock firmware.

b) We use dirty-flash for [14.1 nightly --> New.nightly].

irrespective of what you call them a, b : upgrading or updating.

Comeon, Why don't other experts here comment on this confusion?

Please clarify or clear this.
[LineageOS Questions & Answers] kurtn:
Maybe the other experts don't whant to disturb, becaus they see we are making progress.

and let me add: Best method in my opinion for this is built in OTA feature.

Rest of the discussion is not so importand nowadays, because there are not many people upgrading LOS 13 to LOS 14. From the old days there are many reports of people sucessfully upgrading CM 13 to LOS 14 with a so called "experimental migration build". They did no factory reset and kept their data.
[LineageOS Questions & Answers] bhishmar:
Need to re-install latest-Gapps on Lineage-OS nightly update ?

All the above discussion started with my question, in the post #42 above in this page/thread [posts: #40 - #47].

i.e whether latest-Gapps need to be re-flashed, while updating an existing LOS-14.1 [Nightly --> New.Nightly] by dirty-flashing?

Now after this long winded discussion, it is fair to conclude that the official Lineage-OS-Wiki site on "Upgrading LineageOS", is indeed talking about "Updating an existing LOS-14.1 [Nightly --> New.Nightly], since the operations listed in the site is a dirty-flash (No Factory-Wipe).

(Leaving aside the confusion in terminology "Updating" vs "Upgrading").

So the official site is recommending a mandatory update (re-flash) of latest Gapps, after dirty-flashing a New.Nightly rom.zip.

https://wiki.lineageos.org/upgrading.html

This contradicts the recommendations I have seen in many posts in these forums, which said either don't do it, or not needed (Gapps re-flashing).

Obviously it may be a recent change in the official position, I don't know since I am a recent entry in this field.

Just pointing it out, so that others can throw more light into it.
[LineageOS Questions & Answers] kurtn:
I give up. [MENTION=5126823]bhishmar[/MENTION] flash your Gapps weekly. Everyone else: use built-in OTA for updates.
[LineageOS Questions & Answers] cicuye:
I really admire the LineageOS system and the regular updates, the quality of your work shows in your product. I had the issue with the update process. I would download it to my phone and could never locate it in the internal or external memory, so I'd simply pull my sd card and plug it into my laptop after I had downloaded the update to my computer. I'm using this as a daily on my S3 and would use it with my S4 as everything seems to work except the phone. It seems like it works but the screen will go dark after the call is placed. I can hear the phone but there's no screen or keyboard if you have to enter prompts for voice mail or business calls. So far this has just happened with my S4, the S3 is fine, quite nice in fact. Can someone enlighten me with some input concerning this issue?
[LineageOS Questions & Answers] kurtn:
[MENTION=7475590]cicuye[/MENTION] which problem do you have with update? Don't you see a button for installation after download?

The dark screen could be a defect proximity sensor. You can see the sensor signal with apps like satstat.
[LineageOS Questions & Answers] bhishmar:
Screen Blanking problems in LOS-14.1, during incoming/ougoing calls!

I also faced the very same problem, with my Moto G3 2015 (XT1550: osprey), when I clean flashed LOS-14.1 (08.06.2017), after a factory-wipe from Lolipop-5.1.1.

Screen goes blank for both incoming & outgoing calls. It stays blank till the call is terminated (for incoming). For outgoing calls u have no control over phone, so screen remains blanked till u force power-off/reboot the phone, or after a very long time. Real frustrating.

Also for me it happened while playing voice messages from WhatsApp. But problem was not always there, random.

When I rebooted the phone, the problem went away for some time, then reappeared. Again random.

Searching XDA & other sites I found out that some others also faced this problem. After a detailed research, my conclusion is that this has something to do with Proximity sensor issue or calibration. Not sensor-hardware since before LOS-14.1, I have not faced the problem.

Some suggested the problem is due to accumulated dirt/dust near the proximity sensor, coupled with some weird sensor calibration issues with possibly LOS/Cynogenmod-OS.

This was confirmed when I installed an app "SensorSense" from Playstore, which reports the proximity sensor value in cm.

For all other good working phones (mine & friends), I get a changing value (0 cm/ 5 cm) OR (3 cm /100cm), when I bring my fingers close to proximity sensor, & away. Values differ for diff phones.

But for my problematic MotoG3 alone, Sensor Sense always reports (0 cm),

irrespective of finger near or far, as if proximity sensor is always triggered.

Some solutions suggested were to clean proximity sensor surroundings (front top headphone-grill), and blow air at low pressure, to throw away dirt.

I was using the phone with an headset/handsfree to escape from this problem. (Screen does not blank with headset)

My problem went away, after I dirty-flashed a new nightly recently. But I am not sure that is the reason.

Since I did some other things also like:-

a. Cleared Dalvik/cache, Cache using TWRP-recovery.

b. Physically cleaned the phone, as part of fixing a new Tempered Glass over Screen.

c. Updated to latest LOS-14.1 nightly.(only recently)

d. Also not sure the problem has completely gone, since earlier also problem was random.

But One thing I noted after above:

"Sensor Sense" app started reporting varying values correctly (0 cm/ 3 cm/ 100cm) in the MotoG3 depending on where your finger was near/far from prox-sensor.

You give ur feedback after trying some or all of above, as suits you.

Some useful links, which helped me:-

https://www.reddit.com/r/LineageOS/comments/5xvvd6/black_screen_during_phone_calls_proximity_sensor/

https://xdaforums.com/showthread.php?t=2569141

https://xdaforums.com/showpost.php?p=71084707&postcount=3040

https://quickfever.com/fixing-proximity-sensor-issues
[LineageOS Questions & Answers] cicuye:
Wie gehts?

Thanks for responding. Yes, of course I see the button, I push it, get the alert box (about compatible recoveries, mine is Twerp), then it goes into my recovery and I open the install button, go through the internal and external memories. Et voila! No update download to be found under any, and I do mean any, file header. I reboot> go to settings> about phone> and all downloaded update(s) that haven't been installed are still listed ready for install with the current OS, with its corresponding nightly date, that the unit is running.

So, I just download it to my computer, plug in my SD card and move it there. Then I eject the SD card, put it back into the unit, boot to recovery, locate the update on the external memory and install. It's not that much trouble.
[LineageOS Questions & Answers] kurtn:
This sounds like a massive malfunction. When my moto E goes into recovery I can't open any button. There is a recovery script running for flashing and rebooting.

Do you have latest twrp?

Did you try a clean install of an older official nightly without gapps - then updating?

Have other users reported the same malfunction in your phone's lineage subforum?
[LineageOS Questions & Answers] grega888:
Looking back to the posts in this thread #12-20, I saw the problem of not being able to update via TWRP.

I'm currently on 14.1 20170220-Okeys-bacon on my OnePlus One

I've tried downloading the nightly zips from "lineage-14.1-20170508-nightly-bacon-signed.zip" thru to "lineage-14.1-20170619-nightly-bacon-signed.zip" and I get an error 7 when trying to install via TWRP.

There have to be a lot of stability and security patches I'm missing out on.

Any recommendations on another path to investigate?
[LineageOS Questions & Answers] IronRoo:
normally error 7 means you are trying to flash rom from another model, but with her first official Linage builds when coming from unofficial (I assume that's what okeys is) it means you need to flash the special "migration build". You might have to ask someone if they have it. (or there is a "migration tool" mentioned on github that I downloaded and flashed which did the job on my Samsung, don't know if it works on OnePlus though)

edit: here is link, it was on reddit not github

https://www.reddit.com/r/LineageOS/comments/65gqqg/repopick_function_errors_during_migration_build/