I need help with a question. I am on lineage os 14.1 and I would like to know if I can flash this 17.1 version directly without flashing the latest firmware by Odin since I don't have a computer. All the best!
[ROM]|SM-T520|SM-T900|[UNOFFICIAL] LineageOS 17.1 | Android 10
- Thread starter TechDriver
- Start date
bmwdroid
Senior Member
- Mar 8, 2014
- 1,862
- 1
- 806
Afaik 14.1 already needed latest firmware I assume you can flash 17.1 directly.
Latest TWRP and of course clean wipe with "format data".
Thanks for answering friend. Do you think a format data is 100% necessary? I had thought about doing the installation with a full wipes without the format data that erases everything (internal memory too or so I understand) What would the steps be like according to you? Thanks again!
Having a problem with my SM-T520.
It was with Linage 1.41, followed the 1st post instructions ==> going back to stock, install recovery, but when I try to wipe Cache, it stops with error. Rebooting to recovery shows Cache partition as 0 MB (zero).
Any advice would be helpful.
Thanks.
Fixed.
Installed twrp-3.0.2-0, did the wipe, then upgraded recovery to twrp-3.2.3-0-n2awifi-v2 and then flashed the rom.
It was with Linage 1.41, followed the 1st post instructions ==> going back to stock, install recovery, but when I try to wipe Cache, it stops with error. Rebooting to recovery shows Cache partition as 0 MB (zero).
Any advice would be helpful.
Thanks.
Fixed.
Installed twrp-3.0.2-0, did the wipe, then upgraded recovery to twrp-3.2.3-0-n2awifi-v2 and then flashed the rom.
Last edited:
with twrp-3.0.2-0 works ok. Found in another topic that it is the last twrp that includes a fs from samsung
Last edited:
bmwdroid
Senior Member
- Mar 8, 2014
- 1,862
- 1
- 806
It may not be necessary, but as I've had often problems after upgrading or even boot loops that vanished after a full wipe including "Format Data" I always recommend that to avoid problems.
On some devices it was even necessary to switch file system to and fro to be able to get a working system.
My steps when upgrading (hopping to a higher version):
1. backup EFS/Modem, System+boot and Data in 3 steps (makes it easier to determine incorrect files)
2. wipe caches, system, data,
3. "format data" additionally
4. flash ROM
5. reboot and see if it starts
6. if it does flash Magisk.zip and Gapps (if wanted)
When keeping the version but updating I usually do 1 and 2 (without Data) as well
I've downloaded from here: https://eu.dl.twrp.me/picassowifi/twrp-3.0.2-0-picassowifi.img.tar.html
https://eu.dl.twrp.me/picassowifi/twrp-3.1.1-0-picassowifi.img.tar.html is latest version. Where did you found 3.2.3.0?
bmwdroid
Senior Member
- Mar 8, 2014
- 1,862
- 1
- 806
hi, opengapps arm 7.1 nano 20220215...........I honestly don't know if it's overheating, it reaches 50% and the tablet restarts
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3Hello,
i did a new Build for the SM-T520 with the last security patch 5th Dec 2022
Test on your own risk, Do a Backup before!!!!
Had a strange behavior with dirty flash over my last 20220203 build and TWRP 3.2.3-0-v2
I Flashed the update and end up in a Bootloop, only wipe Data, Cache and Dalvik did help.
Restored and tried it with older twrp versions, but no change to update my device without loosing Data, Same when i did flash the 20220203 over 20220203 again.
After whipe Data, flash 20220203 and then i could also update to the last build without whipe data, maybe its some problem on my device, but be carefull and do a backup.
I tried also to do a Build for the SM-T900, but it end up in a error, so if someone can help me to fix the error i will start the build again, but I do not have time to fix it myself.
Code:les ) && (cp \$modules /root/Lineage/out/target/product/v2awifi/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0/vendor/lib/modules ) && (out/host/linux-x86/bin/depmod -b /root/Lineage/out/target/product/v2awifi/obj/PACKAGING/depmod_vendor_intermediates 0.0 ) && (sed -e 's/\\(.*modules.*\\):/\\/\\1:/g' -e 's/ \\([^ ]*modules[^ ]*\\)/ \\/\\1/g' /root/Lineage/out/target/product/v2awifi/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0/modules.dep > out/target/product/v2awifi/system/vendor/lib/modules/modules.dep ) && (cp /root/Lineage/out/target/product/v2awifi/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0/modules.alias out/target/product/v2awifi/system/vendor/lib/modules); fi )" make: Entering directory '/root/Lineage/kernel/samsung/exynos5420' GEN /root/Lineage/out/target/product/v2awifi/obj/KERNEL_OBJ/Makefile scripts/kconfig/conf --silentoldconfig Kconfig GEN /root/Lineage/out/target/product/v2awifi/obj/KERNEL_OBJ/Makefile CHK include/linux/version.h Using /root/Lineage/kernel/samsung/exynos5420 as source for kernel CHK include/generated/utsrelease.h make[2]: 'include/generated/mach-types.h' is up to date. CALL /root/Lineage/kernel/samsung/exynos5420/scripts/checksyscalls.sh CHK include/generated/compile.h GZIP kernel/config_data.gz CHK kernel/config_data.h CC drivers/usb/gadget/android.o CC drivers/usb/host/ehci-hcd.o CC drivers/usb/host/xhci.o CC drivers/usb/host/xhci-mem.o In file included from /root/Lineage/kernel/samsung/exynos5420/drivers/usb/gadget/android.c:44:0: /root/Lineage/kernel/samsung/exynos5420/drivers/usb/gadget/composite.c: In function 'composite_setup': /root/Lineage/kernel/samsung/exynos5420/drivers/usb/gadget/composite.c:1272:24: error: 'struct usb_composite_dev' has no member named 'redriver_work' schedule_work(&cdev->redriver_work); ^ make[4]: *** [/root/Lineage/kernel/samsung/exynos5420/scripts/Makefile.build:307: drivers/usb/gadget/android.o] Error 1 make[3]: *** [/root/Lineage/kernel/samsung/exynos5420/scripts/Makefile.build:443: drivers/usb/gadget] Error 2 make[3]: *** Waiting for unfinished jobs.... CC drivers/usb/host/xhci-ring.o CC drivers/usb/host/xhci-hub.o CC drivers/usb/host/xhci-dbg.o CC drivers/usb/host/xhci-exynos.o LD drivers/usb/host/xhci-hcd.o LD drivers/usb/host/built-in.o make[2]: *** [/root/Lineage/kernel/samsung/exynos5420/scripts/Makefile.build:443: drivers/usb] Error 2 make[1]: *** [/root/Lineage/kernel/samsung/exynos5420/Makefile:995: drivers] Error 2 make: *** [Makefile:130: sub-make] Error 2 make: Leaving directory '/root/Lineage/kernel/samsung/exynos5420' FAILED: [W][2023-01-01T09:46:31+0100][4766] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files [W][2023-01-01T09:46:31+0100][4766] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files 09:47:34 ninja failed with: exit status 1 #### failed to build some targets (04:28 (mm:ss)) #### -
17I'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!
Special thanks to Exynos5420 team and LineageOS for all the sources.
Use SM-T900 build at your own risk. I can't guarantee you it will work, because I have no device to test it on.
Work
Almost everything
It has pretty much the same functionality as Lineage 14.1
Known Issues
Built in mic not working
USB problems
You tell me...
Installation:
1. Flash latest official Samsung Firmware with ODIN
2. Flash latest TWRP Recovery: SM-T520 - SM-T900
3. Backup all partitions
4. Wipe Cache and Data
5. Install ROM.ZIP
6. Install latest GApps (ARM/Android10) https://opengapps.org/
7. Reboot and Enjoy
8. Optional: Install Magisk
For SM-T520 TWRP recoveries 3.1.1.0 and older will not flash this rom ending up with error 7: incompatible device.
Make sure to flash TWRP mentioned above.
Download:
SM-T520
SM-T900
I ll probably create builds with updated security and device code patches occasionally.
Enjoy fresh new Android!
Sources:
https://github.com/LineageOS (LineageOS 17.1)
https://github.com/exynos5420/ (Kernel, Device, Vendor)6Hi,
i did a build for my SM-T520 with the last updates, test on your own risk.
4I am currently working on building lineageos-15.1 and 16.0. I see theese versions as more stable because of more developed code. I had successfully built los 16.0 multiple times but always run into bootloop. Los 15.1 is even more tricky. I run into multiple problems building it but if I will succesfully complete it and it will be stable enough I will give you link to download.4Just to make things clear, I am not developer of code and not skilled enough to make changes in it. For this job, there is team exynos5420 and other cool contributors to make device sources. I use their device sources from exynos5420 and LineageOS github to build together final product... Rom.zip you install on device. I can't fix bugs, i only can wait until some contributor fixes it and I will build rom with fixes and updated security patches included.3
