Bought KF2 today, rom updated to 10.2.1. Rooted using the automated rooting tool found on this forum with adb and other required pieces installed.
Have superuser installed, have root explorer and ES file explorer installed.
I installed google services framework apk
i installed market apk which works until you attempt to download anything, then it crashes.i could not get it to set to rw/r/r its set to rw/rw/r
I downloaded google play apk but it crashes every time i try to open it. same security set as above
Would love some help in getting this to work.
since rooted facebook keeps crashing but tweetcaster has been rock solid.
Did you installed GoogleLoginservie.Apk?
Sent from my KFTT using xda premium
techknowgn said:
Bought KF2 today, rom updated to 10.2.1. Rooted using the automated rooting tool found on this forum with adb and other required pieces installed.
Have superuser installed, have root explorer and ES file explorer installed.
I installed google services framework apk
i installed market apk which works until you attempt to download anything, then it crashes.i could not get it to set to rw/r/r its set to rw/rw/r
I downloaded google play apk but it crashes every time i try to open it. same security set as above
Would love some help in getting this to work.
since rooted facebook keeps crashing but tweetcaster has been rock solid.
Click to expand...
Click to collapse
You have to get the permissions set to rw-r--r--. That could be causing your problem. to set the permissions in root explorer just long press on the apk and you should see an option for permissions. Then reboot
no matter what rom I use, on any phone. I always chmod 777 all of the modified apks and it seems to work.
Currently waiting on my kf2 to get here. so no help on specifics. sorry.
hmmmmm
onemeila said:
You have to get the permissions set to rw-r--r--. That could be causing your problem. to set the permissions in root explorer just long press on the apk and you should see an option for permissions. Then reboot
Click to expand...
Click to collapse
I'm by no means an expert but on every unix like system I've ever worked with giving more permissions than needed did not compromise the ability of programs to run or the user to do stuff that was needed. It did however compromise the security of the system .... so for what it's worth I don't believe your issue is due to the permissions you set and would look elsewhere first.
---------- Post added at 03:19 PM ---------- Previous post was at 03:06 PM ----------
fmkilo said:
no matter what rom I use, on any phone. I always chmod 777 all of the modified apks and it seems to work.
Currently waiting on my kf2 to get here. so no help on specifics. sorry.
Click to expand...
Click to collapse
If you are using the tablet as a stand alone device, i.e. not networked, and you don't ever take it out of the house; not an issue. However, part of the reason these permission are there and not everything has read, write and execute privileges (777 = rwxrwxrwx) is security. Thus setting everything to 777 is a security risk and potentially leaves gaping security holes which could be used to gain access to your device. Thus I would classify this as a BAD IDEA if you keep any data of value on your device and are worried about having it exposed.
rbto said:
I'm by no means an expert but on every unix like system I've ever worked with giving more permissions than needed did not compromise the ability of programs to run or the user to do stuff that was needed. It did however compromise the security of the system .... so for what it's worth I don't believe your issue is due to the permissions you set and would look elsewhere first.
---------- Post added at 03:19 PM ---------- Previous post was at 03:06 PM ----------
If you are using the tablet as a stand alone device, i.e. not networked, and you don't ever take it out of the house; not an issue. However, part of the reason these permission are there and not everything has read, write and execute privileges (777 = rwxrwxrwx) is security. Thus setting everything to 777 is a security risk and potentially leaves gaping security holes which could be used to gain access to your device. Thus I would classify this as a BAD IDEA if you keep any data of value on your device and are worried about having it exposed.
Click to expand...
Click to collapse
I agree. At google play there's plenty of malware. I think you should play it safe
Enviado desde mi LG-P990 usando Tapatalk 2
I am having the exact same problem as original poster. I have tried everything from resetting to factory settings and rerooting to trying different versions of google play/market
GoogleLoginservie.Apk fails and wont install
I had it working before the kindle updated and undid my root the other day. This was the only post I could find of someone having the exact problem I am having with the KF2. Is this some kind of hidden amazon security feature to keep us from using google? I am at my wits end on this one. =/
I take no credit for this amazing equalizer. All credits go to @zhuhang and the people from his thread for the convolvers.
If you don't know what V4A is check here for more details.
But basically it's an audiophiles dream that can cause serious hearing loss and such audio enjoyment at the same time!
The Zip has all the files included to enable "neon" support for convolvers, which are also included.
The feedback I've received so far is 100% success.
INSTRUCTIONS:
1) DOWNLOAD THE ZIP
2) FLASH IN RECOVERY (no need to uninstall if you already have viper installed)
3) open the app and you will be prompted to install the drivers. (I always choose the top one, although it does consume more batter, we'll worth it)
The EQ can be either super simple with just the basic adjustments or can get really technical in "expert" mode.
To activate the convolvers hit the 3 dots in the top right and click click the "ui settings" and change it to expert
Current version Download and discussion starts here
UPDATE VERSION 2.4.0.1 Neon Enabled + Convolvers
If using my previous zip version a simple flash of the new zip will update your V4A.
If you are running any version other than the one in my previous zip you will need to follow the steps below to ensure a smooth update to 2.4.0.1.
1) uninstall current driver from Viper by selecting the option is the app or use file manager and delete "libv4a_fx_ics.so" from system/lib/soundfx.
2) wipe data app with application manager or TiBackup
3) uninstall your current V4A
4) Flash to new zip
5) boot up and enjoy
6) hit the thanks button.
old version
Viper4Android neon enabled including convolvers
Enjoy!
I am on AT&T Galaxy S6 so I cannot have a custom recovery. Can you flash the neon zip using Flashfire? It should work, correct?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
It did not work. I ended up having to uninstall the drivers then reinstalling them. So any other way to get NEON working?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Bobthahog said:
It did not work. I ended up having to uninstall the drivers then reinstalling them. So any other way to get NEON working?
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app
Click to expand...
Click to collapse
You flashed using flashfire? You could push the files from the Zip with a file explorer with root access and set permissions to the folders (rwxr-xr-x, 755) and files (rw-r--r--, 644).
You should have it like this
system/priv-app/ViPER4Android_FX_A4.x/lib/arm/libV4AJniUtils.so
system/priv-app/ViPER4Android_FX_A4.x/VIPER4Android_FX_A4.x.apk
system/etc/audio_effects.conf (rw-r--r--, 644)
Also if you a folder located in the system/priv-app/SoundAlive_30, delete or freeze it
I posted this same Zip in my rom thread and have confirmation from AT&T edge and S6 users.
I am having a strange issue on my G920F,
I had a previous version of Viper4Android installed which reported the driver status as normal, I then deleted that version completely because it was installed in the wrong priv-app folder.
I then installed this version via recovery and when I installed the driver it reports the drivers status as abnormal and doesn't even report the sampling rate (reports it as 0), even when installed manually.
stangdriver44 said:
You flashed using flashfire? You could push the files from the Zip with a file explorer with root access and set permissions to the folders (rwxr-xr-x, 755) and files (rw-r--r--, 644).
You should have it like this
system/priv-app/ViPER4Android_FX_A4.x/lib/arm/libV4AJniUtils.so
system/priv-app/ViPER4Android_FX_A4.x/VIPER4Android_FX_A4.x.apk
system/etc/audio_effects.conf (rw-r--r--, 644)
Also if you a folder located in the system/priv-app/SoundAlive_30, delete or freeze it
I posted this same Zip in my rom thread and have confirmation from AT&T edge and S6 users.
Click to expand...
Click to collapse
So, two things -
1) This zip contains a BUNCH of needless folders for what looks like other programs. while they are empty as far as i can tell, they make everything more cluttered (doubly so since they get copied over the the phone...).
2) If you stick with just the 3 files you list there, V4A works but still without NEON support. There is a fourth file however, that one brought over, is the culprit for breaking V4A; under /system/lib/ there is the libV4A_FX_ICS.so. If i replace this file with the one included in your ZIP, then sure enough, like the other powers, V4A goes into abnormal state and is broken until the old file is returned. I suspect you are missing something (or this file is wrong), given the hapazard nature of the entire zip itself....
I love you
For anyone else I had to flash this with flashfire.
If i used twrp I'd get the starting apps splash on loop.
Everything is running great here @stangdriver44!!!! Neon is working and status is normal and my ear drums are now blown out lol. Thanks for everything stang!!!
SwornXIII said:
For anyone else I had to flash this with flashfire.
If i used twrp I'd get the starting apps splash on loop.
Click to expand...
Click to collapse
Hummm, it flashed fine for me with twrp. But thanks a lot for confirming it will flash with flash fire though.
I have tried this option and various other options mentioned in other threads and getting no where. The most I can get with installing the app as userapp is drivers working without Neon and Convuler. I have no luck with this option and always get unsupported. Tried installing via flashfire, twrp and also manually copying files without luck. Also frozen sound_alive and Adapt sound.
Can anyone think of any other issues that I may have overlooked.
SwornXIII said:
For anyone else I had to flash this with flashfire.
If i used twrp I'd get the starting apps splash on loop.
Click to expand...
Click to collapse
Did you already have V4A installed or fresh install?
Sent from my SM-G920V using Tapatalk
I had V4A installed previously. I have tried installing this over existing V4A. Also tried uninstallin/deleting all files and then clean installing this. No luck.
Also, I am on stock kernel rooted with pingpong. I think SElinux is enforcing. I tried the SELinux changer but not sure if that works on samsung phones with knox.
Divine_Madcat said:
So, two things -
1) This zip contains a BUNCH of needless folders for what looks like other programs. while they are empty as far as i can tell, they make everything more cluttered (doubly so since they get copied over the the phone...).
2) If you stick with just the 3 files you list there, V4A works but still without NEON support. There is a fourth file however, that one brought over, is the culprit for breaking V4A; under /system/lib/ there is the libV4A_FX_ICS.so. If i replace this file with the one included in your ZIP, then sure enough, like the other powers, V4A goes into abnormal state and is broken until the old file is returned. I suspect you are missing something (or this file is wrong), given the hapazard nature of the entire zip itself....
Click to expand...
Click to collapse
Did some more reading - the secret sauce for people is needing to run this script:
http://forum.xda-developers.com/showpost.php?p=61242973&postcount=18854
Once done, the .so file i thought was bad works just fine....
Can confirm that above script is what was needed to get everything working fine. Now Neon enabled . Thanks all.
What is ""neon support for convolvers" ?! Thanks!
Schweet! Thanks for this @stangdriver44
this worked like a charm, I had a previous version that neon wasn't enabled on, I flashed this on top and lost Viper4A from my app drawer. I had to go in and delete the old version completely, then fight my way through fc's to reboot at which point I was good to then flash this version, happy to say neon is enabled! thanks for this
sent from my S6 using tapatalk
I flashed this zip and worked right out of the box. Thank you for finally enabling us to use the convolver
---------- Post added at 03:16 AM ---------- Previous post was at 03:14 AM ----------
There is one slight problem but I'm not sure if it's just me. I have a wide range of irs and when I select knew it works but when I select another it sounds exactly the same as the first knew and when I select another random irs it works. Anyone else have this issue
rshift said:
Did you already have V4A installed or fresh install?
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Fresh
I fresh installed as well did exactly like it said with the 50viper.sh script and it works perfect. I love using the TRacks Wide.irs
Sent from my SM-G920V using Tapatalk
I have a rooted Nexus 6 and wanted to edit my build.prop file in order to enable Wifi sharing. I made a backup first, and then when I saved build.prop after editing it was 0 bytes. Then I saw the backup was 0 bytes. First I crapped myself, then I copied in a N6 specific build.prop I downloaded off the net to /system, but no matter what I did, that new file was 0 bytes even though the original was 5k. 'df' showed I was not out of space in /system (had about 1.5 meg free). I even tried mounting /system RW just in case it was RO.
I finally decided after 3 hours of this that perhaps the whole thing was RO and a reboot would clear everything (based on a couple of other posts I read).
I held my breath, rebooted..... and as I feared I just get the black screen that says Google with a lock.
I can't shut off the phone (to reboot into recovery mode), the Nexus doesn't have an off button. I hold power down and it reboots. I give it a short press and it does nothing. I hold them all down and it reboots.
Can I get a pointer please to a thread that might help bail me out?
As a side note, I'm having problems connecting to my phone in debug mode with adb (even before the reboot), so if I need to use those tools, that's another hurdle I'll have to figure out.
Hold the power button + volume down to get to the bootloader. Go to recovery and reflash whatever rom you were on . A dirty flash should suffice.
Hit thanks if this solve your problem.
Getting a little further. Managed to boot into TWRP. Got into terminal, tried to copy in the build.prop file to /system that way but am being told I'm out of space.
Found a similar thread here I'm digging through.
http://forum.xda-developers.com/nexus-6/help/nexus-6-bootloops-build-prop-edit-6-0-1-t3473306
Just saw post #2, thanks. Thought I had it. I freed up some space in /system/app by deleting a couple of foreign keyboard files. Then copied in the build.prop file and this time it was the correct file size. Rebooted, but no change. I really thought that would have fixed things.
As an aside, df lies, there really was no space in /system
Looks like what I found was not a stock build.prop. I have no idea how much it differs but it contains this line:
ro.build.display.id=NexZen by VECTUS V07
Ha! Also it's for 5.1.1. Darn! I should have looked at this first.
Does anybody happen to have a pointer to a stock Nexus 6 6.0.1 build.prop? Google has failed me on this one.
Your original problem was, as you've found, that you had no space in your system partition. The reported 1.5 mb is way to little space to do any kind of system mods... I've found i need at least 50-60 mb free.
Stock build.prop is easiest found in the factory images, in system.img. If you're pushing it to your phone in recovery, don't forget to set the correct permissions (chmod 644).
Thanks, I did pull the file out of the stock ROM, but I must have gone wrong somewhere because it didn't work. I then looked at the /system directory and it was empty other than /system/bin. No idea how the heck I could have deleted the other files in there. That would have been a nice clean fix. But now I'm forced to do a flash. What a waste of a night! Thought it would be nice and simple to turn on wifi sharing. Ha!
I figured 1.5MB would be more than enough to add a single line to a file, the file system block size I'm guessing is in the 2-4K neighborhood. Regardless, it clearly wasn't enough for whatever reason.
I was on a stock ROM. Since I can't easily do a dirty flash of a stock rom, and I can't connect with adb, I need to try to find a TWRP version of a stock 6.0.1 or something really close. I'm pulling off whatever data I can save now just in case I have to wipe this.
If your /system is empty in TWRP it means you haven't mounted system. Under "Mount", make sure "system" is checked.
Sounds like the easiest thing for you would be just to fastboot flash the system.img from the factory image. That'll get you back on track.
It was a really late night but I'm back in business this morning. I used this stock ROM image with TWRP and did a dirty flash.
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-6-0-1-mmb29k-t3279185
Now I still need to update my friggin build.prop!!!
robroth said:
It was a really late night but I'm back in business this morning. I used this stock ROM image with TWRP and did a dirty flash.
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-6-0-1-mmb29k-t3279185
Now I still need to update my friggin build.prop!!!
Click to expand...
Click to collapse
Use adb and pull it to PC,edit it and push it back easiest way with newer Android versions
i have encountered this on my newer nexus 6. whereas my older nexus 6 seems to be void of these characteristics.(i have started to believe it is because the older one was moved through the API levels smoother....19-20-21-22-23-24-25....as my new one has gone from 18--------to 25. THAT IS TOTAL PROCESS OF ELIMINATION. no idea if thats what it is.) i was able to to push a reboot and temp. flash into twrp from adb/nrt. i dirty flashed my ROM and GApps and seemed to quick fix.
---------- Post added at 03:54 PM ---------- Previous post was at 03:47 PM ----------
there are a few key issues i have witnessed (as a whole) with a young and older sibling too..... which is not the subject of this issue but i think what i have come to learn can shed light on situational(from time to time) issue that i have to deal with when consistent flashing. the RO/RW is now a part of my routine for the newer phone(cause it will randomly drop its RW for no reason and prevent proper filing for busybox or in my case nethunter libraries)
whew. I was gritting my teeth on reboot tonight after editing build.prop again, but this time it went without a hitch. It sucks how you can find all these great articles about how to do stuff, but invariably I own the one phone where there's a gotcha that one doesn't think to look for
I'll keep an eye out for if/when it'll let persist.root. or the .....persist.dun. Will set =1 without breaking selinux.
Hi all.
Noob here on the forum, my very first post so i am not allowed to post this where i imagine this would belong - the 'Original Android development'. That's why it is posted here.
First of all, i wish to express my sincere gratitude to all you people that work hard on making it possible for rest of us mortals to make the best of those small devices that somehow managed to become so big parts of our lives.. I have been following the forum for a while and been using some things posted here to fiddle with several devices without actually bricking any of them as yet. And this is the first time i felt the need of actually asking for help and/or guidelines.
Anyhew - here's the thing: i still run a N910F on stock marshmallow as my main device. (Please no lectures about this). And lately i came to really, really resent mr.Google. I did make a Lineage version of the Android Pie work together with microG (without google), and that actually is rather sweet, runs smooth as silk. I run that on my backup N910F device. (Ok, so i am a Note 4 freek, sue me).
But for different reasons, actually mainly because i really appreciate the s-pen, i want to continue using stock rom on my daily driver so now i am looking for a google-free version of the stock marshmallow for the N910F (trlte) model. I tried to find it here on the forum, but i couldn't, or i couldn't understand the terminology. Haven't found in the rest of the internet either. So i would appreciate if somebody here could either:
1. point me to the direction of such a version if it's already existing, or
2. give me very specific information as to how i could de-google the stock rom by myself. Either on the device or in Windows. I haven't used adb or fastboot yet, but perhaps i could learn if i don't have to take a class in engineering first…
Or could i simply use Titanium backup and just delete (freeze first of course) all the apps that have 'google' in their name?
The third option is perhaps that some kind sould de-googles the stock rom for me and lets me download it. I would donate, of course.
I would really appreciate all the pointers you could give me.
Regards,
prkfsz
Nope, the N910F stock firmwares are definitely not de-Googled. Flash one for yourself and see. I would recommend flashing a LineageOS/AOSP-based ROM, they are generally Google-free.
If you are really insistent on running stock, then do this to completely de-Google it:
In Titanium backup, search for 'goo', this will find almost all Google apps on the ROM. Uninstall them.
Also, download the latest OpenGapps ARM 6.0 nano zip from opengapps.org. Extract the gapps-remove.txt file from the zip. Use the contents of that file as a reference, find all the files listed in it, manually delete them. The reason for this is that Titanium will miss some things.
Now you should be mostly if not entirely Google-free.
Once you have done that, you can optionally patch your ROM for signature spoofing support, and install MicroG, which is an open source Google Play Services alternative. These 2 steps are optional, your choice.
Very simple. I've done this before, things will work fine overall. But some things (apps) requiring Google components may not work correctly, if at all. MicroG can help mitigate this to an extent. You've been warned.
I'm running Resurrection Remix Nougat v5.8.5 (Android 7.1.2), SPen works fine here. Every app I've tested that can use the pen, works fine. There is really no reason to stay with stock just for pen functionality. I also like the huge amount of customization options that RR has compared to stock. And I can use Substratum (no go on stock) with all black themes, for battery savings.
Thank you! Wasn't aware of the google-remove.txt file within gapps. Will definitelly use it. Otherwise it's like i thought: use Titanium and just go loose on everything that starts with 'go'...
I know about microG and use it regularly. Happy customer…
I do like stock marshmallow on note 4 and want to run it as long as it can go. I will perhaps try the RR nougat you suggested on the backup unit. Even tho i am in no particular need of customisation.
Thanx again.
prkfsz said:
Thank you! Wasn't aware of the google-remove.txt file within gapps. Will definitelly use it. Otherwise it's like i thought: use Titanium and just go loose on everything that starts with 'go'...
I know about microG and use it regularly. Happy customer…
I do like stock marshmallow on note 4 and want to run it as long as it can go. I will perhaps try the RR nougat you suggested on the backup unit. Even tho i am in no particular need of customisation.
Thanx again.
Click to expand...
Click to collapse
You might find this of some interest.
https://forum.xda-developers.com/android/general/guide-degoogle-device-install-microg-t4058743
I'm afraid i got stuck here and i need a bit further assistance.. :-/
Coming from stock marshmallow on Galaxy Note 4. I uninstalled google things first using Titanium. Then manually cleaned some leftovers using file manager in TWRP (not sure i did the right way), altho it looked quite empty in the /system map. Another time erased just the Google Play-services before going to TWRPs file manager and it looked just as empty. At both occasions i lost auto-rotate. Is this normal?
After deleting all the google (and in the second try only google play services app) i tried just for the heck of it to run the Nanodroid patch file but i got an error message that it couldnt deodex services.jar file, which was pretty much expected. My skills are not sufficient for deodexing files so i tried other approaches for patching. Smalipatcher - the damn thing couldn't even see i had admin privileges in Win no matter what i did and just refused to run alltogether.
Then i tried the link that was put here by @MrJavi in the post above (thank you sir!). Did everything as the tutorial says, got no error message, everything seemed to run smooth and the apps i chose were installed. (altho TWRP did freeze a couple of times during aroma setup so i had to reset by taking out the battery). When i wanted to set up the microG settings, the microG icon and the app is nowhere to be found. The modul named NanoDroid exists and is activ in Magisk, but it's not possible to open it.
Last, but not least of course, i tryied patching with fake gapps module in Xposed, but Xposed of course does not want to play nice with mr.Samsung. Even when i try and run Xposed from Magisk...
Not sure how to proceed from here.. I'm thinking of switching my starting point to the already deodexed version of marshmallow i thought i saw around here, because it would be easier to patch.
If it's still out there available for download, which i don't take for granted anymore nowadays..
But i would like to make it work on my device anyway. So, if anyone has any ideas, they will be so welcome.
Perhaps Samsung knox is causing issues with Xposed framework/installer. The link below is for a different "Samy" but the the Knox remover is a flashablw .zip made specifically for the Note 4 .
https://www.google.com/amp/s/forum....-how-to-deodex-root-remove-knox-t3458921/amp/
https://www.google.com/amp/s/forum....al/toad-source-android-deodexer-t3848307/amp/
Always take a full Nandroid backup by checking all partition beforehand and save to your external sd card. You can then choose to flaah an Aroma Google debloater .zip .
https://forum.xda-developers.com/android/software-hacking/aroma-google-services-debloater-t3668456
Mr. JAVI said:
Perhaps Samsung knox is causing issues with Xposed framework/installer. The link below is for a different "Samy" but the the Knox remover is a flashablw .zip made specifically for the Note 4 .
https://www.google.com/amp/s/forum....-how-to-deodex-root-remove-knox-t3458921/amp/
https://www.google.com/amp/s/forum....al/toad-source-android-deodexer-t3848307/amp/
Always take a full Nandroid backup by checking all partition beforehand and save to your external sd card. You can then choose to flaah an Aroma Google debloater .zip .
https://forum.xda-developers.com/android/software-hacking/aroma-google-services-debloater-t3668456
Click to expand...
Click to collapse
wow, those were really some good links! thanks, @mr.javi. However....
tried the first link and to work with firmware but the ext4uninstaller does not want to recognize the ext4 file (wtf??), regardless from where i download the software and regardless what ext4 file and from what firmware (tested a few), and without that part working it was pretty much impossible to go on. So i ran only the deknoxing tool through twrp. No error. But still when i try and install the xposed - boom! it will not boot. Not even damn zip uninstaller for magisk will work as it should..
Tried the second link with the TOAD. Weird: some versions get recognized as malware by my antivirus and windows does not want to run other versions for safety reasons. Strange..
Tried the third and that de-googling script is rather sweet.
But my conclusion from all this is that it is not so hard to exorcise the google, but to patch the rom in the next step... If i understand correctly i have to get the rom deodexed first to be able to patch it with nanodroid?
I tried some deodexing tools on pc, but i'm not really sure if i'm doing it correctly. I take it i have to copy some folders (/apps, /framework and one more) from the phone to the computer to work with them there, but i get error message when i try to copy files through file manager in twrp. Am i supposed to do it some other way? And can you do that directly in the phone? I tried an app called 3c -all in one-toolbox that has native option of deodexing but i get error message there, something about classes i think, i don't remember and i can't see it now cause the phone is just being reflashed..
Any more thoughts and ideas? As usual, grateful for anything you can give me.
AnonVendetta said:
Once you have done that, you can optionally patch your ROM for signature spoofing support, and install MicroG, which is an open source Google Play Services alternative. These 2 steps are optional, your choice.
Very simple. I've done this before, things will work fine overall. But some things (apps) requiring Google components may not work correctly, if at all. MicroG can help mitigate this to an extent. You've been warned.
Click to expand...
Click to collapse
HOW?! did you manage to patch it??
prkfsz said:
wow, those were really some good links! thanks, @mr.javi. However....
tried the first link and to work with firmware but the ext4uninstaller does not want to recognize the ext4 file (wtf??), regardless from where i download the software and regardless what ext4 file and from what firmware (tested a few), and without that part working it was pretty much impossible to go on. So i ran only the deknoxing tool through twrp. No error. But still when i try and install the xposed - boom! it will not boot. Not even damn zip uninstaller for magisk will work as it should..
Tried the second link with the TOAD. Weird: some versions get recognized as malware by my antivirus and windows does not want to run other versions for safety reasons. Strange..
Tried the third and that de-googling script is rather sweet.
But my conclusion from all this is that it is not so hard to exorcise the google, but to patch the rom in the next step... If i understand correctly i have to get the rom deodexed first to be able to patch it with nanodroid?
I tried some deodexing tools on pc, but i'm not really sure if i'm doing it correctly. I take it i have to copy some folders (/apps, /framework and one more) from the phone to the computer to work with them there, but i get error message when i try to copy files through file manager in twrp. Am i supposed to do it some other way? And can you do that directly in the phone? I tried an app called 3c -all in one-toolbox that has native option of deodexing but i get error message there, something about classes i think, i don't remember and i can't see it now cause the phone is just being reflashed..
Any more thoughts and ideas? As usual, grateful for anything you can give me.
Click to expand...
Click to collapse
You're very welcome @prkfsz
https://mtkcustomroms.com/deodex-stock-rom-custom-rom-without-pc-2018/
https://how-to-easily-deodex-android-stock-rom-without-pc/
Mr. JAVI said:
You're very welcome @prkfsz
https://mtkcustomroms.com/deodex-stock-rom-custom-rom-without-pc-2018/
https://************/how-to-easily-deodex-android-stock-rom-without-pc/
Click to expand...
Click to collapse
Thanx again, @Mr. JAVI! :good:
Both links are about the same app and i've tried that one recently, so it seems like we think rather alike.
I get the exact same error message like the guy that wrote that one comment at the bottom of the second link (error saying "needs rebuild classes.dex").
And strangely enough when i open the deodexing window in the app it says that of the number of apps in the rom not all are odexed (says something like "deodexed 124/187"), which is rather perplexing because it's on the freshly installed stock (from nandroid backup directly after factory reset). So I tried to fool the app and get all the apps odexed first, but that didn't fly either..
Btw, thanks for the advice before - i always back the device upp (all partitions) before messing with it.. I forgot to do that on one device before and instantly regretted it..
-------------------------------------------
Edit: the second link in your last post was dead so i tried to correct it in my message, but xda forum doesn't like that.
Tried to post in the right link here in the message too, but that didn't work either for some reason.
but searching the phrase 'how to easily deodex Android stock rom without pc' will give you the first search result.
Oat2dex.jar
https://www.google.com/amp/s/forum....eral/tool-deodex-tool-android-l-t2972025/amp/
https://github.com/testwhat/SmaliEx/releases
---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------
prkfsz said:
Thanx again, @Mr. JAVI! :good:
Both links are about the same app and i've tried that one recently, so it seems like we think rather alike.
I get the exact same error message like the guy that wrote that one comment at the bottom of the second link (error saying "needs rebuild classes.dex").
And strangely enough when i open the deodexing window in the app it says that of the number of apps in the rom not all are odexed (says something like "deodexed 124/187"), which is rather perplexing because it's on the freshly installed stock (from nandroid backup directly after factory reset). So I tried to fool the app and get all the apps odexed first, but that didn't fly either..
Btw, thanks for the advice before - i always back the device upp (all partitions) before messing with it.. I forgot to do that on one device before and instantly regretted it..
-------------------------------------------
Edit: the second link in your last post was dead so i tried to correct it in my message, but xda forum doesn't like that.
Tried to post in the right link here in the message too, but that didn't work either for some reason.
but searching the phrase 'how to easily deodex Android stock rom without pc' will give you the first search result.
Click to expand...
Click to collapse
Well to tell you the truth, even a full Nandroid backup couldn't fix a dm-verity/drk issue on one of my Note 4's. Up until then I have always recovered from softbricking my devices. Stubborn as I am, I spent hours and hours and hours o no avail. I connected my other N4 but still kept trying to revive my old N4. It wasn't until a year and a half later, assisting another member that I came across a possible solution and it worked. Spent more time than my old N4 was worth but my record is untarnished non the less. lol I sure hope you never ever encounter either of thoughts @prkfsz .
Mr. JAVI said:
Oat2dex.jar
https://www.google.com/amp/s/forum....eral/tool-deodex-tool-android-l-t2972025/amp/
https://github.com/testwhat/SmaliEx/releases
---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------
Well to tell you the truth, even a full Nandroid backup couldn't fix a dm-verity/drk issue on one of my Note 4's. Up until then I have always recovered from softbricking my devices. Stubborn as I am, I spent hours and hours and hours o no avail. I connected my other N4 but still kept trying to revive my old N4. It wasn't until a year and a half later, assisting another member that I came across a possible solution and it worked. Spent more time than my old N4 was worth but my record is untarnished non the less. lol I sure hope you never ever encounter either of thoughts @prkfsz .
Click to expand...
Click to collapse
And i thought i was stubborn for this, insisting on tweaking an age-old os and spending hours on looking for solutions.. thank you!
Not sure about what that issue you mentioned was, since i'm not really on that experience level, but i'm sure it was a mean one.. lol Good job of fixing it! I ended up a few times in similar situations (not with that high level issues apparently) and i just couldn't let go untill i resolved them or bricked them completelly... Luckily haven't bricked anything even tho i play mostly with older devices so it wouldn't be such a waste. But as you too apparently feel - unblemished record is a matter of pride..
And yes, i too recently understood that nandroid backup isn't allmighty - it can't for instance save certain safety settings, fingerprints and such. I always thought of nandroid backup like a 'clone' feature on PC. Loved that..
Aanyhew - back to business.
I hit the wall here again, the same one as with Fulmics deodexer. It's not that it isn't working, it's that i don't know how to point it to the right maps for deodexing.
As far as i understand, i have to copy those 3 folders from the phone to the PC, do the deodexing on the pc, and then move back to the phone and replace the original folders. Is this correct? I tried doing this in TWRPs file manager using micro sd card, but i gott error message that it wouldn't copy all the files for some reason. Should i use some other method of copying those folders to the PC?
Perhaps a stupid question but is there any way to let the deodexer on the pc find the folders directly on the phone?
As always - a huge thank you from the struggling noob, @Mr. JAVI. :good:
Perhaps this is the Xposed framework and installer that might be compatible with your N910f
https://forum.xda-developers.com/note-4/themes-apps/unofficial-xposed-v87-3-magisk-v18-t3897017/amp/
As far as TWRP you might be able to patch it and save internal data with Tipatch apk. The drawback is you backups will be much larger.
https://www.google.com/amp/s/forum....pp-twrp-tipatch-backup-internal-t3831217/amp/
PS: Thsnks for the compliment my friend but I'm still learning. Modifications is just a hobby of mine. We learn from each other here on XDA.
PC : skills are not my strong point . Your skills with PC far
exceed your ability. I actually bought a laptop years ago, just so I could flash TWRP Odin and root . The complete ssd laptop cost alot more than my Note 4. I port or create my own flashable .zips. Although, I've never been faced with having to deodex a custom rom, simply because there readily available from the developers on xda for the n910p. Sucks there hasn't been one developed for your n910f.
Something posted by @IBNobody
"Anything past Magisk v15.3 will not pass SafetyNet on QI5.*
Magisk v15.4+ added a check in its Magiskhide subsystem that looks a service (logd) to be loaded. That service is not running on our stock or slightly modified QI5 build. If this service check fails, Magiskhide does not get loaded. If Magiskhide is not running, it can't hide Magisk from the SafetyNet checks.
(You'll know if this is affecting you because the Magisk Manager app won't remember any settings you make in the Magisk Hide tab.)*
Our only options are:
1. Build our own fork of Magisk that skips this check.
2. Enable logd by modifying the init.rc file in boot.img. (logd is commented out. I have not tried un-commenting it.)
3. Remain on v15.3."
DQ15 is the Sprint firmware 6.0.1 and not n910f but it could be the same with yours as well.
A slightly lower version Xpoaed framework api 23
https://androidfilehost.com/?fid=529152257862685344
Mr. JAVI said:
Perhaps this is the Xposed framework and installer that might be compatible with your N910f
https://forum.xda-developers.com/note-4/themes-apps/unofficial-xposed-v87-3-magisk-v18-t3897017/amp/
As far as TWRP you might be able to patch it and save internal data with Tipatch apk. The drawback is you backups will be much larger.
https://www.google.com/amp/s/forum....pp-twrp-tipatch-backup-internal-t3831217/amp/
PS: Thsnks for the compliment my friend but I'm still learning. Modifications is just a hobby of mine. We learn from each other here on XDA.
PC : skills are not my strong point . Your skills with PC far
exceed your ability. I actually bought a laptop years ago, just so I could flash TWRP Odin and root . The complete ssd laptop cost alot more than my Note 4. I port or create my own flashable .zips. Although, I've never been faced with having to deodex a custom rom, simply because there readily available from the developers on xda for the n910p. Sucks there hasn't been one developed for your n910f.
Click to expand...
Click to collapse
Laptop cost way over Note 4? I see i'm not the only one..... ehh, let's say determined bloke around here haha.. Hope it was worth it.. And btw creating your own flashable zips is way above my level of skills, i can tell you that, my friend. Never did that, nor am i planning to. But since i am stubborn (or so i've heard.. lol) and i feel uttermost distaste for mrGoogle and, like you said, noone has apparently done the deodexing the stock N910F - I am simply forced to take matters into my own hands. Flashing a pie and microG is ... apparently too easy. Besides, i am already running that on one of my spare Note 4s.. And i appreciate xda, just like you say people can give each other a hand. What i dislike tho is lots of dead download links... Oh, well..
ok, back to business again.
I guess i am going to need a more detailed help now.
I tried with that version of Framework you linked to. At that page the link for Xposed installer app for Magisk is dead. Tried to play a little with the other file, the version 87.3 of Xposed and just flashed it in TWRP, but nothing happens.
As far as the Tipatch, excuse my ignorance but i have to ask here: what difference would it make for deodexing to be able to copy internal storage? I am thinking it's other folders that need to be copied, like /system.
Apart from that, i love the idea of Tipatch! Will install it anyway.
--------------------------------------------------------
I am beginning to realize that there are not many reasonable options left, since i'm not sure it is worth much more time and effort on my part. I am not going to be an engineer over this..
So there is but one more question to perhaps get solved before i run out of options and go with custom Pie anyway.
And that is - how do i copy the needed 3 folders intact to PC for deodexing software? I can't find that information anywhere together with this pc based deodexers.
Oh well. I have vague memory of ES file manager being mentioned somewhere. So i guess that will be my last attempt before i give up. Unless some new solution emerges.
Mr. JAVI said:
Something posted by @IBNobody
"Anything past Magisk v15.3 will not pass SafetyNet on QI5.*
Magisk v15.4+ added a check in its Magiskhide subsystem that looks a service (logd) to be loaded. That service is not running on our stock or slightly modified QI5 build. If this service check fails, Magiskhide does not get loaded. If Magiskhide is not running, it can't hide Magisk from the SafetyNet checks.
(You'll know if this is affecting you because the Magisk Manager app won't remember any settings you make in the Magisk Hide tab.)*
Our only options are:
1. Build our own fork of Magisk that skips this check.
2. Enable logd by modifying the init.rc file in boot.img. (logd is commented out. I have not tried un-commenting it.)
3. Remain on v15.3."
DQ15 is the Sprint firmware 6.0.1 and not n910f but it could be the same with yours as well.
A slightly lower version Xpoaed framework api 23
https://androidfilehost.com/?fid=529152257862685344
Click to expand...
Click to collapse
Ok, i managed to actually copy the system directory from the phone to the pc using Root explorer app. And none of the deodexers work. Fulmics says it needs smali and baksmali versions over 2.2 even tho i fed it with versions 2.4. SVADeodexerforart runs through all the files without actually doing anything. Logfile shows error 'cannot acces jar file' on all 300+ files.
So i believe this is it for me at this point. I just can't see how further struggle would be meaningsfull since it would just take even more time and i already invested way too much of it on this. But i guess being stubborn has it's price.. :silly:
I want to extend my sincere gratitude, @Mr. JAVI, for your patience, tips and guidelines. I think if it wasn't for you i would given up much quicker.. Which perhaps would've been a smart thing to do... But i wouldn't learn anything..
We will probably bump into each other more times here, since we seem to share the common affection towards a certain gadget.
all the best to you
prkfsz said:
Ok, i managed to actually copy the system directory from the phone to the pc using Root explorer app. And none of the deodexers work. Fulmics says it needs smali and baksmali versions over 2.2 even tho i fed it with versions 2.4. SVADeodexerforart runs through all the files without actually doing anything. Logfile shows error 'cannot acces jar file' on all 300+ files.
So i believe this is it for me at this point. I just can't see how further struggle would be meaningsfull since it would just take even more time and i already invested way too much of it on this. But i guess being stubborn has it's price.. :silly:
I want to extend my sincere gratitude, @Mr. JAVI, for your patience, tips and guidelines. I think if it wasn't for you i would given up much quicker.. Which perhaps would've been a smart thing to do... But i wouldn't learn anything..
We will probably bump into each other more times here, since we seem to share the common affection towards a certain gadget.
all the best to you
Click to expand...
Click to collapse
I am just one of the "common folk". One of my hobbies is modifying my rooted Note 4. I have learned from my failures as well. The creating custom zips is not as hard as you think, in fact it was a failed camera .zip fash that ended in FC's. I came up with an idea to take the previous working camera .zip. left the meta-imf and replaced tge rest with an N7 camera from another rom and fkashed it. It's much easier explained with screen shots.
One of my favourite apps is ZArchiver apk. Downliad it and you'll see why. Ext4, tar, zip, roms, jar, apks and more. Freaking Awesome!!!
https://play.google.com/store/apps/...pk&pcampaignid=APPU_1_YUIBX4STE-aD9PwPh7ylmAg
Its like gold and did I mention free? lol
Welcome to XDA @prkfsz
Mr. JAVI said:
I am just one of the "common folk". One of my hobbies is modifying my rooted Note 4. I have learned from my failures as well. The creating custom zips is not as hard as you think, in fact it was a failed camera .zip fash that ended in FC's. I came up with an idea to take the previous working camera .zip. left the meta-imf and replaced tge rest with an N7 camera from another rom and fkashed it. It's much easier explained with screen shots.
One of my favourite apps is ZArchiver apk. Downliad it and you'll see why. Ext4, tar, zip, roms, jar, apks and more. Freaking Awesome!!!
https://play.google.com/store/apps/...pk&pcampaignid=APPU_1_YUIBX4STE-aD9PwPh7ylmAg
Its like gold and did I mention free? lol
Welcome to XDA @prkfsz
Click to expand...
Click to collapse
Why thank you good sir, @Mr. JAVI! :good:
Every noob should get this friendly a welcome..
See? All that meta-inf, FC-talk is a bit over my lever right now. But i will check out your tool. Might come in handy for some future project. And free it is you say? Sold! haha
As for this project i had, i had to abandon it for now. I realized it wasn't the degoogling that was the problem, but the patching afterwards, and the deodexing that turned out to be downright impossible to get done. And it just gotten too time-consuming in relation to how much time i actually have and how much win i would get out of it. So i took the easy way for now and i went with the custom Pie. I do want the audio from the headphones..
@prkfsz: I used Tingle patch to integrate signature spoofing. You have a few options:
Tingle patch (requires deodexed framework.jar)
Needle patch (requires deodexed framework.jar)
Nanodroid patcher (requires deodexed services.jar)
Haystack patch (requires deodexed services.jar)
Smali patcher (services.jar can be odexed or deodexed, it will deodex and patch the file for you)
FakeGApps (requires Xposed)
Options 1/2/4/5 require a PC. Options 3/6 can be done on device without PC.
Hope this helps!
I don't really have a lot of time to go into detail, but if either of you are looking for a comprehensive way to properly deodex a ROM, check out SuperR's Kitchen. There a free and paid/donate versions. The free version can do what you want just fine.
I had recently used this to deodex the latest stock MM UK firmware for the N910F. In addition to deodexing, the Kitchen can also customize your ROM, and even build a zip that you can flash in TWRP. It flashed and booted fine for me. Once you have done this, you can debloat the ROM (or let the Kitchen do it for you). It won't remove all Google stuff by default, but you can configure it to delete pretty much any file/directory in the system partition. My advice is to use the Kitchen's debloater/Knox removal features, then use gapps-remove.txt and a root file manager to delete the rest. Once you have debloated/deodexed, you can then easily signature spoof patch with any of the tools I mentioned in my previous post.
I have also discovered that you can also run the Tingle patch without a PC, by using QPython3 app. Just supply the deodexed framework.jar and build.prop, it will do the rest. Grab the Tingle master zip from GitHub, unpack it into QPython3's scripts directory on the internal storage, then provide the 2 files into input folder, and run main.py from within the app. You will find the patched jar file in output folder, replace your ROM's framework.jar with the patched one. Use Signature Spoofing Checker to confirm that it worked. I don't think root is required, but it's better to have it anyway, just enable root in QPython3 settings.
Some last notes: don't use Titanium to debloat Google apps, it may also remove some needed shared library files that Android uses. Namely, a library file called libgnustl_shared.so, which will cause autorotation to not work. Use Titanium to determine the locations of Google apps, then delete them manually. This will keep the shared library files while still deleting the apps. On top of this, use gapps-remove.txt.
But while you are debloating, there may be 2 Google apps present that you should not remove, period:
/system/app/WebViewGoogle
/system/priv-app/GooglePackageInstaller
The first is needed by Android and apps to provide webview functionality (this might not sound important, but it is). The 2nd is needed to install apps, remove it and you won't be able to install any app from anywhere (Play Store, manual APK install, etc).
On the subject of Xposed, do *NOT* install the Xposed installer from the Magisk Manager downloads. It isn't designed to work on stock Samsung MM firmware, you won't be able to boot. Use the custom Xposed by wanam (available on XDA). Or you can google for "Xposed kevintm78", this will come up with an AndroidFileHost link that you can install from Magisk. The latter is just a systemless Magisk version of Wanam's Xposed.