When the Verizon S5 first got SS, there was a zip floating around on XDA with the stock browser for the S5. I've been looking and Googling(Googlin?) for it but all the ones I try give me constant fc's.
Anyone have a link or zip of a working version?
jayandare said:
When the Verizon S5 first got SS, there was a zip floating around on XDA with the stock browser for the S5. I've been looking and Googling(Googlin?) for it but all the ones I try give me constant fc's.
Anyone have a link or zip of a working version?
Click to expand...
Click to collapse
Your request is vague, leaving us without a clear idea of what you need. What is wrong with your existing S-browser? For that matter which S5 model and carrier is this for? Are you talking about the SM-G900V on Verizon?
What firmware version do you have? Is your phone rooted? What do you mean when you say "zip"? A zip file is simply a compressed file. Or did you actually mean a flashable zip file which is something different.
You didn't tell us how you tried to install the other S-browser versions.. but the forced closures are usually caused by people failing to wipe cache and data in the settings menu application manager, followed by wiping the phone cache from recovery mode.
.
A cursory Google search suggests that Verizon may not include the necessary S-browser libraries on their phones. Just one more thing that would cause the app to crash. Way to go Verizon. If you have a rooted, Verizon phone then you can install S-browser as follows (or alternate directions here):
Download these two files:
PORTED_S5SBROWSER.7z
libswev8.so
Extract the S-browser files (Sbrowser.apk and SbrowserTry.apk) from the zip to the /system/app/ directory
Confirm that permissions are set to 0644
The three library files (libsbrowser.so, libsbrowser_ext.so, libswev8.so) go to /system/lib/
They require 0644 permissions as well
After rebooting, S-browser will probably work fine for you. But it's good practice to clear the caches, particularly if you had a previous S-browser installation.
Go to the settings menu:
Settings > Applications > Application Manager > All > Internet > Force stop > Clear cache > Clear data > OK
Now go to recovery mode
Confirm that your device is off by removing the battery for a few seconds. Then replace the battery.
Press and hold the volume up, home and power keys at the same time until you see the phone enter recovery mode on the screen
Choose wipe cache from the menu and confirm.
Your phone will then reboot normally. You may see an "Android is updating applications message". This is routine and is just the OS doing a one-time update (rebuild) of your cache.
Enjoy your working S-browser.
.
Related
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
DISCLAIMER
The process of flashing a custom recovery/kernel/firmware may and will trigger your device's Knox Counter. Neither XDA nor I can be held responsible for your actions. Proceed with caution. During this process you will lose all your settings and apps. As long as you follow the instructions, your device's storage, internal and external, won't be touched
Still not compatible with x64 systems! Not compatible with Samsung 5.1.x (sdk22) ROMs!
Hello, Ladies and Gentleman
Many people seem to have a hard time to understand how all of this here on XDA works. I constantly get PM's from users, asking how to do the most basic stuff like flashing a .zip or stock firmware via Odin. Usually, I don't even read them and just hit delete. I know it's not ok to deny people help, so I decided to show you how you can get Xposed working on your TW based stock or custom ROM since it's the most frequently asked question I get.
It's nothing you couldn't do if you'd just....
We're going to use @arter97's customized Xposed Framework as the one made by @darkera13 needs the user to manually modify and replace files which may be too complicated for some.
Preparation
-READ EVERYTHING OVER AND OVER AGAIN.
-A custom recovery System like TWRP or CWM (PhilZ or Stock)
-A deodexed ROM. It's the only way to go. YOU NEED A DEODEXED ROM. If your ROM is not deodexed and you flash the framework, you'll end up in a bootloop. To deodex your existing ROM carefully follow Post #2
Here are a few made by XDA Senior Member @_alexndr
Stock deodexed for SM-N9005 Galaxy Note 3 International Qualcomm.
Stock deodexed for SM-G900F Galaxy S5 International Qualcomm
-And the framework itself from here
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
-Flash a custom recovery system of your choice. This is listed under preperation on purpose since this guide is about getting Xposed on your TW Lollipop device. A guide on how to get a custom recovery system is most certainly available in your device's forum.
-Store the ROM and the Framework in an easy to find folder, which we're gonna call "folder x". It doesn't matter where you store it (ext. SD or int. SD)
The Fun Part
-Boot into your custom recovery and make a full wipe:
TWRP users: "Wipe>Advanced Wipe> Tick System, Data, Cache, Dalvik Cache> Slide to format.CWM users: "Mounts and Storage> hit Format /System; hit Format /Data; hit Format /Cache.
-Still in recovery system, install, or flash the files we put in folder x;
TWRP users: "Install> Navigate to folder x and choose the ROM file first> Add Zip> now choose the Xposed Framework from folder x> Slide to flash.CWM users: "Install Zip> Choose zip from /sdcard if folder x is on internalt storage or /storage/sdcard1 if folder x is on ext. storage (SD-Card)>choose the ROM file first> -Yes - install ROMXY.zip.Do the same with the Xposed Framework zip file.
-Still in recovery system, reboot device and wait for it to boot. It can take up to 20 minutes. Enjoy Xposed on your Samsung TouchWiz Lollipop ROM.
-Stuck in a bootloop? Try this and repeat the process.
XDA Senior Member @Honzze kindly pointed out to keep following in mind; You have to start JoelDroid Lollipop Batch Deodexer with Admin permissions. Otherwise this error might return "path variable" of Java "is not set".
Deodexing your existing ROM without having to flash an entire ROM
As the title says, with this awesome guide by XDA Senior Member @townsenk you don't have to reflash an entire new ROM to your device. Instead, youll just deodex those parts of your System which need to be modified in order to get Xposed working. You don't necessarily have to perform a full wipe if you do it this way. But if you encounter fc's or end up in a bootloop, you know what to do
Guide for this guide:
Regarding point 1: "...launch a DOS shell..." just means, you need to open the so called "CMD" programm in Windows. To "launch a DOS shell" or CMD from within a folder, you simply have to hold down the shift key and right click in that folder. The context menu will show an entry "open command window here". And that's it! (Windows XP users may have to search the internet for another solution)
For Galaxy S5 and Note 3 users: If ADB returns "device offline" or an empty line after "List of devices attached" make sure your using a USB 2.0 data cable on a USB 2.0 port
townsenk said:
How to DeOdex YOUR (...) Rom.
I would like to note that I appreciate all the work that developers have put forth in creating and maintaining modified Roms. there are some awesome feature rich implementations available. My intentions are not to be critical of any specific Rom or mod. Without the developers we would have nothing.
(...)
This method is very common knowledge I thought I'd just explain it in an easy to understand way.
Here is what you need.
A stock (...) ROOTED configurated phone. Debloat as needed. Set the phone up exactly how you like it with apps and such.
Make sure it's stable. (If you have issues before DeOdexing they will be there afterward!)
Here's the files you may need to make this happen
LBD2.4.zip
7-Zip
Installer template (at end of post)
1> Make sure ADB is working on your computer. USB debugging turned on. Create a folder to store your soon to be download system files and launch a DOS shell from that working folder. Working folder name should NOT contain spaces. With the phone hooked up you should be able to type adb shell and get a prompt.
2> Type these commands
adb pull /system/app app/
adb pull /system/priv-app/ priv-app/
adb pull /system/framework framework/
This will take awhile and you will be left with three folders
Create a new folder named "system" and place these three folders inside.
3> Extract and launch LBD2.4 (This is the DeOdexer and is AWESOME). Point it at your recently created "system" folder and let it do it's thing.
I'll assume this will occur without errors as I have never had any.
4> At this point you can manually apply modded apk's to the system folder but I don't really recommend it. They can be applied afterward using the seperate installer zips.
5> with 7-Zip installed open the provided Installer template. Do not Extract it. Just open it in the 7-Zip file browser using the right click context menu in windows.
Drag-Drop the contents of your system folder into the empty system folder in the 7-Zip browser It should be the three folders previously created but now they are Deodexed. Close the 7-zip file manager and select Yes if it asks you to save.
Note: The provided installer template has been modified to only wipe and replace the three system directories.
6. Copy the created installer to your sdcard and install with recovery. Wipe cache and Dalvik before rebooting.
Go have lunch. You will sit at a boot screen for about 10 minutes. Then another 20 to rebuild caches. Time varies.
7. Your system will now be Deodexed! At this point you can install your mods one at a time, I recommend this so you can test your system between installs to determine if a specific mod is creating problems.
This method has so far removed ALL of my stability issues.
Click to expand...
Click to collapse
Since I no longer own this device, I'm retiring from this thread as of now. Hope I could help you.
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
omg brilliant @nitrous² ! thanks so much! its been days i keep trying to deodex with others tool...
Sachitoge said:
Don't know if someone can help me as you stated that you're retired from this thread.
I did every step you do mentioned here (for self deodexing existing rom)
I did everything successfully and deodexed my files with 2.5 deodexer, putted files in the system folder to the 7zip folder and sent to my device and flashed zip, cleaned cache and dalvik and it stuck on booting for about 15 minutes. I know, it takes alot time during rebuildup of cache, but guys, it's 15 minutes! for me, if i cleanup cache and the dalvik/art cache, it just takes 1minute on boot screen to show up the image of each apps cache, but i just sat there with lots of patient for 15 minutes or a bit more and still same, stuck in same crappy booting logo.
I did restore my system files, now i'll try to retry it and send it again. Im suspicious of the zip file being corrupted during trasmitting to Device, however install was a big success so im very sure it wasnt corrupted. I'll do 2nd test and see it again if it's happening again.
If it does, i'll most likely try to figure out other ways to deodex as there is already deodexed roms out there, so they must have done is somehow.
Thanks, hope someone can help me out with this.
P.S: My adb works fine, i got usb drivers for my device, i got usb debug on, i got lots of space on phone, i got TWRP recovery which got very high compatibility when it comes to install anything from zip via recovery where almost all roms do work stable with TWRP.
Click to expand...
Click to collapse
Same happened to me.... Did you solved this problem?
Maurizio1953 said:
Same happened to me.... Did you solved this problem?
Click to expand...
Click to collapse
Nope, i ended up using CM12 (at that time, right now i got cm13 update).
Well i had to deodex apps to get xposed on TouchWiz, but i failed and didn't get headache because of the Xposed modules being not really well compatible on TouchWiz, so i jumped to CM, i find it more stable, and the CM13 is insane because it saves so much battery at stand by, compared to lollipop, the Android 6.0.1 Marshmallow is the biggest update in android history, that saves hell lot of battery (it can be also maybe because i don't have Xposed Framework in recent rom).
Anyway, im tired of it, and i don't need to hassle with Link2Sd because of Android Marshmallow offering to mount the SD Card, in the end, all my needs are being offered in this (for me) huge, best android update, being Marshmallow.
Try it i would say, so amazing.
Ok i would like to go to cm13 as you but i stil need the support to the gear s smartwatch so i decided to stay with touchwiz without xposed.
My device Stock in USPM and no way that i can turn it off.
here is some ways i read in different threads.
charge 100%
use different launcher
wipe cache
wipe dalvik
and more i don't want to bored you with them.
here is solution i came up with and it solved my problem without lose anything
Requirement:
TWRP recovery
1. reboot to recovery (TWRP)
2. Advanced - File manager
-- look into system\app
-- and change every "emergency " Folder name or
-- or simply rename apk file and delete extension
3. reboot (this is how you get color and full setting)
4. setting - app manager - reset app preference (this is how your all apps working without losing any data (only if you disabled some apps this will enabled them again))
5. reboot to recovery
6. Restore apk files that renamed
7. reboot
8. disable UPSM
9. reboot
and it's done
Xposed or not Xposed? Well either one may or may not be good depending on the situation.
I did not create anything. I am just putting steps together and giving instructions. I am not responsible if anything breaks or catches fire. This requires at least Android 7.0.
Given what I put this phone through already (a pretty good story if you're a little nerdy like me), I decided to try it out.
1) Download FlashFire and install. Make sure it's granted root access. It might force close the first time, just swipe it closed in recent button and reopen it.
2) Download the .zip and installer from here.
3) Via ADB, install the Xposed APK, but DO NOT open the app yet.:
Code:
adb root
adb install nameofpackage.apk
4) Place the .zip it into internal storage (sdcard). I pushed it through ADB:
Code:
adb root
adb push nameofzip.zip /sdcard
5) Open FlashFire. Tap the '+' at the bottom right and select 'Flash ZIP or OTA'. Find the .zip you just put on your sdcard and select it.
4) In the 'options' window, please select 'mount /system read/write'. make sure ONLY that option is selected. Tap the check mark at the upper right.
5) Some say to do a davlik and cache wipe. If you have a near freshly flashed device or out of the box new, I wouldn't wipe anything. I have had some issues when flashing Xposed via FlashFire on this device when doing so. BUT, if you're like me and like to walk on the wild side; tap the plus sign again, select wipe and select davlik and cache ONLY. Tap the check mark.
6) I've done this next step both ways, but not sure if it makes a difference. It might though I have no real idea. Make sure the Wipe cache is first, then Xposed. I am on a fresh ROM so I did not wipe cache at all.
7) After reboot, go to the Xposed App and tap it. You're welcome.
I had a feeling this wasn't working and removed it. Everything went smooth, but I am pretty sure it wasn't working. Modules seemed to install, but didn't do anything. A few apps I use have modules and they didn't respond to Xposed. Seems like they couldn't see Xposed.
Hi there,
First of all, lemme tell what i did.
Phone model : Huawei p9 lite VNS-L31 ( Dual Sim )
I downgraded my p9lite to andriod 6.0
After that, i unlocked the bootloader, unlocked my Phone etc and installed TWRP.
Phone was still working at this point. Installed the magisk root and Phone still worked.
main reason i wanted to root is to spoof at pokemon go ( yeah it sounds silly, but it is ).
In order to make it work i had to do some stuff, heres a copy paste from the website i followed the tutorial from :
* Step 5- Download a GPS Spoofing app of your choice. I prefer GPS Joystick but I have had great success with Fake GPS Floater. HERE is a known working GPS Joystick apk from my phone to use instead of converting the app over.
Download Service Disabler
Download a root file manager. I use root explorer but I believe its a paid only app, give Root Browser a try from HERE.
Download GPS Test app from HERE
Now its time to convert your spoofing app to a system app. If you downloaded my apk open your root explorer and copy/paste the apk to /system/priv-app and select the file and change permissions to 644 (all read selected and owner write selected), skip the rest of these steps below. If you downloaded from the Play store Open up your root explorer and navigate to /data/app and find the gps spoofing app that you installed and select the entire folder and cut it to /system/priv-app. Now go into the folder that you just moved and delete everything but the apk, All odex files and folders must go. Now long press highlight the apk and change permissions of the file to 644 (all read selected and owner write selected). Back out to the folder that the apk is in and do the same but set permissions to 755 (all read, owner write, and all execute).
Next up is Service Disabler, open the app and go to the system tab, search for location, open fusedlocation and disable it (samsung owners need to do the same for Samsungfusedlocation), search again for google and select google play services, navigate down to fusedlocation and disable it.
Next open GPS Test and go to hamburger menu, AGPS and select clear only.
Reboot to recovery and select wipe, advanced, select dalvic cache and cache. swipe to wipe and then reboot. Boot up time will take a few minutes to optimize all apps.
I followed the steps verry carefully.
My Phone starts to huawei logo, it stays on the logo and it goes to the Huawei eRecovery.
any suggestions?
Restart your phone by holding power button (Hold it until it vibrates).
try this 20 times for example , till it boots into system
FunnkyHD said:
Restart your phone by holding power button (Hold it until it vibrates).
try this 20 times for example , till it boots into systen
Click to expand...
Click to collapse
Tried it, but it does not boot.
solvathus said:
Hi there,
First of all, lemme tell what i did.
Phone model : Huawei p9 lite VNS-L31 ( Dual Sim )
I downgraded my p9lite to andriod 6.0
After that, i unlocked the bootloader, unlocked my Phone etc and installed TWRP.
Phone was still working at this point. Installed the magisk root and Phone still worked.
main reason i wanted to root is to spoof at pokemon go ( yeah it sounds silly, but it is ).
In order to make it work i had to do some stuff, heres a copy paste from the website i followed the tutorial from :
* Step 5- Download a GPS Spoofing app of your choice. I prefer GPS Joystick but I have had great success with Fake GPS Floater. HERE is a known working GPS Joystick apk from my phone to use instead of converting the app over.
Download Service Disabler
Download a root file manager. I use root explorer but I believe its a paid only app, give Root Browser a try from HERE.
Download GPS Test app from HERE
Now its time to convert your spoofing app to a system app. If you downloaded my apk open your root explorer and copy/paste the apk to /system/priv-app and select the file and change permissions to 644 (all read selected and owner write selected), skip the rest of these steps below. If you downloaded from the Play store Open up your root explorer and navigate to /data/app and find the gps spoofing app that you installed and select the entire folder and cut it to /system/priv-app. Now go into the folder that you just moved and delete everything but the apk, All odex files and folders must go. Now long press highlight the apk and change permissions of the file to 644 (all read selected and owner write selected). Back out to the folder that the apk is in and do the same but set permissions to 755 (all read, owner write, and all execute).
Next up is Service Disabler, open the app and go to the system tab, search for location, open fusedlocation and disable it (samsung owners need to do the same for Samsungfusedlocation), search again for google and select google play services, navigate down to fusedlocation and disable it.
Next open GPS Test and go to hamburger menu, AGPS and select clear only.
Reboot to recovery and select wipe, advanced, select dalvic cache and cache. swipe to wipe and then reboot. Boot up time will take a few minutes to optimize all apps.
I followed the steps verry carefully.
My Phone starts to huawei logo, it stays on the logo and it goes to the Huawei eRecovery.
any suggestions?
Click to expand...
Click to collapse
As far as i noticed, on a huawei p9 lite you can't disable a system module, such the fused location module. I know, I did this mistake by myself time ago for the same purpose as yours and i did'nt find a solution. Another strange thing is that after the wipe data and th magisk reflash (reinstall) the safetynet test won't pass. That's strange..