Related
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:
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
NOTE: Development has been shifted to a LineageOS port: here.
First, the usual disclaimer
Code:
/*
* Your probably long expired warranty is now void.
*
* 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
* and point my finger right back at you.
*/
About the ROM
This is a build of OmniROM 7.1.2 (Nougat) for the Samsung Galaxy SL (GT-I9003)
Things to take a note of
This ROM is still a Work In Progress. As such, some features do not work, as listed ahead
GApps is NOT RECOMMENDED as there is very low amount of /system partition space
Make sure you keep a backup of your files. If flashing from stock, this WILL wipe every partition
This ROM does not come with CJK fonts to make it fit in the /system partition. Therefore, Chinese text rendering will be broken
This ROM does not come with AOSP WebView or Chromium. They will be offered separately
This ROM is not rooted. Flash a root zip manually.
Steps to flash
Reboot to Recovery.
Wipe Data / Factory Reset.
Select the ROM zip from your SD Card and flash.
Reboot
Downloads
ROM: https://drive.google.com/file/d/0BwV3ZBepyFp0WXAtUkJhZ1FmUG8/view?usp=sharing
AOSP WebView: https://drive.google.com/open?id=0BwV3ZBepyFp0VllqcmdJVVd4TFU
Chromium: https://github.com/omnirom/android_vendor_omni/raw/android-7.1/prebuilt/app/Chromium/32bit/ChromePublic.apk
Things that work
WiFi
Bluetooth
Things that don't work
RIL
Adopted storage
Internal storage (detected as portable storage)
Vibrator control
XDA:DevDB Information
Samsung Galaxy SL Forward Ports, ROM for the Samsung Galaxy SL i9003
Contributors
Technohacker1995
Source Code: https://github.com/Technohacker/android_device_samsung_galaxysl
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: OmniROM
Version Information
Status: Alpha
Created 2017-05-06
Last Updated 2017-08-26
Great work, I suggested this to be considered for a shoutout from XDA.
Contact me if you want me to edit the stickied thread in General and update it to reflect your Nougat port
Skander1998 said:
Great work, I suggested this to be considered for a shoutout from XDA.
Contact me if you want me to edit the stickied thread in General and update it to reflect your Nougat port
Click to expand...
Click to collapse
Thanks for the support!
You could add this thread to the post, but currently I'm in the process of moving towards LineageOS which happens to be a much better home for the Galaxy Sl. Many of the missing features are present in Lineage
WoOooOow, This is so cool!
Waiting for the LineageOS Version to try
Very happy, you have all my support. cheer up
Yehia2amer said:
WoOooOow, This is so cool!
Waiting for the LineageOS Version to try
Click to expand...
Click to collapse
The LineageOS version is available on my Drive, but it needs some prerequisite setup before installing. If you're ready to mess with the Linux/Android terminal, you can message me
waiting to try LOS, can you post the instruction & the download link thanks.
blacklist3d said:
waiting to try LOS, can you post the instruction & the download link thanks.
Click to expand...
Click to collapse
Sure
LineageOS: https://drive.google.com/open?id=0BwV3ZBepyFp0NV9oX3lTdTNUZDA
GApps recommended: https://opengapps.org Pico package
In case it doesn't print my messages:
1. WARNING! This update removes the Internal SD card for a bigger /system and /data. Make a backup of everything present in your Internal SD card.
2. This update uses a different logical partitioning scheme (LVM, for those who know it). Reverting back to an old ROM is non-trivial.
3. The first time you flash the update package, it checks if you're on the new partitioning scheme. If not (like on older ROMs), it will reboot into this ROM's TWRP build. Reflash the package from TWRP.
4. Before applying the new partitioning scheme, it warns you of data loss (due to formatting of partitions) and exit with an error. Make sure you have backed up any important data and reflash the ROM file to accept the procedure. It will format the Internal SD Card and continue installing.
5. ***EFS IS BACKED UP TO THE EXTERNAL SD CARD***. If there is no External SD card, it should warn you and ask you to pull the efs folder to your computer via adb (adb pull /tmp/efs /some/place/safe)
Note:
1. I'm still fixing issues related to GApps, currently the Google Sign In page does not load (and so doesn't Jelly [Browser]). To access the internet, you'll need to install a different browser. Firefox and Chrome work nicely
2. Camera doesn't work
3. Connectivity is complete. Phone is usable, SMSes can be received. I couldn't test Mobile Data, however.
4. GPS is non-working
5. After I'm done fixing issues with GApps, you should format /data (WARNING: Contains the emulated SD card. Make a backup), install the update and without exiting recovery, install GApps (Cited from the OpenGApps wiki).
Cheers!
I want to use an old i9003 for music player based on Google Music to play music via Bluetooth to my speakers.
I tested this rom.
1. install rom
2. flash gaaps aroma with choice to include Google Keyboard and Google music and with options to remove all obsolete apps
3. After login to google account and pairing to speakers everything working but after reboot I cant connect via Bluetooth to speakers and cant delete this speakers from BT menu
4. Flashed from scratch everything and after boot first time pairing working but after reboot again cant connect to speakers and cant delete speakers from menu.
My conclusion i something is broken in Bluetooth
Can You check this?
Technohacker1995 said:
Sure
LineageOS: https://drive.google.com/open?id=0BwV3ZBepyFp0NV9oX3lTdTNUZDA
GApps recommended: https://opengapps.org Pico package
In case it doesn't print my messages:
1. WARNING! This update removes the Internal SD card for a bigger /system and /data. Make a backup of everything present in your Internal SD card.
2. This update uses a different logical partitioning scheme (LVM, for those who know it). Reverting back to an old ROM is non-trivial.
3. The first time you flash the update package, it checks if you're on the new partitioning scheme. If not (like on older ROMs), it will reboot into this ROM's TWRP build. Reflash the package from TWRP.
4. Before applying the new partitioning scheme, it warns you of data loss (due to formatting of partitions) and exit with an error. Make sure you have backed up any important data and reflash the ROM file to accept the procedure. It will format the Internal SD Card and continue installing.
5. ***EFS IS BACKED UP TO THE EXTERNAL SD CARD***. If there is no External SD card, it should warn you and ask you to pull the efs folder to your computer via adb (adb pull /tmp/efs /some/place/safe)
Note:
1. I'm still fixing issues related to GApps, currently the Google Sign In page does not load (and so doesn't Jelly [Browser]). To access the internet, you'll need to install a different browser. Firefox and Chrome work nicely
2. Camera doesn't work
3. Connectivity is complete. Phone is usable, SMSes can be received. I couldn't test Mobile Data, however.
4. GPS is non-working
5. After I'm done fixing issues with GApps, you should format /data (WARNING: Contains the emulated SD card. Make a backup), install the update and without exiting recovery, install GApps (Cited from the OpenGApps wiki).
Cheers!
Click to expand...
Click to collapse
chudczan said:
I want to use an old i9003 for music player based on Google Music to play music via Bluetooth to my speakers.
I tested this rom.
1. install rom
2. flash gaaps aroma with choice to include Google Keyboard and Google music and with options to remove all obsolete apps
3. After login to google account and pairing to speakers everything working but after reboot I cant connect via Bluetooth to speakers and cant delete this speakers from BT menu
4. Flashed from scratch everything and after boot first time pairing working but after reboot again cant connect to speakers and cant delete speakers from menu.
My conclusion i something is broken in Bluetooth
Can You check this?
Click to expand...
Click to collapse
Yeah, I'm on it. Same occurs for me with my Sony Smartwatch SWR50.
Thanks for letting me know
I can not finish the assembly of the partition, possible small tutorial?
Enviado desde mi SM-G950F mediante Tapatalk
joam280 said:
I can not finish the assembly of the partition, possible small tutorial?
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
Sorry, I'm not sure as to what you mean by assembling the partitions, do you mean the LVM setup?
Technohacker1995 said:
Sorry, I'm not sure as to what you mean by assembling the partitions, do you mean the LVM setup?
Click to expand...
Click to collapse
sorry for my bad English.
My phone stayed in internal memory and does not recognize the micro sd.
Come back again and again to recovery
joam280 said:
sorry for my bad English.
My phone stayed in internal memory and does not recognize the micro sd.
Come back again and again to recovery
Click to expand...
Click to collapse
I'm assuming you've flashed my update zip, and it rebooted to TWRP.
TWRP should have an option in the Install menu to choose from where to select the zip file. Choose Micro SD Card in that and you should be able to install the ROM again
This time you try to install, it will warn you of data loss [1] and exit with an error. Just flash the zip file again and it should continue
[1]: (which, now that I think of it, is no longer useful, considering you can't access those partitions)
joam280 said:
sorry for my bad English.
My phone stayed in internal memory and does not recognize the micro sd.
Come back again and again to recovery
Click to expand...
Click to collapse
I had similar symptoms before reformatting sd card
Great work! I will try as soon as possible.
Can I suggest to open a new thread, with lineage is in the title. It will be useful for other people to find this ROM ( it will be more easy also from google search)
Best Regards and good work
ILCAMPIONE said:
Great work! I will try as soon as possible.
Can I suggest to open a new thread, with lineage is in the title. It will be useful for other people to find this ROM ( it will be more easy also from google search)
Best Regards and good work
Click to expand...
Click to collapse
Thanks for the compliments
Yeah, I'm planning to start another thread (and possibly delete this one) after I've got a few features fixed (Bluetooth in particular)
Cheers!
Status update on LineageOS port:
Bluetooth seems to be working fine now.
Mobile Data doesn't work
GPS works (tested with Google Maps)
Performance is (as expected) slow.
No hardware decoding of video is available at the moment
Cheers!
Please download link
Technohacker1995 said:
Status update on LineageOS port:
Bluetooth seems to be working fine now.
Mobile Data doesn't work
GPS works (tested with Google Maps)
Performance is (as expected) slow.
No hardware decoding of video is available at the moment
Cheers!
Click to expand...
Click to collapse
chudczan said:
Please download link
Click to expand...
Click to collapse
Could take a while, I was patching files on my phone so I'll need to build an update zip
EDIT: Since the build and upload could take a lot of time, here's the file to replace. Place this file as /system/lib/hw/bluetooth.default.so
https://drive.google.com/file/d/0BwV3ZBepyFp0VGlsUG16M3ZWZHc/view?usp=sharing
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.- Don't worry about taking the battery out when the tutorial says to.- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Kernel Source: here
Just yesterday I've dusted off this tablet, and so I was browsing the forums to see what rom I can put inside, and lickily, about the same time this thread was created! Installing it right now, gonna post a follow-up once I'm finished tinkering with it.
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
LukaHM said:
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
Click to expand...
Click to collapse
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
SaberShip said:
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
Click to expand...
Click to collapse
Haha, I've turned the damn thing over, looked at the sensor, and you're right. Havent actually used this device previously to know about it, so glad we have that one sorted out!
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
Click to expand...
Click to collapse
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
Click to expand...
Click to collapse
What app are you using? I have not seen any issues with downloading yet. If you see 10.43Gb it sounds like your internal storage is formatted correctly. I haven't seen any download issues with Firefox and ES-File Explorer.
Unable to flash firmware - because unable to install Android USB driver on Windows 10
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Main post updated with signed drivers. Please try it now.
Thank you @SaberShip!
The installation of Resurrection Remix 5.8.5 was successful after installing the signed Android USB driver!. System is stable and fast. Thank you again.
App issues:
1. Netflix app (not available on playstore, but at netflix web site) works online, but does not allow video downloads.
Netflix diagnostic error for download is OF.NA.4 -which probably means device does not meet security requirements. ? any workarounds?
// Amazon Prime video works, with offline video downloads as well. Google chrome works. Tried other apps as well.
Documentation issues (minor):
1. "- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)" --> Google Apps Super package did not install since the device ran out of space (error 70). Google Apps "Nano" worked.
System issues:
1. Wifi still does not auto-reconnect after Wireless Access Point is rebooted, but given that this has happened with different ROMs I am concluding it is due to a hardware issue with this device (and not ROM specific).
// Skype camera issue fixed. Camera image is NO longer upside down.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Netflix app not working on ROM due to Widevine DRM
Great job on the ROM!! - it is fast and stable.
I have been investigating why the <latest> Netflix app with offline download capability does not work with Resurrection Remix 5.85 ROM.
I found that some other ROM has similar problem, and it was caused because Widevine DRM was not supported. Netfix (latest app and offline download) started working after Widevine DRM support was added to that ROM.
Is it possible to support Widevine DRM in this ROM?
Here is the quote from another ROM:
"Quote:
Originally Posted by Federek
I recently found out the reason why after opening the Netflix app it shows the error "this app is not compatible with your device". The only workaround right now is to download an old APK directly from Netflix website (it doesn't support the feature of downloading movies). After some digging, I'm pretty sure the error is due to the fact that on, I think any Oreo rom available for bacon, Widevine Drm is not supported (as u can see in the screenshot below). I think it's connected to the files in the screenshot below, but I didn't manage to find a solution. I believe it must be implemented by someone directly in the rom code (I'm absolutely not an expert). I'm also sure it's not connected with root or anything else (the Netflix app is available in the play store for me).
(sorry is my first post)
[/IMG]"
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected] I'd be grateful for any pointers you might have.
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
jfaheyfan said:
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected]. I'd be grateful for any pointers you might have.
Click to expand...
Click to collapse
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
Catfish78 said:
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
Click to expand...
Click to collapse
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
SaberShip said:
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
Click to expand...
Click to collapse
Thanks for your answer. If only i could do something like that of my own... i have so much interests, i don't know if i could learn that in a usefull time!
By the way, why did you call it "old"? i'm using the Galaxy S2 build 2011, with LineageOS 16. I think this is an old device , like my Galaxy Tab 1 and 2.
But anyway, thanks for your work. After some time i'll write again about issues i found, if it will be helpful.
Regards
Thank you, SaberShip. It's been on my list to get a DD-WRT enabled router, so maybe now's the time.
I've had no problems with WiFi.
If you build an updated Oreo ROM, I volunteer to test it. I'm fond of my A7600-F.
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)
- Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time
- Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
Does usb otg work?
thierry_w said:
Does usb otg work?
Click to expand...
Click to collapse
Just tested, It works perfectly with my USB wireless Keyboard and mouse combo.
When I tried a USB flash drive it did not mount automatically, however "SDA" does appear in the /dev/block/ directory so you can likely mount the flash storage manually with some terminal commands. YMMV
USB OTG works with both my wired and wireless trackballs (Logitech).
I mount/unmount flash drives with StickMount and explore them with Total Commander.
excellent. Works very well
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