Develop Bugs

Lenovo IdeaPad A3000-H update (A422_013_025_140624_WW_CALL_FUSE)

Hi, today I've received an OTA update for my IdeaPad A3000-H (3G+WiFi, 16GB).
Old version: A3000_A422_011_022_140127_WW_CALL_FUSE
New OTA version: A3000_A422_013_025_140624_WW_CALL_FUSE
For now, the only thing I noticed was the different boot animation.
I have attached the image of the updated version (The language is set to Italian).
Download old version (140127) from here:
https:*//copy.com/qCjNzpBfyFrRB4hp
and Flash Tool (ver. 3.1336.0.198) from here
https:*//copy.com/fmqX4YR9FphdBAQS
Source: http:*//lenovo-forums.ru/topic/6218-rom-a3000-a422-011-022-140127-ww-call-fuse/
NOTE: remove * from links!

Hi there,
I received the same update today, but after downloading and rebooting, nothing happened, the update simply not installed!
After some useless retries, I used the CWM to install the archive from the folder sdcard0/googleota/ and it did work, for no clear reasons..
The difference so far I notice is only the boot logo ? but I believe there should be other benefits
Sent from my Lenovo A3000-H using XDA Premium 4 mobile app

faissl said:
Hi there,
I received the same update today, but after downloading and rebooting, nothing happened, the update simply not installed!
After some useless retries, I used the CWM to install the archive from the folder sdcard0/googleota/ and it did work, for no clear reasons..
The difference so far I notice is only the boot logo ? but I believe there should be other benefits
Sent from my Lenovo A3000-H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, its very strange... but its important that you were able to install it!
However, my device isn't rooted and maybe, in your case, CWM has blocked update... (this happened to me on a rooted smartphone!)
With this OTA update, my A3000 seems more stable, with fewer reboots than before (old version: once a day; new version: once a week!)

Plz link of update
Where is the link for the new update

Braveheart850 said:
Where is the link for the new update
Click to expand...
Click to collapse
This new update is only OTA!
To get this OTA update, you must have the "old" version, dated 2014-01-27!
Then search new version, from Android settings (see attached image)!
Here is the link! (remove * )
https:*//copy.com/qCjNzpBfyFrRB4hp

brunix86 said:
Hi, its very strange... but its important that you were able to install it!
However, my device isn't rooted and maybe, in your case, CWM has blocked update... (this happened to me on a rooted smartphone!)
With this OTA update, my A3000 seems more stable, with fewer reboots than before (old version: once a day; new version: once a week!)
Click to expand...
Click to collapse
Strange, this is never happened with my Sony Xperia tipo.. Anyway, you are missing a lot with your mobile not being rooted ?
I noticed the battery life got somewhat longer, there still no way to move apps to the sdcard.
And the Android version still the same ???? #I_want_Kitkat (Heh, don't be silly.. The update was just 3.5Mb or so)
I forget to tell you that it you use my method of CWM upgrade and tried to check for other system updates you will be greeted with the same update install screen! Don't panic, Your system has already been updated.
Fix: just remove/rename the Googleota folder and retry update check, You should be refreshed with calming screen that tells you how you already have the latest version..
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app

faissl said:
Strange, this is never happened with my Sony Xperia tipo.. Anyway, you are missing a lot with your mobile not being rooted ?
I noticed the battery life got somewhat longer, there still no way to move apps to the sdcard.
And the Android version still the same ???? #I_want_Kitkat (Heh, don't be silly.. The update was just 3.5Mb or so)
I forget to tell you that it you use my method of CWM upgrade and tried to check for other system updates you will be greeted with the same update install screen! Don't panic, Your system has already been updated.
Fix: just remove/rename the Googleota folder and retry update check, You should be refreshed with calming screen that tells you how you already have the latest version..
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app
Click to expand...
Click to collapse
You're right! On smartphone I have TWRP, not CWM!
However, for now, I'm fine with the stock firmware (In the future I will evaluate to flash an unofficial ROM)
The battery works two days (over 24 hours, tablet is turned off at night) of normal use (wifi on, 3g on, bluetooth on, several phone calls every day, several app with push notifications).
In addition, 16 GB are so many, while having numerous apps installed (more than smartphone).
In the MicroSD card (the other 16 GB) I'll put my music, pictures and videos made with the camera!
I think it's unlikely that we'll see KitKat on A3000... All I want is find a solution to the problem of BT headset that does not detect anything when I use voice commands or voice recorder!!

The stock rom is just too good to be replaced ? the only feature I really miss is CM theme chooser because I don't like the default white on black theme of the settings' screens.. Sigh, you can't have everything, this device is by far the best I ever had.
Sent from my Lenovo IdeaPad A3000-H using XDA mobile app

update
brunix86 said:
Hi, today I've received an OTA update for my IdeaPad A3000-H (3G+WiFi, 16GB).
Old version: A3000_A422_011_022_140127_WW_CALL_FUSE
New OTA version: A3000_A422_013_025_140624_WW_CALL_FUSE
For now, the only thing I noticed was the different boot animation.
I have attached the image of the updated version (The language is set to Italian).
Download old version (140127) from here:
https:*//copy.com/qCjNzpBfyFrRB4hp
and Flash Tool (ver. 3.1336.0.198) from here
https:*//copy.com/fmqX4YR9FphdBAQS
Source: http:*//lenovo-forums.ru/topic/6218-rom-a3000-a422-011-022-140127-ww-call-fuse/
NOTE: remove * from links!
Click to expand...
Click to collapse
Even though there seems to be no new feature, I noticed that my tablet seems more responsive to touch and the boot animation and boot time have changed. The boot time has considerably come down. Thank you for providing the link and info

[Q] Very low screen bright after reboot

Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot

reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411

muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again

Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help

reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment

You must install the UKM scripts from recovery. Read the op from the red kernel thread...

edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...

muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium

ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.

muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium

ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.

muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium

ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055

x9076 with R63419 LCD working recoveries

TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...

tonyjih said:
TWRP 2.7.1.0 , stock revovery (v1.2), unlocked recovery (original by wmjan)
hope there will be some custom roms for this LCD soon...
Click to expand...
Click to collapse
Could you please explain the difference between these 3 recoveries?

GaroRobe said:
Could you please explain the difference between these 3 recoveries?
Click to expand...
Click to collapse
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/

tonyjih said:
they both for newer model of find7 comes with a newer screen
You'll need these recoveries ONLY if you own a R63419+ LCD model
reference:
http://www.oppoforums.com/threads/r63419-cannot-install-3rd-party-rec-rom.24924/
Click to expand...
Click to collapse
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model
2. My phone is x9076 int'l, manufactured in december 2014
3. I have the "bleached screen" bug on 3rd party ROMs and namelessTWRPs
4. The twrp-x9076 takes only half of a screen area (it does work though, but still identifies my phone as find7a which is incorrect)
5. you still didn't describe the difference between the other two

I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).

GaroRobe said:
I tried flashing CM12 nightly with twrp-x9076 (had to remove assert from update script). No good - same as before, bleached screen and such. So this particular recovery seems to be useless for anything other than backup/restore and rooting (which is awesome, but still not what I'd like to have access to).
Click to expand...
Click to collapse
you have to wait CM update their drivers , otherwise it just .... don't work.

I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!

sof006 said:
I also have an issue with this and have installed this recovery and its fixed the problem. Now we wait for custom ROM developers to catch on.... I'm going to keep myself glued to cyanogen to see if they change anything!
Click to expand...
Click to collapse
Same here. Other than the official beta rom there seems to be nothing available for us. I am seriously considering returning the Oppo since I can't even get hold of 1.2.8i (only stable version which ships with the phone).

So sad... I really want to use 5.0 on my OPPO Find 7. I've reached out to Cyanogen but had no replies, reached out to other ROM developers only to either be ignored or have my question washed away by a sea of people complaining that they can't get a game to work on their phone.

Just found out that cyanogen is working on the new oppo find 7 with new lcd panel issue. So anyone disappointed they'll have it sorted soon hopefully!

Does the offical TWRP and CM support this find7 with new LCD????

Any updates on this? I have managed to get the official AOSP ROM working but nothing else unfortunately.

Double the question. Lack of working TWRP is just fatal to any tinkering.

GaroRobe said:
1. The "*##*37847#" method doesn't work for me since I'm on 1.2.8i , thus cannot verify the screen model [...]
Click to expand...
Click to collapse
Test with adb (requires root):
Code:
adb devices
adb shell
su
cat /proc/devinfo/lcd
the answer for me (X9006 with COS 2.0.8i) is
Code:
Device version: R63417
Device manufacture: JDI
close the shell
Code:
exit
exit

Maybe if the ROM is compiled from source, the extra driver could be included? I am noob to this so if someone experienced could take a look that'd be great!

Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks

betoNL said:
Just found this thread and didn't read much.
I am on unified storage (stock 2.0.8I). Are these recoveries compatible (unified partition)?
And yes, I have the new LCD screen...
Thanks
Click to expand...
Click to collapse
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!

djzic said:
Yes they are compatible with LVM, using it with the official AOSP rom since it's been the only way for me to get Lollipop so far, will probably test out the new beta ColorOS 2.1 Lollipop ROM as well.
EDIT: Actually just noticed some issues with it, can't mount internal_sd or data partitions and thus can't back up, avoid. I thought I'd backed up on LVM but clearly not.
Speaking of ROMs... I've taken the screen driver of the original Oppo kernel from the github and added it to the cm12.1 kernel (ie overwritten the cm12 driver with the Oppo one), I'm now compiling it from source and will report back if this works. If so, this will mean working Cyanogenmod for the new panel!
Click to expand...
Click to collapse
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.

betoNL said:
Ok thanks,
I am on stock 2.0.8i with unified storage and gonna have a look on some CM / AOSP based roms soon ...
.
Click to expand...
Click to collapse
Edit I did a backup of the stock recovery (2.0.8i) with Flashify app for instance so I think I am going to try this out anyway ....

Twrp cant seen to find my internal storage. Im using unified storage setting on colorOS 2.1

[ROM][LineageOS 13][Marshmallow][6.0.1][MOB31K][Mar.18.2017][XT907][JBBL][Share]

Unofficial LineageOS 13 (Android Marshmallow) for JBBL dated March 18, 2017 from the 4PDA forums courtesy of developer ilichva!
Again, this is only for JBBL. Flash at your own risk and please do a nandroid backup prior to doing so!
All credits and thanks go to the original developer ilichva!
____________________________________________
Latest Build - LineageOS 13:
lineage-13.0-20170318-port-ilichva-xt907_jbbl.zip (405.4 MB)
Mega
SolidFiles
PCloud
MD5 :: 63FB23666399844E5BB7A8D9C347374D
____________________________________________
Prior Build - CM13:
cm-13.0-20161205-ilichva-xt907_jbb.zip (411.9 MB)
Original Link
Mega
SolidFiles
PCloud
MD5 :: 3c786a57929d024010a0fce36287ea7d
____________________________________________
NOTE: If you are on KitKat Bootloader (KKBL), you will need to revert to the JellyBean Bootloader (JBBL) before you can flash this ROM. Instructions on how to do so may be found here and here and here
____________________________________________
Latest TWRP 3.0.2 recovery by ilichva may be found/downloaded here

Updated to 03.25.2016 build

Hallo Rahimali
Thanks for the share. I have tried this and apparently works ok. I'm unable to get WiFi working. Tried different gapps but there are force close issues. Any recommended gapps versions available?

Opengapps usually does the job. Flashing gapps with marshmallow is different than with prior android versions. With MM you have to flash gapps immediately after you flash the ROM (before booting up the ROM for the first time). Try and see if that resolves your FC issues

Updated to April 02, 2016 build!

I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?

Updated to April 05, 2016 build!
ultrasoniic said:
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Click to expand...
Click to collapse
Sorry no idea. Nobody is complaining in the 4pda forums about any WiFi issues. Did you do a clean flash? Maybe the developer, @ilichva can help?

bootloader and recovery
My XT907 is showing that my bootloader is "0x109B" and I am unsure what version of TWRP supports 6.0.1 (currently running 2.8.6.0)
Can anyone verify their settings and let me know?
I am running CM12.1 currently, so I should be able to dirty flash correct?
Thanks guys!

KKBL?
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?

crzypcdude said:
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
Click to expand...
Click to collapse
Marshmallow not yet available on KKBL

rahimali said:
Marshmallow not yet available on KKBL
Click to expand...
Click to collapse
Are there any significant reasons to stay on the KitKat bootloader? Otherwise I'll just downgrade now that I'm rooted with an unlocked bootloader.

One of the most compelling reasons to stick with the KKBL would be the availability of the 3.4x kernel as opposed to the 3.0x kernel on the JBBL but feel free make your own decision. I was on the JBBL (by choice) for a considerable length of time without any apparent side effects...

Would you mind adding dates to post #1?

Any updatefor this rom?

crzypcdude said:
Would you mind adding dates to post #1?
Click to expand...
Click to collapse
The dates are already present in post #1 as well as in the filenames.
dedik46 said:
Any updatefor this rom?
Click to expand...
Click to collapse
Updated!

Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?

crzypcdude said:
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
Click to expand...
Click to collapse
That is correct.

Confirmed Working!
Can confirm this works, flashed the recovery included in the 4pda post, used it to flash the rom, gapps, and supersu. Initially booted up in Russian, but after waiting for 30 seconds or so, switched to English on its own. Setup was flawless after that, no issues to report as of now. Anyone that needs help installing the rom or downgrading from kitkat to jellybean just message me.

I thought I was the only one that ended up with default language in Russian... All the previous builds defaulted to English on install... Also when I downloaded the latest update it downloaded on my phone as a .bin not a .zip I checked the file size and contents vs what is online (after changing the extension to .zip) and everything seemed to be Ok so I installed and been up and running on latest version for 24 hours....
Had a few FC's in the beginning while changing the language to English (I have a feeling that some of my already installed apk's caused the issue) . I did do a test run before restoring my stuff and didn't have any issues during initial setup and the phone auto corrected language based off sim during initial setup.
Haven't gotten a chance to fully test this build, but I know that the issue that I was having with the native tethering soft rebooting the phone every couple of hours when active is gone! After a few more days of messing with it I will post any other issues that I come across
Sent from my Moto Razr M on cm13 4-16-16 using XDA Free mobile app

Any clue about why I'm getting error 7 while finishing the last steps of the ROM flashing procedure?

Lineage downloader can't connect

Dear reader,
since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version. So I gave the app the instruction to look for updates, and it gave me the following notification.
Can't connect to download site. Please retry later.
When actually
You device is supported by the lineageOS team, but there are no versions that support this type of publication: Nightly. (this is translated from Dutch, so actual English sentece might be different).
Switching to Snapshot instead of Nightly in the Settings didn't help.
Then when searching again for updates it gave me the message:
No source file
Request for file: lineage-14.1-20181124-nightly-herolte-signed.zip To reconstruct the last update, the zip of the app should actually be installed. Do you want to select this file manually from storage, or download the last full zip-version?
When I press: download full zip-file it gives the following:
Error during implementation. Try to refresh.
When I click on select file (from storage), and select lineage-14.1-20180927-nightly-herolte-signed.zip, it gives me the message:
You should select the right source file. But I don't have that one on my storage; it's froma different date.
Can anyone help me please?
Kind regards,
Chris

Joheee said:
Dear reader,
since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version. So I gave the app the instruction to look for updates, and it gave me the following notification.
Can't connect to download site. Please retry later.
When actually
You device is supported by the lineageOS team, but there are no versions that support this type of publication: Nightly. (this is translated from Dutch, so actual English sentece might be different).
Switching to Snapshot instead of Nightly in the Settings didn't help.
Then when searching again for updates it gave me the message:
No source file
Request for file: lineage-14.1-20181124-nightly-herolte-signed.zip To reconstruct the last update, the zip of the app should actually be installed. Do you want to select this file manually from storage, or download the last full zip-version?
When I press: download full zip-file it gives the following:
Error during implementation. Try to refresh.
When I click on select file (from storage), and select lineage-14.1-20180927-nightly-herolte-signed.zip, it gives me the message:
You should select the right source file. But I don't have that one on my storage; it's froma different date.
Can anyone help me please?
Kind regards,
Chris
Click to expand...
Click to collapse
S7 is no longer officially supported by lineageOS. You can search here in XDA for unofficial ROMs.
I have no big hope that a new ROM will really solve your battery issue. Most of the the success stories are a result of a clean ROM installation.

Joheee said:
Dear reader, since a couple of days my device (samsung S7: SM-G930F) is running low on battery really quick. So I thought; it has been a while since my device asked me to update the new Lineage version.........
Click to expand...
Click to collapse
In addition to the outstanding information that @kurtn had provided...
There's no Official LineageOS Updater Apps on the Play Store.
The reason is that they have an implemented LineageOS Updater built into the Firmware and has no need to provide any such app separately from the firmware. That would just be counterproductive to the built in Updater.
The LineageOS Updater App(s) on the Play Store is via a 3rd party developer. I'm not stating that any/all of them are either good or bad but, individuals need to know that their Unofficial and is in no way supported by the Official Lineage Team Maintainers.
Just a few (so to speak) words of advice to keep in mind. I remember asking about them (quite a while ago) and those were the types of words/thoughts by @invisiblek and @haggertk (whose a part the Official Lineage Lead Maintainers).
No lectures here... Just some friendly information for you My Friend!
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX1 Forum App on my Sanyo Juno device.

Hi Kurt and Ibuprophen, thanks for your answers!
Now I have finally holiday and time to actually fix things it's time to continue this
So current situation;
Phone running out of battery within half a day without frequent using, apps crashing > update definitely required.
Phone model: Samsung S7 SM-930F
LineageOS version: 14.1-20181124-NIGHTLY-herolte (so last update is over a year old)
Android version 7.1.2
Options:
1. Just reset to factory settings? Most easy option, but I think it will have negative influence when I use the phone for another year?
2. I found this unoficcial ROM https://forum.xda-developers.com/galaxy-s7/development/beta-lineageos-16-0-s7-herolte-t3842465, however, it doesn't include instructions and it is very technical and it speaks of Android 9 as base, which I don't have; just 7.1.2. Would that be a problem?
3. Update to 15.1 instead if that is easier?
So what would be your advice? Please bear in mind that I am a technical noob and can only follow instructions that are extremely clear & correct
Until now I haven't found instructions I felt comfortable with unfortunately.
By the way my laptop has Linux Mint Cinnamon 19.2

Joheee said:
Hi Kurt and Ibuprophen, thanks for your answers!
Now I have finally holiday and time to actually fix things it's time to continue this
So current situation;
Phone running out of battery within half a day without frequent using, apps crashing > update definitely required.
Phone model: Samsung S7 SM-930F
LineageOS version: 14.1-20181124-NIGHTLY-herolte (so last update is over a year old)
Android version 7.1.2
Options:
1. Just reset to factory settings? Most easy option, but I think it will have negative influence when I use the phone for another year?
2. I found this unoficcial ROM https://forum.xda-developers.com/galaxy-s7/development/beta-lineageos-16-0-s7-herolte-t3842465, however, it doesn't include instructions and it is very technical and it speaks of Android 9 as base, which I don't have; just 7.1.2. Would that be a problem?
3. Update to 15.1 instead if that is easier?
So what would be your advice? Please bear in mind that I am a technical noob and can only follow instructions that are extremely clear & correct
Until now I haven't found instructions I felt comfortable with unfortunately.
By the way my laptop has Linux Mint Cinnamon 19.2
Click to expand...
Click to collapse
Oh, looks like ivan does a good job. I think it is a good idea to install his rom.
But be aware: whatever it is, that eats your battery, it can come back.
Edit: be aware: from the threads it looks like 15.1 and 16.0 are not SELinux enforcing. So the gain of security is not as high as one would expect from security patch level. So you can try a factory reset of 14.1 as well.

Do you think there is an easy, technical-illiterates-friendly way to install this version of ivan? I am not that keen to have the highest possible security.
When I am emptying the phone anyway, it seems best to me to have the most recent version (if it doesn't matter that I have android 7.1 and not android 9).

Joheee said:
Do you think there is an easy, technical-illiterates-friendly way to install this version of ivan? I am not that keen to have the highest possible security.
When I am emptying the phone anyway, it seems best to me to have the most recent version (if it doesn't matter that I have android 7.1 and not android 9).
Click to expand...
Click to collapse
Download the zip files for rom (and GApps if needed) boot into twrp wipe system, data and caches (not internal: there are your pictures and downliads etc)
Install: navigate to downloads folder select the zip file and hipe it works.
If not: ask in the thread you linked.

How to use lineage downloader app
Hello sir,
I have redmi note 4 (mido) device which is officially supported by lineage team and I heard about lineage downloader app and (Delta Update) so please guide me how to use this app.
My latest built is 2020-01-15 (pie).
Thanks.
Waiting....

[email protected] said:
Hello sir,
I have redmi note 4 (mido) device which is officially supported by lineage team and I heard about lineage downloader app and (Delta Update) so please guide me how to use this app.
My latest built is 2020-01-15 (pie).
Thanks.
Waiting....
Click to expand...
Click to collapse
Don't use that app. Use the procedures described in wiki.lineageOS.org