Phillips Sonicare for Kids Root Check bypass wtf - Android Q&A, Help & Troubleshooting

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!

Related

[GUIDE] XPOSED on FIRE STICK

For those who use Xposed framework and would like to use it on the Fire stick ive managed to find a way how to install xposed v85 on Fire stick without a recovery.
Ive successfully installed it onto my own Fire Stick and a friends Fire stick.
Before you go on im not responsible for any bricking you might encounter.
Your more than welcome to wait for Rbox to release a custom recovery for the stick.
Please note, im only passing on what i found and tried, i did not make the tool.
Be very careful on what modules you install, again im not responsible for any bricks that might arise.
This obviously requires root. Im rooted with kingoroot.
The Fire sticks i tested where on 5.0.5 and 5.2.1.0
If your on a higher firmware version and are rooted use this guide and come back:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
Im explaining the guide from a windows pc and using the program ADBlink to transfer files, if your going to do this a different way please modify instructions to suit.
First download this:
http://s000.tinyupload.com/index.php?file_id=13649473132596741692
Next extract the folder to your desktop.
Open up ADBlink and connect to your Fire stick.
Upload the entire contents to your Fire sticks internal sd card, (make sure the files are going to /sdcard).
Head over to your Fire stick and install busybox, open busybox up and click install and wait till its finished.
Very important to click install inside of the Busybox app, if it wont let you exit the app and try again. You will have problems trying to run the script further in the guide
Install Terminal (not sure if this step is necessary as you will be using ADBlink's ADB Shell, but it was used when i found this info). Finally install Xposed installer, make sure you DO NOT open the Xposed apk yet, just click done.
Now if you used a different way to do this and the files are not in the /sdcard directory now is the time to move them to the /sdcard directory.
Back over to windows pc.
Click ADB Shell in ADBlink (you should have it still open and connected to your Fire stick).
Type the following commands:
su then hit enter.
sh /sdcard/installer.bin then hit enter.
Choose option 1 hit enter.
You will see alot of errors, ignore these and restart your Fire Stick.
It will take a while to boot and go to the optimizing apps screen and take about 10 minutes to boot up.
After its booted go ahead and check Xposed is installed !
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Would be a good idea to list working modules you guys might try, give the community a heads up on whats working.
I will update the guide with modules i test and/or you guys report work.
*edit***
This also works on 5.2.1.0, was informed by user @metallica this worked on 5.2.1.0
Ive just got the time to test this on a brand new Fire Stick and can confirm it also.
Thanks @metallica
*edit
*Ive now successfully installed xposed v85 on 6 Fire Sticks*
Working Modules: (not limited to, just ones ive tried or been told work)
AdBlocker
Lucky Patcher
RootCloak
SpotifySkip
YouTube AdAway
RboxFireTvMods v1.4 *This mod will hide stock launcher without disabling settings* (finally got amazon screen launcher gone)
*update*
I should of included this information when I made the guide but in order to be able to select and activate any xposed mod in xposed menu after you have installed it using the fire stick remote alone will not allow you to navigate to the checkbox and put a tick into it.
In order to do this you must have an app to turn the remote into a mouse or some other way to manoeuvre the pointer.
The 3 ways I know of doing this are:
1/ Mouse toggle for fire tv. This is the easiest way but its a paid app. Download it from Google play and send it to your Fire TV.
2/ Droidmote server, agaim another paid app from Google play store but this must have Google play store/services installed as to allow for license check. There is a guide to follow to have this installed on here somewhere.
3/ Use Bluetooth mouse if you have one.
4/ Use an USB mouse with an OTG connector, the commands to start OTG are on AFTVnews.com, I have this command autorun at boot to enable otg after a restart (very handy).
There may be other ways but these are the omes ive had experience with and use myself.
As per usual I recommend that you wait for a working recovery system, if you install something from an Xposed Module & it bricks your Stick you will have no way back! Rbox is working on the recovery & a prerooted rom for the stick. Use at your own risk I would say.... this is just a helping hand & I'm not trolling your thread, just some newer users may not know the risks.
deanr1977 said:
As per usual I recommend that you wait for a working recovery system, if you install something from an Xposed Module & it bricks your Stick you will have no way back! Rbox is working on the recovery & a prerooted rom for the stick. Use at your own risk I would say.... this is just a helping hand & I'm not trolling your thread, just some newer users may not know the risks.
Click to expand...
Click to collapse
I think I have made my point already about the risks involved and im almost certain that anyone wanting xposed on the fire stick will already know the risks, as with anything involving root/xposed etc.
I have tested this myself and know it works and have listed some modules I have installed that work fine. As long as people stay away from modules that are definitely no use to fire stick and heavily moddify /system (im sure when reading the description of modules it will say in the write up about them) I cant see there being any problems.
I will continue to list any modules that I find are of any use to fire stick and list them here. If people want to wait for a custom recovery that is there choice, as ive pointed out in the guide. In my eyes everything you have said is already pointed out in the first post.
Also I will add as long as your Rooted and have a working adb connection either through WiFi or USB there is a chance you can come back from a bricked state with my other guide I put together.
sconnyuk said:
For those who use Xposed framework and would like to use it on the Fire stick ive managed to find a way how to install xposed v85 on Fire stick without a recovery.
Ive successfully installed it onto my own Fire Stick and a friends Fire stick.
Before you go on as i stated ive installed it onto 2 fire sticks i am not responsible for anyone's Fire stick bricking.
Your more than welcome to wait for Rbox to release a custom recovery for the stick.
Please note, im only passing on what i found and tried, i did not make the tool.
Be very careful on what modules you install, again im not responsible for any bricks that might arise.
This obviously requires root. Im rooted with kingoroot.
The Fire sticks i tested where on 5.0.5, i do not recommend this to be tried on 5.0.5.1 or 5.2.1.0.
AGAIN, this is for 5.0.5, ive not tested on any other firmware version !!!
If your on a higher firmware version and as the Fire sticks are still rootable you can hop over to my other guide on how to downgrade the Fire stick then come back afterwards:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
Im explaining the guide from a windows pc and using the program ADBlink to transfer files, if your going to do this a different way please modify instructions to suit.
First download this:
http://www.filedropper.com/xposedfirestick
or
http://www.megafileupload.com/76x5/Xposed_Fire_Stick.rar
Next extract the folder to your desktop.
Open up ADBlink and connect to your Fire stick.
Upload the entire contents to your Fire sticks internal sd card, (make sure the files are going to /sdcard).
Head over to your Fire stick and install busybox, open busybox up and click install and wait till its finished.
Very important to click install inside of the Busybox app, if it wont let you exit the app and try again. You will have problems trying to run the script further in the guide
Install Terminal (not sure if this step is necessary as you will be using ADBlink's ADB Shell, but it was used when i found this info). Finally install Xposed installer, make sure you DO NOT open the Xposed apk yet, just click done.
Now if you used a different way to do this and the files are not in the /sdcard directory now is the time to move them to the /sdcard directory.
Back over to windows pc.
Click ADB Shell in ADBlink (you should have it still open and connected to your Fire stick).
Type the following commands:
su then hit enter.
sh /sdcard/installer.bin then hit enter.
Choose option 1 hit enter.
You will see alot of errors, ignore these and restart your Fire Stick.
It will take a while to boot and go to the optimizing apps screen and take about 10 minutes to boot up.
After its booted go ahead and check Xposed is installed !
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Again im not responsible for anyone's Fire Stick and/or any modules you may try.
Would be a good idea to list working modules you guys might try, give the community a heads up on whats working.
I will update the guide with modules i test and/or you guys report work.
*edit
*Ive now successfully installed xposed v85 on 6 Fire Sticks*
Working Modules:
AdBlocker
Lucky Patcher
RootCloak
SpotifySkip
YouTube AdAway
RboxFireTvMods v1.4 (finally got amazon screen launcher gone)
Click to expand...
Click to collapse
Assume this will work on gen 1 AFTV box w OS5? (feel late to the game)
I have/still have xposed installed from when it was running OS3. Do I need to flash the uninstaller?
Also what version youtube are you using to get Youtube adaway to work? Thanks
KLit75 said:
Assume this will work on gen 1 AFTV box w OS5? (feel late to the game)
I have/still have xposed installed from when it was running OS3. Do I need to flash the uninstaller?
Also what version youtube are you using to get Youtube adaway to work? Thanks
Click to expand...
Click to collapse
Ive no idea if this works with gen 1 FTV. With the gen 1 FTV now having custom recovery you could flash the zip the normal way to have xposed on (Im sure you would flash the same version, arm 22?) please double check that first.
I put this guide together for use with the fire stick, as it has not got a custom recovery and we cant use the tool flashify.
I use the latest version of youtube downloaded directly from within the fire sticks interface.
sconnyuk said:
Ive no idea if this works with gen 1 FTV. With the gen 1 FTV now having custom recovery you could flash the zip the normal way to have xposed on (Im sure you would flash the same version, arm 22?) please double check that first.
I put this guide together for use with the fire stick, as it has not got a custom recovery and we cant use the tool flashify.
I use the latest version of youtube downloaded directly from within the fire sticks interface.
Click to expand...
Click to collapse
Well it's gen 1 but running OS5 so I'm pretty confident it'll work but was just hoping for confirmation (if not from you then anyone who may've tried it).
That's interesting that the adaway is working with amazon stock youtube. I used to sideload one from playstore and it had it's glitches because it was designed for tablets. Even the android tv version wasn't perfect but the ads got blocked at least.
KLit75 said:
Well it's gen 1 but running OS5 so I'm pretty confident it'll work but was just hoping for confirmation (if not from you then anyone who may've tried it).
That's interesting that the adaway is working with amazon stock youtube. I used to sideload one from playstore and it had it's glitches because it was designed for tablets. Even the android tv version wasn't perfect but the ads got blocked at least.
Click to expand...
Click to collapse
Since theres a custom recovery in place for fire tv 1 if I was you too minimise any risk id follow the guides on AFTVnews on installing TWRP recovery. Then at least if you run into problems you can restore it.
I have xposed on my gen 2 fire tv and im sure its 64bit version, but the gen 1 and fire stick are just normal arm version(sdk22 for 5.1)
Yes, the stock amazon youtube, whole better experience when ads are removed.
I followed the guide and successfully installed xposed and a few modules (AdBlocker, YouTube AdAway, and RboxFireTvMods).
Unfortunately, somewhere along the way I lost the stock launcher. My firestick is on OS v5.0.5 as per the guide and I also have FireStarter V.3.2.3 installed and running fine, so my firestick isn't useless. I can still launch FireTV Settings from the apps menu but FireTV Home is no longer there. I also made sure that it wasn't just hidden and oddly enough it is still listed under the hidden apps menu, although I have it unchecked so that it should be visible.
Is there some way that you are aware of to get the Stock launcher back without factory resetting?
skwirmy444 said:
I followed the guide and successfully installed xposed and a few modules (AdBlocker, YouTube AdAway, and RboxFireTvMods).
Unfortunately, somewhere along the way I lost the stock launcher. My firestick is on OS v5.0.5 as per the guide and I also have FireStarter V.3.2.3 installed and running fine, so my firestick isn't useless. I can still launch FireTV Settings from the apps menu but FireTV Home is no longer there. I also made sure that it wasn't just hidden and oddly enough it is still listed under the hidden apps menu, although I have it unchecked so that it should be visible.
Is there some way that you are aware of to get the Stock launcher back without factory resetting?
Click to expand...
Click to collapse
Rboxfiretv mods disables it.
You can still access the settings by the fire tv settings icon but if you want to see fire tv stock launcher you cant have Rboxfiretv xposed mod running.
Also very glad to see another user benefiting from this guide
sconnyuk said:
Rboxfiretv mods disables it.
You can still access the settings by the fire tv settings icon but if you want to see fire tv stock launcher you cant have Rboxfiretv xposed mod running.
Also very glad to see another user benefiting from this guide
Click to expand...
Click to collapse
Ahh, that was the problem. Thank you very much for the quick and informative reply!
I need to do some more research into that module. It appears from the reading that I should be able to use the stock launcher with it enabled since it has options for modifying what is displayed in the stock launcher. Of course this all should be addressed in that post. Its good to highlight that this may occur for other people though. Thanks again!
skwirmy444 said:
Ahh, that was the problem. Thank you very much for the quick and informative reply!
I need to do some more research into that module. It appears from the reading that I should be able to use the stock launcher with it enabled since it has options for modifying what is displayed in the stock launcher. Of course this all should be addressed in that post. Its good to highlight that this may occur for other people though. Thanks again!
Click to expand...
Click to collapse
Your welcome.
The mod is quite old and has not been updated in a while.
It is useful to disable the stock launcher, that is what I use it for, disabling certain things from the Amazon launcher is broke, im not sure if and when Rbox is updating it.
There is a guide I followed to remove some menu features before (photos, music etc) through adb commands.
The same thing can be accomplished by using Titanium backups freeze feature as long as you know which ones to disable.
Here are the ones I disabled on my fire stick:
package:com.amazon.precog
package:com.amazon.recess
package:com.amazon.whisperplay.contracts
package:com.amazon.bueller.photos
package:com.amazon.kindle.cms
package:com.amazon.client.metrics
package:com.amazon.device.software.ota
package:com.amazon.whisperlink.core.android
package:com.amazon.application.compatibility.enforcer
package:com.amazon.whisperplay.service.install
package:com.amazon.device.software.ota.override
package:com.amazon.bueller.music
This is info found at:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
Thanks to @Ludacrisvp
Well xposed is working on aftv1 box but youtube adaway (probably the only mod I care about) is not.
Which version of youtube is working? I have 1.2.0
KLit75 said:
Well xposed is working on aftv1 box but youtube adaway (probably the only mod I care about) is not.
Which version of youtube is working? I have 1.2.0
Click to expand...
Click to collapse
The latest one downloaded directly from Amazon.
I have the same set up on my fire tv 4k box with latest youtube and xposed youtube adaway and it works on that also.
I might add also make sure you have the latest xposed framework installed.
I can confirm, this Xposed installation work with 5.2.1.0 too, have successfull installed on my rooted Firestick in my Kitchen xD experimental tested *fg*
damn good work. @sconnyuk can you build a installer for fully working google play? Just a idea.
Gesendet von meinem LG-H850
EDIT: Adaway and Rbox Tools working without issue
MetaIIica said:
I can confirm, thisXposed installation work with 5.2.1.0 too, have successfull installed on my rooted Firestick in my Kitchen xD experimentsl tested *fg*
damn good work. @sconnyuk can you build a installer for fully working google play? Just a idea.
Gesendet von meinem LG-H850
Click to expand...
Click to collapse
Thats good news. I will test this myself and update the guide tomorrow.
As for Google playstore, that would be the icing on the cake, its what im trying to find an answer for at the moment.
The closest and next best thing I have is my Google account and Google services setup so im able to use my paid apps that do a license check.
Also using DroidMote on firestick is excellent.
morning, i install it on my firestick (same config) in the living room to see it will work again...
but i'm sure it will work
Gesendet von meinem LG-H850
Only way I can think of Google play store installation would be with flashify:
https://play.google.com/store/apps/...ery&pcampaignid=APPU_1_kWqFV-OkMevCgAa28oSIAg
With gapps version arm-5.1-pico from this page:
http://opengapps.org
BUT IVE NOT TESTED THIS.......
As im unsure if flashing this would brick the device.?
Has anyone tried using Flashfire?
http://flashfireapk.com
I'm just curious. It works on Fire Tablet running OS5 and I've ONLY used it on that. I'm not looking to possibly contribute to a bricked device, just wondering if it's been tried...
Feels like I'm beating a dead horse, but I can't understand why Youtube Adaway isn't working with Youtube 1.2.0 on my device. Pretty sure that's the latest version because there's no update available. According to others it works.
***What would be cool is to get Awesome Popup video to work fully with xposed. I was able to use it on OS3 but never could get it working right--open youtube video, have option of playing in a smaller window while I go to another app.
All I could do was get it to work with videos from within the awesome popup UI, which is no where near as good (much smaller selection, can't access your subscriptions, playlists, etc.)
KLit75 said:
Has anyone tried using Flashfire?
http://flashfireapk.com
I'm just curious. It works on Fire Tablet running OS5 and I've ONLY used it on that. I'm not looking to possibly contribute to a bricked device, just wondering if it's been tried...
Feels like I'm beating a dead horse, but I can't understand why Youtube Adaway isn't working with Youtube 1.2.0 on my device. Pretty sure that's the latest version because there's no update available. According to others it works.
***What would be cool is to get Awesome Popup video to work fully with xposed. I was able to use it on OS3 but never could get it working right--open youtube video, have option of playing in a smaller window while I go to another app.
All I could do was get it to work with videos from within the awesome popup UI, which is no where near as good (much smaller selection, can't access your subscriptions, playlists, etc.)
Click to expand...
Click to collapse
You could try the obvious, uninstall youtube disable xposed mod reboot, reinstall youtube from Amazon and re enable xposed mod.
As for flashfire, it won't work as it requires chainfires supersu.
Until a way tp swap kingoroot for supersu comes along then we can only wait for custom recovery.
second firestick running 5.2.1.0 in living room successfull xposed installed after small issue (newest kingo root from homepage must be installed)
think this with Kingo Root is a important information!
after rbox tools, stick start faster *fg*
Gesendet von meinem LG-H850

[HOW-TO] CM 11 and beyond for the 8 GB Nook Tablet, BNTV250a

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.

[ROOT METHOD] 2018 Updated Stock firmware

Hello all, I have been driving myself mad all night trying to root my friends phone because it's close to unusable today. I figured I give him root to help with battery and memory.
All the root methods listed in this forum technically will work but only with a custom ROM which will very likely require a custom kernel and bootloader.
Today I save your time and sanity with the latest and greatest in root technology. MAGISK.
==============================================
Files
--------
Stock G900T ROM (For if you mess up)
Compatible TWRP
Odin
Official Magisk Thread - Grab the zip
==============================================​Guide
--------
I ran into some weird behavior during this so be sure to read carefully and follow everything word for word.
1. Preparation:
- Put magisk zip on an sd card or internal storage of the phone
- Ensure drivers are installed. Open Odin and put device in Download mode. (Hold power, volume down and home until you arrive at the download mode screen), Plugin the phone and make sure you see "added"
- If you don't see the added dialogue install the proper drivers for the phone.
- If you see added, you can move on.
2. Flash TWRP:
- In the options tab make sure only F. Reset time is checked.
- Select the box AP and navigate to the TWRP tar.md5 file, the UI will stop responding for a minute while it calculates and checks the md5 hash to authenticate it.
- Then hit start, wait until the box says PASS. If you forgot to uncheck reboot, quickly put the device into recovery mode. (Holding power, volume up and the home button)
- If the phone is still in download mode just put it in recovery mode, and allow TWRP to modify.
3. Flash Magisk
- Don't worry here, Magisk is systemless and if something goes wrong there are no consequences. Go to install and navigate to magisk zip file.
- Swipe to flash it.
4. Check. Make sure root works. Use a root check app like the one by JRummyapps.
- grab a couple apps that require root and test them, make sure magisk can give root perms.
- There's a possibility that Magisk's app wasn't installed correctly. You can extract the zip to get the APK file from inside and install it manually.
- If magisk manager is installed, and you can't seem to get the superuser perms, install SuperSU, and install the supersu binary via TWRP/CWM
- You can now choose which super user you want.
5a SuperSU
- Uninstall Magisk by going to the app and hitting install, count to 5 then reboot.
- Go back to SuperSU and install the binary again via TWRP.
- You should now have root.
5b Magisk
- Uninstall SuperSU my removing the app.
- Test a root needing app if it doesn't work, reboot to recovery and reflash magisk, then reboot to android, and test again, you should have root.
worked for me.
no need to download a root checker app if your on stock since samsung tells you its rooted and how bad it is for your phone.
i used adb for most so i got a su shell and confirmed that way too.
Google's "uncertified device" scheme is driving me mad!
Good job, Vamp!
Were you able to determine if the method that you described resolved the Google "uncertified device" problem? Also, does it bypass Google SafetyNet?
The Google's "uncertified device" scheme is driving me mad. I went through several cycles of installing stock Play Services and Play Store. Each time I would immediately re-gain access to Play Store and the gremlins in my phone would immediately disappear. (Gremlins such as "Running Applications" app and widget becoming intermittant, Total Recall recorder not responding to incoming calls, "Android Services" (with the fanbelt and pulley icon) increasing to 30-40% CPU utilization, etc.) In the meantime, some apps (notably in my case "NOAA Weather" app, which I have subsequently come to believe must be a Google shill) would complain about not being able to work without updating Play Services. I had to update Play Services to avoid the pop-ups. But doing that appears to be a final nail in the coffin. Soon after, symptoms reappear and it becomes increasingly difficult to get into the Play Store by reverting to old Playstore/Play Services versions.
Finally I finally white-listed my SuperSu rooted S5 stock MM on Google's "ROM developer" white-list website. In a twinkling of an eye, Google obviously "flipped the switch" for my phone and I had immediate access to Play Store. I then began locking down the same misbehaving apps as always by freezing with Ti and blocking Internet access with Netguard. As I did each lockdown step, I made sure that I could open Play Store and see my apps. After finishing, I assumed that all was well, as I could still see my apps in Play Store.
Not to be... After the passage of a few hours or less, enough time for the Play Store app, the tweaked Google Services, and whatever installed apps are tightly integrated with Play Services and are reporting the phone state back to Google (e.g., the NOAA Weather app) provide enough information back to Google, another switch appears to gets flipped. The phone again enters the same chaotic state described above, finally sutting down from thermal overload caused by "Android System" swallowing up an enormous quantity of CPU cycles.
Thus it appears to me (after much experimentation) that the new Play Services (12.6.75 and then 12.6.85) appear to enforce or re-enforce the "SafetyNet" scam. It appears that Google may be scrambling to get the lockdown tweaked without burning customers' batteries too much, as they seem to be updating Play Services at an alarming rate.
Peeking at some of the Google Services databases at /data/data/com.google.android.gms/databases using SqLite is enough to make the devil blush; and those likely to be most incriminating are encrypted. For the latter, only their structure and key field identifiers are visible, not the data. NOAA Weather appears by itself in one of the visible databases. I stored away a TWRP image of the entire phone in this state in a safe place should I need to prove up this nightmare in the future.
The bottom line is that I bought an $850 phone several years ago with an OS (subsequently force-updated to Marshmallow) and a set of Google system apps, in a technical and legal environment that did not exclude customizing my phone or the use of privacy tools such as Ti and Netguard. Now Google appears to be intruding physically into my phone in order to suck out data (even though sync is off) and change my settings ("sync data" continues to get re-enabled as does "auto-update" in the Play Store). And, (at least as it appears tentatively) software (probably the new Play Services) is being planted that could eventually phsically destroy my phone by causing too many thermal overload shutdowns.
I am seriously hacked, both literally and emotionally!
A Bit Confused...
Your heading says: "[ROOT METHOD] 2018 Updated Stock firmware."
But then you say:
"All the root methods listed in this forum technically will work but only with a custom ROM which will very likely require a custom kernel and bootloader."
It is unclear whether by "in this forum" you mean in the T-Mobile Galaxy S5 Android Development forum or in your thread.
So, were you successful with installing Magisk on TMO Galaxy S5 (SM-G900T) with stock ROM? If so, which version of Android? Stock Marshmallow 6.0.1 per chance?
Thanks!
Stock ROM is the latest 6.01.
USA (T-Mobile)
2017-04-02
Version
PDA
6.0.1
G900TUVU1GQC2
CSC
So... going to this from LOS 15.1 would this be the order:
Backup (if that's the way you roll)
ODIN the latest stock firmware (GQC2 2017 from TMO)
Reboot and let it get into the system for the initial party time
Follow the steps in the OP
Is that about it?

Live without Gapp - FDroid, Yalp, microG at a LOS15.1

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 ?

Failing SafetyNet shortly after a fresh upgrade install of Rooted Stock US998 30b

I decided that I needed a fresh start with my LG v30+ after over a year on Oreo, and figured I would go ahead and wipe everything and install rooted stock pie per this thread (using the TWRP flashable method).
From there, I went ahead and installed the Magisk Modules for Busybox, Riru - Core, and Riru -EdXposed, because I wanted to have a few Xposed modules. I started out with XPrivacyLUA, and GravityBox [P], making TWRP Backups and checking SafetyNet status after each install. Because it kept passing every time, I got complacent, and stopped checking. I installed Buttered Toast Revived, GM Dark Theme Enabler, and MinMInGuard in EdXposed, followed by several apps. I then installed the 4.4.153_haumea_I.base_1.9_3 kernel, and a bunch of more apps.
It was around this time I decided that I should try and set up Google Pay, only for it to complain about the device it was installed on. I went back to Magisk Manager and sure enough I was failing SafetyNet checks on both ctsProfile and basicIntegrity. And because I wasn't checking every step of the way, I don't know what caused it to break. I've tried unloading the various modules but none of them seem to be a smoking gun, as both check continue to fail even when some or all of them are turned off.. It's not the custom kernel is it? and if so, what do I do to to roll back to stock?
I also looked into the Magisk Module, MagiskHide Props Config but the developer of that says it doesn't have much chance of fixing basicIntegrity fails. Also, they don't have a device fingerprint in their database for v30+ Pie yet. So when I have some free time to dedicate to phone tinkering, I'm going to back up what I have now, revert to an earlier backup from before things broke, pull a getprop ro.build.fingerprint, and then restore my backup of the current broken state so I can give it a try anyway. Because I'm stubborn like that.
That is, unless I get easier suggestions to try first. Passing SafetyNet would be a nice to have thing, but I wasn't passing before I did my wipe, and so I won't really miss it if I'm not passing now either.
Try looking through here: https://github.com/ElderDrivers/EdXposed/issues/386
Seems a recent SafetyNet update is halfassedly checking for the edXposed Magisk module and workarounds are hit-and-miss, with no word from the dev(s) if they're working on it or intend to.
Septfox said:
Try looking through here: https://github.com/ElderDrivers/EdXposed/issues/386
Seems a recent SafetyNet update is halfassedly checking for the edXposed Magisk module and workarounds are hit-and-miss, with no word from the dev(s) if they're working on it or intend to.
Click to expand...
Click to collapse
This was it. Blacklisting Google Play, Google Play Services, and Google Services Framework in EdExposed (the suggested workaround) seems to be working for now.
And if anyone's curious, the device fingerprint on my US998 30b is
Code:
lge/joan_nao_us/joan:9/PKQ1.190414.001/192451445de41:user/release-keys
Not that that's changed at any point in my installation process, according to the backups that I've checked. So MagiskHide Props Config wouldn't have been any use, because that wasn't the problem in the first place.
radwolf76 said:
Code:
lge/joan_nao_us/joan:9/PKQ1.190414.001/192451445de41:user/release-keys
Not that that's changed at any point in my installation process, according to the backups that I've checked. So MagiskHide Props Config wouldn't have been any use, because that wasn't the problem in the first place.
Click to expand...
Click to collapse
Well I mean...the device fingerprint is only a contributer to the long list of crap that'll trip Safetynet; Google really, really doesn't want non-compliant devices to use Safetynet apps. The scans have become quite invasive.
All the official ROMs should have compliant fingerprints, anyway.
Thing is...I didn't mean "halfassedly" in a offhand or facetious way; they probably have implemented a check, in an experimental and thus inconsistent way, that only catches the module often enough to be annoying. Or the way they're checking might depend on other things in the environment (looking for signs of its presence rather than the module itself), which would explain why the workaround works on some phones and not others. Try to keep track of any root- or Magisk-requiring changes you make.
I couldn't get a pass when I tried a few days ago, and ultimately couldn't figure out why despite doing the usual stuff and the workaround above. Decided Ingress and PokeGO were more important than GravityBox, which I've done without for years anyway :v
Enjoy being able to pass the checks, but be prepared for it to break at any moment. Google has been annoyingly persistent about patching workarounds, and the workarounds for the patches to workarounds, and so on.
I've had the same problem, although blacklisting Google play, Google services framework, and Google play services didn't help.

Categories

Resources