Related
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?
Hi,
I have TWRP 3.1.1 installed on my LG G4 (h815). My current OS is Lineage, but I always have a backup of the stock rom on my sd card, so that I can switch between Stock Rom and Lineage whenever I want.
When I have the stock rom installed and boot into TWRP, the date and time is correct.
But when I have LineageOS installed and boot into TWRP, the time is wrong and I'm somewhen in 2015.
My backups include the partitions: System, Data, Boot
So I restored them separately to find out, which partition "holds the date and time". It is the Data partition. When I have Lineage installed and restore my Data partition from the Stock Rom, my time in TWRP is correct again. So for some reason, the time of the Data partition of LineageOS is wrong. I checked the time in Lineage, but there it is correct set. It is only wrong in TWRP.
Any idea how I can correct the time on my Lineage Data partition?
Bleuzen said:
Hi, I have TWRP 3.1.1 installed on my LG G4 (h815). My current OS is Lineage, but I always have a backup of the stock rom on my sd card, so that I can switch between Stock Rom and Lineage whenever I want...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3442424
https://forum.xda-developers.com/showthread.php?t=3166384
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
I don't have this device but, your best bet is to post this question within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3442424
https://forum.xda-developers.com/showthread.php?t=3166384
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I don't have the problem anymore. I updated LineageOS from the latest official build to the latest unofficial testing build for BUGBASH-498.
As a side effect, this build also fixed my time and date problem in TWRP. So it was a bug of LineageOS, which is fixed now.
Anyway, thanks for you reply
I've noticed the same issue with the time in TWRP on my LG G4.
How interesting that this was fixed for you by the same code change that hopefully when merged will also allow nightly updates to be released again for the h811 I have.
Exabyter said:
I've noticed the same issue with the time in TWRP on my LG G4.
How interesting that this was fixed for you by the same code change that hopefully when merged will also allow nightly updates to be released again for the h811 I have.
Click to expand...
Click to collapse
We won't get new official nightly builds until this bug got fixed:
https://jira.lineageos.org/browse/BUGBASH-498
Until than, you can use my unofficial build, if you want:
https://forum.xda-developers.com/lineage/general/temporary-unofficial-builds-h815-t3721909
I have OP3T with latest official TWRP. Date and time is incorrect but i can change on twrp on the terminal however after reboot it will jump back to the incorrect one. Any idea to fix it?
I was succesfully pulling out the build.prop but when i try to edit on my PC just can not find the date and time line...
So I had rooted my Tab S back in 2016 or so (if you check the forums here you'll see my posts for this...). Have had that working for a while now. It tripped the Knox (I didn't personally care about this) except now I want to install a couple streaming apps on the tablet and the OS is too old to handle it
I had loaded TWRP onto the Tab S and rooted it with Lollipop stock ROM and loaded it with SuperSU. It has worked like a charm up till now, issues with Link2SD notwithstanding (I have ZERO intentions of going back to that app).
My question is: what do I need to do to install the newest possible version of Android that the tablet can take? I know it's an older tablet now but I still use it for reading and other stuff, and I'd like to keep it alive a bit longer by installing a new Android OS and ROM on it.
(aside: I did remove a bunch of stuff once I rooted it, so I am not sure how much this may interfere with any attempt to update it to a newer version of Android)
(aside #2: I never updated SuperSU through the app store as I was afraid it would break the root process, so I left that app alone and eventually it stopped showing up in my update list on google play. I'd have to check the tablet to see what version of it I have installed at present)
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
cbb77 said:
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
Click to expand...
Click to collapse
Hey thanks for your reply!
Do you need to update the android version to get Lineage OS installed?
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Hi again,
Sorry could you point me in the direction of said thread?
cbb77 said:
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Click to expand...
Click to collapse
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
bsquared938 said:
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
Click to expand...
Click to collapse
Yes, that is the correct thread.
cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
Perfect. Will also update this table to give it a further lease on life .
Thanks man!
cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
@cbb77
Cannot find the Lineage OS ROM image, I think it may have been removed from their site given the age.
Do you have a working download link for this?
Edit: please ignore post, I found it as soon as I posted this -.-
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Trung Gs said:
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Click to expand...
Click to collapse
I assume I have to load the marshmallow bootloader before I do anything?
bsquared938 said:
I assume I have to load the marshmallow bootloader before I do anything?
Click to expand...
Click to collapse
Personally I like the Resurrection Remix rom. https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243
Just do the standard stuff. You've got TWRP installed, so you're most of the way there. Back up whatever you want to back up, and then:
1. Wipe System, Data, Cache, and Dalvik Cache.
2. Install OS.
3. Install Magisk (if you want to use Magisk for your rooting needs. It seems to be the popular root tool now. It's pretty boss.)
4. Reboot into system, then back into recovery, and:
5. Install GApps or whatever. I like NanoDroid myself. It's the alternative to GAPPS. There are a few odd programs that just plain won't work with it yet, but the official Google apps have an annoying habit of wasting processing power on pointless background nonsense, so I prefer the alternative. Also there's an Xposed module that improves compatibility. https://nanolx.org/nanolx/nanodroid
Hmm I'll take a look at this other ROM
Currently, I have a rooted stock ROM (SuperSU ad root manager), and interested in moving to a custom ROM that is well supported
My only 2 concerns before starting are:
1) Do I need to update SuperSu
2) Do I need to update the bootloader before doing anything else (even the ROM that you suggested @FailSafeNow ? )
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
bsquared938 said:
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
Click to expand...
Click to collapse
I know this is a somewhat old thread. I have a T800 myself and am looking for a ROM. Want to try Lineage OS 14.1 like you have tried. Was curious as to whether you still have it and if you still liked it? If so, what version are you running now and how is your battery life compared to stock? Thanks so much! :good:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using pico/nano gapps.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Full wipe all
4. Flash firmware and gapps
Work
almost all
Known Issues
- camera
- screenshots
- missed icons in trebuchet tauncher (install nova or microsoft launcher and other)
Links
LineageOS Builds
1. 20200821: init build: https://drive.google.com/file/d/19-rPOcmlYIhcoZleG4MKRROk9TXytEOe/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official version from: https://twrp.me/samsung/samsunggalaxynotepro122exynoswifi.html
Sources
Sources: https://github.com/Lineageos
Device: https://github.com/Valera1978/android_device_samsung_v1awifi
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos5420
Vendor: https://github.com/Valera1978/android_vendor_samsung_v1awifi
Thanks
Thanks to LineageOS team
Thanks to exynos5420 team for the right kernel
Thx @Valera1978 that's great news.
Gonna test today.
Edit 6h later first impressions:
Coming from Lineage 14.1 Vanilla with TWRP 3.4.0-0.
Backed up everything, full wipe plus data format.
Installing purely the ROM with TWRP 3.4.0 led to "Error 7" 3.3.1 did the trick.
Made a reboot to check if it starts.
Noticed screen failures in form of small black bars/stripes which vanished after a few seconds when I let the screen settle.
(Appearing very often even now after full installation of everything I need.)
Rebooted to TWRP and installed BiTGapps (prefer them to opengapps as they are even smaller than pico) and Magisk.
After each flash wiped cache/dalvik of course.
Installed Nova prime (dark mode) and all my other apps.
Camera doesn't work with Lineage App (as said) but does with opencamera from f-droid.
Screenshots neither but using Quickboot is a workaround when activated in its settings.
When writing text and correcting failures the magnifier shows only a white field with now text in it even when dark mode is off.
Great work @Valera1978 will carry on testing.
Edit 18h later:
Firefox seems to have problems with it, doesn't often even open its add-on page or urls.
Lightning browser has no probs.
Only one sudden reboot until now.
Edit 24h later:
Tried to upload a pic with the screen problems but didn't work.
Mostly occuring when switching from portrait to landscape (reproducible).
Because of the Firefox problems I've tried the 79 version but starting it resulted directly in a reboot (reproducible).
I'm surprised there aren't more responses
Can confirm TWRP 3.3.1 is the latest recovery to work. Doesn't seem to work with 3.1.1
Can't change wallpaper. Not sure why. I have to go to live wallpaper to get the default one back
Ok Google needs to be installed manually
I get security flags from SELinux and Public trust certificates. Probably because the release is so early
Overall it's not bad for a Pre-Alpha release.
First of all: an awesome thank you to Valera1978 since I was expecting a newer version than 14.1 a long time
Have the same issue with the wallpaper change and some flickering in the display. Installed nova prime too but can`t close all apps in task manager only each manually single (wipe up)
I am eager for the next version and improvements :fingers-crossed: and willing to give further feedback.
THX a lot for your passion
the current version is rather a technical build for testing (public, the most stable, there were already about 40-50 internal builds for fixing bugs and checking various things).
In any way - lineage 17.1 coming soon (later today), release build done, on tests right now. And I like it much more, then technical 16.0 build.
I tried 16 and I like it. Looking forward to 17.1. Thanks for saving the P900 from an early grave you are and have been the best ?
i will try this process for the first time. Is there a video tutorial? thank you.
kayamece said:
i will try this process for the first time. Is there a video tutorial? thank you.
Click to expand...
Click to collapse
This ROM will probably not be in development any further as the brilliant dev @Valera1978 is already working on a 17.1.
About a video I don't know. Searching in YouTube might help finding out
Here is a very good description which I followed from @thompatry who's ROM is very stable, has a working camera (skype) and gets regularly updated.
[ROM][7.1.x|SM-P900| Unofficial LineageOS 14.1 (v1awifi)
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.* (Nougat), which is designed to increase performance and reliability over stock Android for your device. #include /* * Your...
forum.xda-developers.com
Download it to SD.
As he quoted install a TWRP first to exchange the stock recovery.
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.
bmwdroid said:
Easiest to do is use a windows PC with Odin version 3.13.
Battery fully loaded before starting.
1.Download TWRP 3.3.1 for v1awifi from twrp.me but choose the tar version and save it in Odin folder.
2.Get P900 into download mode (turn it off, then press buttons Pwr, home, vol- altogether).
Will give you a warning but continue with vol+.
3.Start Odin then connect P900 to PC and check in Odin if a field on the left turns blue (com+).
4.Uncheck "auto reboot" in Odin.
5.Flash TWRP 3.3.1 with Odin onto P900 putting the downloaded TWRP file in "AP" field in Odin.
When Odin says "Pass" all is fine.
6.Turn P900 off with pwr button but press afterwards directly home and Vol+ together as it automatically reboots.
Then you access the new recovery.
If you fail the Samsung recovery gets reborn and you have to repeat steps 2-6 again but that does no harm.
Save all what is possible with TWRP to external SD using Backup.
Then wipe everything in TWRP (except SD ), select "format data" after that.
Select install and choose the ROM from SD.
Test if system starts. Might take a while.
If you want to use Google apps, download Gapps from opengapps (choose ARM, 7.1 and pico) and save it in advance to SD.
If system starts, turn it off, restart to recovery (pwr, home, vol+) and install Gapps.
Click to expand...
Click to collapse
Hi everyone, I hope you are all safe and well.
Just a quick question, do I use the latest version of TWRP for my P900 (note pro 12.2 wi-fi). There are versions on the website which are later than the 3.3.1 version in this post. At the moment my version is 1.22, so this is really old! This was obviously installed and I did the flash to 14.1.
Like I say, at the moment, I am using LineageOS 14.1 with an old security patch level (September 19) because I cannot seem to update it. I have tried the auto update, this fails and I have also tried to manually apply but this also does not work.
I was wondering whether it was time to upgrade to version 16 or 17.
I'm not an expert on this by any means and I recall I did struggle with some error message when trying to update to I think at the time line Lineage 15.
Any comments or suggestions would be much appreciated.
@mattgod69 auto updater I don't use/like at all.
My suggestion is download TWRP 2.8.7-0 as zip and flash this with your TWRP. It is the latest zip released.
From that on it can use img files and you can update further to 3.3.1 or higher.
For me 3.4.0 was needed to flash @Valera1978 LOS17.1.
3.3.1-0 for LOS14.1 by @thompatry which's Vanilla (version 20201215) I use for here camera is working instead of being on LOS17.1.
Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.
mattgod69 said:
Thanks for the reply @bmwdroid, i was talking about the app which is version 1.2 (doh)... i have just booted into TWRP and i have version 3.3.1. So if you are using the same tablet as me, what would you upgrade to or would you leave it as is. Also, do you think i need to update the security patch level? Cheers and apologies if these are silly questions.
Click to expand...
Click to collapse
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.
bmwdroid said:
Mine is a P900 v1awifi.
I suppose that the app 1.2 refers to the TWRP app which I don't use and I've always read warnings to install it so I never did.
It is said that it sometimes causes problems when flashing.
And imo it's not needed anyhow.
If you need camera working for skype or else I recommend to flash the latest LOS14,1 mentioned above.
https://download.exynos5420.com/LineageOS-14.1-Deathly/v1awifi/
with the deathly adiutor built in
or
https://download.exynos5420.com/LineageOS-14.1-Vanilla/v1awifi/
which is a plain android system
The development of this LOS16 seems suspended as the dev is already working on LOS17.1 which I've tested, but as said has no working camera.
Therefore I can't say much about its stabilty but it worked with Bitgapps and Magisk for 4-5 hours until I switched back to LOS14.1.
If you want to test it: I had to upgrade TWRP to 3.4.0 to avoid "Error 7".
To go back to 14.1 I had to downgrade to 3.3.1 first.
Questions show that someone is willing to learn which should be appreciated.
Click to expand...
Click to collapse
Thank you for the detailed response, very helpful.
I dont really use the camera with my tablet, but i might, so its probably best to wait til 17.1 is working. The tablet is really just a browsing device i use beside my bed, its not an everyday machine.. so i am willing to try new things and play about with it.... it also does not matter if it is wiped accidentally etc.
i have to say it has been overall much better with 14.1 installed, far better than the stock OS. It is faster and more responsive.
Presumably I need new google apps etc download any new OS? If i install the latest LOS 14.1 do i also need new gapps etc? Is this OS much better than the one i have?
I do not know what Bitgapps and Magisk are?
Many thanks for all your help.... this community is great because even though i have done this a couple of times on different devices, there are long time gaps between doing it and it is still quite scary because i dont want to brick the device!
Just looked at Magisk... is it not a good idea to have this in any event? it looks like this would be earier to install later OS like LOS17.12? Is this right?
@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.
bmwdroid said:
@mattgod69 BitGapps are an even smaller Google Apps version than Opengapps pico.
I use them on Android Q, as opengapps weren't working properly at that time being.
I don't use Google TTS and always had to block it when using opengapps.
Magisk is an equivalent to SU which is no longer continued.
It's neede for all apps needing root like AFWall, DeviceInfo and many others.
If you or your tab are happy without there's no need flashing it.
It causes no probs when switching ROMs as long as it's a clean flash.
Even updating ROMs dirty works on mine.
If you already had LOS14.1 installed and google apps as well you don't need a newer gapps version when updating dirty as gapps get updated by Google itself.
When flashing cleanly I recommend a newer gapps version but you can use any old (designed for the specific android version) as well.
Only setting up might take longer as the gapps will be updated automatically as soon as they find an internet connection.
The newer version of LOS14.1 will imo only be different in patch level nothing else.
Hope I didn't overlook a question.
Click to expand...
Click to collapse
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....
mattgod69 said:
Many thanks for the message and info. i think maybe i will leave as is for a bit as the tablet is working fine at the moment.... look at this again when 17.1 is ready.....
Click to expand...
Click to collapse
But I hope you will be updating the ROM to be on the latest patch level.
bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
ok, i will update with the lastest 14.1 OS.... is there a step by step guide for this on here....?
bmwdroid said:
But I hope you will be updating the ROM to be on the latest patch level.
Click to expand...
Click to collapse
i think i am going to try 17.1... i think most issues have been sorted now?
i did have some questions before i do this which i have put in another post.....
Also, how do you do a dirty install... is this where the cache etc is not wiped?
would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?
Many thanks for your help and advice.
mattgod69 said:
.... would you update TWRP to 3.5.0. (the latest one). I assume this can be done from the program in recovery mode?...
Click to expand...
Click to collapse
Updating TWRP can be done with itself.
Working up- and downwards.
Just select "install" switch to "image" choose the file and select "recovery".
Afterwards reboot directly into the new recovery.
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Horninho10 said:
Does anyone have experience with this Official LineageOS Rom in Pixel 3a?
Official Device Info/Wiki:
https://wiki.lineageos.org/devices/sargo
Official Installation instructions:
Install LineageOS on sargo | LineageOS Wiki
wiki.lineageos.org
Official Download Link for LineageOS ROM and Lineage RECOVERY:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
Yes, it runs nice and smooth, I was recently on LOS.
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
pojr said:
The post I'm about to make is not related to anything technical, so I'm not sure if it's appropriate on this forum, but I'm going to post it anyway...
Is there any advantages lineage has over stock? Seems like it's not really worth it. Right? What do you guys think about build?
Click to expand...
Click to collapse
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
MoistPicklez said:
I personally am running stock for SafetyNet purposes at the moment. I do think it's worth checking out if you want a few more options for customization. It was a very smooth ROM, but LOS in specific is not my cup of tea.
Click to expand...
Click to collapse
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
pojr said:
That is a very good point actually. That is one thing I was never a big fan of with the stock OS, is just the lack of options you have to customize your device. Might be worth getting it, even though it's a downgrade to Android 10
Click to expand...
Click to collapse
Test it out if you're interested, but A11 ROMs are likely around the corner. I bet we'll get a build or two of something else down the road. Cheers!
I've personally had GPS issues (while using OpenGapps Pico) with the official release. Hoping A11 builds fix it.
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
I seem to have overcome my GPS woes! My installation process was the following:
Install the last Android Q factory image
Flash LOS boot, go to recovery
Factory reset
Install update > adb sideload LOS zip
Very important(?) - go back to main menu, advanced, reboot to recovery
Install update > adb sideload opengapps pico zip > yes, install anyway
Sign in to your Google account during the initial setup process
Test GPS with an app (Google Maps, Waze, OSMAnd, Pokémon Go... )
The only issue I seem to have now is that the Google Fi app doesn't seem to get that my Fi service is ESIM based, and prompts me to order a physical SIM card, but playing with the mobile service settings seems to have gotten my service set up anyway.
EDIT: After talking with Google Fi support, going to Settings > System > Reset Options > Reset Wi-Fi, mobile & Bluetooth, check erase downloaded SIMs, then trying to activate Google Fi again in the app, it worked.
In addition to the helpful tips from @Mokura3rd. My two cents: I had some gps issues as well, but didn't test it to great extent. Here's a description of my (rather weird issue):
When I first installed Lineageos (jan16 - my previous comment), Google maps and Gps status were able to find gps signal (and quicky), but strava didn't find any gps signal (it didn't even ask for permission, which I granted manually - to no avail).
Some time after the first OTA update, I checked strava again. And it worked without issue. So there might have been merged some bugfixes that fixed gps issues on recent builds.
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
pojr said:
guys, is it true you have to jump down to Android 10 in order to get the latest lineage? that doesn't make sense. Don't you have to wipe your phone in order to switch from stock to custom anyway? seems pointless to downgrade to stock 10 first. what's your guys stance on this?
Click to expand...
Click to collapse
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
MoistPicklez said:
Because lineageos 17.1 is based on Android 10, you have to revert to stock Android 10 before you install it. The same goes for any ROM that is based on Android 11.
Click to expand...
Click to collapse
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
pojr said:
Thank you for clearing that up with me. Now I at least have an answer on that. With that said, why would that be? Don't you have to wipe your phone in order to switch from stock to custom anyway? Is the ROM gonna say "we have somehow detected the you once had Android 11 before you wiped your OS"
Click to expand...
Click to collapse
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
MoistPicklez said:
Android changes quite a bit between versions like dynamic partitions and other jazzy stuff. For example TWRP. It works on Android 9, but changes to our device made TWRP incompatible with A10 and A11. (Good news on that though, we just got TWRP 3.5.0_9-0, though I have not tested it.)
Click to expand...
Click to collapse
did not realize we got a new twrp version. thats a step in the right direction. with that said, that info is good to know. i'm a lazy ass and prolly not gonna test out lineage os until it gets on 11 lmao.
For whoever needs it. I sure did after a derped update last week!
tl;dr install update, disable all modules before booting, get the latest recovery image and patch it, install with fastboot. long version below, just in case.
How To OTA With Magisk, Painlessly:
Open updater and download the OTA.
Press install and let it do its thing, but DON'T REBOOT YET.
Go to Magisk and disable all your modules.
Okay, you can reboot now. It might take longer than usual, it's a system update.
Open Magisk and note that it's no longer installed, don't panic.
Download the recovery image matching your update from here: https://download.lineageos.org/sargo
Open Magisk and patch the img you just downloaded.
Copy the magisk_patched_(random).img to a folder on your computer where you're able to access fastboot.
Reboot your phone to bootloader: either by the advanced power menu, enabled in developer settings, or by restarting and holding Volume Down while the phone boots up.
Open up your terminal/commandline/etc where you moved the image file.
Type the command "fastboot flash boot magisk_patched_*****.img", where the last part is the random string that got generated in the patching process. Press Enter.
After the command finishes, use the volume keys to scroll through the bootloader menu until you see "Start". Press the power button.
Your phone should reboot back to the OS, you can now go back to Magisk and re-enable your modules at your leisure.
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
harryharryharry said:
Aah, a much needed rom option for sargo/pixel 3a ! There has been a lot of silence around the pixel 3a in this regard.
I'm trying it out now. First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). If there is a dev out there I can supply a logcat or something like it if needed.
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications. I'll try and report back any issues I encounter (But if there are too many of them, I'll have to revert back to Dirty Unicorns, although that rom development seems to have stalled pretty much).
Click to expand...
Click to collapse
Just go into app settings and kill now & disable. I noticed that if you installl gapps, get rooted, setup the phone you prefer. Backup with google backup....use the lineage recovery to do a factory reinstall. Once you recover all the sim issues, installation issues simply stop.
nylar357 said:
So the one problem 'I've been having is with custom kernels. I've tried Elemental X & Gats Gulch. With both I lose wifi capability. Once I restore my lineage kernel viola problem solved. Now I've used both these kernels in the past on different builds so I know it isn't the kernel itself rather something related to the lineage build itself & the act of installing a custom kernel. Both kernels returned exactly the same type of error. WIFI attempts to turn on but returns to the off Position. If one attempts to activate the Wifi Icon dropdown during the System UI Crashes. Any input would be great. Other than this little hiccup
Lineage is running absolutely great. Best battery life of any custom OS by far. Sargo stays snappy, my kernel tweaks remain in place. Root maintains over system restores. Love it.
EDIT: ## By the way using Elemental X Kernel Manager App to flash ##
Click to expand...
Click to collapse
The kernel issues might be because they're targeted toward Android 11, and LOS 17.1 is based on Android 10.
harryharryharry said:
[...] First thing I noticed is SIM manager keeps crashing every minute or so (I'm in the Netherlands on the Ben/T-mobile network). [...]
Meanwhile I disabled the SIM manager to get rid of the constant crash notifications.[...]
Click to expand...
Click to collapse
It happened to me the same way. I am in the German T-Mobile network. I also disabled 'SIM Manager'.
Unfortunately, I do not receive any 'missed call'-SMS in case the mobile phone was in flight mode.
I think the app could have something to do with it because everything fits on the ISP side. So far, I haven't found an option to reactivate the App in the settings. Apparently it's some kind of hidden app. Can someone help please?
EDIT: There is a "hidden" "System-apps" option in the app settings. Unfortunately the error still occurs.