Related
LineageOS 13 for Life One X2 Mini
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org
Screenshots:
Changelog
Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)
reserved 4
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)
srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"
mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.
debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.
debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.
Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing
I'm skipping 90% of words here because if you are here I assume you know what you are doing. And you can either Google, use the search button, or ask.
This is a private work of mine, that I use normally on my spare device. Supported as is.
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
- Camera not working
INSTRUCTIONS
Clean Flash
Download The ROM & GApps (pick latest one in drive, I use opengapps)
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps (Pico Opengapps)
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Download Folder Link:
https://drive.google.com/open?id=1D0Od55prO_Q_e8RY6QkZ-DjO36Qb188X (Choose Tilapia)
Credits to:
Unlegacy Team
Initial Release:
Dec Security Patch
No idea why anyone would use this device , but I use it for movies and youtube lol.
Reserved --
KiD3991 said:
Initial Release:
Dec Security Patch
No idea why anyone would use this device , but I use it for movies and youtube lol.
Reserved --
Click to expand...
Click to collapse
YOU ARE NOT ALONE!!! THANK YOU VERY MUCH.
I grabbed out the nexus 7 to have it as a "on the go document reader/youtube device". I was wondering if there was any new rom and then I saw that there was a 2019 thread :angel:
thank you so much, please keep up the updates :good:
Thanks a lot, I own this device and It is nice to see new development!
Thanks for publishing this version!
To save others some time: When using OpenGApps make sure to use the pico version. The system partition is only 185 MB of size and even nano will not fit.
Update is up!
Sorry I can't be consistent of the updates, but I will try to be at least monthly.
Direct Link: https://drive.google.com/open?id=1O68tXhgNggBKCBQpqG-0Tn9vco7fTvTx
Changelog:
- May Security Update!
- Codes update in the source
New Update
Direct link: https://drive.google.com/open?id=17MnCLoFvIiX-iN-ISQGWay68pIMgliyz
Changelog:
- Still May
- LOS changes
- IDK why I update this, but I still use this device so
PS: Double reboot after flashing
Tried clean install of both May and June Images. I cannot get past the boot animation. I cleared dalvik cache/cache/system/internal storage, factory reset and also format data.Still no change.Kindly help.
Guys, I apologize but this month's upload will be slightly delayed due to my work and studies having major setbacks. Again, I apologize.
itsirfandude said:
Tried clean install of both May and June Images. I cannot get past the boot animation. I cleared dalvik cache/cache/system/internal storage, factory reset and also format data.Still no change.Kindly help.
Click to expand...
Click to collapse
Only time I remember that being an issue is when partition is in f2fs instead of ext4... Is that the issue?
New update:
https://drive.google.com/open?id=1TkoJ5TfkUBugN_IY6jhOfkEXw-Ow7idS
Changelog:
-I optimized build a little
- Security update is the same though
itsirfandude said:
Tried clean install of both May and June Images. I cannot get past the boot animation. I cleared dalvik cache/cache/system/internal storage, factory reset and also format data.Still no change.Kindly help.
Click to expand...
Click to collapse
Just the same trouble. Eternal boot.
Maybe it depends on TWRP version? Or something's wrong with partition?
P.S. I am more than sure there's the problem with boot.img. Just flashed another boot.img over this ROM and it's OK.
I'm getting random freezes. Like the whole tablet freezes and I have to force shut it down holding the power button.
New build up, sorry I was really unavailable.
I tried fixing a couple of things, see if it helps, do tell me though, mention me and I will show up.
Direct link: https://drive.google.com/open?id=1TkIWTFha5EFBQeqqKw2pu6nRoVgmvV3X
Changelog:
Minor bug fixes
July Security Patch
OsitKP said:
Just the same trouble. Eternal boot.
Maybe it depends on TWRP version? Or something's wrong with partition?
P.S. I am more than sure there's the problem with boot.img. Just flashed another boot.img over this ROM and it's OK.
Click to expand...
Click to collapse
THEVAN3D said:
I'm getting random freezes. Like the whole tablet freezes and I have to force shut it down holding the power button.
Click to expand...
Click to collapse
For booting make sure you're using ext4 instead of f2fs(I forgot this existed and my N7 froze forever until I figured it out)
I might take a look at bootimg from other devs to see if anything can be further improved.
Get update:
Direct Link: https://drive.google.com/open?id=18Q8ynmdkNEGfkVM4wsF1ljyMiavFmjOR
Sorry for the holdup. Been trying to score interviews
GPS not working and not showing up in the system tray, can you help me. sorry for my bad English, i used google translate.
rockafellor said:
YOU ARE NOT ALONE!!! THANK YOU VERY MUCH.
Click to expand...
Click to collapse
Not alone at all.
I use it to read magazines/comics/news when I'm on SPA/sauna.
In SPAs are forbidden all devices with camera, and almost all devices now have a camera!
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
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,. https://androidfilehost.com/?fid=11410963190603878004 This method preserves IMEI and Baseband.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
##
I find the earliest of these metro pcs firms have a working vendor image.
https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/
I got bluetooth working today, and lots of clues where I found the fix...
####Bluetooth
Now that I can set it up from a clean install, here's the basics for Bluetooth...
You'll need files from the stock system image. You can use a backup to get these or also use simg2img with dd and 7zip, I'll make a zip installer when I have more time.
1. Copy the following files, from stock image directory "/system/etc/" to the "/vendor/etc/" directory on device
mixer_paths* (14 files)
audio_* (5 files)
media_profiles* (3 files)
Edit the file /system/etc/ld.config.26.txt
add this text to the very end of line 61 :/system/${LIB}/vnd-sp/hw
You're done! If you did everything as described, and it doesn't work, check the permissions of the files you add to vendor partition with other xml files in same directory. I did mine on the device while running, it worked in place, without rebooting device. The GSI system is new to me, however the "Same Proccess HAL(hardware abstraction layer)" voodoo can likely be configured correctly to fix screen and port other GSIs' to our device.
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
edit: 9/21 6pm
I think it's because mine is TMO variant.
Mattswad said:
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
Click to expand...
Click to collapse
Trying based on this now. I'll update you.. been trying for TOO LONG lol it's almost the same time you posted 2 days ago!
---------- Post added at 04:12 AM ---------- Previous post was at 03:45 AM ----------
I've been up all night trying to get either one to work.. I think I came close but I am stuck at a looping blank screen.
If you could step through a bit more for us? I'd REALLY love to have lineageOS on it.
mrbox23 said:
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
Click to expand...
Click to collapse
I have the Metro PCS version
Moto e5 Play XT1921-3
Mattswad said:
I have the Metro PCS version
Moto e5 Play XT1921-3
Click to expand...
Click to collapse
Ahh That is excellent news. I am about to take a focus supplement, and dive into trying again I'll let you know. I found a few more of MrBox23's posts and I think I MAYBE onto something.... wish me loads of luck. If it works for me I THINK it should work for you, but you might need to start with a diff image than me, or use a different boot and vendor img than I will.. not sure if I can help you find those files or not..
I'll be back later to update what I find.
Sorry I haven't been on for awhile. I'll go ahead and post my working vendor and boot images. On Google drive for download. Doing this will trash your speaker if you play music very loud at all, expect that. I do not understand how to fix it. Other than that it's a daily driver. I have been asked about encryption this and that.. You have to modify fstab.qcom within vendor partition. Also the TWRP for this device will format your data partition as ext4 while the ramdisk and init stack are configured for f2fs(if you try and boot with ext4 data, you get corrupted/encrypted data message). You have to change data partition back to f2fs in TWRP every time you format that partition. Or you could modify the TWRP image like I did to fix it permanent.
Files will be uploaded soon, make sure you understand what's involved before getting into this. I'll answer questions best I can, but this is for those who are dediced and willing to get down on some bootloops to figure it out, especially if you're not used to this sort of thing. Some magisk modules will cause bootloops, do those one at a time and gapps separately. I seriously recommend taking apart the firmware from OP and focus on getting to the aosp boot animation, THEN take care of verity/root and fstab. You're formatting data partition anyway you might as well successfuly backport the graphics first.
Vendor image TWRP backup, put this on its own with boot image. I keep it as vendor_fixed for easy reference. The fstab is already patched if you use mine.
Boot image TWRP backup, it is patched with magisk (19.4 likely) install magisk on your own anyhow. KEEP YOUR ORIGINAL VENDOR/BOOT PARTITIONS! There's stuff in there that you might want later on. Like the /vendor/etc/wifi folder for example or the pieces from the original ramdisk.
Vendor and boot with md5 sums to verify integrity.
https://drive.google.com/folderview?id=1-2KO_iRFTjLv6pyx-7Qmhi8kWZBpVIWD
Wipe everything, including internal storage(after backing up a working system).
Format data partition back to f2fs in advanced wipe options.
Get LineageOS 15.1 beta or RR you can find these here on XDA.
Flash Lineage zip its the old style zip install that copies idividual files, not an image, the boot image it installs needs to be replaced per instructions that follow.
Or flash RR system image from official repository link is found here on XDA.
If you flash a system image with TWRP you'll need to reboot back into recovery right after and resize the system partition in advanced wipe options or your system partion will be incorrect size afterwards, if flashing system with fastboot(recommended) then skip the resize instruction.
After you have a system installed, restore the vendor and boot images from the link. A good approach would be to backup your existing boot/vendor as a pair, then replace originals with downloaded images.
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me. I dealt with the fstab and boot verity patching AFTER I first saw the default Android boot animation. Once you see that plain white "android" with the slow moving left to right animation, your in. From what I can tell our device needs the older kernel within the boot image and the libs/binaries from the vendor image to get the screen working correctly. Your trading your working speaker, for a working screen. I have attempted to find exactly what it is that's different between the two, but it's over my head. Overall it's relatively stable, go easy with magisk modules, some of them will cause kernel panic(bootloop) use a recovery based magisk tool to disable offending module if this happens. Sometimes the device will not boot normally, usually this means the cache was erased(its okay) for whatever reason and I wait it out, otherwise I restore the vendor_fixd backup I made. I have not had gone back to stock ROM, however I have had to flash the vendor partition to get it booting, usualy happens if i flash a module or when updates break substratum theme.
Good luck!
Oh email me for quick response, within reason.
mrbox24 at gmail
Bonus screenshot and the TWRP 3.1.1 I modified with correct data format. If you have an sdcard with second partition it will show up as "linux" named after the chroot partition from mine.
Screenshot shows LSM kernel found here, yes it works.
mrbox23 said:
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me.
.
Click to expand...
Click to collapse
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
aka.bugle said:
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
Click to expand...
Click to collapse
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
mrbox23 said:
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
Click to expand...
Click to collapse
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
aka.bugle said:
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
Click to expand...
Click to collapse
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
I make custom scripts and have a custom build.prop, for example this.....
resetprop 'media.camera.ts.monotonic' 0
resetprop 'persist.camera.HAL3.enabled' 1
resetprop 'audio.deep_buffer.media' true
Those three lines are saved to a file called mediafix.sh in /data/adb/service.d to be ran at boot. it helps with media and camera issues. As well as a one line file called led-chg.sh
echo battery-charging > /sys/class/leds/charging/trigger
Which turns on the light, otherwise never used, in front of phone when charging.
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
I find the vendor/boot firmware here(oldest 2018) https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/ to work best. Audio is completely a loss though. My speaker is blown now and no Bluetooth unless running stock, not even the headphone jack works. All sound comes from the one speaker, even with headphones plugged in I'm at a loss with that issue.
I also modify the boot image. turns out the 1921-3(possibly others?) uses the sdk26 8.0 android ld(library config) instead of the ld.config.27.txt that matches its sdk level. in fact if i try to force the 27 lib config, the gray/black screen comes back. it boots up, i know because my charger light comes on, but no screen. Anyhow i change the os level in boot config to 8.1.0, this gets me to where i am now with only bluetooth(mixerpath/lib issues i suspect) and a couple missing ui features due to what i imagine originate from missing whitelists in /system/etc/permissions xml files.
Another thing of note is how i spoof the mac adress for wifi, this(and other things) is done by modifying the kernel command line config in boot.img. my second e5 play xt-1921-3 has a broken screen, and serves exclusively as a wifi-repeater, captive-portal, and ssh server/tunnel. i spoof the busted screen wifi mac, with an old device mac address that is still registered on xfininity wifi network. it repeats that connection to my other devices. very efficiciently at that. with 3+MiB/s average. it took some hacking but after i found out the oem partition on this device can be formatted, and removed from the ramdisk/system all together, without consequence(not to lineage, bootleggers, or rr remix that is) and be re-purposed to whatever else. its roughly 700MB in size perfect for a debian chroot with my custom wifi repeater and misc servers. running in its own dedicated internal(FAST)partition. This device, and its kernel level mac spoofing with the now almost phased out WCNSS qualcom configurable wifi firmware, is incredible. the busted screen one has been on every day non stop functioning as a repeater, router with captive portal, and dhcp service, for almost two months. it automatically connects to wifi, kills the android zygote/system server, kills its backlight and starts up a hotspot and sshserver/captive portal, all without cell service, and without any interaction.
Anyway, new mpcs files up soon.....
mrbox23 said:
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
###bugle added### my Att is an xt1921-2, can't even unlock the bootloader... But 30 bucks isn't bad for a new screen and a new speaker. ###
Another thing of note is how i spoof the mac adress for wifi, this(and other things) .
Anyway, new mpcs files up soon.....
Click to expand...
Click to collapse
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
aka.bugle said:
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
Click to expand...
Click to collapse
My first "Android" phone was the HTC HD2 wich was actually a Windows phone that can boot linux from the sdcard. I came across it while learning how to get linux booting on laptops. I was fascinated with booting a mini linux on a portable device. I learned about Android and linux in that way, at the same time. Kernel, ramdisk, java machine, broadband cellular modem, and wifi radio in my pocket. I abandoned windows entirely, to this day lol
Right you are! @mrbox23 ... I've got camera on RRemix on the metro 1921-3!
I'm gonna put the lineage/no camera issue on the back burner for when I try to use your older boot/vendor img trick (boot Lineage 15.1) on the unlocked 1921-5.
(I only have a 1Mb/s dsl connection here, takes about 4-5 hours for a 1 gig file to dl)
So, for the Metro 1921-3, I can't find libeffects.so or even the soundfx folder to copy into. (studder fix)
Your script 2 files for media/camera and charge led, other than making them executable (0755? 0700?) will they be called (without any other mod) being in /data/adb/service.d ?
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
Click to expand...
Click to collapse
I pulled one out of my Att phone that is a james xt1921-2 but has a locked bootloader, all stock ... I used #getprop ro.build.fingerprint.. not sure if i should use this, or wait to see your build.prop...
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
Click to expand...
Click to collapse
All the best to you and yours in 2020. Meeeerrrry eXksMix, hic up'
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
mrbox23 said:
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
Click to expand...
Click to collapse
mediafix line 2... set or resetprop?
1 resetprop 'media.camera.ts.monotonic' 0
2 setprop 'persist.camera.HAL3.enabled' 1
what are these last lines in mediafix for?
16 resetprop net.dns1 1.1.1.1
17 resetprop net.dns2 1.0.0.1
and i'm guessing the deb.sh is for your wifi repeater? swap space in oem?
how is mpcs.prop called? where is its proper folder?
can you host a copy of libeffects.so ?
@mrbox23 Bluetooth working! check.
aka.bugle said:
@mrbox23 Bluetooth working! check.
Click to expand...
Click to collapse
something I just noticed here recently is that's all the audio output now. I can't test cellular calls, Hangouts only works when i restore that vendor path Back to where it was. My camera broke again to. I want to reach out to phh here or github.
Well that's a big bug, sorry. I've reverted the metro 1921-3 to stock for now, but on the positive side, I tried using your older boot/vendor imgs trick on the 1921-5 (Sprint)... and success! it boots Lineage 15.1 and bluetooth works, I haven't tried using the GSM Att Sim yet and still no camera, (I haven't tried your other camera recommendations yet.) One step closer for the 1921-5.
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