Comes with the November 1, 2018 Security Patch
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sammobile Link
Mega.nz mirror
You need the Odin3 v3.13.1 (attached below) to flash it. (Older versions won't work)
Most of you probably already know this but here's a quick tutorial on how to flash the stock rom after you extract the zip file:
1. Reboot into download mode.
- From PC, open cmd -> cd <your adb directory> -> type adb reboot download
- Turn off your phone, hold down Home + Volume Down + Power Button, release the keys once the screen with the "Warning" pops up
2. Open Odin3 3.13.1, go to options and make sure Auto Reboot and F. Reset Time is checked.
3. Connect your device and hit the Volume Up button to start the process.
4. Go back to logs,
- Click BL and select the file starting with BL (wait for the MD5 check to complete)
- Click AP and select the file starting with AP (wait for the MD5 check to complete)
- Click CSC and select the file starting with CSC (wait for the MD5 check to complete)
(Note: Since this device does not have an LTE modem the CP box will remain empty.
You can ignore the file starting with HOME)
5. Hit Start and wait for the process to complete, keep checking the logs, it should not take more than 15 minutes.
6. Once the device restarts you can unplug the USB cable. The device will now perform the final steps of installation and reboot the device once more.
(The device should finish its initial boot in 5-10 mins)
That's it. Not sure if it can be rooted safely at this moment.
Update:
To roll back to 7.0 after flashing this rom flash this rom: 7.0 T580XXS4BRI1 DBT
Here's a Mega.nz Mirror: https://mega.nz/#!brJyWIAJ!hisbxGderr08lWuHuv8eRa_rXJyDDqrnuGaZmRL68bU
Can you check if the binary blobs are 64-bit or still 32-bit? If they're 64, we're practically set for Treble-enabled ROMs with even less bugs!
I have updated to 8.1.0 and now I can not go back to the previous version: Android 6.
Hi. I have updated to 8.1.0 and now I can not go back to the previous version, how can I remove this version 8.1.0? I have tried by all possible means and it has been impossible for me, now I have to have version 8.1.0 with no possibility of putting Android 6 or 7. I am very worried because I can not go back to the previous version. THANK YOU.
My tablet is: Samsung Galaxy tab A 6 (SM-T580)
My previous android: Firmware Android 6.0.1 (Marshmallow) - 06-01 - 2016 - T580XXU1APE8
Sorry for my bad English, but I'm from Spain and I've used Google translator.
:crying:
indaliax said:
Hi. I have updated to 8.1.0 and now I can not go back to the previous version, how can I remove this version 8.1.0? I have tried by all possible means and it has been impossible for me, now I have to have version 8.1.0 with no possibility of putting Android 6 or 7. I am very worried because I can not go back to the previous version. THANK YOU.
My tablet is: Samsung Galaxy tab A 6 (SM-T580)
My previous android: Firmware Android 6.0.1 (Marshmallow) - 06-01 - 2016 - T580XXU1APE8
Sorry for my bad English, but I'm from Spain and I've used Google translator.
:crying:
Click to expand...
Click to collapse
Simply said, you can't. Samsung bumps the bootloader version with every major OS update, and you can't downgrade bootloader.
fonix232 said:
Simply said, you can't. Samsung bumps the bootloader version with every major OS update, and you can't downgrade bootloader.
Click to expand...
Click to collapse
Yes, you can. I did it and went back to the latest DBT nougat ROM. Just flash the Nougat ROM files in the same way as described by the OP in the first post using the latest Odin version.
Best, maris
maris__ said:
Yes, you can. I did it and went back to the latest DBT nougat ROM. Just flash the Nougat ROM files in the same way as described by the OP in the first post using the latest Odin version.
Best, maris
Click to expand...
Click to collapse
Weird. This FW does bump the BL version (last 5 numbers of the bootloader version, OS version, year, month and release: 4CRJ8 means 4th bootloader version, third major OS update (C is the third letter of the alphabet), R means 2018 (R is the 18th letter), J is October (J is the 10th letter), and 8 means it's the 8th build in October). My previous BL was 3, so bumping to 4 means I can't go back. But if there are firmwares with BL version 4, but on older FW, you can go back.
I went back to the latest DBT Nougat ROM, which is 4BRI1. So the latest DBT Nougat ROM also has the 4th bootloader of the series.
fonix232 said:
Can you check if the binary blobs are 64-bit or still 32-bit? If they're 64, we're practically set for Treble-enabled ROMs with even less bugs!
Click to expand...
Click to collapse
Still 32
Does this mean we will still be able to flash TWRP and use arm A-only GSI Roms? Which I can tell is a limited number of Roms.
Edit: I would settle for 32bit if it meant everything works and I can run a Pie GSI Rom.
Solved
Thank you very much everyone for the help offered, I have been able to go back to the Nougat 7 version, the problem is that I installed the Nougat 7-PHE version of Spain and Odin3-v3.13.1 gave me an error, I had to download the 7 Nougat 7.0 -DBT Germany and then install TWRP and I have already recovered my Tablet staying exactly as I had before.:good
srgrusso said:
Does this mean we will still be able to flash TWRP and use arm A-only GSI Roms? Which I can tell is a limited number of Roms.
Edit: I would settle for 32bit if it meant everything works and I can run a Pie GSI Rom.
Click to expand...
Click to collapse
After extracting the Oreo update, vendor still resides inside the system image. I answered my own question. The update isn't project treble compatible.
srgrusso said:
After extracting the Oreo update, vendor still resides inside the system image. I answered my own question. The update isn't project treble compatible.
Click to expand...
Click to collapse
There IS a Treble-ish solution that hacks around Samsung's ****ty implementation and uses /cache as /vendor, but it hasn't been updated to these new binaries. Unfortunately they're still 32-bit, and not many (or pretty much, no) GSI images exist for 32-bit. Samsung is apparently consciously trying to keep us on stock firmware.
fonix232 said:
There IS a Treble-ish solution that hacks around Samsung's ****ty implementation and uses /cache as /vendor, but it hasn't been updated to these new binaries. Unfortunately they're still 32-bit, and not many (or pretty much, no) GSI images exist for 32-bit. Samsung is apparently consciously trying to keep us on stock firmware.
Click to expand...
Click to collapse
I'm currently using it. It's pretty impressive if you think about it. I wonder if we went with the 32bit vendor that everything would work.
srgrusso said:
I'm currently using it. It's pretty impressive if you think about it. I wonder if we went with the 32bit vendor that everything would work.
Click to expand...
Click to collapse
Most of the stuff would work, yes, but there's little to no 32-bit GSI images available. I'm not even sure if Treble itself works with 32-bit.
fonix232 said:
Most of the stuff would work, yes, but there's little to no 32-bit GSI images available. I'm not even sure if Treble itself works with 32-bit.
Click to expand...
Click to collapse
Here is a list of 32bit GSI roms I found here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list.
Android 9 Pie:
AOSP 9.0
Pixel Experience
Descendant
Android 8 Oreo:
AOSP 8.1
AOSP Extended
CarbonRom
DU
LineageOS
Resurrection Remix
XenonHD
Edit: Might be able to compile other ones as long as they have 32bit sources.
Android 8.1 Oreo
Hey Xda member...Recent installed on my T580 very success and fast/smooth problem zero! After several apps install, too. Also battery great!! Thanks srgrusso Thumb up!
No USA version of this update? Any idea when?
I'm running a modified rooted stock rom with TWRP based on nougat and 1 february 2018 security patch on my t580. Can I still just flash over that with the ROM from this thread? I think I might have to update my twrp first though, I've not updated it in months.
Swizzy88 said:
I'm running a modified rooted stock rom with TWRP based on nougat and 1 february 2018 security patch on my t580. Can I still just flash over that with the ROM from this thread? I think I might have to update my twrp first though, I've not updated it in months.
Click to expand...
Click to collapse
You can, you don't need to update twrp (you will lose it anyway), just flash this through odin.
But you'd be better off updating twrp, and flashing a rooted, de-bloated 8.1 which is flashable through twrp.
It has all the stock features, and it's a bit faster in my experience.
You can find the new twrp and the rom in this thread:
https://forum.xda-developers.com/galaxy-tab-a/development/rom-07-11-2018-stock-rom-v1-0-t3866751
UK version updated this morning( OTA update). November security patch. I am a light user, so havent noticed a huge amount of changes, but two what I have noticed so far. 1. When the charger is plugged in , the charge percentage value is flashed for a few seconds in the middle of the screen. 2. When I play Netflix and press home button, instead of killing netflix, if comes into a small screen in the corner . This is nice... Only worked for netflix though..
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there, everybody! I am still using Marshmallow on my phone for various reasons. But the latest clean Lineage 13 that we have is with March 2017 security patches - so it is quite old now. I saw that there is a new MM ROM in XDA - the Lineage OS 13 with MicroG patch one. But when I saw what MicroG is, I really didn't even think about flashing this ROM - I am not privacy-concerned because all the Google services are useful to me, and I don't like using custom kernels on Lineage. The stock one works the best for me.
So for people like me - who like the clean Lineage and don't want to have any issues with Google Services, I built a Lineage 13 from Source with the latest security patches from Google.
Again, I am not telling you the ROM with MicroG patch is bad. It's actually a pretty great ROM. I'm just uploading this one, so that people like you have choices - either flash this clean one, or the one with the MicroG patch.
It has root built in. You can find it in the developer options. No need to flash the extra ZIP.
ChangeLog:
Version 20180319:
Updated Lineage sources (including new fixes, improvements, etc.)
Theoretically should work better
1 March 2018 security patch
Using Squid Kernel 22b by default
Version 20171115:
Initial booting Release
Contains KRACK fix and BlueBorne fix
Rooted by default
Installation:
Download the ROM from the downloads tab on the top of this thread
Download OpenGAPPS (or other ones which work with Lineage)
Wipe the Data, Cache and Dalvik (ART Cache)
Flash the ROM
Flash the GAPPS (optional)
Reboot and enjoy!
Important:
Each build of this ROM is made via the Windows 10 Subsytem for Linux. If anyone has problems with building Android on WSL, simply PM me and I'll be glad to help you.
XDA:DevDB Information
LineageOS 13 (2018), ROM for the Moto G 2015
Contributors
nicolasmart, squid2, CyanogenMod (formely Lineage)
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.x
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 2017-11-05
Stable Release Date: 2017-11-05
Created 2017-11-05
Last Updated 2018-03-19
Nice initiative.. Is VOLTE is added in this ?
rahul9999 said:
Nice initiative.. Is VOLTE is added in this ?
Click to expand...
Click to collapse
I don't personally use VoLTE since my carrier doesn't have it yet. It should be there but I can't really test it out, so I would wait for you to tell me.
nicolasmart said:
I don't personally use VoLTE since my carrier doesn't have it yet. It should be there but I can't really test it out, so I would wait for you to tell me.
Click to expand...
Click to collapse
I would like to test but not possible for me.. hope someone confirm this..
I have a problem here in instalation.
The rom does not start. It stays on the first screen and nothing happens.
the ROM has a problem and is that it does not start when we just installed it, I hope and fix it, great.
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
ironzy said:
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
Click to expand...
Click to collapse
Whaat? It works for you? I can't get my device to boot on my own ROM XD. What SKU are you using? I'm on XT1451
nicolasmart said:
Whaat? It works for you? I can't get my device to boot on my own ROM XD. What SKU are you using? I'm on XT1451
Click to expand...
Click to collapse
not sure what SKU means, I flashed the squid kernel after flashing the rom and it all works fine, the battery life is awesome.
ironzy said:
not sure what SKU means, I flashed the squid kernel after flashing the rom and it all works fine, the battery life is awesome.
Click to expand...
Click to collapse
He mean to say which variant you're on.. like I'm on XT 1550 2GB Ram.. If you dont know how to check this then just remove back cover of you're phone & see Model no. mentioned..
rahul9999 said:
He mean to say which variant you're on.. like I'm on XT 1550 2GB Ram.. If you dont know how to check this then just remove back cover of you're phone & see Model no. mentioned..
Click to expand...
Click to collapse
xt1541
Im using LineageOS 13 25/05/2017 build. Please, can you update the same for Moto G3-TE (merlin).
My SKU (XT1557) .
Thanks in advance:laugh:
ironzy said:
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
Click to expand...
Click to collapse
wft, ami does not work for me, it stays in the moto logo and does not advance.
I have the xt1540
Erick_Summer said:
wft, ami does not work for me, it stays in the moto logo and does not advance.
I have the xt1540
Click to expand...
Click to collapse
try doing a full wipe then flashing the rom and then the squid kernel, that's the way I installed it and it works fine.
ironzy said:
try doing a full wipe then flashing the rom and then the squid kernel, that's the way I installed it and it works fine.
Click to expand...
Click to collapse
Ooooh!!! I know why it works for you!! You changed the kernel! My kernel is just bad!!! OK. Replacing it with stock Squid Kernel
Project Update
Old build deleted. The new one is coming up tomorrow.
nicolasmart said:
Old build deleted. The new one is coming up tomorrow.
Click to expand...
Click to collapse
you compiled it wrong this time, it gives error when installing it by recovery
Erick_Summer said:
you compiled it wrong this time, it gives error when installing it by recovery
Click to expand...
Click to collapse
the rom doesn't install on the latest twrp
Erick_Summer said:
you compiled it wrong this time, it gives error when installing it by recovery
Click to expand...
Click to collapse
ironzy said:
the rom doesn't install on the latest twrp
Click to expand...
Click to collapse
The ROM is installable with twrp-osprey-3.1.1-r1, the newer version adds support for newer android version. I guess it also means dropping support for older version of android. But again this ROM doesn't boot for me even after flashing was successful.
ajaysingh23 said:
The ROM is installable with twrp-osprey-3.1.1-r1, the newer version adds support for newer android version. I guess it also means dropping support for older version of android. But again this ROM doesn't boot for me even after flashing was successful.
Click to expand...
Click to collapse
support wasn't dropped for older versions of android, the rom just needs changing to work with the new twrp, the micro g version installs fine on the latest twrp.
How is this different to the 'Official' Build?
From October 17th onwards, the Official builds had merged N9 sources which has ridden users the chance of flashing custom kernels due to the new N9 dependency. These builds aim to backtrack that, reverting to S9(+)'s Oreo Vendor, to gain custom kernel support again. Also, the firmware source used in the 'Official' builds have become fairly antique, so it was time for a refresh and use the latest and final Oreo source (BSB1) Samsung had to give, and an upstreamed kernel of latest (almost always) ELS thanks to @Eamo5's Endurance Kernel being baked into the builds.
Aside from these factors and a few more listed below, this is the LineageOS you know and love. Although LineageOS' nightly-build system is great, there is only so much change that can happen over a night. You can expect these builds updating to cover latest Security Patch a.k.a Monthly Builds, but maybe more if a great change is required.
Simple motive: Have a solid daily driver before the Pie Tree sources are dropped.
Screenshots
If you are on the App they may instead be at the bottom of the post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's working:
As this build is based on the 'Official' LineageOS build, it complies with the device support requirements, which means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
NFC
Camera
Fingerprint Sensor - Noticeable speed improvement reverting to an S9(+) Vendor.
Software:
The build has overridden auto-generated fingerprint keys, with an official, whitelisted fingerprint from Samsung, which can also be found in MagiskHideProps. This ensures SafetyNet passes without the need for extra flashing - refer to above screenshot also.
F2FS Support - Instructions to switch from default ext4 to f2fs
Miscellaneous - Overlays:
- Dialer - Call recording enabled. If your country is not blacklisted (for legality reasons) you should see a 'Record' button during your call.
- Trebuchet - Notification Badges
- Files - File Operation Dialog Box, Default Show Internal Storage
- Settings - Default Enable Autobrightness for Night Time flashers; Default Disable Bluetooth and LED
- SystemUI - Button to Expand Notifications; Notifications fade on dismiss
- Snap: api v2 enabled for better quality pictures and remove green artefacts & flashing.
What's not working:
Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. They may have their own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port.
Encryption Support as of now, exploring for a workaround (if there is one).
Bugs:
Lock screen shortcut - Camera: Screen flashes white, and then Camera force closes using shortcut.
Work around: Install another app using Camera action (e.g. SnapChat) and set stock Camera to default for shortcut.
Instructions:
Make sure TWRP has been installed and is functional.
Download the latest build, Vendor and optionally GApps - Links found under the header below.
Reboot to Recovery
Wipe data and cache (required if you are not currently using LOS and are coming from OneUI or SamExp.)
Install Vendor image to Vendor partition.
Flash the latest build (and GApps if you downloaded it)
If you are on and beyond April Patch (OneUI), do not flash a found Oreo Firmware as you will lose Baseband (Sim, Network, RIL). There is also no need to change firmware.
Reboot to System.
If a new build is released, to update:
Downloading and flashing a later build, will automatically replace (wipe & install) the /system partiton and retain your compatible User /data partition and firewall due to LineageOS' addon.d supprort.
You also do not need to flash GApps again, as they too have addon.d support, backing up which GApps you have installed and holding them until after the /system partition wipe has been done.
Same applies to Magisk Root due to (you guessed it) addon.d support too. It holds your currently installed Modules until after the /system partition wipe has been done.
Therefore, due to these addon.d files surviving because of the way LineageOS.zip manipulates the wipe to the /system partition there is no need to wipe partitions manually. Just leave it to the lone flash.
However, do remove any system modified theme overlays (substratum) to ensure no loop on boot, which may then result needing to wipe.
Downloads:
Vendor: Included to the respective Device drives below
Samsung Galaxy S9 (G960F): https://drive.google.com/drive/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Samsung Galaxy S9+ (G965F): https://drive.google.com/drive/folders/1cr-ivOdTj8lo3p9kYjGcxT1AvgFYy3M9
OpenGApps (Optional): https://opengapps.org/
Contact:
Telegram Group - Handle @invisibazinga2 a.k.a Lil' G-Raf
Contributors:
Big thanks to: @jesec ; @Synt4x.93 ; @Ivan_Meler ; @Eamo5 ; please check GitHub commit history for anybody that I may have missed out, you have all been great!
ROM Information
LineageOS Source: https://github.com/LineageOS
Android Security Patch: May
Android Version: 8.1.0
Kernel Version: ELS - 4.9.xx - Endurance Kernel - Version subjected to change with ELS updates.
Device Source: https://github.com/AzzyC
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
enetzlsg said:
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
Click to expand...
Click to collapse
Hey man! Yeh on the official build as the vendor was N9 based, our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
the screenshots look like pie roms... clock is on left side ..i thought finally a good lineage 16 build.. yet thanks for the 15.1 build though.. ??
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
kmo1997 said:
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
Click to expand...
Click to collapse
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
AzzyC said:
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
Click to expand...
Click to collapse
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
kmo1997 said:
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
Click to expand...
Click to collapse
Glad you're back to normal state!
Users has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks
AzzyC said:
Glad you're back to normal state!
If I remember correctly a User has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks and hope it works out!
Click to expand...
Click to collapse
yep, works like magic. thank you very much!
AzzyC said:
Hey man! Yeh on the official build as the vendor was N9 based our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
Click to expand...
Click to collapse
one ui lib didn't work out for me
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Muntasir Mahmud Saif said:
one ui lib didn't work out for me
Click to expand...
Click to collapse
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
LavaSnake54 said:
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Click to expand...
Click to collapse
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
AzzyC said:
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
Looks like a solid daily driver for me. Will definitely try it soon.
AzzyC said:
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Muntasir Mahmud Saif said:
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Click to expand...
Click to collapse
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Hey guys!
I was doing a test run for a particular change and I thought I'd do a quick update for both devices. Starlte built just fine but I ran out of disk space when finishing star2lte so the compile failed (at 91% ?)
Not to fret, the May Security Patch has not yet been merged into LineageOS so this would have been just another build on April Patch. However, the included kernel has updated to latest of Endurance, though you can just flash Eamon's latest kernel zip to update and have the same effect.
Both devices will of course get an update when May Patch is out. Gracias bien
For starlte:
https://drive.google.com/drive/mobile/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Gcam link please?
AzzyC said:
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Click to expand...
Click to collapse
sorry if i did wrong or hurt your feelings but can you please provide those two files?
LavaSnake54 said:
Gcam link?
Click to expand...
Click to collapse
Muntasir Mahmud Saif said:
can you please provide those two files?
Click to expand...
Click to collapse
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
AzzyC said:
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
Click to expand...
Click to collapse
you are dope bro .thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
Disclaimer
This is specially designed for Nokia 7 Plus . With the help of this tool we can flash any stock home brew Roms and the links will be attached below .
How to use this?
Note - Make sure your phone bootloader is unlocked
1. Download Nokia-SDM660-Tool.zip & Copy Nokia-Tool.exe
2. Download latest HOME BREW Stock Rom And extract in one Folder and name it as STOCK ROM
3. Now add Nokia-Tool.exe in to that respective STOCK ROM Folder
4. Now connect phone to pc
5. Go to download mode
6. Now Open Nokia-Tool.exe
7. Now select Button according to your Phone code
8. Example Iam Using Nokia 6.1 Plus & My phone code DRG & so i will choose [ DRG B2N CTL PL2 ] same option for 6.1 , 7.1 & 7+ but for 7.2 & 6.2 users choose [DDV SLD]
9. i will click on [ DRG B2N CTL PL2} According to my phone as i explained in point no.8
10. wait for 10 min Tool will flash the rom & your phone reboots to system.
11. So finally this is what the exact standard method to flash stock rom on Your devices
Download Tool
Download stock roms
Credits
Massive thank you for hikari_calyx ( Without him and his support during hmd journey iam nothing )
&
My entire Nokia 7 Plus community Thank you all for your massive support Again
XDA:DevDB Information
Stock-Rom Flash Tool Nokia 7 Plus
Contributors
Raghu varma , hikari_calyx
Source Code:
https://github.com/RaghuVarma331/Nokia-Tool.git
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date 2019-12-23
Created 2019-12-23
Last Updated 2020-04-07
Now Some common Questions
Q1. we still receive monthly updates?
A. obviously you will receive updates as like before
Q2. Can we try this on Locked Bootloader?
A. No
Q3. Can we use this without Adb Tools?
A. No
Q4. Can we use this tool on any Android version?
A. Yes works On Oreo , pie & Q but keep this point in your mind update your platform tools time to time due to For Q & Pie & Oreo all these 3 having different different platform tools so if you face any erros don't get scared just download latest adb platform tools
How to unlock the bootloader?
Raghu varma said:
Note - Iam Not Responsible for bricked devices
Disclaimer
This is specially designed for Nokia 7 Plus . With the help of this tool we can flash any stock home brew Roms and the links will be attached below .
How to use this?
Note - Make sure your phone bootloader is unlocked
1. Download Nokia-SDM660-Tool.zip & Copy Nokia-Tool.exe
2. Download latest HOME BREW Stock Rom And extract in one Folder and name it as STOCK ROM
3. Now add Nokia-Tool.exe in to that respective STOCK ROM Folder
4. Now connect phone to pc
5. Go to download mode
6. Now Open Nokia-Tool.exe
7. Now select Button according to your Phone code & Stock Rom code
8. Example Iam Using Nokia 7 Plus & My phone code B2N & latest Stock rom for my phone is 354H so i will choose B2N354H
9. i will click on B2N354H According to my phone as i explained in point no.8
10. wait for 10 min Tool will flash the rom & your phone reboots to system.
11. So finally this is what the exact standard method to flash stock rom on Your devices
Download Tool
Download stock roms
Credits
Massive thank you for hikari_calyx ( Without him and his support during hmd journey iam nothing )
&
My entire Nokia 7 Plus community Thank you all for your massive support Again
XDA:DevDB Information
Stock-Rom Flash Tool Nokia 7 Plus
Contributors
Raghu varma , hikari_calyx
Source Code:
https://github.com/RaghuVarma331/Nokia-SDM660-Tool
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date 2019-12-23
Created 2019-12-23
Last Updated 2019-12-23
Click to expand...
Click to collapse
So after updating to stock rom, will the bootloader stay unlocked ?
why is it booting on Android Oreo, even after flashing Android 10 Stock ROM ?
---------- Post added at 05:20 AM ---------- Previous post was at 04:48 AM ----------
Also, it doesn't detect any wifi at the setup page !
All the .imgs get flashed, except this one:
fastboot: error: cannot load 'B2N-410C-0-00WW-B03-cda.img': No such file or directory
This might be useful information to you. When starting up after this, the phone does boot, but Google Apps keep crashing
for me, all the .img files are failing !!!!
All I get is
"'fastboot' is not recognized as an internal or external command,
operable program or batch file."
And yes of course the phone is in Fastboot/Download mode.
EDIT: Got it working by copying everything in that STOCK ROM folder into adb. Instructions unclear.
Liftedcorn said:
So after updating to stock rom, will the bootloader stay unlocked ?
Click to expand...
Click to collapse
Is there anybody that can answer to this question? Thanks
Ninotzz said:
Is there anybody that can answer to this question? Thanks
Click to expand...
Click to collapse
Yes. Bootloader will stay unlocked no matter how many ROMs you flash. Talking from experience ?
Liftedcorn said:
Yes. Bootloader will stay unlocked no matter how many ROMs you flash. Talking from experience
Click to expand...
Click to collapse
Thanks a lot for sharing your experience! I lost all backups of stock ROM by accident so it would be very handy if I could get back to it someday without locking the bootloader again ahahhaha
Would it fine if you could update the ROMs to the latest patches if that's possible? I don't want to spend an hour updating my phone each time I come back from trying a different ROM XD
(I use a Nokia 7 Plus btw)
#Raghu varma: Man you saved my life. Thank you so much and anyone involved.
You also need to put Minimal ADB and Fastboot files in that folder.
when i try to flash the stock rom using nokia tool it gets stuck at "erase ssd" then the nokia tool shows not responding . is there any solution to this?
LordMashie said:
All I get is
"'fastboot' is not recognized as an internal or external command,
operable program or batch file."
And yes of course the phone is in Fastboot/Download mode.
EDIT: Got it working by copying everything in that STOCK ROM folder into adb. Instructions unclear.
Click to expand...
Click to collapse
how did you do it? because mine gets stuck and the tool doesn't respond. can you give me the instructions ?
if i can make software update (OTA)? after instalation stock system by pc my phone tell me that i must update system before configuration.
phone will be bot bricked?
hubert987 said:
if i can make software update (OTA)? after instalation stock system by pc my phone tell me that i must update system before configuration.
Click to expand...
Click to collapse
phone will not be bricked?
Liftedcorn said:
for me, all the .img files are failing !!!!
Click to expand...
Click to collapse
Same! More documentation for this tool is needed.
I would like to flash stock rom because of lack command NFC in custom roms. Can I flash stock rom without wipe and format data of custom rom?
This is posible Thanks to Sravan kalasapati from TechiBee !
Oneplus team starting to push the incremental rollout of OxygenOS 12.1 A.14 for the OnePlus 10 Pro for IND and Global region.
Incremental, of course.
OxygenOS 12.1 A.14 Changelog for GlobalSystem- {Improved] system stability.- [Fixed] an issue where music playback would stutter when your phone was connected to a Bluetooth car kit.
- [Fixed] a noise issue that might occur when you record audio.
- [Updated] Android security patch to 2022.05
Camera
- [Fixed] an issue where the HDR photos might be overexposed in some cases.
Network
- [Optimized] the phone call stability.
Official post, with Incremental Download link :
Oneplus 10 PRO gets OxygenOS 12.1 A.14 Global Update with May security Patch and System Changes
Oneplus starting to push the incremental rollout of OxygenOS 12.1 A.14 for the OnePlus 10 Pro for IND and Global region now
techibee.in
Other link with download for incremental :
OnePlus 10 Pro and Nord N10 pick up May 2022 security update
The May 2022 security update is rolling out to the OnePlus 10 Pro and OnePlus Nord N10. The OnePlus 9RT has also received a new update.
www.xda-developers.com
For easy install the Incremental.zip you must bee on A.13.
Download OTA & manually update your phone. All you have to do is grab the correct OTA package corresponding to your device, transfer the package to the root of internal storage and flash it from the System Update menu.
old news
i cannot update to this version after convert from ColorOs to OxygenOS although i receive this update officially. Any help?
g96818 said:
old news
Click to expand...
Click to collapse
yeah, aren't we all on A.15
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gagan007 said:
yeah, aren't we all on A.15View attachment 5630737
Click to expand...
Click to collapse
oh boy. If you read the op forum, you would have seen a15 is a test build that got leaked on oxygen updater. Hopefully there's no major bugs and you can update when the final a15 gets released.
Hi guys i have a few questions:
1. If I have the Chinese NE2210 model of oneplus 10 pro, then I can use flash this global ROM to the phone?
2. Do I need to flash a different ROM if my OP10 pro is the 12gb/256gb compared to 8gb/128gb?
3. I heard you do not need to unlock bootloader to flash if you are using the official ROM given by OnePlus, is this true?
4. If I want to flash ROM, my current OS version needs to be any version lower than the desired OS version, whether on ColorOS or OxygenOS
5. If my stock os is COLOR OS and model NE2210 (Chinese model), and I flashed oxygen rom, can I revert back to the STOCK color os version OR any color OS version ? (in case the new flashed rom has bugs or issues on my device)
thank you
file in the link is NA not for Glo/Eu
jayejays said:
Hi guys i have a few questions:
1. If I have the Chinese NE2210 model of oneplus 10 pro, then I can use flash this global ROM to the phone?
2. Do I need to flash a different ROM if my OP10 pro is the 12gb/256gb compared to 8gb/128gb?
3. I heard you do not need to unlock bootloader to flash if you are using the official ROM given by OnePlus, is this true?
4. If I want to flash ROM, my current OS version needs to be any version lower than the desired OS version, whether on ColorOS or OxygenOS
5. If my stock os is COLOR OS and model NE2210 (Chinese model), and I flashed oxygen rom, can I revert back to the STOCK color os version OR any color OS version ? (in case the new flashed rom has bugs or issues on my device)
thank you
Click to expand...
Click to collapse
1. YES
2. NO
3. NO. if you change from Color to Oxygen and vice versa, you need to unlock
4. NOT SURE. I don't think that matters
5. YES. Same as step 3.
itongx said:
file in the link is NA not for Glo/Eu
Click to expand...
Click to collapse
So both forums lie ?...
null0seven said:
So both forums lie ?...
Click to expand...
Click to collapse
connect tru Denmark vpn you will get update notification but download speed quite slow, finally you will get A14 global update.
Full zip link would be great to share, because of rooted devices.
kouzelnik3 said:
Full zip link would be great to share, because of rooted devices.
Click to expand...
Click to collapse
You should just need to use the uninstall option in Magisk, hit restore images, install the OTA, then install to inactive slot and reboot in order to install the incremental OTA.
I'm on A13 I use oxygen updater and nothings come through for me as yet.
dladz said:
I'm on A13 I use oxygen updater and nothings come through for me as yet.
Click to expand...
Click to collapse
Europeans must wait..., wait..., wait some more...
EtherealRemnant said:
You should just need to use the uninstall option in Magisk, hit restore images, install the OTA, then install to inactive slot and reboot in order to install the incremental OTA.
Click to expand...
Click to collapse
Unfortunately not, because once I root incremental update, device might start lagging in this case of OP10P, it is known
kouzelnik3 said:
Unfortunately not, because once I root incremental update, device might start lagging in this case of OP10P, it is known
Click to expand...
Click to collapse
Incremental updates get the OS to exactly the same software as a full OTA of the same version so what you're saying doesn't make any sense.
EtherealRemnant said:
Incremental updates get the OS to exactly the same software as a full OTA of the same version so what you're saying doesn't make any sense.
Click to expand...
Click to collapse
But it changes only incremental files, it won't install whole system at all. It won't make sense, but it is known to happen on oneplus 10 pro once you are rooted.
Where does the download go to?
If you're rooted and you attempt to install a14 it'll fail then offer the 4.20GB full zip..
But where the hell does it download to?
dladz said:
Where does the download go to?
If you're rooted and you attempt to install a14 it'll fail then offer the 4.20GB full zip..
But where the hell does it download to?
Click to expand...
Click to collapse
If your rooted go to data/misc/oplus_update_engine_log/update_engine_log it will show you the link to the ota.zip
dladz said:
Where does the download go to?
If you're rooted and you attempt to install a14 it'll fail then offer the 4.20GB full zip..
But where the hell does it download to?
Click to expand...
Click to collapse
you git offered the full zip? ne2215?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience
How to download:
Reboot to recovery
Wipe data, cache, and dalvik if coming from another ROM
Flash ROM zip
(optional) Flash Gapps
(optional) Flash Magisk (root)
Reboot and voila!
Download:
here
Join our Telegram channel :
https://t.me/buildingSasuke
https://t.me/Galaxy845Updates
PixelExperience, ROM for S9, S9+ and N9
Device: starqltechn, star2qltechn and crownqltechn
Maintainer: KkjSasuke
Build Type: Unofficial
ROM OS Version: 12.1
ROM Kernel: klabit kernel
ROM Firmware Required: Must be on
Sources:
Device tree
Device tree comon
Kernel
Vendor Common
Bluetooth can't work, i have tried solution in telegram, but it makes my device cannot enter system
Isiishakkakakkwwi said:
Bluetooth can't work, i have tried solution in telegram, but it makes my device cannot enter system
Click to expand...
Click to collapse
does yours also restart often?
aditya2tiga said:
does yours also restart often?
Click to expand...
Click to collapse
No, it just stay in the Samsung logo interface
Isiishakkakakkwwi said:
No, it just stay in the Samsung logo interface
Click to expand...
Click to collapse
what do you mean bootloop?
from my friend who uses a CrDroid 8.10 cusrom, fixing his bluetooth problem he edited the buildprop file, from 26 it was replaced by 29 the value
aditya2tiga said:
what do you mean bootloop?
from my friend who uses a CrDroid 8.10 cusrom, fixing his bluetooth problem he edited the buildprop file, from 26 it was replaced by 29 the value
Click to expand...
Click to collapse
You're right, i changed it to 32, so it leads to bootloop... Now i change to 29 and it works well
I cant boot after reboot. Clean install.
I miss sometjing?
The phone does not work properly. During the call, the voice cannot be transmitted or heard.
acabreram said:
I cant boot after reboot. Clean install.
I miss sometjing?
Click to expand...
Click to collapse
flash Tomkernel v4 before flash PixcelExperience
and when it arrives at the "secure start-up" option, select NO
aditya2tiga said:
flash Tomkernel v4 before flash PixcelExperience
and when it arrives at the "secure start-up" option, select NO
Click to expand...
Click to collapse
Yes, thanks!! Secure start-up it's the problema if Select yes
Your original post says "ROM Firmware Required: Must be on" but doesn't finish the sentence.
I'm currently running rooted version of Stock Firmware with May 2022 security update and klabit v6.5 kernel on my S9 snapdragon (SM-G9600).
Can I flash this ROM over my current system?
aditya2tiga said:
what do you mean bootloop?
from my friend who uses a CrDroid 8.10 cusrom, fixing his bluetooth problem he edited the buildprop file, from 26 it was replaced by 29 the value
Click to expand...
Click to collapse
Which item in build.prop was edited?
I have several items in build.prop with values 26 and 32. Changes in some of them lead to bootloop, others don't change anything
Well! I found the solution in tg. It's ro.product.first_api_level in /vendor/build.prop (not in /system/build.prop)
Bluetooth Fix:
[ROM] [12.1] [UNOFFICIAL] LineageOS 19.1 for S9, S9+ and N9
Lineage is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Hello, I got a SM-G9650 and I was never able unlock its bootloader. Most tutorials talk about some CROM Service app but it isn't working anymore. Does anyone know how to unlock it in 2023? Thanks.
Hello, I got a SM-G9650 and I was never able unlock its bootloader. Most tutorials talk about some CROM Service app but it isn't working anymore. Does anyone know how to unlock it in 2023? Thanks.
Click to expand...
Click to collapse
All you need to do is turn on Developer Options (Settings/About phone/Software information/, then tap Build number 10 times). Under Setting/Developer options/, look for the "OEM unlocking" item.
RAExda said:
All you need to do is turn on Developer Options (Settings/About phone/Software information/, then tap Build number 10 times). Under Setting/Developer options/, look for the "OEM unlocking" item.
Click to expand...
Click to collapse
Hello, sorry for the late reply. I have tried flashing TWRP on my SM-G9650 and this is what happened:
No error whatsoever, the phone (in DL mode) looks as if I didn't try flashing anything. I know the cable works because I just used it for backing up files and OEM Unlock is ticked in Dev settings. Thank you.
Here's pictures of the phone after trying to flash.
PS: I got the TWRP image from here, I think it's the one for my device.
FranGamer1892 said:
Here's pictures of the phone after trying to flash.
PS: I got the TWRP image from here, I think it's the one for my device.
Click to expand...
Click to collapse
Still not seeing the picture.
If the download completed, did you avoid rebooting into the system. If you just boot into system, the default Recovery image is simply re-installed and you're left back where you started. Once you complete downloading you need to reboot to Recovery and complete some addition steps. Check out:
[OFFICIAL] [TWRP] [SM-G9650] star2qlte/chnSM-G960/G965/0/U/U1/Android_10_Root_RMM_Forceencrypt_Remover_Add_US_Carriers_Fix_Safetynet_AIOI've used both methods to install TWRP and root my SM-G9600. If you're interested in gaining root access check out:
[KERNEL] [Q] [G9650] [G9600] klabit kernelNeed to acknowledge klabit87 for all the great work that he does for the Snapdragon versions!
RAExda said:
Still not seeing the picture.
If the download completed, did you avoid rebooting into the system. If you just boot into system, the default Recovery image is simply re-installed and you're left back where you started. Once you complete downloading you need to reboot to Recovery and complete some addition steps. Check out:
[OFFICIAL] [TWRP] [SM-G9650] star2qlte/chnSM-G960/G965/0/U/U1/Android_10_Root_RMM_Forceencrypt_Remover_Add_US_Carriers_Fix_Safetynet_AIOI've used both methods to install TWRP and root my SM-G9600. If you're interested in gaining root access check out:
[KERNEL] [Q] [G9650] [G9600] klabit kernelNeed to acknowledge klabit87 for all the great work that he does for the Snapdragon versions!
Click to expand...
Click to collapse
The problem is that the download didn't even seem to start in the first place. It's weird that the images can't be seen. I'll send them again. Thank you!
PS: All the images are after trying to flash
FranGamer1892 said:
The problem is that the download didn't even seem to start in the first place. It's weird that the images can't be seen. I'll send them again. Thank you!
PS: All the images are after trying to flash
Click to expand...
Click to collapse
First thing I noticed was the RPMB fuse blown and RPMB PROVISIONED. I don't remember seeing this when I tried to download awhile back.
This thread, quite old and for different device, but probably still relavant (Rpmb fuse blown - rpmb provisioned ) implies that RPMP fuse blown is expected but the PROVISIONED may imply that you don't have the current stock image? Are you currently on Android 10 with May 2022 security update?