Database Info

[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw)

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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05

reserved

Hallelujah!
Is this the eighth or ninth life of this great phone?

@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?

Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!

Nice job! Wich partitions can I mount as f2fs?

Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!

Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!

@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs

Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )

Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs

Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111

Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs

Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.

Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111

Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs

Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.

Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.

Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs

Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:

Current state of Nougat encryption

Since well functioning encryption seems to be a rarity these days, I decided to make a list for everyone interested in protecting their device. Majority of roms out there seem to have issues with it for some reason. Feel free to add in the comment section if you have tested other roms.
With "fully" working I mean that you can also mount /data with latest twrp (for e.g. omni currently fails in this regard). And please note that I mostly have tested the roms with everything EXT4.
FULLY WORKING
1. LinOs, tested 13.2. build
2. Slim7, tested 24.2. build
3. RR, tested 2.2. build
4. Tesla, tested 25.2. build
5. Validus, tested 25.2. build
CURRENTLY NOT WORKING
1. OmniRom
2. Nitrogen, tested 1.3. build
3. AOSP Extended
4. AOSPlusone
5. Android Open Source Project
list updated 6.3.2017
Any others? Please feel free to correct me if I'm wrong or if you have noticed that situation has changed.

I tried a fresh installation and encryption of RR onto my OPO and it wasn't a success; always responds that encryption was unsuccessful and had to end up wiping and re-installing. Can I ask what RR 7.11 release you were using so I can give that a try?
tofu said:
Since well functioning encryption seems to be a rarity these days, I decided to make a list for everyone interested in protecting their device. Majority of roms out there seem to have issues with it for some reason. Feel free to add in the comment section if you have tested other roms.
Currently, after testing Nitrogen, omnirom, AOSP extended, AOSPlusone, Android Open Source Project, LinOs, Slim7, RR 7.1.1, only the latter three have encryption working:
1. LinOs
2. Slim7
3. RR
Any others?
Click to expand...
Click to collapse

Deangus said:
I tried a fresh installation and encryption of RR onto my OPO and it wasn't a success; always responds that encryption was unsuccessful and had to end up wiping and re-installing. Can I ask what RR 7.11 release you were using so I can give that a try?
Click to expand...
Click to collapse
I found this (my old post): https://forum.xda-developers.com/showpost.php?p=70891641&postcount=3236
So if you find a build dated 5.2.2017 or earlier, it should work. At least mine did back then
But remember to format everything EXT4.

[ROM] [7.1.2][MARKW] ViperOS 3.1.1 Final by qwertyTom

ViperOS for markw is here!
Thanks to qwertyTom, karevn, Razziell, Anomalchik,TheScarastic for working on the source code for MARKW.
Kernel: Nosgoth V3 +
Security system from Dec'17
Current version 24/12/2017: Final
Highlights:
1) Beautiful animations.
2) Beautiful design.
3) Advanced functionality settings.
4) Shuster.
5) Very fast fingerprint scanner. (Personally, tester's fingerprint scanner fires very quickly, faster than on other OSes)
Changelog:<full>
Code:
24-12-17
-Final version
-Enabled camera2api (hal3)
28-11-2017
* kernel/xiaomi/markw/
5ccdc6f core_ctl: disable at config [Nikolay Karev]
5b37dcc DTS housekeeping [Nikolay Karev]
70a3c66 Merge branch 'core_ctl' into experimental_work [Nikolay Karev]
Downloads:
20171224-Server, MD5:
20171224-Gdrive
20171128-Gdrive
20171116-Gdrive
Original Thread: 4pda
Final update announcement!
Shared here instead of ROM section as sources are not disclosed.

Hello my Friend,
Please share screenshots for this ROM.

Mithrandir107 said:
Hello my Friend,
Please share screenshots for this ROM.
Click to expand...
Click to collapse
You'll find screenshots on 4pda thread.
I haven't tried this rom yet. In distant future, maybe. I'll post my own screenshots then, and move this thread on rom section.

Here you go...
Mithrandir107 said:
Hello my Friend,
Please share screenshots for this ROM.
Click to expand...
Click to collapse

How is battery life brother?

saravuthream said:
How is battery life brother?
Click to expand...
Click to collapse
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).

BJumperBR said:
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
Click to expand...
Click to collapse
Can you share the thread you followed for dual boot? Or write a thread on it? I've dual boot patcher apk, ends up booting into recovery every time I want to boot into secondary rom. If the ramdisk file of primary rom is modified, it also ends up booting into recovery.

I remember having some partition encryption issues when I first started using DBP and I had to format data/system partition to remove encryption.
As you can see from the screenshot I posted, I've been using all ROMs as "DATA" slots. Secondary ROMs don't work for me either.
kibria.mgk said:
Can you share the thread you followed for dual boot? Or write a thread on it? I've dual boot patcher apk, ends up booting into recovery every time I want to boot into secondary rom. If the ramdisk file of primary rom is modified, it also ends up booting into recovery.
Click to expand...
Click to collapse

BJumperBR said:
I remember having some partition encryption issues when I first started using DBP and I had to format data/system partition to remove encryption.
As you can see from the screenshot I posted, I've been using all ROMs as "DATA" slots. Secondary ROMs don't work for me either.
Click to expand...
Click to collapse
I have data partition formatted, phone shows not encrypted now. I'll try installing in data slot.
No extra tweaks are required then?

Just patch the ROM zip to a new data slot and flash it from TWRP.
And remember to patch all zip files you want to flash on the ROM (GAPPS, SuperSU/Magisk) to the same slot you used for the ROM.
kibria.mgk said:
I have data partition formatted, phone shows not encrypted now. I'll try installing in data slot.
No extra tweaks are required then?
Click to expand...
Click to collapse

Nice rom. But Vpapers did not work.

BJumperBR said:
Just patch the ROM zip to a new data slot and flash it from TWRP.
And remember to patch all zip files you want to flash on the ROM (GAPPS, SuperSU/Magisk) to the same slot you used for the ROM.
Click to expand...
Click to collapse
Many thanks. Applied rom in data slot booted up successfully.

BJumperBR said:
Here you go...
Click to expand...
Click to collapse
Thank you friend!

New 281117 build.
Download: Server, Gdrive
Changelog: <textfile>

hello,friend,can you help me to tell ZMIJGORYN something?i find Lineage OS 14.1 Extended one issue,can't set USB to Charge this device only work on Transfer files when i connect the mobile to computer,thanks a lot.And i waiting for him Lineage OS version

lovekobeme said:
hello,friend,can you help me to tell ZMIJGORYN something?i find Lineage OS 14.1 Extended one issue,can't set USB to Charge this device only work on Transfer files when i connect the mobile to computer,thanks a lot.And i waiting for him Lineage OS version
Click to expand...
Click to collapse
Have you checked the settings in Developers option? You can switch default usb option there.

kibria.mgk said:
Have you checked the settings in Developers option? You can switch default usb option there.
Click to expand...
Click to collapse
Yeah,i try it to solved that,thanks.

New 20171222 build is up, comes with hal3.
Download: server

BJumperBR said:
I can't say how's the battery life.
I just flashed this ROM and after flashing Magisk 12, Gapps and restoring some settings from Titanium Backup, I've got areally nasty overheating on my device and just went back to my previous ROM (AOSiP).
Btw, I've been using Dual Boot Patcher app to test all recent ROMS (RR, AoSiP, Validus...). Good app to switch between ROMs easily (screenshot attached).
Click to expand...
Click to collapse
Hi. Im new to flashing and I want to use the dual boot. Where can I download it and how can I use it? A thread for our device would be nice. Thanks

I tried to download the latest build from qwertytom.cloudapp.net but the site can't be reached. Is there another download link?

[ROM][7.1.2][UNOFFICIAL] AIM OS v2.5 for Lenovo A7600-F [MT6582][Port]

Hello to all you Lenovo A7600-F owners! I've Got yet another Android Nougat ROM ported to the Lenovo A7600-F Tablet! This one is very stable, smooth, and has the least bugs of any ROM i've ported to the A7600-F.
Android Version: AIM OS v2.5 (Android 7.1.2)
Security Patch Version: November 6, 2017
Kernel Version: 3.4.67 (kk)
First of all special thanks to:
-The AIM OS ROM team
-S M Nahid Emon (From romclaims.com for the portable MT6582 ROM)
Working:
-Wifi, Bluetooth, Root, Storage, etc...
-Camera (Pictures, Video)
-Youtube (Up to 720p30)
-Substratum Themes (Latest OMS Themes work great! Still smooth!)
-FM Radio
-GPS!
Not Working (kind-of):
-Camera video recording is laggy on default settings.
-FM Radio in loudspeaker mode (It only works in headphone mode)
-Let me know if you find something else.
Installation:
-Step 1: Don't download this ROM, I recommend you try this ROM instead. It is also ported by me but has far fewer bugs and has newer patches. Over a year later, I still see people installing this ROM ): Do yourself a favor and try out the newer one.
-Download Rom
-Download Gapps
-Backup your current ROM
-Flash ROM using TWRP 3.x.x.x
-Flash Gapps
-Reboot
Notes:
-To get brightness to change, turn off Adaptive brightness.
-Substratum seems to work best with root enabled (in Developer Settings) and after a reboot.
Downloads:
-TWRP Download
-ROM Download
-GAPPS Download (Choose ARM - 7.1 - pico or nano)
Emulated Storage Fix:
-For those of you who have wiped/formatted "Internal Storage" with my TWRP recovery, you will likely not have proper access to internal storage in this ROM. If you have internal storage issues try to flash this boot image to /boot with TWRP's builtin .img flash utility. Download storage fix image here.
Kernel Source: here
Changes:
-Revision 2:
Fix Storage issue (For people with physical internal storage).
Update Launcher to new Pixel Launcher 8.1 4429924
Removed unnecessary service startups related to SIM/Modem

SaberShip said:
Hello to all you Lenovo A7600-F owners! I've Got yet another Android Nougat ROM ported to the Lenovo A7600-F Tablet! This one is very stable, smooth, and has the least bugs of any ROM i've ported to the A7600-F.
Android Version: AIM OS v2.5 (Android 7.1.2)
Security Patch Version: November 6, 2017
Kernel Version: 3.4.67 (kk.......
Click to expand...
Click to collapse
Thank you so much.. Give your link so that we will donate you.. I will definitely try it. .. But could you try any other roms like resurrection remix or rom with android 8.0.. Anyway thanks a lot again

Really good work. Thank you very much. This ROM is a new Life for this device. I have flashed a while ago and I'll test It this afternoon.

Hello. @SaberShip, I'd like to build RR on this tablet. Where can I find the device and the kernel source code for this device? Is it tough to build?
Thanks

Srisri7 said:
Thank you so much.. Give your link so that we will donate you.. I will definitely try it. .. But could you try any other roms like resurrection remix or rom with android 8.0.. Anyway thanks a lot again
Click to expand...
Click to collapse
In regards to the Resurrection Remix: I'll look into it. Iv'e got a Resurrection Remix rom running but its got some issues that need fixed.
pacorrop said:
Hello. @SaberShip, I'd like to build RR on this tablet. Where can I find the device and the kernel source code for this device? Is it tough to build?
Thanks
Click to expand...
Click to collapse
Lenovo has the source on their developer pages I believe. I have not even messed with the source though, I've also heard that it might not be complete.

SaberShip said:
In regards to the Resurrection Remix: I'll look into it. Iv'e got a Resurrection Remix rom running but its got some issues that need fixed.
Lenovo has the source on their developer pages I believe. I have not even messed with the source though, I've also heard that it might not be complete.
Click to expand...
Click to collapse
Ok cool! Thanks for that. I'll give it a try.
Anyway, given that you're trying to build RR as well... may I ask you where to find this needed stuff? I mean, I'll download the sources from Lenovo (which are for KitKat, according to their website); but you're not using these sources for RR and Nougat, right? Where can I find the sources you are using? Ahh or you may be using compiled kernel and device blobs, right?
Sorry for the off-topic; if further conversation is needed, I'll write you a PM instead.
Thanks again

pacorrop said:
Ok cool! Thanks for that. I'll give it a try.
Anyway, given that you're trying to build RR as well... may I ask you where to find this needed stuff? I mean, I'll download the sources from Lenovo (which are for KitKat, according to their website); but you're not using these sources for RR and Nougat, right? Where can I find the sources you are using? Ahh or you may be using compiled kernel and device blobs, right?
Sorry for the off-topic; if further conversation is needed, I'll write you a PM instead.
Thanks again
Click to expand...
Click to collapse
Nope! Im just porting Roms right now. Which is to say, i'm taking Roms already built for other devices with the same SOC (MT6582 in this case) and doing whats needed to convert them to run well on the A7600-F.

No bugs so far, aside from weird background noise - every time I click something, like a playing audio file but with no sound for 3 seconds, speaker goes on and off..

/sdcard is not well mounted
First, thanks for your greeeaaat job !!! I've beginning to install 6.01 and now i try this version 7.1.2?
I've an error with quasi all apps i've installated (ex : EZ Pdf reader, SyncDrive). The error is /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message)
And, indeed, with ES File Explorer, when i click on /sdcard, it show an error...

Yes, I have this error too. If I try to download a file with chrome, it can´t because there is no sdcard

freddie2000 said:
Yes, I have this error too. If I try to download a file with chrome, it can´t because there is no sdcard
Click to expand...
Click to collapse
It happened to me.. Try another browser
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
Almironi said:
No bugs so far, aside from weird background noise - every time I click something, like a playing audio file but with no sound for 3 seconds, speaker goes on and off..
Click to expand...
Click to collapse
Yeah.. This is happening to me also.. I have tried various mods but couldn't solve it.. And also there is too much distortion when volume is high..

Can some one port this rom to A7600-F..rr rom 7.1.2 (bugless)
http://www.techonarena.com/resurrection-remix-5-8-5-n-rom-for-mt6582/?i=1
5.1.1 bugless rr.. I wanted to try lollipop on this device.
http://mtk65roms.blogspot.in/2016/02/bugless-resurrection-remix-for-mt6582.html?m=1

coucout said:
First, thanks for your greeeaaat job !!! I've beginning to install 6.01 and now i try this version 7.1.2?
I've an error with quasi all apps i've installated (ex : EZ Pdf reader, SyncDrive). The error is /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message)
And, indeed, with ES File Explorer, when i click on /sdcard, it show an error...
Click to expand...
Click to collapse
Seems like the usual storage bug, I've run into this as well, I'll work on a fix and release an update soon hopefully.

Two new [mt6582] roms on romclaims:
Viper-OS v3.1.1
Colt-OS v1.3

Almironi said:
Two new [mt6582] roms on romclaims:
Viper-OS v3.1.1
Colt-OS v1.3
Click to expand...
Click to collapse
Thanks, saw these earlier too. But, what ones do we want more, Resurrection Remix or one of those? Let me know.

Port Revision 2
Updated the ROM to hopefully fix the storage issues. Check the OP for full changelog/download link
Please test and let me know if it helps!

SaberShip said:
Thanks, saw these earlier too. But, what ones do we want more, Resurrection Remix or one of those? Let me know.
Click to expand...
Click to collapse
AIM OS rom suits me best for now, till the new lightweight oreo go edition arrives

Internal storage error
SaberShip said:
Updated the ROM to hopefully fix the storage issues. Check the OP for full changelog/download link
Please test and let me know if it helps!
Click to expand...
Click to collapse
THX for the fast error fixes, but the internal storage error is still exist (in chrome /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message), when connect the tablet to the computer, no internal storage space). In TWRP when connect, the internal storage exist, you can copy files.

szelezola said:
THX for the fast error fixes, but the internal storage error is still exist (in chrome /sdcard doesn't exist or "cannot access /sdcard". The integrated file explorer within the rom itself cannot open (no error message), when connect the tablet to the computer, no internal storage space). In TWRP when connect, the internal storage exist, you can copy files.
Click to expand...
Click to collapse
Thanks for the info. Strange, mine seems to work just fine. Iv'e tried from Chrome, built in storage manager, other storage managers, and over USB. They all seem to work fine for me.
Have you ever wiped data AND internal storage with TWRP? Perhaps the TWRP I ported isn't properly formatting the internal storage, this is one thing I haven't done since having stock on my tablet. I'll try it soon.

SaberShip said:
Thanks for the info. Strange, mine seems to work just fine. Iv'e tried from Chrome, built in storage manager, other storage managers, and over USB. They all seem to work fine for me.
Have you ever wiped data AND internal storage with TWRP? Perhaps the TWRP I ported isn't properly formatting the internal storage, this is one thing I haven't done since having stock on my tablet. I'll try it soon.
Click to expand...
Click to collapse
Yes I do, format-wipe everything (internal storage to). I use the TWRP in your OP message.

[ROM][UNOFFICIAL][9.0][MIDO] AospExtended 6.7

Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
AospExtended 6.7
Properties
Selinux mode: Enforcing by default
Build type: user
Gapps: not included
Known issues
Some users report non-functional mobile data after clean flash, reportedly works after manually adding APN or dirty flashing from Official AospExtended build
Notes
Dirty flash from Official ROM not tested, backup EVERYTHING before flashing!
Downloads
21.1.2020
Download
Checksum: a83c665feace3066580f2344af38fc1d
Older builds
14.12.2019
Download
Checksum: f44bdbc961fe2b64a281ec0785975f21
23.11.2019
Download
Checksum: a4043774306c86b3968c826b9ca1ba98
13.10.2019
Download
Checksum: d85208f4ead011dc0e9488b9591ac5d6
Working apps
OpenGapps
MicroG
Magisk
JamesDSP
Sources
ROM
Device tree
Kernel
Vendor
Credits
AospExtended team - ROM
dotOS team - device sources
@gadmei.tw - mobile data fix
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][MIDO] AospExtended 6.7, ROM for the Xiaomi Redmi Note 4
Contributors
Golbinex
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AospExtended
Version Information
Status: Stable
Created 2019-11-02
Last Updated 2020-02-04

Reserved
Changelog
21.1.2020
January security patches
14.12.2019
December security patches
23.11.2019
November security patches
Mobile data tryfix - @gadmei.tw
13.10.2019
Initial build
October security patches

Dirty flashed from AospExtended Official without issues.

:laugh:tks, :good::good:
Only upgrade OCT security patch on offical AEX Rom-0822-mido , right?
i will guess AEX 7.0(Android 10) release stable ver. in Jan 2020:laugh:

Any changes
Changelog

grvkrsaini said:
Changelog
Click to expand...
Click to collapse
3rd post above yours.

gadmei.tw said:
:laugh:tks, :good::good:
Only upgrade OCT security patch on offical AEX Rom-0822-mido , right?
i will guess AEX 7.0(Android 10) release stable ver. in Jan 2020:laugh:
Click to expand...
Click to collapse
Device sources are also different because official ones aren't updated at all, so maybe kernel version and behaviour will be little different.

martinknl said:
Dirty flashed from AospExtended Official without issues.
Click to expand...
Click to collapse
Same here. Rom works great and latest security patch is included. Thanks @Developer

A very good rom
Hello,
I've tried this rom, and it's a good idea , it' works fine !
Very thanks for the developers.

Great ROM
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?

WareWareX said:
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
Click to expand...
Click to collapse
OTA is generally not included in unofficial build

WareWareX said:
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
Click to expand...
Click to collapse
Updates will be available in this thread, there will be probably one update per month.

Audio playing on multiple outputs
Hi All,
Firstly thank you very much for providing this ROM with the latest security fixes - everything important is working fine and I have also better battery life than in the AOSP Extended 8 ROMs.
However I have one problem that did not exist in the previous ROM. I use AirAudio (in combination with the Magisk AirAudio module) to stream any sound from the phone to a DLNA audio output. Usually when I activate the AirAudio streaming the sound on the phone stops and the output is redirected to the DLNA speaker. In this ROM though the audio plays on the phone and also on the DLNA speaker.
I contacted the AirAudio developers and they responded that this is a problem with an incorrect audio implementation in the custom ROM I'm using as they have seen this before. This is what they wrote:
-------
I assume you have a custom ROM, eg. Pixel Experience installed?
There are some ROMs around at the moment that have a broken implementation of the audio-driver.
Android-devices MUST only play the audio locally _or_ remote via AirAudio, this is defined by Google.
I think you have to wait for an update of your ROM or switch to another ROM like others did :-/
-------
Is this something that could possibly be taken into consideration for a future update as this means I cannot stream audio from all sources (e.g radio apps and Spotify)to any DLNA output.
I really like AOSP Extended and would rather not switch to a different ROM.
Many thanks,
herges

herges said:
Hi All,
Firstly thank you very much for providing this ROM with the latest security fixes - everything important is working fine and I have also better battery life than in the AOSP Extended 8 ROMs.
However I have one problem that did not exist in the previous ROM. I use AirAudio (in combination with the Magisk AirAudio module) to stream any sound from the phone to a DLNA audio output. Usually when I activate the AirAudio streaming the sound on the phone stops and the output is redirected to the DLNA speaker. In this ROM though the audio plays on the phone and also on the DLNA speaker.
I contacted the AirAudio developers and they responded that this is a problem with an incorrect audio implementation in the custom ROM I'm using as they have seen this before. This is what they wrote:
-------
I assume you have a custom ROM, eg. Pixel Experience installed?
There are some ROMs around at the moment that have a broken implementation of the audio-driver.
Android-devices MUST only play the audio locally _or_ remote via AirAudio, this is defined by Google.
I think you have to wait for an update of your ROM or switch to another ROM like others did :-/
-------
Is this something that could possibly be taken into consideration for a future update as this means I cannot stream audio from all sources (e.g radio apps and Spotify)to any DLNA output.
I really like AOSP Extended and would rather not switch to a different ROM.
Many thanks,
herges
Click to expand...
Click to collapse
I only compile unofficial builds. You can try to contact AospExtended devs, but mind that Pie entered final state and they're focusing on Android 10 now. However if the problem can be fixed with some simple patch in sources and it wouldn't affect anything else in negative way, I am willing to apply it to my builds.

Mobile data is not turning off from QS. I have to click airplane to switch it off completely.

I dirty flashed this ROM over official build yesterday and everything was fine, but today I was just checking out LOS 17, and then decided to roll back to this ROM, so I clean flashed this ROM, but after clean flashing the mobile data wasn't turning on.
And my SD card wasn't getting detected either. It lead to a lot of mess because I was not able to flash the official build either which was also in the SD card, I can't connect my phone to computer either because the USB port of the phone is bit defected, when I did managed the SD card to get detected, the recovery wasn't installing the official build. I tried to install los17 again and it worked.
Right now I am using los 17 and I would really like to go back to aex pie (official or unofficial) can someone help?

Golbinex said:
I only compile unofficial builds. You can try to contact AospExtended devs, but mind that Pie entered final state and they're focusing on Android 10 now. However if the problem can be fixed with some simple patch in sources and it wouldn't affect anything else in negative way, I am willing to apply it to my builds.
Click to expand...
Click to collapse
Hi,
I went and installed the official ROM and there the audio routing using AirAudio works correctly so something must have got broken when you recompiled this using the latest security fixes.

mobihack said:
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
Click to expand...
Click to collapse
It works for me, make sure you don't have any app with root access, which can block it.
BlackWhale2108 said:
I dirty flashed this ROM over official build yesterday and everything was fine, but today I was just checking out LOS 17, and then decided to roll back to this ROM, so I clean flashed this ROM, but after clean flashing the mobile data wasn't turning on.
And my SD card wasn't getting detected either. It lead to a lot of mess because I was not able to flash the official build either which was also in the SD card, I can't connect my phone to computer either because the USB port of the phone is bit defected, when I did managed the SD card to get detected, the recovery wasn't installing the official build. I tried to install los17 again and it worked.
Right now I am using los 17 and I would really like to go back to aex pie (official or unofficial) can someone help?
Click to expand...
Click to collapse
I think you broke your firmware partition so network drivers (wifi, mobile data) don't work. Try to flash official xiaomi firmware (not ROM). https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917
herges said:
Hi,
I went and installed the official ROM and there the audio routing using AirAudio works correctly so something must have got broken when you recompiled this using the latest security fixes.
Click to expand...
Click to collapse
This ROM is different than official one, because it has different device sources, the issue is caused by dotOS device sources. You can try to contact devs of some ROM where AirAudio works and ask them how they fixed it or use official one.

Golbinex said:
I think you broke your firmware partition so network drivers (wifi, mobile data) don't work. Try to flash official xiaomi firmware (not ROM). https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917
Click to expand...
Click to collapse
I think firmware does not get affected when ROM is changed/messed with, also the mobile data was working when I was using the los 17 (which I flashed after this rom wasn't turning on the mobile data).
I did a lot of things that I don't remember now (rebooting into recovery couple of times helped with the sd card detection issue), but in the end I was able to clean flash the official build with opengapps.
I can't be sure but I think bitGapps is responsible for this mess, which I used with LOS 17.
The order of ROMs on my phone from yesterday is aex official (everything fine)> aex unofficial (fine)> los 17 (I think the problem started here when I flashed bitGapps)> aex unofficial (no mobile data)> los 17 (mobile data works)> aex official (everything fine).
Thanks anyway for your help.

mobihack said:
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
Click to expand...
Click to collapse
For me, mobile data is not turning on
---------- Post added at 10:46 PM ---------- Previous post was at 10:30 PM ----------
BlackWhale2108 said:
I think firmware does not get affected when ROM is changed/messed with, also the mobile data was working when I was using the los 17 (which I flashed after this rom wasn't turning on the mobile data).
I did a lot of things that I don't remember now (rebooting into recovery couple of times helped with the sd card detection issue), but in the end I was able to clean flash the official build with opengapps.
I can't be sure but I think bitGapps is responsible for this mess, which I used with LOS 17.
The order of ROMs on my phone from yesterday is aex official (everything fine)> aex unofficial (fine)> los 17 (I think the problem started here when I flashed bitGapps)> aex unofficial (no mobile data)> los 17 (mobile data works)> aex official (everything fine).
Thanks anyway for your help.
Click to expand...
Click to collapse
Mobile data does not work only with this rom.
Flashed Pixel Experience and mobile data worked. Flashed AEX unofficial again and it doesn't.