Database Info

(ROM) Cyanogen 7 RC 2 Unofficial Release Updated 3/8/11

Sorry can't post in dev section yet but drod was nice enough to let me get my hands on cyanogen mod 7 release candidate 2 and said I could share. This is not an official release and not supported yet. To flash place zip on internal sd boot in clockwork wipe data and install zip.
I used clockwork .08
Update: fix for internal sd problem
Credit goes to drod2169
Updated Install
www.mediafire.com/?usumbwxusn8vnzj
Here is a link to the gapps for Gingerbread that gives full market out of the box
I installed the rom first and let it boot up then went back in clockwork and installed gapps. Don't know if it matters.
http://goo-inside.me/gapps/latest/7/universal/

When you say the internal SD doesn't work, do you mean it doesn't show up at all? Or could it possibly be /mnt/emmc?
Roadzero said:
Sorry can't post in dev section yet but drod was nice enough to let me get my hands on cyanogen mod 7 release candidate 2 and said I could share. This is not an official release and not supported yet. only problem I saw is the internal sd doesn't work. To flash place zip on internal sd boot in clockwork wipe data and install zip. Clockwork sees the internal sd just not cm 7.
Sorry can't post links yet
w w w dot mediafire dot c o m /?wxbtl23g46vxvho
Click to expand...
Click to collapse

Anyone tried this yet?

Went thru the archive, seem genuine, I may give it a try later, I'll post mileage...

Lets make this easy: http://www.mediafire.com/?wxbtl23g46vxvho

Up and running as I type. Looks really nice. Put soft buttons on status bar which will help me at night not having to feel for the home and back buttons on the side since they don't illuminate. Market is full and working quite nicely as it backed up all of my purchases and dl's right away.
Only thing not working for me so far is the docking station. Still a nogo. Just came off of bitrix to try this......
Well done!!!

dezufnoC said:
Up and running as I type. Looks really nice. Put soft buttons on status bar which will help me at night not having to feel for the home and back buttons on the side since they don't illuminate. Market is full and working quite nicely as it backed up all of my purchases and dl's right away.
Only thing not working for me so far is the docking station. Still a nogo. Just came off of bitrix to try this......
Well done!!!
Click to expand...
Click to collapse
FruitLoop here, even after wipe... curious... retrying...
Tried wipe, removing SDHC cart, reflash still a FruitLoop oh weel back to
my trial of Calkulin's G-Tab v1.0 [ 3991 l Battery Saver script w/ Profiles
which boot...

P00r said:
FruitLoop here, even after wipe... curious... retrying...
Tried wipe, removing SDHC cart, reflash still a FruitLoop oh weel back to
my trial of Calkulin's G-Tab v1.0 [ 3991 l Battery Saver script w/ Profiles
which boot...
Click to expand...
Click to collapse
Odd it worked fine for me coming out of vegan 5.1.1 just by wiping data. you could try wiping system or re downloading the zip

Where is the recovery folder? I downloaded the update...... .zip folder and it wouldn't load the rom, CWmod said it was "bad"

tomgillotti said:
Where is the recovery folder? I downloaded the update...... .zip folder and it wouldn't load the rom, CWmod said it was "bad"
Click to expand...
Click to collapse
What version clockwork are you using? I used .08

Installed this last night from a link he sent on twitter. Think its the same version. Only issue i see so far is my sdcard is not showing up. I get sdcard for internal memory but not for my actual card. A message comes up when I insert it saying that one was inserted then it says its safe to remove. Not sure how to mount it. I don't see it in /mnt either.

P00r said:
FruitLoop here, even after wipe... curious... retrying...
Tried wipe, removing SDHC cart, reflash still a FruitLoop oh weel back to
my trial of Calkulin's G-Tab v1.0 [ 3991 l Battery Saver script w/ Profiles
which boot...
Click to expand...
Click to collapse
Calkulin has a nice format all zip (see first post here)that you flash like a rom before flashing a new rom. works good only 1 step instead of many. only thing it doesn't seem to format is Delvik so that has to be done manually but it cuts out a few steps in the rom prep work.

This rom has the same shape icons in the right corner as the vegan roms and the same notification icons as cm rc2. The mounts are sdcard and emmc for external. The res has been changed so some apps wont scale properly. If it wasn't for that I would have kept using it because I prefer the minimal notification icons compared to vegans experimental new icons.

qubit76 said:
This rom has the same shape icons in the right corner as the vegan roms and the same notification icons as cm rc2. The mounts are sdcard and emmc for external. The res has been changed so some apps wont scale properly. If it wasn't for that I would have kept using it because I prefer the minimal notification icons compared to vegans experimental new icons.
Click to expand...
Click to collapse
On my tab the internal storage is mapped to /sdcard while /emmc is empty. my external (actual) sdcard is nowhere to be found. settings-storage shows the sdcard as having 13.07gb total. my actual sd card is 4gb so this is confirming its actually the internal memory. All the Vegan roms showed my sdcard as mounted at /sdcard2. was just curious as to how I should go about mounting my sdcard so i can access it? I have no issues with this memory mounting setup just curious how to get my card to be mounted. Can i type something in a terminal to mount it?
I realize that the vegan series is a moddified version of cm and this is an attempt to be true cm tweaked to run on our tabs and that some things are gonna be different. So if I am missing something with the sdcard mounting please let me know. I think Drod2169 does great work and have loved rubix on my X for months now.

I jumped on this rom from Bitrix and my sd card reads exactly the same as it did before as sdcard while my internal is emmc. It seems as if it's not liking the change from your previous association to this new association of internal/external storage. Were you using a pre-Gingerbread rom before? If so check out this link for the association of storage files...this may help
I also use rootexplorer and have no problems accessing/copying/moving files etc.

I was on Calkuins beta, then wiped and installed vegan ginger experimental 3/8/11. After it started and loaded apps from market Drod2169 sent me a link to this one on twitter so I wiped and installed this. Maybe that the kernel didn't install right our something.will try to redownload and try again.
Sent from my DROIDX using Tapatalk

Unofficial? So it isn't really Cyanogen 7 RC 2 then. Just saying.

adampdx said:
Unofficial? So it isn't really Cyanogen 7 RC 2 then. Just saying.
Click to expand...
Click to collapse
It is cm 7 rc2 I say unofficial release because it may be changed slightly before they officially announce its release. If you don't want it you don't have to use it, I just thought I would post it for people that do.

So. It turns out that if I knew how to read I could have fixed my problem a while ago. The first post says right on it that it was updated to fix sdcard problem. The version I had was from before this "fix". Downloaded updated one and installed. All is well. Market seem good so far all items are mounting speed seems good. Don't use youtube so cant comment on video but flash works on the sites i've tried it on. Thanks Drod2169 for giving us some more of your time.

I'm curious as I've ran bittrix's unofficial and several of gojimi's Ginger vegan. Do installed apps show up on the market under My Apps? On every other Ginger rom I've tried, Market-My Apps just shows nothing. Love gingerbread but it makes it a pain trying to keep apps up to date. Also does purchasing work, or does vending FC when trying to?
Thanks

CM12.1 for Huawei Honor 3C

This is the link to the guide for flashing cm 12.1 on our Honor 3C - H30-U10. I don't own any of these builds or fixes, i just wanted to make this thread so that these things are easily available to people who CRAVE for Cyanogenmod on their honor 3c devices like me and ask for some help regarding the installation of apks. http://www.carbontesla.com/2015/08/install-honor-3c-cyanogenmod-12-1-lollipop-custom-rom-unofficial/
this is the link to the various builds of cm 12.1 https://cloud.mail.ru/public/3SBd/vVnPaUJ4C/ , however the one which has 20150923 in its name doesn't seem to boot up after flashing so i have flashed the one with 20150309 in its name which boots up fine and works pretty well.
Flash the Gapps also for the play store and google play services to work. Here is the link for it - http://www.carbontesla.com/download-google-apps-gapps/
Now, i tried PA Gapps mini and cyanogen 12.1 Gapps but they didnt work for me but AFH Gapps did work. You guys can try the former ones as there might have been some issue at my side.
The IMEI lost problem is there which can be solved by either restoring IMEI numbers using MTK or this zip http://1drv.ms/1FNtZUj. This may not be a permanent fix and the SIM not detected error may start showing up after a reboot but, it can be fixed by re-flashing this zip at recovery OR another rather stupid looking workound XD XD by turning on the airplane mode before rebooting and then switching it off after the boot up has finished.
I couldn't find the "Select default storage option" in the storage settings nor could i find the select preferred app installation location option in the Apps settings, so i found a workaround for linking the /sdcard in the root folder to /storage/sdcard1. Here is the script for it which has to be run everytime after booting the device in the terminal emulator:
1. first gain root privileges by entering su int the terminal.
2. type: mount -o bind /storage/sdcard1 /sdcard
That's it!! Now the default storage is your external sd card, one drawback of this is that you can't access the internal storage. If you want to access it, reboot your device and everything will revert back. if you want to set the default storage to the ext sd card, follow the above steps again.
THE PROBLEM: Apparently apks dont get installed most of the times even after enabling Unknown sources in the developer options, i don't know if this is the problem of google services or something, i would like someone to help out with this issue.
EDIT 1: The one which has 20150923 in its name boots up just fine, it needs more than one time dalvik cache deletion and factory resets.

Thanks for sharing ... some upgrade or new information in the last days...

This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs

Nothing new has happened mate
internauta2000 said:
Thanks for sharing ... some upgrade or new information in the last days...
Click to expand...
Click to collapse
No new updates have been release
I'll check the builds again and report back if i find any fixes for the bugs ASAP

Thanks for notifying!
Rayquaza said:
This rom has several bugs. The only one version i still prefer to use is 151129 version
The latest 151202 doesn't booting after flash. Seems there's something wrong with boot.img
Anyway, i wish the developers will keep research and improve this rom to fix the bugs
Click to expand...
Click to collapse
could you please provide the link for these builds? these couldn't be found on cloud.ru site

CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520

Great WORK!!
kernel.killer said:
CM 12.1 ROM Development:
http://forum.xda-developers.com/android/development/rom-cyanogenmod-12-1-port-huawei-honor-t3307520
Click to expand...
Click to collapse
Your Thread is amazing! Great work @kernel.killer !! Love your work! The ROM worked perfectly on my phone after flashing the modemFix zip

[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:

[GUIDE] HOW To Multiboot on Lenovo P2

Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!

so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?

tanush said:
so my P2c72 is on the way, you think it's not supported? Isn't everything the same except for the internal space? I was planning to flash the official P2a42 ROM anyways.
Thoughts?
Click to expand...
Click to collapse
I don't think, I'm sure it's not supported because I put the codenames on github and P2c72 is not in the list. No problem if you want to multiboot I'll add it in no time. You can flash all the roms available here for p2a42 on your P2c72 just fine by removing the first lines "assert get prop" in the updater-script. You can flash these roms the usual way via twrp. But if you use the DualBoot Patcher as for now it won't recognize the P2c72.

911-Future_Maker said:
I don't think I'm sure it's not supported because I put the codenames on github and P2c72 is not on the list. No problem if you want to multiboot I'll add it in no time.
Click to expand...
Click to collapse
Cheers! My phone is on the way from china. Might be another week or so Right now just browsing everything that we have here.
Thanks for this. After so many ROMS ported recently, this would really help me out with having one stable daily driver and others to try to. Not an android developer but I'd like to try my hands as well finally to make a ROM and maybe look into the two bugs that are persistent across all ROMS. Let's see. I've just developed apps for now.
Anyways, thanks, this is indeed good stuff.

Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?

911-Future_Maker said:
Yes, I love this app. It's the future of Rom's flashing, just switching between Roms like a boss. Btw congrats you bought the P2c72, it's 64gb right?
Click to expand...
Click to collapse
yes, thats the only reason I had to get it from china. Apparently, only 32 gb version is available outside china.

Thank You Bro

Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!

911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?

tanush said:
thanks, waiting for the bootloader to get done with its 15 days. All ready to flash everything!
Although can you tell me how it works? Like my phone is flashed with the global p2a42 ROM but it is p2c72. Should I change the name in build.prop?
Click to expand...
Click to collapse
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.

911-Future_Maker said:
Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
911-Future_Maker said:
This is why I made this tutorial, just follow it closely and all will be fine. You don't need to mess with the build.prop.
Click to expand...
Click to collapse
Sorry brother didn't go through as I can't actually do it. Still waiting on my bootloader :/

So anyone had any success with p2c72?
I tried, but it fails. Doesn't throw any error but gets stuck in the boot and eventually reboots in twrp.
My only doubt is how does it know that the phone is p2c72? The build.prop says p2a42 so does the app thinks that its p2142 and wrongly patch it?

Is this just for experimenting or is there any advantage using 2 os same time? Isn't this can be cause a heat problem because of the more cpu/ram usage?

Can't find supported version of app! Can anyone here help me out wuth version?
---------- Post added at 04:29 AM ---------- Previous post was at 04:20 AM ----------
911-Future_Maker said:
Hi guys I'll share with you how to multiboot roms on Lenovo P2 using an app called DualBoot Patcher.
Currently I'm using 3 roms, they're simultaneously installed on my phone and all I need to switch the rom is a single tap via the app we'll discuss below.
The roms I have installed right now:
-S062_170117_ROW as primary
-RR 5.8.2 as secondary
-S232_170320_ROW as data-slot
As you may already think about it, yes having 3 roms or more installed on your phone is eating your internal storage a bit.
Check the shots attached below for all the storage details for each Rom. I currently have 12GB free on the internal storage.
---
Okay let's start with the tutorial.
Requirements:
-Root
-Unlocked Bootloader
First of all I want to say Big Thanks to the developer of the DualBoot Patcher @chenxiaolong. Feel free to visit the official thread of the app, say/press thanks and if you're good even donate to him.
Also you can thank me for adding our great device Lenovo P2 to the supported devices. I opened pull request on GitHub that is already processed.
I'll start with the steps of my tutorial:
1)
The first thing of course is to download the app from it's official page
As of the time this guide is written make sure to download the build 9.2.0.r8.g4da14ed or newer as the older builds don't support Lenovo P2. Currently only the P2a42 model is supported, if there is interest from a P2c72 owners I'll add a pull request on GitHub.
2)
You have the apk, install it and set the kernel when the app asks you. Good thing is to update the ramdisk of the primary rom, but you still can multiboot even if you didn't. You can force update the ramdisk by hitting the update ramdisk button 3 times. Always reboot after setting kernel or updating the ramdisk.
3)
Now I assume you have the zip file for the other rom. Select "Patch zip file" from the side menu and choose where to install it. You have a choice of:
-Primary Rom Upgrade (not recommended, it will override your primary rom! For security reasons can only be selected from a rom different from primary.)
-Secondary (I recommend this if you wish to use only 2 Roms, the rom will be installed on the same partition as the primary rom, it won't affect the internal storage. Only the data will be on internal. The system partition of P2 is 3.87GB and you can put 2 roms there easily.)
-Multi-slot (not recommended, suitable for phones with large cache partitions, 1.5-2G)
-Data-slot (this will affect your internal storage, system and data on internal, reliable option if you use 3 or more roms.
-Extsd-slot ( the rom will be installed on your extsd card! Yeah you hear me, an awesome feature, but unfortunately kind of unstable, you have issues here and there and also you have slightly decreased performance as you're running the rom from your sdcard which is several times slower than the internal storage unless you're running one of the most expensive extsd cards.
Select secondary or data slot, choose a save path and patch the rom.
4)
Install the rom. Easy as it sounds. Press the pink button in bottom right, press it once again and select the rom you patched in the previous step. As you can see you can even restore a backup made with the app. It's not for restoring a twrp backup. You can backup roms within the DualBoot Patcher. Also you can flash roms patched with this app in twrp. Choose where to install it or leave it as it is and press the ✓ button in up right. The rom will be flashed.
Important! Don't switch to another app or do anything else when the rom is being installed, otherwise the patcher will crash! 1-2 minutes and you're done, not much of a waiting.
5)
Hey you made it. You now have 2 roms simultaneously installed on your phone! When you install a new rom the patcher will automatically switch to it. That doesn't mean it will auto reboot to the new rom, it will just switch to it in the Roms list, you can always switch to the primary or other rom again. I think that's pretty much about it guys. Now just switch to the new rom and select reboot from the side menu of the patcher, it will reboot to the new rom. You can repeat the procedure as many times as you want.
My record is 8 Roms, that was in the past with other phone. Because of this crazy number I'm a proud winner of the gold medal for the "Most number of multiboot roms installed lmao.
If you have questions feel free the write below and as always hit thanks if I was helpful. See ya. :highfive:
Update: Starting from build 9.2.0.r54.g8b79a2b the patcher now supports the P2c72 too!
Click to expand...
Click to collapse
Not able to find the version as mentioned. Tried newer version but not supported.

Multuboot log uploaded.

What to do for setting up kernel in 2nd step?

Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it

muniphs said:
Hi , dual boot patcher app crash every time whenever I try to flash patched ROM in ROM section .pls help me with that .I really want it
Click to expand...
Click to collapse
Try different version.

kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse

muniphs said:
kanwaljeetsm said:
Try different version.[/QUOTE
Thanks for reply
I tried these both versions
DualBootPatcherAndroid-9.2.0.r54.g8b79a2b
And
DualBootPatcherAndroid-9.2.0.r8.g4da14ed
These are recommended on this thread
Is there any other supported version for our model
Click to expand...
Click to collapse
I had tried r201.
Click to expand...
Click to collapse

[DISCUSSION] LineageOS 17.1 [HLTE/CHN/KOR/TMO][OFFICIAL]

Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator

Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?

asassello said:
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
Click to expand...
Click to collapse
1 : yes
2 : yes..update maybe your modem

re 1: yes2 (using it quite some time on various devices and it seems to do what I expect it should do, though some apps seem to bypass the 'normal' DNS resolution. OT: And I'm still haven't made up my mind yet if DoH or DoT are good or bad ...)
re 2: dark mode? What's that?

rayman95 said:
1 : yes
2 : yes..update maybe your modem
Click to expand...
Click to collapse
Are you sure NFC works? I mean paying in shops? I updated modem and now it's N9005XXUGPQB1. And paying still doesn't work. I've just tried.
odoll said:
re 2: dark mode? What's that?
Click to expand...
Click to collapse
Sorry. It's dark theme (I don't have English set as default language). [emoji846]

installation error

https://download.lineageos.org/hltetmo

Can somebody please confirm that paying through NFC works? If so - what's your modem and baseband?
Also I've installed GAPPS PICO maybe that's the case? Although on LOS 16 I also had Pico and it worked, but maybe I'm missing some app like Google search or something?

Been using Lineage OS 16 ever since it was officially released for HLTE. I gotta say, the development of that release has came a long way and by the time of writing this, I'd say it's the most stable and clean custom rom for the Note 3 out there.
I did try the new release the second I received a notification for an update. How did it go? Well let's just say I'm glad I created a full system backup before wiping LOS 16. This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
I do appreciate all of the time that the devs are still willing to put into the platform. However I'd recommend users that are looking for a rock stable experience to stick with Lineage OS 16 for the time. You're not missing out on a lot.

loudseries said:
This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
Click to expand...
Click to collapse
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx

odoll said:
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
Click to expand...
Click to collapse
I have to agree with you, because except my 2 issues (with NFC payments and night mode that doesn't switch automatically) I actually don't have any other problems.
Ver. 17 seems faster and snappier than 16.
Also on 16 sometimes sharing from ie. Firefox to WhatsApp caused the later one not loading (just black screen).
So for me only that NFC seems to be a real issue. Other than that I'd advice anyone trying 17.

made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...

rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
for me the only difference is the size of the home screen changed (changed trebuchet to a larger grid before), otherwise i would not even have noticed it is not 16 anymore, rock stable even after a dirty flash

rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect.
Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?

Scorpionea said:
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect. Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Click to expand...
Click to collapse
I'm on PQB1 nordic modem and BRL1 bootloader.

rayman95 said:
I'm on PQB1 nordic modem and BRL1 bootloader.
Click to expand...
Click to collapse
Have the same as you . I thought it could be bootloader issue but guess not.
Thx

Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...

odoll said:
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Click to expand...
Click to collapse
Hello. I have the latest version of LineageOS 16 installed and TWRP (3.3.1.0). I ask you if, after transferring the ROM file to the phone, it is possible to use TWRP to upgrade to 17.1 (by installing the zip file) or if I have to use ADB shell (as it says on the LineageOS official site).
Sorry I'm not an expert and some steps are not clear to me
Thank you
PS
Why you wrote "dirty"
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.

Hi Apten
i) think your Qs won't need a full quote
ii) drity flashing
iii) sure you can DL the ROM (and TWRP) to your (internal RAM) of your phone and upgrade or clean install from recovery (twrp)

rayman95 said:
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
Click to expand...
Click to collapse
I've just dirty updated from 1010 to 1017 build . Will see how it goes later on.
Just tested with chrome downloading lineage and no issue with Fc