Related
(This is a thread @POWerSUrgeSW3 and I will be maintaining and checking regularly, so if you have any questions feel free to ask. We will always try to post a root method for the latest firmware version once we figure it out, so expect us to be updating this thread as firmware updates roll in)
Nougat Root Method SM G930P QG1 (Latest):
(Start from a CLEAN ODIN INSTALL of Nougat. If you need Nougat, go here: http://updato.com/firmware-archive-select-model?record=2C3C1C6245EF11E7963AFA163EE8F90B .
1. Go through initial activation process; Turn WiFi on and let the phone register through WiFi; log into Google and Samsung accounts if desired
2. For WiFi Calling to work, click on Sprint Zone, this will load a bunch of Sprint software. This will also load the WiFi Calling APK needed for later. The rest of the unused Sprint software can be debloated after rooting the phone.
3. Test WiFi Calling, to ensure it connects through your Wireless connection.
4. Disable AlwaysOnDisplay under the Display under Settings. This can be enabled again after the rooting process is completed.
5. Go into System updates; disable ‘Download updates automatically’.
6. Next, go back into Settings -> About Device -> Click build number 7 times to unlock developer options.
7. Under Developer Options, enable OEM unlock, and USB debugging; turn off Auto update system and verify apps over ADB
8. Go into ‘Lock screen and security’ -> other security settings -> turn auto update off
9. If a PIN has been entered for security: Lock screen and security -> Secure startup -> Do not require – Otherwise root will not be active on startup after going through the process.
10. Install Adhell
11. Diisable these packages:
- com.android.sharedstoragebackup
- Chameleon
- Security policy updates
- SecurityLogAgents
- Samsung DM Phone Interface
- Samsung DM Service
12. Download these apps for later use:
-L Speed
-Kernel Adiutor
-BuildProp Editor
13. Turn off WiFi for the rest of the rooting process. This will ensure that any remembered WiFi passwords are saved and not erased.
14. Use Odin again to flash the engineering boot image from here: https://www.androidfilehost.com/?fid=745425885120714389 . (It goes in the AP Slot).
15. Once it reboots, download this file: https://www.androidfilehost.com/?fid=889764386195909311 . Thanks to @jrkruse for this.
Extract and run the root file.
Opt for root with tweaks, or press 2. Follow the prompt, it's fairly simple.
17. Go into BuildProp Editor, and set these values:
Set ro.cdma.default_numeric to 310120
Set ro.cdma.default_alpha to Sprint
Set ro.build.characteristics to Sprint
18. Reboot.
19. If you don't want updates to download/install, uninstall these packages:
com.sec.android.soagent
com.wssyncmldm
com.samsung.sdm
Then, remove the update file from data/fota.
20. You should have a fully functional phone now.
Thanks to:
@POWerSUrgeSW3 for helping me root nougat and for his PL6 root method (which this was based off of).
@colormedroid for his initial APE1 root method
@paul2112 for the hotspot bypass.
@JUSMEJOSE for the nougat engineering image and su.
@Chainfire for SuperSU and the other tools that have been very useful in different rooting applications
Huge thanks to @jrkruse for the modded root.bat!
@ Everyone who has contributed in one way or another to all of these different applications!
Hit thanks if I helped and enjoy a rooted nougat!
P.S: PL6 root method is located here: https://forum.xda-developers.com/sp...hmallow-pl6-marshmallow-t3573135/post71434273 .
Q&A + General troubleshooting section:
Q. Is there a hotspot bypass?
A. Yes there is, find it here: https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446 .
Q. My phone is lagging, how do I fix it?
A. For maximum performance do this:
Use the settings for L Speed as follows:
- Set the profile to performance.
- Under virtual memory, set OOM Killer to default, cache reclaiming to doubled, and cache allocation to large.
- Set the ram manager to multitasking.
- Set seeder and fstrim to run on boot.
Use the settings for Kernel Adiutor as follows:
Set both cpu governors to performance and to apply on boot.
Turn core control off and temperature throttle on under thermal.
Set the GPU governor to performance.
Debloat, first freezing and then uninstalling to ensure system stability.
SM G930U QF3 Nougat Root:
1. First, download the Universal QF3 firmware from here: http://updato.com/firmware-archive-select-model?record=8AE0CC7C625711E7963AFA163EE8F90B and flash it via Odin.
2. Completely finish activating and finish initial setup.
3. Update PRL and Profile.
4. Then enable USB debugging under developer settings and turn off verify apps via ADB.
5. Go into other security settings from lock screen and security settings, click security policy updates and turn auto updates off.
6. Turn off auto update system in developer options.
7. Disable the following packages via adhell (Knox needs to be activated in order to disable packages).
-Chameleon
-Sprint OMADM
-Sprint OMADM Phone Interface
-MDMApp
-SecurityLogAgent
-Security Policy Updates
-Security Storage
8. Flash the modified boot image via Odin, you can find it here: https://www.androidfilehost.com/?fid=457095661767149794 .
And grab Odin from here:
https://www.androidfilehost.com/?fid=673368273298965444
9. Go into connections, mobile networks, and delete the Wholesales OTA APN. Click the remaining one and edit as follows:
Name: Set it as whatever, I named mine Sprint LTE/MMS/Hotspot.
APN: n.ispsn
MMSC: http://mms.sprintpcs.com
Multimedia message proxy: 68.28.31.7
Multimedia message port: 80
MCC: 310
MNC: 000
APN Type: default,supl,mms,dun,fota
APN/APN ROAMING PROTOCOL: IPV4/IPV6
Bearer: Unspecified, LTE, eHRPD.
Click save.
Activate it (make sure the dot is filled in).
10. Run the root.bat file. (GET IT HERE: https://www.androidfilehost.com/?fid=889764386195909311 ).
(Here's how:
1. Download the file
2. Extract it.
3. Shift click and open a command/ powershell window there.
4. Type root.bat
5. Hit enter
6. Follow the command prompt.
)
11. Download and install Kernel Adiutor, and set the CPU governors to ondemand. Turn core control off, and turn VDD Restriction on. Set your GPU to simple_ondemand.
12. If you want hotspot do this:
Download and install Termux
Type "su", press enter and allow root access.
Type "settings put global tether_dun_required 0" and press enter.
Type "settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
Turn off mobile data.
Turn on hotspot and it should work just fine.
13. Install L Speed and set your settings as such:
Go into Virtual Memory: Set cache reclaiming as Doubled.
Go into Ram Manager: Set Ram Manager as Multitasking.
Set Cleaner to run on boot.
Set FStrim to run on boot and set the FStrim scheduler to 60 Minutes.
Go into main tweaks, and set boost scheduler to 60 Minutes.
14. I'd recommend using a custom launcher (I use nova launcher with animations set to the fastest speed).
15. I'd also recommend debloating via Titanium Backup. After you remove the apps you don't want just reboot to get rid of the "This (insert app here) has crashed" message pop ups.
16.Change the animation speeds to .5 via developer options.
Enjoy your blazing fast rooted S7 with full activation and hotspot.
Thanks to @jtash01 for the activation settings for the firmware, and @paul2112 for hotspot.
YMNDLZ said:
Q&A + General troubleshooting section:
Q. Is there a hotspot bypass?
A. Yes there is, find it here: https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446 .
Click to expand...
Click to collapse
If you put this in for 5b, you should get phone and tether data simultaneously.
Code:
"APNDUN,n.ispsn,,,,,,,,,310,120,,default,mms,dun"
Otherwise, you get one or the other. Still have to do the data cycle though. Can you use sqlite for this to edit the apn?
Sent from my SM-G930P using XDA-Developers Legacy app
lvpre said:
If you put this in for 5b, you should get phone and tether data simultaneously.
Otherwise, you get one or the other. Still have to do the data cycle though. Can you use sqlite for this to edit the apn?
Click to expand...
Click to collapse
Nope, you need to use the hotspot bypass in the Q&A section.
YMNDLZ said:
Nope, you need to use the hotspot bypass in the Q&A section.
Click to expand...
Click to collapse
Ok. Not rooted, but have hotspot. Had to add something to his code to have tether data and phone data at the same time; otherwise, if I was tethering my phone data wouldn't work.
I know that method worked on mm root. Just asking.
Sent from my SM-G930P using XDA-Developers Legacy app
Currently getting a 404 error on your google drive links.
vunuts said:
Currently getting a 404 error on your google drive links.
Click to expand...
Click to collapse
Will be updated asap.
Much appreciated man. Just wanna give this method a shot and get it working!
Thank you guys so much for cracking at it and giving us this process.
vunuts said:
Much appreciated man. Just wanna give this method a shot and get it working!
Thank you guys so much for cracking at it and giving us this process.
Click to expand...
Click to collapse
Links fixed.
Outstanding job!
Rooted and everything works. Followed all instructions, everything is working, data, text, voice. currently debloating and gonna mess with some more stuff and run through my normal daily functions just to make sure it all works. If I have any issues, I shall let y'all know.
vunuts said:
Outstanding job!
Rooted and everything works. Followed all instructions, everything is working, data, text, voice. currently debloating and gonna mess with some more stuff and run through my normal daily functions just to make sure it all works. If I have any issues, I shall let y'all know.
Click to expand...
Click to collapse
Sweet! We took a good couple of days to fine tune the method before we released it, glad to know it works!
My SM-G930P / PL6 Firmware Root Instructions (Updated 07/25/2017)
UPDATED 07/25/2017
It has come to my attention some of the links listed here are outdated. All of the Google Drive links are to my my account. These are the files I collected for this process. If there are any other links that are not working, please let me know by PM.
We are keeping these instructions just because there has still been interest shown for Marshmellow.
Extra THANKS to @YMNDLZ for the continued support, and allowing me to help out where I can!
Disclaimer: This is the process I used, which I put together after a weeks’ worth of messing around and rebuilding my phone over and over. This is not the first time I have messed around doing this sort of stuff. If you are inexperienced, not sure what root/Odin/flashing is, I highly recommend keeping your phone the way it is and be happy. I take no responsibility for any damage that might come from following my process. THIS WILL VOID YOUR WARRANTY if you take your phone into Sprint and try to get it serviced. Your phone will be running an engineering version of the kernel for your phone, letting you obtain root. In addition, your battery life and performance is going to probably be different from before, and it will be up to you to tweak the kernel and other system settings to fix that.
Recommend starting over from scratch. If you already have your phone setup, I know it is not the best to start over from scratch. Nevertheless, I have tried doing this from a phone already setup, configured, and tweaked. Even though it is not rooted, something seems to screw up the process and things will not work. I had issues with MMS and hotspot not working. When I rebuilt the phone from scratch, everything seemed to work fine.
NOTE: My instructions were done using a Windows 10 Pro 64-bit computer. If you have another OS, you are kind of on your own.
ALSO TO NOTE: When I got my S7 (Not Edge), I switched to a new plan from Sprint. My plan now provides HotSpot with my contract. If yours does not, results may vary then. I am unable to test all different configurations of plans with this process.
What May Not Work: I have tested everything I could think of on my phone.
Any application that checks for Root/Custom device software (because I do not know them all). Applications like Samsung/Android Pay. In addition, snapchat, though if this is installed and logged into before the Engineering Boot image is installed, Snapchat should continue working after phone is rooted. There are some work arounds depending on the app being installed, consult the Internet before rooting. You have to make the decision whether you can accept not using the app once rooted.
WiFi Calling. I think this is because I forgot to set it up before I rooted the phone. I did not even think about it until days after I had my phone setup. Because I did not use this feature on the G930U/PL2 firmware, did not think about it. But when I came back to the PL6 firmware, I did know it was working because I was messing around with it before I rebuilt the phone another 4-5 times.
First, download the firmware from one of the usual sites:
http://updato.com/firmware-archive-select-model
http://www.sammobile.com/firmwares
http://www.sammobile.com/firmwares
Then download and extract everything from this ZIP: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lblk3TUo5ZjdlanM?usp=sharing
This gives us the modified Odin we will need later, as well as the bootloader we will need.
Grab this SuperSU ZIP:
Chainfire direct link: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
As a backup, here's my link: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lcWxtOFptRzVFLXM?usp=sharing
Also grab the V15 FIX ZIP:
https://drive.google.com/drive/folders/0Bz6QOPY0cm2lUGRCSW01WHlLRHM?usp=sharing
If you don’t have the Android SDK already installed, I found this to give us the needed ADB/Fastboot options we need. You can download from this page, scroll to the bottom (linking to give them credit):
http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Extract the SuperSU ZIP and the ADB/Fastboot zip into the same directory for later. I recommend putting them in c:\S7files as this will make life easier in the future.
With all that done, open the Modified Odin and load the different parts of the Firmware into the associated Odin slots. Whatever the file name starts with is the slot it goes in. BL_, AP_, CP_,CSC_... now there is an extra “HOME_CSC_) file, we will not be using this and don’t worry about it. This file is if the original service settings were to be kept after flashing. As this could cause issues, I recommend not using it. If you do, you may have different results.
With all that done, your phone should be ready to start as if it was just turned on out-of-the-box. Let the phone go through its process and reboot to “install updates”. Then, it seems, Sprint is installing its software, reboots, and then loads up to the “Welcome” screen. Go through the whole process. Make sure the phone activates, which will cause a reboot and I think flashing of your SIM card (that is the image that comes up and looks like anyway). Then you can finish the activation process and log into your Google account/restore apps on your phone.
Once the launcher loads, any apps you wanted to restore is done, time to start the actual rooting process. Enable ‘USB debugging’ under ‘Developer Options’ and turn off verify apps via ADB. If you do not know how to get Developer Options to show under Settings… Google It (and might be a first sign this is not for you if you’re new to the process)
Next, while in Settings, go into ‘Lock screen and security’, scroll to the bottom to ‘Other Security Settings’, click ‘Security policy updates’ and turn auto updates off.
This next part requires purchasing Package Disabler Pro. If there is another way that you know, please try to report back. However, I bought he app and it does the job. This app will be used to disable services on a non-rooted device. The following services will need to be disabled:
(Knox needs to be activated in order for Package Disabler Pro to verify it's license)
Chameleon
Security policy updates
SecurityLogAgents
(The next ones I did from a lot of late night reading, sorry I forget where I found these)
Samsung DM Phone Interface
Samsung DM Service
CMHProvider
com.samsung.dcmservice
Now we are going to flash the Engineering Boot Image file. Again, if you are not sure how to use, or what Odin does… stop here! Run Odin, and flash the Engineering Boot image, I used the AP slot. Then under ‘options’ disable ‘F. Reset Time’.
Once rebooted, the phone is running the engineering kernel now. This is what is going to allow us to root. However, until we are rooted and do some tweaking, battery is going to drain a lot faster than expected. This is due to the kernel not being efficient with the processor/system resources. Your phone will get warm, because of the above reasons. Don’t worry, once rooted everything can be tweaked to fix this.
At this point, LTE will not be working. Also after every reboot your phone will not remember any WiFi networks it was connected to do not worry it will get those fixed down the road.
Now we are going to go through the actual root process on the phone. Connect phone to a computer via USB cable. If the phone asks to allow/deny access, ALLOW. Open up Command Prompt as an administrator on attached computer. Move to the directory c:\S7Files that we created earlier. This should be where the root.bat, SuperSU, and ADB/Fastboot files are located. Once inside this directory simply run the root.bat file.
This will execute a bunch of commands to be run on the phone; phone should reboot at least once (or twice – cannot remember). Once the phone boots up and loads “normal”, SuperSU will be loaded. I kept the phone awake while the files were being transferred over to the phone. On a few times doing this, when the phone went to sleep the process seemed to “hang” until the phone was “woken up”.
Of course we have, an older version of SuperSU is installed, but do not worry about it now. We are going to finish the process, and then update SuperSU last. That just seemed to have the best/smooth/stable results for me.
Please note, you have SuperSU access to the phone. Now you can screw it up, even possibly hardware brick the thing if you do not know what you are doing. Again, I caution if you are not comfortable with knowing what root really does or how it can affect your phone, reflash your phone back to factory using Odin NOW.
Copy the S7_or_S7Edge_Fixes_V15.zip file to your phone storage. Download ‘[root] FlashFire’ by Chainfire (In Google Play) and flash the fixes zip. This will reboot the phone a couple of times; you will see the FlashFire logo at the top and then a bunch of scripts being executed.
Download BuildProp Editor, and change the following values (use the search function at the top is easiest method):
ro.securestorage.support to false. (This fixes the phone forgetting WiFi networks on reboot)
Set ro.cdma.default_numeric to 310120
Ro.cdma.default_alpha to Sprint
Ro.build.characteristics to Sprint
Reboot the phone to apply changed.
Now another app that costs money, but this seemed to work for me over the other method mentioned by @YMNDLZ in his rooting tutorial to get HotSpot working. (found here https://forum.xda-developers.com/showpost.php?p=71118378&postcount=1021 )
Install SQLite Editor. Click on “files” tab, and navigate to:
/data/data/com.android.providers.telephony/database/telephony.db
Select ‘carriers’ and scroll down to the bottom. On my phone, it was lines 30 and 31, ‘APN2 LTE internet’ and ‘APN2 EHRPD internet’ respectively. Select each one, click the edit button at the top (looks like a pencil) and scroll down to the ‘type’ line. It should read: default,mms
click the line and add ‘dun’ to the end. The line should now read: default,mms,dun
No spaces between the words and the commas.
At this point everything should be working. If you go into the Mobile Networks and check out the Access Point Names, there should be a bunch of names listed. I have 8. LTE should be working, HotSpot, and WiFi should remember all of the names. The phone should be fully functional now, with root access, just runs hot and kills the battery. We will deal with that next. Here is the apps I used, L Speed, and Kernel Auditor. Now @YMNDLZ has his own setting recommendations for L Speed, check out the post referred to earlier for screen shots. @swick1981 also has a thread with recommendations, found here https://forum.xda-developers.com/ve...guide-to-fix-s7-lag-root-s7-variants-t3441715 . I started with both of their recommendations, one at a time, and tweaked things, as I wanted. Personally, I found that my phone still felt warm, like it the processor was still working harder than it needed to. Therefore, I hanged my settings. I suggest reading, research, testing. Figure out what works best for you. This for me seems still fast, battery lasts all day, and phone does not get hot at all. I do think I still have a bit of a nasty battery drain on LTE networks compared to when my phone was not rooted, but I am surviving with it.
L Speed: I left everything default. When the app loads and you are at the profile screen, I changed the Profile, IO Tweaks, and LNET options all to the Balance profile for each. After I changed each one, I exited the program and loaded it again. I did this because sometimes I noticed the app would not acknowledge changes to profiles. I have screen shots of my settings at the bottom of this thread. To experiment, I recommend using the BACKUP feature, and saving different options. That way you can go back to an exact configuration to try different settings without having to manually reprogram them each time.
Kernel Auditor: All I am currently using this app for is to change the CPU Governor to INTERACTIVE for all the cores. I like it because it has thermal options, if that is a concern down the road. As well as has options for the GPU. Among a bunch of other options, I doubt I will touch. However, I have a feeling maybe the GPU needs to be adjusted to help save some battery life as well… sometime I will tackle later.
Note: that on reboot or booting phone from powered off state, the stock options for the kernel are used. Therefore, my phone usually sucks about 4% battery and gets warm everytime. Then when the scripts run for L Speed and Kernel Auditor, things “regulate” themselves and the phone settles down. For the rest of the time until I reboot my phone again, it stays cool for the most part. Even with the screen on a lot and/or using LTE/WiFi/Voice.
I have heard that the stock launcher seems to cause lag. I did not notice that really myself, but in the event, it was causing the phone to work harder… I switched. I have been a huge Nova Launcher fan; use to use it a lot on my S3 and S5. I also have the PRIME version. I installed that and tweaked it, and am actually a lot happier with that personally. Again, it is another app that can require root access for some features, why I stopped using it when I first moved to my S7.
I would also recommend debloating via an App Remover program. Personally, I like Titanium Backup, you can freeze apps you’re not sure about… or even back them up to restore later if needed. Remember removing some apps may cause error messages to pop up, rebooting should fix that. IF not, undo whatever you did (IE unfreeze or restore the app. @YMNDLZ has a screen shot of the apps that can be removed, found here https://forum.xda-developers.com/showpost.php?p=71119004&postcount=1024. Know what you use and do not use. I have a Samsung Galaxy S2 watch, so I kept a lot of the Samsung apps (except the Pay stuff), I use Gmail, etc. Nevertheless, it’s a good reference.
Or if you want you can try running this debloat script: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lTXBWWHVNN1o0SXc?usp=sharing
Personally I think it removes more than I want, but if new to this rooting process it's woth a try to see if it works out for you.
EmergencyManagerSerivce seemed to come up as not responding on a few of the times I experimented rebuilding my phone for this process. If that happens, just go to the service and wipe the cache for it. Reboot, and that should take care of the issue.
Last thing I did, trying to figure out why the EmergencyManagerService was not working, I re-enabled the following in Package Disable Pro:
Samsung DM Phone Interface
Samsung DM Service
CMHProvider
My phone seems to still be working fine with them enabled.
How to Update SuperSU: If anyone has tried updating SuperSU from the PLAY store, it updates fine. But then the binaries need updated, and that's where we run into the problem. The update process always fail, and because of the locked bootloader we can't restart in TWRP or a custom recovery to install the update. My process is pretty easy, and so far seems to work every time (I should know I've done it about 11 times over the past couple of weeks). The current newest version is v2.79 (December 14, 2016) as of writing this post.
NOTE: This will remove root access from your phone temporarily, and then all apps that require root will have to be granted access again. So yes until this is done we're back to the stock kernel settings and your phone may get a little warm again/battery will die a bit faster than normal again.
Open up SuperSU app on your phone, go to the SETTINGS tab scroll all the way down. On my phone "Reinstall" will now be the first thing listed when scrolled all the way down to the bottom of SETTINGS, it's the first item inside of the "CLEANUP" section. If it's not for you, scroll back up until you see it.
DO NOT CLICK FULL UNROOT!!!!
This will unroot your phone. I have not done this, but potentially you would have to rebuild the phone from scratch.
When "Reinstall" is clicked, SuperSU will give a little informational box. Read it, it pretty much gives you the instructions you need. Click "Continue" and the process is started. For me I usually have to restart my phone manually. When the phone restarts, simply go to the Google PLAY story and download the newest version of SuperSU. Once downloaded, open up SuperSU. There should be no notification to update (as you're on the newest binaries). Go back and tweak your settings if needed, install Pro if you bought it, and go through all your apps that need root to grant it.
Other SuperSU method/Other apps that try to do certain mods on reboot: I know that there is a version on @Chainfire website to download and install the SuperSU updates through FlashFire. This isn't the only situation that that will cause issues, but be aware that this will probably soft brick the phone and it will not boot. If you see the picture below, keep reading for a fix.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
'custom binary blocked by SECURE BOOT (boot.img)'
Scary message huh? No matter if you reboot your phone, try clearing the cache in Recovery, nothing will get it to go away. First time I saw it, I ended up rebuilding my phone last time because I figured all was lost... praying something didn't "lock" in the firmware to cause me to have to actually call Sprint! This time I was messing around with 'Magisk Manager', because I ran into more apps that wouldn't install on a rooted device). Was trying to figure out a work around and flashed something and BOOM on reboot.
Fix When I read the message again this time, and saw the 'boot.img'... it stuck out in my head. I figured I would try using our modified Odin and re-upload the engineering boot.img file again. That was the fix for me! After that, phone rebooted and loaded back into the launcher like normal. So far everything seems to be working fine, my L Speed and Kernel Auditor scripts ran at bootup just like I had normally rebooted my phone.
I can't promise this is the overall fix for everything. But if you happen to be messing with your phone, like I do, and get this... hopefully this will be a quick fix and get the phone back up and running.
I have not reinstalled XPOSED yet, maybe down the road I’ll mess with it. Trying not to add too many variables while figuring out a few of the other things. However, I did test the process and it works.
Framework ZIP to be installed using Flashfire: https://www.androidfilehost.com/?fid=529152257862685343
XPOSED APK installer: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lLUVuVnBlalRHbWM?usp=sharing
@colormedroid also posted up an FQA post in this thread that may be helpful to anyone having issues, found here https://forum.xda-developers.com/showpost.php?p=67595435&postcount=2
The End
That is my notes on everything I did to get the Sprint PL6 firmware rooted and functional with Voice, LTE, MMS, and Hotspot. I enjoy the phone, and I am SOOOOO happy to have root again. Just for stupid stuff like access NTFS partitions on thumb drives, I connect to my phone, Adaway, Titanium Backup, and just general apps to let me use MY phone MY way.
Again, these are the instructions I followed for what I did. I think I wrote down all the steps, if I missed anything or something is not clear, PM me! I am always here to help when and where I can. If there is an edit to be made, I will make it. There is a bunch of people to thank here, if I forget anyone let me know! If this process helps you, think about giving everyone involved a THANKS for their contribution/hardwork! Samsung is really making life hard for us now after they made it so easy with the S5.
@colormedroid and everyone in the OP of the thread here! This is where I met @YMNDLZ and got really into figuring out the rooting process for The SM-G930P phone.
@YMNDLZ who has put up with my insane posts throughout this thread trying to figure this out. Plus responding to a few PMs with questions
@@bodyshop who suggested the SQLite Editor part for the Hotspot.
@swick1981 for the thread on S7 lag.
The other random threads I read through and picked up bits here and there, and forgot to bookmark.
My wife, for putting up with this crap and my sleepless nights messing with my phone.
I think you should hyperlink on the OP to the PL6 instructions since they are on the 2nd page of the thread.
Great write up guys. This will help many since the other threads have outdated links and zips and instructions...
One thing I wanted to know, do you know where the Update.zip is located on marshmallow so it can be deleted?
I've noticed if the Nougat update was deleted you no longer get the notice to reboot and install it. I'm sure it won't pop up after following instructions, but it can't hurt to delete it completely.
I also froze both packages (com.sec.android.soagent and com.wssyncmldm) in Titanium Backup. Had to search for them and 2 Software update files appeared. I Don't know if it makes a difference but I got that part from the other thread that you posted the link to your instructions in.
bodyshop said:
I think you should hyperlink on the OP to the PL6 instructions since they are on the 2nd page of the thread.
Great write up guys. This will help many since the other threads have outdated links and zips and instructions...
One thing I wanted to know, do you know where the Update.zip is located on marshmallow so it can be deleted?
I've noticed if the Nougat update was deleted you no longer get the notice to reboot and install it. I'm sure it won't pop up after following instructions, but it can't hurt to delete it completely.
I also froze both packages (com.sec.android.soagent and com.wssyncmldm) in Titanium Backup. Had to search for them and 2 Software update files appeared. I Don't know if it makes a difference but I got that part from the other thread that you posted the link to your instructions in.
Click to expand...
Click to collapse
I'll hyperlink the PL6 method in the OP, thanks for the suggestion. The update file is located under data/fota by the way.
YMNDLZ said:
I'll hyperlink the PL6 method in the OP, thanks for the suggestion. The update file is located under data/fota by the way.
Click to expand...
Click to collapse
Thanks...
The superSU still said it needs to update binaries. on 2.79 for me but its still working. On PL6 Sprint
bodyshop said:
The superSU still said it needs to update binaries. on 2.79 for me but its still working. On PL6 Sprint
Click to expand...
Click to collapse
When it asks to update binaries click ok, it'll fail the update and ask you to reboot. After you reboot it'll quit asking you to update.
Does this work for the nougat update from sprint or only the universal firmware?
outerdepth said:
Does this work for the nougat update from sprint or only the universal firmware ROM?
Click to expand...
Click to collapse
Sprint...
QAA and PL6 are Sprint. PL2 is Universal
This is my first attempt of creating any Android Rom myself, so don't expect too much.
Changes to the original OTA update which was the base for all:
Removed Superuser in favour for a fully integrated SuperSU by Chainfire.
Changed some root related settings in the kernel to allow a full root instead of factory default.
Keyboard bug fixed for all included keyboards and added a definition for those cheap wireless keyboards with touchpad you often get with the box.
This means pressing ENTER or OK really does just that instead of only producing unwanted characters.
Several versions for download (once I managed to test and upload all), all include a power menu for Kodi to shut down the box without the need for the IR remote.
General instructions:
Download the RAR archive of your choice and unpack the contents to a micro SD formatted in FAT32.
Insert SD into box and press the little button inside the AV port while you power the box up.
Once the logo appears release the button.
TWRP recovery will start and you should do a full backup of your box first!
I do recommend a full wipe after the backup to avoid conflicts after the firmware installation.
Install the ZIP and reboot once done.
Take your time as the initial boot will take quite some time, especially for the versions with more added programs.
Just the recovery image - for those who need it.
X96 stripped down...
In this version I removed all content from the OTA update that might be considered to be a concern in legal terms.
So no Kodi addons, no streaming apps, just a naked system with the standard Google apps and a modified Kodi.
The crappy file browser was replaced by the FX filebrowser.
For those with the need for more than the Media Box Launcher I added the ADW Launcher as well as the XMBC Launcher to have Kodi as the homescreen.
After the boot is finnished I strongly recommend to update the SuperSU binary.
I left this part manual as a confirmation that the first boot and setup really completed.
Only then can SuperSU update the binary in normal mode with success.
After that reboot to clear the memory and all leftovers.
Once you are done with all modifications and app installations you might need do a full backup trough TWRP again to safe you the time if something goes wrong.
Download RAR
After a lot of swearing, flashing, more swearing and flashing I finally managed to create a fully unbranded system that can be installed through TWRP.
If you still know how the original X96 looks with the original firmware you will be surprised
What has changed from the branded firmware:
Bootlogo original S905X.
Google bootanimation - that was the hardest part, allowing for a custom animation...
Media Box Launcher unbranded and with unbranded theme.
Unbranded Kodi completely removed so the rom will comply with all piracy laws and restrictions - more in the added apps section.
OTA updater removed.
All programs from the branded version removed, so no social media, Chrome, Netflix and so on.
Apart from the naked system with Google apps I included:
AdAway
ADW Launcher
XMBC Laucher for Kodi
File browser replaced by FX filemanager
Power Menu added - still requires to root the box! More under added apps.
Added apps and modifications:
Kodi was removed, but the install script for the addon packs is still valid.
The script no longer refers to the system folder but to /sdcard/apps
This means if you decide to install Kodi you can place the tar.gz archive for the addons in the apps folder of the internal SD.
Kodi itself is not included.
The additional apps I thought to be of use will be in the apps folder of the internal SD.
In FX file explorer it is called "Main Storage".
Here you will find:
Chrome
Facebook
Film On (from the branded firmware)
Lucky Patcher
Mobdro (from the branded firmware)
Netflix (from the branded firmware)
Showbox (from the branded firmware)
Skype
SuperSU by Chainfire
Twitter
VLC for Android
Three different Youtube apps to choose from, including a TV version.
How to install SuperSU:
All modifications to the boot image, scripts, libraries and so on are done and included.
This means the system is rooted except for the actual Superuser app.
Install from the apps folder and let the binary update, once done reboot and enjoy.
Ads...
Not all ads in programs or while surfing can be disabled by AdBlock.
For example everything coming from "trusted sources" like Google will still be allowed.
This is the only reason I included Lucky Patcher as it can be of use for some apps to enjoy without ads.
Install and use at your own risk!
Installation of the ROM:
As before wipe all through TWRP then install the ZIP file from extracted RAR archive - so unpack the RAR first to your SD card.
Installation through TWRP does take a few minutes due to the hash verification.
Since all included apps are integrated into the system the first boot is a bit faster compared to the above ROM.
And the additional apps land on the internal SD for everyone to choose or delete if not wanted.
Please allow about 5 minutes after after the launcher selection appeared before you actually start using the apps - some things are still installing in the background!
Once you finnished the network and personal setup of accounts and such bott into TWRP and make a full backup in case you need it.
A factory reset will set you back to the point of the installation of the rom - so no SuperSU and the added apps folder might be gone too.
Known bugs:
Just noticed the WiFi is not available at first activation.
As the chipset is identified during activation you might have to select the network twice until you see WiFi available.
Watch the boot on Youtube
Download from Filefactory
Beta2 with shutdown using F12 on the Wifi Keyboard and some other fixes. - This is just with the most basic apps.
I finally found a neat way to use the WiFi remote to shut down the box the same way the power button on the IR does.
Just press F12 and you will be asked if you want to power down
Will upload the Beta2 with this fix soon.
What's left to do?
Well, now that there is an unbranded and working S905x system out there it means someone could use it to make a ROM that works on all S905X systems out there...
Just needs including WiFi and where existant BT drivers, libraries and calls....
And of course a recovery capable of working on all boxes but that should not be too hard actually
Update: 12/05/2017:
Beta 3 and a Fully Naked Rom is available now.
The Fully Naked Rom has the FX File Explorer and SuperSU included, apart from that it is a naked Android without any Google apps left - great if you want to play around with different GAPPS packages.
The Beta 3 has some minor fixes and most apps moved into the system area instead of the user space.
If you need more apps or launchers then please check the Playstore.
Both have a system partition inflated to 1536mb, which is the same size as the factory OTA update.
On the Fully Naked Rom you can only install apps through the filemanager as no store of any kind is included.
Update 17/07/2017:
A new firmware was released and finally we have a navbar and notification shade "out of the box".
Other changes include the launcher and Kodi, now you find KD Launcher and KD Player...
The OTA can be found here, just unpack to the SD and use as usual, either with the supplied original recovery or your favourite TWRP.
Only downside is we have a locked bootanimation again
A cleaned rom with the usual fixes for keyboard and root can be found here as my Beta 4.
All removed and some additional apps can be found in this archive, just unpack to your SD and install with FX.
Those with just 1GB system memory or wanting to customise all themself can try the Beta 5, which is made small enough to fit on 1GB systems.
Use the above archive to add the programs you need.
Libreelec for SD or USB install.
Unpack the archive to your PC and use Rufus to get the tar.gz image to your SD/USB stick - all existing data will be wiped.
Copy the dtb.img to the SD, overwriting the existing file.
Plug in the box and boot using a toothpick.
Once Libreelec is set up it will work with the SD/USB inserted without you boot the normal Android from the internal memory.
Videoboot
With this version you can use a MP4 video file instead of a bootanimation.
Works with sound of course and should support every MP4 video the normal video player can play.
For your own video simply replace the bootvideo.mp4 in the systems media folder.
Update 04/06/2017: Finally with Open GAPPS!
The X96 showed some real resistance to overcome the chinese limitations and to allow a working installation of updated Google Apps.
As I already spent a lot of days trying to get it to work I only focussed on Open GAPPS but no manual install or the XIAOMI Gapps installer.
With the troubles in the beginning I created a way of installing it all that worked with no errors for me - I suggest to follow it before you try other ways.
This Beta is right now considered to be in an experimental stage until users provided enough feedback to confirm it indeed works fine.
All is based on a naked and slightly modified Beta 5.
The system itself is pretty much naked except for the usual fixes, everything that could make troubles was removed, this includes:
Camera, video and music, wallpapers and so on - install what you want and need through the playstore once all is working.
Main reason for this was to avoid problems with the GAPPS package and to allow the use on 1GB systems as well.
How to install:
Unpack the RAR archive to your favourite SD card or USB stick.
Plug into the box and start with a toothpick - TWRP will show up.
Go to Wipe, Advanced Wipe and wipe Dalvik/Art cache, Data, Internal Storage and Cache.
Go back and install the X96-no-gapps archive and add the opend gapps archive into the line.
Upgrading the neural network takes a few minutes, once the AI is fully operational the GAPPS package will install.
Simply ignore the fact that some of the listed apps will not be available, like Faceunlock - this is due to the removed camera and other things but also because of our harware platform.
After that reboot.
If all goes well and the intial boot goes well you can simply follow the on screen instructions from the wizard.
In case after 10 minutes the Google animation is still going you have to try again but with a different approach (50/50 chance for the first to work).
Start over with a another wipe as above, then install only the X96-no-gapps firmware.
Reboot and do your usual setup of network and screen settings - don't start any apps or mess with SuperSu yet!
Once all is good reboot into the TWRP recovery and install the Open GAPPS package.
Reboot.
Now all should go according to plan.
Troubleshooting and additional infos:
If neither the first nor the second way of installing works for I suspect that your previous ROM was not based on mine or the OTA firmware.
In this case try one of my other beta firmwares if the included firmware itself already failed to boot.
The initial connection to Google can take 4-5 minutes instead of the advertised 2 minutes, so please allow 5 minutes before you panic.
The additional Google apps are not available at this stage and the loading will stay on the screen until you click next - simply add whatever Google app you need from the playstore.
This included Google Music and Google Play TV.
Again: no additional apps of any kind are included, I suggest to use VLC for audio and video or simply whatever you prefer.
Oh, before you ask: Navbar and notification shade are active and working.
Allow some time and check the notification shade for the updates once the system is running, I did not include all updated versions at this stage.
Download the new Beta 6 - Open Gapps version.
Update 15/11/2017:
They finally released another update, got available two days ago but file date is a bit older.
You can check on the Baidu servers yourself if you like Baidu X96 Downloads
Password there is: hp7u
Download as a RAR from Filefactory.
Once I find some time I will check if and what fixes are needed that I can do.
My new x96 arrived yesterday also I found this thread and instructables yesterday. I'm really glad that you take care of this little machine.:good:
Sent from my I9195I using XDA Labs
Guess I was just in the same boat as everyone else with these noname things.
Figured almost everything out I need, ecxept how to change the bootloader/kernel to allow for a custom bootanimation.
Main thing though was to have a working recovery to avoid weird UBS cables and manual flashing.
I wish I was 2 weeks further so I could test your build but I have to look through these things atm. Its interesting that the youtube tv app hasn't changed for a while.
Too many boxes available but I do think x96 is a solid little machine.
There's also opportunity to work with libreelec.
On my s4mini I have a dolby atmos app running modded by ahrion here on xda. Maybe it would be interesting.,wheather it runs on our little devices or not.
I am working on a fully unbranded firmware for the X96 atm.
The problem of converting USB burn images into flashable ZIP was one problem to get the "unbranded" original firmware to at least install another.
They really don't like you messing with their toys in china LOL
If I can't solve the bootanimation problem I will at least upload the otherwise unbranded version with a choice of launchers and updated apps.
Chinese toys. LOL.
Who has made the custom rom from February 16th. Rar @entertainmentbox?
No clue as I did not do it and did not check either.
But the fully unbranded firmware is on the way to upload
Finally custom bootanimations are possible
The pictures I've seen on instructables are awesome. Nice launcher.
Hope you're having fun tuning these Chinese toys.
Sent from my I9195I using XDA Labs
Congrats to your unbranded system. Hope there will be soon more users for testing and enjoying your work
Fixed the shutdown through WiFi remote problem
Is it possible to have look like the normal android tablet/phone?
Hey Downunder35m http://www.tvboxforum.com/archive/index.php?thread-671.html
Just curious is the remote working? I btw changed the keyboard layout so the annoying enter key is fix as well as added the F1 = Power function
Nevermind I fixed my issues with the remote too. Now it is 100% working.
Wasn't aware that the keyboard needs fixing as it works fine here, including powering down the box
I didn't upgrade to the Beta2
Hello!
I have the X96 box mentioned here. Exactly this 2GB model: https://www.aliexpress.com/item/Hot...32779857015.html?spm=2114.13010608.0.0.dF9x4G
The problem is... No matter what i do, i get the error 7 in TWRP. I tried beta1 and beta2, but same error.
I have tried retrying, rebooting, but no effect.
Any suggestions?
What i did was;
-backup files (to internal memory)
-wipe all (byebye backup )
-try to install image from sd-card or usb-stick (both fat32)
-installed TWRP recovery (which caused SD card not to be recognized anymore)
The recovery is specifically for the X96, I had no time to make a generic recovery for all S905X boxes, but seems it should be the next step here.
The error 7 through TWRP is caused by two things (at least during all my tests):
a) The system is totally wiped and the updater script is unable to find the correct hardware info as the build.prop is no longer present.
For this problem and during my tests it just works if you flash again without a wipe.
So right after the error 7 go back and install the firmware again without any reboot or anything else and it should flash successfully.
b) Your system uses different space allocations for the boot, bootloader and recovery partitions.
For this problem the only real cure is to first use the OTA installer for the genuine firmware to get the system working again.
Then only wipe Dalvik, cache and data - the system partition will be overwritten once the update starts but then the installer can find the build prop and if compatible will continue.
If you have a download for the original firmware I will try to incule your system stuff into the next recovery I make.
Otherwise you can always try the hard way if the system is currently toast anyway:
Open the updater script in the META-INFO folder (down in the last subdirectory) and remove the device check for the X96.
That would be the first two lines of the script- everything before th OTA check.
Downside of this approach is that your entire system will be replaced by mine and if your hardware is differernt or the partition sizes won't match then it still won't boot.
Let me know how you go and I will see that by tomorrow evening I have a universal TWRP for all S905X ready.
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question.
Instead this thread is intended to share experiences as I spend quit some days to become my phone as free from Google.
I did this on a Galaxy A3 (2017) with LOS.
First of course is not to install Gapps. We can replace many of its functionality. First of all we need a store to download apps. I highly recommend FDroid as a first choise. You can download the app at their website.
With this you get a variety of apps for almost all, but not all problems. Nevertheless I recommend to take your time and check what is offered there, even if you used other apps before.
If you don't find an equivalent, you might want access the google playstore. In FDroid there are two apps available for this purpose. With both you can anonymously access all (not payed) apps on Playstore. You can of course login with your google accound, but ... ok, that's not so anonymous anymore
What else do we miss without Gapps. There is a way of receiving push notifications, that is often handled via GCM (google cloud messanging).
First of all we need to enable spoofing. This was quite a challange, as usual tools (tingle, ...) work with non-odexed ROMS, while that for A3 is an odexed ROM.
Finally I found a zip here, that works for me:
https://forum.xda-developers.com/showpost.php?p=77456471&postcount=3775
Download that zip, goto TWRP.
Before installing it you have to do two steps.
Mount /system
Create a link (with advanced/terminal): ln -s /system/vendor /vendor
Otherwise install of this zip will fails. Be patient, it takes around 5..10min to pass.
Now we can work with microG, that will replace some google-APIs.
Add the repo "microg.org/fdroid/repo"
Then install micoG core, fakestore and proxy.
To get unifiedNLP running (this is for location services) the microG core must be a system app.
So do a reboot in the TWRP. Mount system first.
Than copy with integrated filemanager the folder com.google.android.gms-xxxx
from /data/app/
to
/system/priv-app
and reboot.
You will find in your app-overview the microG app - please open and let selftest run.
Enable permissions there and also disable battery optimisation
unifiedNlp should be registered. Next is to enable them.
Download from FDroid these two apps:
Local GSM Location (with this you can download a database of cell towers and their location, giving you a chance to get a rough estaimatin where you are, without waste of energy for GPS)
and
NominatimNlpBackend (to get your position as street/city/country instead of coordinates).
Very important:
Apps that require this gapps need to be installed after microG. Otherwise they will not work properly.
I guess that are usually apps that needs location.
Feedback for microG installation
I´ve tested your microG installation these days. Worked like a charm ! Thanks for your post.
The Nanodroid patcher referred in your link was gone, so i used http://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-18.1.20180909.zip.
I had the same problems with Yalp downloads you´ve described earlier, after reboot it worked.
GCM works, but just not with Threema ;-( But it´s a known problem.
Getting NLP to work was a little bit of hassle, but I found many articles about it. Was not sure which of the backends to use, there are many.
What is interesting - I didn´t use encryption and patched the ashyx_no_encryption patch right after flashing LOS and I didn´t use SU or Magisk right now. Result: absolutely no boot loops and no reboot after power off !
From which stock variant you came ?
@cyberbix:
The patcher for spoofing was quite beta at that time. Did you have to do any preparations to let it run? I remember in TWRP I had to mount /system and create that /vendor-link. Is it still required? I reported my issued there but I am not sure he cooked it with these patches finally.
The Yalp issue is completely independent on microG. It seems that there is a bug in the Downloader of LOS15.1. There are others suffered from this issue, not just the A320FL. The workaround to use internal download works.
Can you give more details about the NLP-hassle? That might help others to not go that painful way. Imho all is fine if you copy (or move) the folder I described above and reboot.
About the backends ... I think there is no alternative for Nominatim, which works only online. For the cell bases location I prefer a offline solution, I found that "Local GSM Location". The microG-Packages usually contain the mozilla-online backend.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I had latest Oreo 8.0 installed before. But I am not sure whether or not I updated the bootloader too with Odin.
@starbright_
Did you have to do any preparations to let it run?
Yes. I did exactly the same as you did in TWRP.
Can you give more details about the NLP-hassle?
I wasn´t sure if its needed at all and even if microG went green, the backends seemed not wo work at all.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I did it in the same way as you. Flashed the patcher, installed the rest from FDroid. That´s it.
Moreover: i didn´t install Magisk or any other root and I didn´t use Xposed. I used the push notification tester to test GCM. Everything was fine.
I can check if installing an su package or Magisk will lead into the same problems.
Installed Magisk on top of your microG setup. Everything works, see McFys thread. I guess you just didn´t read what TB tells about SU.
starbright_ said:
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question..
Click to expand...
Click to collapse
My experience below:
-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green
-yalp works fine, i like it, but in the end i had to use my goggole account instread of the experimental 'internal account' and this because of gmaps
-gmaps works fine BUT it doesn't find the current gps position unless i restart it (long press on back arrow). This is odd because other map-apps (openstreet, tomtom..) work! Also, when i need to use the google account to save some locations or simply the offline maps, it does work only for the first time, later it doesn't recognize my (already set) googke account
-i don't know if it's related to microg but camera doesnt find the gps, while opencamera yes, fotej camera neither
-again, i don't know if it's related to microg but each time i add the google account i loose my contact list
-apps that need to talk with playstore doesn't work at all, I wanted to use Europe3D by geoflier and it didn't load properly until i installed also the playstore
- the same for those apps that need to purchase some addons
-BUT worst, above all (crying) is that the speechTotext is not wotking and it's a feature I really miss!
I don't know if a proper patched rom would work better, I always hope that mcFy finds some time to release the rom already patched.
Anyhow next days I will try to reinstall the stock rom to see if these behavioours happen also there.
I did another installation again. More details next.
But finally I gave up. I couldn't solve two issues
- neither telegram nor whatsapp works after a few minutes (doesn't wake up at incoming calls)
- heavy instabilities with LOS15.1/Magisk/Xposed/microG
I didn't find which component is responsible for that, but I remember that I didn't always get SU with Magisk. After a reboot it works again.
Even such components as DuckDuckbrowser crashed.
I couldn't recover my apps backup by TB from my previous S5mini on A3 with TB and Magisk (Parser error).
I need a rest from all this stuff.
starbright_ said:
I
I need a rest from all this stuff.
Click to expand...
Click to collapse
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
pink0 said:
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
Click to expand...
Click to collapse
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means this.
I installed localGSMbackend which created an offline database with celltowers. This works fine in energy saving mode I get a rough position without any waste of energy or privacy (as offline).
Altogether I did at least 20 complete wipes and started from scratch.
At the first I started early with root (either Magisk or LOS-addsu).
Than there are two options to get a spoofed ROM.
Either via Xposed/Fakestore module or via nanodroid patcher.
Both works in general.
Than installed microG (different ways - manually, nanodroid, unofficial installer, that are the 3 options I know).
But it always become instable. Apps don't get root anymore or does FC ....
So I did it another way around.
I first installed all required via FDroid (without any root, Xposed ...). That seems to me rather stable. The good thing: this are around 80% or apps I need. Than I did a backup, so that I don't have to starts from scratch, which is painful as hell with around 40 .. 60 apps.
My last attempt was after that install Magisk, Xposed, Fakestore. Spoofingchecker was red, but a microG gets green.
I installed it with nanodroid (created first with setup wizard a file, so that only microG and mapsapiv1) gets installed.
This was first time my apps work fine with maps. Other attempts to manually install the maps framework/lib wasn't succesful (why ever).
Problems started when installing TB. First it doesn't get root permission. After a restart it works, but I get parsing errors. If I understand FAQ this is due to different busyboxes ?!? Ok, the backups I created at another device with LOS14.1 and addsu.
But this was not the only issue. Browser crashed and I never get neither Telegram nor Whatsapp to get wake up after a few minutes of deep sleep (they arn't get registered at microG too, so this might be another issue).
@pink0:
Did I understand it right, you use GMaps?
@cyberbix:
My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Does your system keeps stable after all?
To be honest, that Magisk and Xposed seems to add to much intrusive stuff that might fail altogether. But even with the manual way it wasn't perfect. Maybe after a rest and with the next version from McFy I try this again. Good luck I didn't sell my old S5min til now.
starbright_ said:
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means
@pink0:
Did I understand it right, you use GMaps?.
Click to expand...
Click to collapse
it's here i writed down because my personal memory buffer, at my age, is really small
yes gmaps is working quite good except the behavour I wrote, but enabling developer options I can easily kill the program to get the new/current position (also I noriced tgat because of this gps problem ir cannot calculate any route while navigating)
I also dislike the idea of using xposed bexause I never needed it but now it's different
about telegram/whatsup i'm not using such softwae so I can't say what's wrong
starbright_ said:
...My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Click to expand...
Click to collapse
I do not use WhatsApp, I use Threema and Threema has known problems with microG GCM.
starbright_ said:
Does your system keeps stable after all?
Click to expand...
Click to collapse
Yes, but I didn´t flash Xposed, just Magisk.
Ok.That spoofing can happen via Xposed Module or nanodroid patcher. For non-odexed ROMs are more options (tingle,...) but not for ours.
So after all I am now happy with my current installation:
- install TWRP via ODIN
- Wipe in TWRP (system, data, cache, dalvik)
- install Lineage via TWRP
- boot into system
- install FDroid
install and setup most of needed apps - there is a good selection of apps in FDroid now
- Create Backup (via TWRP)
- Install Magisk (viaTWRP) and Magisk Manager in LOS
- Setup adaware and afwall (both from FDroid as they need root)
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
- install Yalp from FDroid and via Yalp the missing apps that are not available via FDroid.
I found that Telegram (and Whatsapp not 100% sure yet) push-notification work. I disabled battery optimization for both.
starbright_ said:
So after all I am now happy with my current installation:
[...snip..]
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
Click to expand...
Click to collapse
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
pink0 said:
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
Click to expand...
Click to collapse
I am not sure, but the LOS15.1 for A3 2017 (by @McFy from 08/21) ROM is in a state you need the patcher. Other methods (as tingle - what I used before with other mobiles) don't work.
Not sure what is odexed and deodexed. The only other method works for spoofing is Xposed framework. There is a module that fakes this. But until now I did't see a need for Xposed and I don't want to increase complexity. (From that point of view I rather should go for addsu instead of Magisk)
I did first a Magisk installation, as root is more important and you have later the chance to chose between microG and Gapps. (Did it step by step with backups not to start again from scratch).
But I didn't use Magisk for installation, but TWRP. How does it works? I am a Magisk newbee.
An update of LOS15 requires to redo it. I also updated microG in this sequence. Just as a short summery:
- boot into TWRP
- wipes system/cache/dalvik
- installed new LOS
- installed Magisk
- reboot into system (just for curiosity, probably not required) and back to TWRP
- let run uninstaller of microG (I used the zips from here: https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- install (run) the patcher (be patients, that takes long time, maybe 15min)
- install (run) setup wizard (selected only few things, as maps-api, can remember exactly)
- install the real package (install what has been selected in setup).
check this out https://hackernoon.com/e-first-beta-soon-to-be-released-82d7ec950dd
basically, this is a LOS-based rom including microG, aiming at avoiding google applications/usage.
or https://download.lineage.microg.org/a5y17lte/
Nominatim backend
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
cyberbix said:
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
Click to expand...
Click to collapse
My selfcheck gives just 2 unchecked points:
Playstore signature (I installed Fakestore+Yalp and Fdroid)
Radiocell based location (altough Nominatem is setup).
"Playstore signature" I could manage after apply permission spoofing to Fake Store (system app).
But, I don't get any app registered, although I have enabled Google registration and GCM.
I even deinstalled ebay and installed it again - no effect. ?!? What can I do?
I remember @cyberbix mentioned the Push notification tester:
It fails for me with step1 - "No register" ?!? How can that be? What did I miss.
[/COLOR]
starbright_ said:
?!? How can that be? What did I miss.
Click to expand...
Click to collapse
Did you do the device check-in ?
See https://f-droid.org/en/packages/com.thermatk.android.xf.fakegapps/
What is push notifcation exactly claiming ? Unable to register or missing Play services ?
Backstory: So got my daughter a bluetooth enabled toothbrush named in title, and loaded up the app for it:
Philips Sonicare For Kids - Apps on Google Play
Transform brush time into fun time!
play.google.com
Running on a OnePlus 6, Android 10 stock firmware other than bootloader unlocked, Magisk installed. Start it up, whines it is rooted and refuses to run. Sputter some colorful language, add app to Magisk Hide, restart, poof, works great.
Now daughter likes it, and don't want to give her my phone twice a day... so open the drawer and pull out an older phone, LG G6. Old firmware, prob full of security issues, figure I'll install LineageOS on it. OK, great, get through all that, shiny running system... repeat app install... and ugh... "t3h r00t3d phone!".
This time, Magisk Hide isn't "fixing" the problem, and I am curious what the difference is... same app version on both phones. Safetynet check passes on both phones. The only real differences I can cite are (1) Android 11 OS base and (2) Roar Gapps MiniMe build (vs full Gapp suite on stock OnePlus rom). At this point, there aren't other apps on the device (e.g. SuperSU or similar usual suspect).
Any suggestions on what is different that an app could check and call out a rooted phone?
Answering my own post, in case anyone searches this and finds it helpful...
Turns out this app appears to blacklist Lineage OS.
Reflashed clean, OS only... fail. (No root or safetynet at this point)
Added somewhat normal Gapps, now with working safetynet... fail.
Didn't need to install Magisk at this point.
Lets test the theory... grab another OS image at random, flash it (still no Gapps, Magisk, SN)... success!
Install Magisk, still success!