So I found this many many months ago on 950U root and Xposed not being completely compatible with our s8,Like in previous Xposed versions Wanam and such have modified Xposed To properly work on Galaxy devices... Btw Thank you Wanam and Rovo for All the hard work. :good::good::good:
So What it comes down to is this is not a @partcyborg Rom issue.....
It is even talked about Here on github on Xposed
https://github.com/rovo89/Xposed/issues/294
Now there are files here for a possible fix But please be-aware that I have tried them out right many times today in different combinations today and from total FC to no boot To now Bluetooth just not turning on after reboots I have bricked every which way with these modified as they are as now.....
Some have had reports of fixing this issue Which is very similar to previous Samsung Models and root and forgetting WiFi upon each reboot if some of you remember correctly....
But Either way I figured I would toss this up for all to check out to put our heads together to get something possibly going....:good::good::good::good:
Tried this on Partctborgs ROM and got a kernel panic after reboot after my first try (BQL1). Haven't touched it since. I was hopeful though.
Sent from my Samsung SM-G950U using XDA Labs
bradical711 said:
Tried this on Partctborgs ROM and got a kernel panic after reboot after my first try (BQL1). Haven't touched it since. I was hopeful though.
Sent from my Samsung SM-G950U using XDA Labs
Click to expand...
Click to collapse
I did to I got as far as good reboots but Bluetooth wouldn't turn on. I ended up doing a stock system img with root. Unbloated and no xposed Bluetooth works great now. Since no xposed
Working Solution
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
Followed your steps and worked like a charm on s8+. Thanks!
Tried @nationalicon 's method and it worked flawlessly on Cyborg's (BQL1) ROM. I was a bit skeptical to try it on my s8 since when I had tried it the first time this didn't work but I hadn't tried this method. But after following these steps perfectly, everything works flawlessly. One less issue now with my ROM overall and it's even better than before. WiFi and Bluetooth connections were all lost at first but after repairing with them all and rebooting, everything is still connected now and works. Thank you!
Sent from my SM-G950U using XDA Labs
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
The mediafire-sourced lib64 files aren't in my original lib64 directory. Is that a problem? Should I still add them? I all because i tried this before and it started not remembering wifi on reboot.
Thanks!
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Supernoobsammyson said:
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Click to expand...
Click to collapse
Thats weird I havnt had really any drop offs unrooted stock,Part cyborg rom,Or pure stock rooted.
Just paring loss upon reboots...
I actually commend Samsung for the most part.
My Bluetooth has been quite exceptional.
Maybe something is interfering and cutting yours out
I run several speakers 2 gear s2 watches My car and prob a few other items,Was actually looking into pairing my PS Vita with it and see what it will do
Supernoobsammyson said:
Bluetooth on the s8 is bad on a stock rom unrooted. It is a s8 problem. After a few hours Bluetooth drops and reenables itself. I have had it happen on rooted partcyborg rom. Also on a stock rom. Samsung and Google try to take over Bluetooth. Samsung has a factory Bluetooth app and Google has Bluetooth enabled for scanning location. I noticed when I get the location scan icon it drops Bluetooth even mid song. I tried turning it off but Samsung location also runs it too.
Click to expand...
Click to collapse
No problem with Bluetooth on my end either. I have to resynch after rebooting, but that is simple on my car stereo so I haven't done the fix. I am running Partcyborg ROM for quite a while now, but I didn't have any issues on stock either.
Smithfolk4 said:
No problem with Bluetooth on my end either. I have to resynch after rebooting, but that is simple on my car stereo so I haven't done the fix. I am running Partcyborg ROM for quite a while now, but I didn't have any issues on stock either.
Click to expand...
Click to collapse
That is the problem. It drops sync. When restarting. Also dropping for no reason. This is after playing all day. Both phone and Bluetooth device are right next to each. And not just on Bluetooth device and/or s8. It happens on one that has never been rooted. Only factory OTA updates.
https://www.google.com/amp/s/forum....lp/bluetooth-issues-oreo-update-t3765757/amp/
It is an issue.
Works thanks
jj972 said:
Followed your steps and worked like a charm on s8+. Thanks!
Click to expand...
Click to collapse
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
Just wanted to confirm it does work follow steps. Only had to clear cache. I left the xposed installer installed and had no mods installes. Copy pasted the correct files files, edited the prop restarted into recovery. Then deleted only cache. Restarted paired with speaker then restarted one more time to test and boom.
Thanks for the help
dmosley said:
The mediafire-sourced lib64 files aren't in my original lib64 directory. Is that a problem? Should I still add them? I all because i tried this before and it started not remembering wifi on reboot.
Thanks!
Click to expand...
Click to collapse
Not sure, but I don't think there is any harm in trying. You can always delete the files later.
OKAY, Extremely excited here. I am ready to do everything but I am unclear as to how to uninstall Xposed. I was under the impression you'd need TWRP to do so. Unless all I need to do is the uninstall the Installer app that shows up in SETTINGS>APPS>XPOSED INSTALLER? Would I just uninstall that app and reinstall the apk from the official xposed thread?
we87 said:
OKAY, Extremely excited here. I am ready to do everything but I am unclear as to how to uninstall Xposed. I was under the impression you'd need TWRP to do so. Unless all I need to do is the uninstall the Installer app that shows up in SETTINGS>APPS>XPOSED INSTALLER? Would I just uninstall that app and reinstall the apk from the official xposed thread?
Click to expand...
Click to collapse
Thats what I did
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
This worked for me. I didn't uninstall xposed. I just disabled all my mods. from xposed and followed the instructions.
Can confirm, worked for me as well. Even survived a factory reset.
im VERY confused but I cant seem to find these files ANYWHERE ... what am I missing?
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
matthewd769 said:
im VERY confused but I cant seem to find these files ANYWHERE ... what am I missing?
Click to expand...
Click to collapse
Have you tried reading the thread and comments on GitHub? Lol the link for the files aren't that far down in the comments. Everyone else seemed to find the links pretty easily so idk.
Sent from my SM-G950U using XDA Labs
nationalicon said:
I posted this in the PartCyborgRom ROM thread, and was asked to post here as well:
I can confirm that this (https://github.com/rovo89/Xposed/issues/294) fixes the issue with losing Bluetooth pairings after reboot . I was able to get this working with Xposed installed, and without reinstalling the rom or wiping data. It is not that clear what to do, so in case this helps anyone, here is what I did:
1) Uninstall Xposed, then reboot
2) Download the files from the "Lib directory" link, and copy them to /system/vendor/lib. Overwrite the existing files.
3) Download the files from the "Lib64 directory" link, and copy them to /system/vendor/lib64. Overwrite the existing files.
4) Modify build.prop by changing ro.securestorage.support to "false". I used the BuildProp Editor app.
5) Reinstall Xposed
6) Reboot into Recovery, and wipe Cache only (not Data)
7) Reboot, and voila! Bluetooth pairings that you create from now on will survive a reboot.
Click to expand...
Click to collapse
bradical711 said:
Have you tried reading the thread and comments on GitHub? Lol the link for the files aren't that far down in the comments. Everyone else seemed to find the links pretty easily so idk.
Sent from my SM-G950U using XDA Labs
Click to expand...
Click to collapse
thanks for the reply .... VERY helpful. I did find it.
Related
So for many people getting the galaxy S3 on verizon, you are without the praised app, google wallet. You can only get it on sprint. However, like many people who tinker, people have found ways to get it to work on their GS3's. I just got my phone yesterday. Had it rooted and romed in less then an hour of owning it of course. Then I set fourth onto getting google wallet to work.
Here is the problem I ran into. There are so many ways of doing it, and some don't always work. and it gets confusing. I went back to the beginning and worked out a way that works, and it is more simple.
First thing that I found. You do not have to mess with build properties at all. That was a pain.
Step 1: Reboot into recovery.
Step 2: Mount system
Step 3: Push the latest com.google.apps(ETC) file to system/app. For instance I used "com.google.android.apps.walletnfcrel.modaco.1.5-R79-v5.apk" because that was the latest I could find.
Step 4: Push nfcee_access.xml to /system/etc which I will include as a download on this thread.
Step 5: Reboot and run wallet. it will work.
Once you have pushed the nfcee_access.xml file, which give the app appropriate permission to work, when ever you have to update with a newer com.google.app(etc) file, all you have to do is this.
Stepv1: Using root explorer or other root file manager, copy the new com app file to system/app
Step 2: Copy the name of the existing file that is already in there then delete it.
Step 3: rename the new com app file to the old file.
Step 4: Reboot into recovery.
Step 5: Reboot normally.
The new version will now work.
You could very easily make a bat file to do this for you, but we are talking 2 adb commands.
I hope this helps other new S3 owners and people who have not yet tried to get google wallet working.
Will this work on beans town? K1 baseband
g1g said:
Will this work on beans town? K1 baseband
Click to expand...
Click to collapse
I'm wondering the same thing.
awalkerz said:
I'm wondering the same thing.
Click to expand...
Click to collapse
No it wont, this will only work on AOSP based roms. OP should note that, my guide has the information but I havent updated it in a while.
OP would you like to take over my work? Or merge information to one post we dont need two posts on a mod.
This is by far the easiest method for installing Wallet: http://forum.xda-developers.com/showthread.php?t=1810040
Use the automated script and it's as simple as... Setting script to edit, rebooting into flash, flashing the zip, rebooting, configuring wallet to your liking, setting script to stock.
It takes minutes maybe. Also, when flashing new roms, I just make a backup of wallet+app data in titanium, set script to edit, reboot, restore wallet from titanium and make sure it's configured, set script to stock and reboot.
Skrypt said:
This is by far the easiest method for installing Wallet: http://forum.xda-developers.com/showthread.php?t=1810040
Use the automated script and it's as simple as... Setting script to edit, rebooting into flash, flashing the zip, rebooting, configuring wallet to your liking, setting script to stock.
It takes minutes maybe. Also, when flashing new roms, I just make a backup of wallet+app data in titanium, set script to edit, reboot, restore wallet from titanium and make sure it's configured, set script to stock and reboot.
Click to expand...
Click to collapse
My guide has also been locked from a mod. Can be located here though http://rootzwiki.com/topic/37284-latest-google-wallet-112912/
Deleted post
Updated: 03/24/2015
Hi all,
I did this mostly for practice but I thought it might be helpful so I went ahead and posted.
Stock LG D850 20f ROM
[*]Rooted/SuperSu
[*]Most bloat removed
[*]Oversharpening fix
[*]Flashable zip
[*]init.d support*
[*]CarrierIQ Remover*
*Init.d support is implemented in ROM only, not the kernel. CarrierIQ is removed automatically after first boot via an init script. Say thanks to @skeevydude for his help in getting this done. I shouldn't say "help", he pretty much did it!
Installation
Flash the Lollipop modem - see @autoprime 's thread here for modem zip
Flash the ROM zip
Wipe cache and dalvik (and in some cases data) if coming from a different ROM
Download
v3* - https://www.androidfilehost.com/?fid=95916177934548695
[QRCODE]https://www.androidfilehost.com/?fid=95916177934548695[/QRCODE]
*No change at all to the ROM itself since v2, I just realized that I've been forgetting to zero out the free space on the image file before uploading, which saves about 600 MB when zipped. New flashable zip is about 1.1 GB instead of 1.7 GB.
Older versions:
v1 - https://www.androidfilehost.com/?fid=95916177934543883
Apps Removed
/system/app:
Google Books
Google Chrome
Google Cloud Print
Google Drive
Facebook
Hangouts
Google Newsstand
Google Play Games
Google Play Music
Google Play Movies and TV
Google Plus
Twitter
/system/priv-app:
ATT Address Book
ATT Caller Name ID
ATT DriveMode
ATT Games
ATT Locker
ATT Lookout
ATT Mobile Locate
ATT Remote Support
ATT Smart Wifi
ATT Mobile TV
ISIS Wallet
ATT Visual Voicemail
MLT (LG tracker)
/system/vendor/app:
Amazon Kindle
ATT Family Map
ATT Home
ATT Keeper
ATT MHS Launcher
ATT Navigator
Uber
DeviceHelp
myATT
YP Mobile
ATT Apps
In case you want some of the ATT apps back, I have uploaded a zip here with those apps. This is NOT a flashable zip. You have a couple of options:
1. You may be able to install these as a normal (user) app by just pulling out the apk and installing the usual way.
2. If that doesn't work as expected, copy the app folder from the zip into the appropriate system folder as listed in the "Apps Removed" section.
Download: ATT Apps
Xposed Info
cmulk said:
Xposed has a couple of bad side effects at this point, so before doing anything you need to use Titanium or something similar to Freeze (this basically what the "helper" does):
LGSmartCover
Weather
Weather Theme
WeatherPlatform
Then you can install xposed as in the thread here: http://forum.xda-developers.com/showthread.php?t=3034811
However, there is still one more bug to keep in mind: Xposed will crash the Tethering and Networks menu. There is no fix for that yet, but as a workaround you can download some apps from the play store (like Mobile Network Settings), to shortcut around the menu that force closes.
Click to expand...
Click to collapse
Credits
@autoprime - Flashable zips, bump'd boot.img, and very clear instructions in his thread here
@timmytim - uploading the lollipop stock images (although I know a lot of others were working on that too)
@Skin1980 - Oversharpening fix
@skeevydude - init.d support and carrierIQ remover
CarrierIQ Removal
CarrierIQ has now been removed!
The removal is done via an init script that runs at boot to disable the IQ service before removing the files in order to prevent a force close. However, if you have to wipe data/factory reset without re-flashing the ROM, you will get a force close on the first boot. The good news is that I've tested this scenario and it should fix itself if you just wait about 20 seconds. In other words, the mentioned script does it's thing to stop the service to fix the force close and you are good to go after that.
Old info below:
cmulk said:
On the 20f lollipop rom (either mine or stock, there's no difference) either freezing LADDM or removing the libraries and LADDM as you mention will cause a force close unless you disable the "IQService" first, which is built into the framework-res.apk. I have repeated it multiple times and it has been discussed quite a bit in the Lounge and other threads. Disabling the service is easy for users to do with the "DisableService" app, and then you can remove LADDM and the libraries as mentioned. The difficulty is that disabling a service is a user setting, so, for example, if I reflash my ROM without the IQ files onto a phone with clean /data, I will again get the force close and an unusable ROM.
Click to expand...
Click to collapse
Manual Steps
In the meantime, here is how users can manually disable CarrierIQ. I take no credit for this method, it is posted in several places by several people, I'm just putting it here for convenience:
YOU MUST DO THIS IN ORDER (or at least the first few steps)
1. Download the "DisableService" app from the play store
2. In the DisableService app, go to System -> Android System and disable the "IQService" service
3. Use a root explorer to delete the folder /system/app/LADDM
4. Use a root explorer to delete /system/lib/libiq_client.so and /system/lib/libiq_service.so
5. (Optional) Uninstall DisableService
Remember, disabling the service is a user setting, so if you need to wipe /data for some reason, you will need to re-flash the ROM (which has the CarrierIQ files included) or else you will get a constant force close when your phone boots.
I'll give it a try, thanks
Flashing now. Will report.
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
JeffDC said:
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
Click to expand...
Click to collapse
Just clean flash to save yourself a hassle
2SHAYNEZ
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Sent from my LG-D850 using Tapatalk
Flashing lollipop Issues
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
shayneflashindaily said:
Just clean flash to save yourself a hassle
2SHAYNEZ
Click to expand...
Click to collapse
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
JeffDC said:
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
Click to expand...
Click to collapse
I always do a clean flash.. dont need to back up and restore and still get bad results.
louvass said:
I always do a clean flash.. dont need to back up and restore and still get bad results.
Click to expand...
Click to collapse
That's not encouraging.
louvass said:
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
Click to expand...
Click to collapse
I have not seen that issue, but in case you are not clearing data you may need to try clearing dalvik cache.
Also, (and this is just a shot in the dark) you could try formatting system before doing anything else just in case something strange is left behind there.
JeffDC said:
That's not encouraging.
Click to expand...
Click to collapse
You can try dirty flashing first without losing any of your data.
1. Back up your current Boot and System
2. Back up your current modem (if you're coming from the Kitkat modem), or just download a flashable KK modem already posted on XDA
3. Flash the modem and ROM in this post
4. Wipe cache and dalvik
5. See if it works
If it's not working, then you will need to restore your boot, system, and modem to go back to your original kitkat setup without losing data.
Otherwise, you'll have to backup with Titanium and do a clean flash (wipe data) as already mentioned. Using Titanium makes clean flashing not so bad
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Pdj7969 said:
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Click to expand...
Click to collapse
I agree that I use most or all of these Google apps as well. However, they update so often anyway that I prefer to just have them as user apps (otherwise you end up with 2 copies - the old static version in the system apps folder, and the updated version in the user apps folder).
As for the visual voicemail, I have posted the ATT apps in a zip in the OP. Visual voicemail is in the VVM_ATT folder.
Thanks!
cmulk,
Would you please clarify post 5 and 9 questions?
JeffDC said:
cmulk,
Would you please clarify post 5 and 9 questions?
Click to expand...
Click to collapse
Sure thing! That's actually what I meant to do in post 13. I am not sure if you can flash over 10f without wiping data, but you could give it a try without losing anything (except time) if you look at post 13.
You should clear cache and dalvik mostly any time you are flashing, unless you are just flashing over another stock 20f ROM.
louvass said:
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Click to expand...
Click to collapse
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
cmulk said:
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
Click to expand...
Click to collapse
Thanks I do clear everything but my external mem.
Ever since flashing this I'm getting "no sd card" messages every time I try to download anything ( I don't have an external sd card) but it's never been a problem before. I've restored a backup of my stock Tim and the problem followed me after full wipes.
**Root access required**
Download:
- G900V_OD5-OE1_Batch_DeBloater
- G900V_OE1_debloat_linux_mac by @klabit87
Instructions:
1. Extract the G900V_OD5_Batch_DeBloater folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click DeBloater.bat to launch the program.
4. Select "Light," "Medium," or "Extreme" **debloating and press Enter.
5. Grant Root Access if primpted by your device and press Enter to begin.
6. Once complete press Enter to return to the Main Menu and select ***Reboot Device.
7. Last, select Exit from the main menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use notepad++ or other text editor to view/edit the lists of removed apps in the DeBloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
Very nice. Took the guesswork out for me.
The Mobile Hotspot icon is part of Settings. Is there any way to safely remove this icon?
Muniz here is the linux/mac version of your script.
Add to OP if you wish. G900V_OD5-OE1_debloat_linux_mac.zip
MD5: 04836594e91658fdb62761c87e37745a
klabit87 said:
Muniz here is the linux/mac version of your script.
Add to OP if you wish. G900V_OD5-OE1_debloat_linux_mac.zip
MD5: 04836594e91658fdb62761c87e37745a
Click to expand...
Click to collapse
Thanks, added to OP.
I converted this to a flashable zip with a script in it, but the setup wizard gets really pissed off. Anyone know how to disable that? I've looked around and nothing I've found thusfar works. I'd like to be able to modify it so I can flash it without having to boot the ROM first.
Thanks.
Nevermind, I wasn't deleting SamsungSetupWizard.apk. If I do that, it's fine.
The 'extreme' version is attached. ACtually, don't download it yet. Well, you can, but it's not the one I Wanted to upload. I think it's still on my sdcard. I'll get to it later.
@muniz_ri, would you please add the VZW Accessories and YouTube apps to the script? I'd recommend they go under Light and Medium, respectively.
I'll of course be installing YouTube from the Play Store, but it's nice to be able to move the app to SD once it's out of ROM, plus it's not an essential app that's required immediately following a wipe.
xxxstar said:
@muniz_ri, would you please add the VZW Accessories and YouTube apps to the script? I'd recommend they go under Light and Medium, respectively.
I'll of course be installing YouTube from the Play Store, but it's nice to be able to move the app to SD once it's out of ROM, plus it's not an essential app that's required immediately following a wipe.
Click to expand...
Click to collapse
Whenever I have the time to really go through it all, I will release a doubleplusextreme version that, ideally, will leave you with a play store and some tools. heh. What I'm going to try to do is split groups of files out from the original ROM into their own flashable zips.
OK, so I've used Extreme twice and both times, afterward, if I go to recovery, wipe cache/wipe data and reboot, the Setup app fails to complete successfully. Setup fails right after Google account setup and the app keeps restarting preventing getting to the homescreen.
Something in Extreme is not stable.
So far I only know how to get out of this loop by odin to 4.4.4, towelroot, flash OV5, then OE1 and try again.
xxxstar said:
OK, so I've used Extreme twice and both times, afterward, if I go to recovery, wipe cache/wipe data and reboot, the Setup app fails to complete successfully. Setup fails right after Google account setup and the app keeps restarting preventing getting to the homescreen.
Something in Extreme is not stable.
So far I only know how to get out of this loop by odin to 4.4.4, towelroot, flash OV5, then OE1 and try again.
Click to expand...
Click to collapse
The debloater has only been tested after the device has gone through the setup wizard.
Can anyone else validate that the extreme option makes the device unstable after a factory data reset? thx
xxxstar said:
OK, so I've used Extreme twice and both times, afterward, if I go to recovery, wipe cache/wipe data and reboot, the Setup app fails to complete successfully. Setup fails right after Google account setup and the app keeps restarting preventing getting to the homescreen.
Something in Extreme is not stable.
So far I only know how to get out of this loop by odin to 4.4.4, towelroot, flash OV5, then OE1 and try again.
Click to expand...
Click to collapse
The problem with Extreme is that it doesn't delete both setup wizards. You can use the flashable zip I posted instead--that should work.
---------- Post added at 02:49 AM ---------- Previous post was at 02:46 AM ----------
muniz_ri said:
The debloater has only been tested after the device has gone through the setup wizard.
Can anyone else validate that the extreme option makes the device unstable after a factory data reset? thx
Click to expand...
Click to collapse
Yeah, I vouch for that. The problem is that it doesn't delete SamsungSetupWizard _and_ SetupWizard, so one tries to invoke the other, fails, and restarts.
The flashable zip I uploaded works--unelss I uploaded the wrong one from my mess of a 'work' directory.
xxxstar said:
@muniz_ri, would you please add the VZW Accessories and YouTube apps to the script? I'd recommend they go under Light and Medium, respectively.
I'll of course be installing YouTube from the Play Store, but it's nice to be able to move the app to SD once it's out of ROM, plus it's not an essential app that's required immediately following a wipe.
Click to expand...
Click to collapse
blair.sadewitz said:
The problem with Extreme is that it doesn't delete both setup wizards. You can use the flashable zip I posted instead--that should work.
---------- Post added at 02:49 AM ---------- Previous post was at 02:46 AM ----------
Yeah, I vouch for that. The problem is that it doesn't delete SamsungSetupWizard _and_ SetupWizard, so one tries to invoke the other, fails, and restarts.
The flashable zip I uploaded works--unelss I uploaded the wrong one from my mess of a 'work' directory.
Click to expand...
Click to collapse
Thanks, I have added the setupwizard, youtube and accessories apps.
I can confirm that Extreme now accepts a factory data reset. Thanks!! This really is a great time saver.
A couple of thoughts on the script execution: I find I have to run it twice to get the list of apps to scroll in the command window and to fully clear out the apps from the device. May be associated with the timing of the USB debugging request on the device and when the commands are sent.
For future feature, it would be helpful to have a popup on the device to indicate completion and status, e.g. "x of y apps successfully deleted", etc. I don't even know if that's possible via adb.
There could be a level above "Extreme", which is basically removal of anything which is not integral to the system booting and, let's say, running apps you install which don't require Samsung-specific features/support.
Maybe call it "Ludicrous" ("Ludicrous Speed" from "Spaceballs") or "Slash-and-burn"? It should leave you with a play store and the phone app, maybe.
xxxstar said:
I can confirm that Extreme now accepts a factory data reset. Thanks!! This really is a great time saver.
A couple of thoughts on the script execution: I find I have to run it twice to get the list of apps to scroll in the command window and to fully clear out the apps from the device. May be associated with the timing of the USB debugging request on the device and when the commands are sent.
For future feature, it would be helpful to have a popup on the device to indicate completion and status, e.g. "x of y apps successfully deleted", etc. I don't even know if that's possible via adb.
Click to expand...
Click to collapse
The tool will only show an message/error if there was an issue deleting a file, so if you go from starting the process to seeing "done!" without any error message in between you can assume there were no errors and all files were successfully deleted.
Any issue with updates in the future?
Will there be any issue with updates in the future if I am debloated? I remember debloating a while back causing all sorts of issues.
mat2332 said:
Will there be any issue with updates in the future if I am debloated? I remember debloating a while back causing all sorts of issues.
Click to expand...
Click to collapse
Yes, ota updates will fail.
muniz_ri said:
Yes, ota updates will fail.
Click to expand...
Click to collapse
Is there a way to "rebloat" with your program?
Sent from my SM-G900V using Tapatalk
muniz_ri said:
The debloater has only been tested after the device has gone through the setup wizard.
Can anyone else validate that the extreme option makes the device unstable after a factory data reset? thx
Click to expand...
Click to collapse
Verified. I did the extreme debloat and then a factor reset. Setup failed after logging into gmail. Only fix was to go back to NCG and root and flash back to OE1
I have a flashable zip that I have tested, and it works, but only if I use Safestrap or tell Flashfire (by using "mount common paths") to mount /system beforehand.
https://www.androidfilehost.com/?fid=24052804347772843
There has to be some stupid error in there. I also attempted to do what you did in the ROM zip with wipedata.sh, and it still doesn't work. ARGH. Feeling pretty stoked at failing to run like three commands.
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
speedycuban said:
Verified. I did the extreme debloat and then a factor reset. Setup failed after logging into gmail. Only fix was to go back to NCG and root and flash back to OE1
Click to expand...
Click to collapse
Both setup wizards have to be deleted. The batch files were updated, I think.
---------- Post added at 09:55 AM ---------- Previous post was at 09:16 AM ----------
Oh, also, there is more stuff to delete, e.g. all of the voices for SVoice. No sense keeping that around if it's deleted. There's plenty more besides that.
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Thank you! This saved me from several hours of tweaking this stupid samsung security.
Thank you @Chamelleon! I was about to get in to a full reflash stock, reroot, reinstall situation. Damn, I love xda!
BTW, the thing I did differently was to remove the three lines inclusive of
<disabled-components>
<item name="com.samsung.android.kgclient.receiver.KGAgentReceiver" />
</disabled-components>
...and changed enabled="3" to enabled="1" in this line
<pkg name="com.samsung.android.kgclient" ceDataInode="2643" enabled="1"
Probably not required, but thought I'd mention it.
Galaxy Tab S6
Android 9
Stock-Rooted
i cant find the line even if i search it
I tried attempted to debloat an S8 (running Pie), but I started receiving this message afterwards. There's no “com.samsung.android.kgclient” in the package-restrictions.xml file. Is there any other place this restriction could be enforced?
Found Another Way 2
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
I went in and deleted package-restrictions.xml and the bak file, I can reboot now and get in with the message, I initially uninstalled payment services, I tried flashing a zip of payment services apk couldn't get that going, now I'm getting android set up pop ups and my twrp won't boot to the recovery loader from within the app, and super su has lost all the settings for applications!?¿ rlly don't want to do a clean flash and re root ... bloody system packages arggghf help
Wow, this was easy. Thanks!
harismuntazir said:
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
Click to expand...
Click to collapse
Hi..how to restart system ui within so limited time
Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
i cant find this xml anywhere, please help
Any advice if twrp isn't yet installed but device is already rooted?
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
JoshReuben said:
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
Click to expand...
Click to collapse
luckily factory reset solves it. i was already getting anxious about paying "ransomware" to samsung service oof
thanks
but my TWRP doesnt mount data
CANDco said:
but my TWRP doesnt mount data
Click to expand...
Click to collapse
Only hard reset can fix Your phone then. If TWRP can't mount data it means that your phone is encrypted and without full wipe you won't be able to unlock it.
Thanks! I just fixed my m51 with this method. I was thinking about restoring full TWRP backup or flashing stock rom as last resort. So glad I found this thread.
I don't know what is wrong with my phone. I disabled the app, and got the message. I did what you suggested and rebooted. but the app re-enabled itself. I tried disabling again and the message came up again. I checked and that line is no longer in my package-restrictions.xml
Luckily for me, just rebooting unlocks my phone, but I think that defeats the purpose....
I kinda want to get rid of that app
adb shell pm enable com.samsung.android.kgclient
will solve the problem
jafferkhan said:
i cant find this xml anywhere, please help
Click to expand...
Click to collapse
Man, that was a trip to do, but on my unlocked S9+, it worked! I could only see the exact file when I opened the .xml file with wordpad on my Win. 10 to edit it, otherwise it's very hard to spot scrolling in TWRP on the device, particularly since the long package list can freeze up while you scroll down.
I should add, that I used an OTG USB Bridge with a type C connector to paste the copied .xml file to the connected flash drive I mounted in TWRP (just scroll up through the directories for "OTG USB' to find the drive to paste it), then put it on my PC, this made the process go even faster.
But it's better to proactively check what apps can be disabled, removed, or in my case frozen with Titanium Pro, before ever having to deal with such a scare as this!
Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" />line from the file. It can have different values butIpackage name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
What are procedures on how to remove the file after disabling the package, my Samsung A03 CORE can't mount. So kindly assist me here..
No matter what TWRP version I use as my recovery, OOS loses all the emojis. I want to stay stock and rooted. I achieved root via magisk, but the OS is impossible to use without graphical symbols with square boxes instead of them. Please help me. I'm on oos 10.3.3
bythelaw said:
No matter what TWRP version I use as my recovery, OOS loses all the emojis. I want to stay stock and rooted. I achieved root via magisk, but the OS is impossible to use without graphical symbols with square boxes instead of them. Please help me. I'm on oos 10.3.3
Click to expand...
Click to collapse
So what's basically happening is that you somehow like many others don't have the Reserve partition which includes Emojis, Fonts and some OnePlus Apps.
There are a couple of things that you can try to fix it.
You can try to install OOS through local upgrade without wiping anything. This may work or not. From my experience it never worked but for some it did so it's worth to give a try.
If the first method doesn't work you can give this Magisk module a try, it contains everything that's included in the Reserve partition. Just install it via Magisk and reboot.
https://androidfilehost.com/?fid=1899786940962618515
For both methods you may need to wipe the app data and cache of your keyboard app for the emoji's to reappear.
If both methods don't work for you, you probably need to do a complete reinstall of OOS. You could try to clean flash OOS via TWRP or restore your device with the MSM Download Tool.
Good luck! :good:
Mr.FREE_Bird said:
So what's basically happening is that you somehow like many others don't have the Reserve partition which includes Emojis, Fonts and some OnePlus Apps.
There are a couple of things that you can try to fix it.
You can try to install OOS through local upgrade without wiping anything. This may work or not. From my experience it never worked but for some it did so it's worth to give a try.
If the first method doesn't work you can give this Magisk module a try, it contains everything that's included in the Reserve partition. Just install it via Magisk and reboot.
https://androidfilehost.com/?fid=1899786940962618515
For both methods you may need to wipe the app data and cache of your keyboard app for the emoji's to reappear.
If both methods don't work for you, you probably need to do a complete reinstall of OOS. You could try to clean flash OOS via TWRP or restore your device with the MSM Download Tool.
Good luck! :good:
Click to expand...
Click to collapse
I tried the first method, didn't work. I'll try the second method and reply here.
After installing "Reserve_V1" via magisk, do I have to data-reset via twrp? Wipe internal storage? Or anything else?
Or
Just reboot after flashing the zip, and hopefully emojies are back?
bythelaw said:
I tried the first method, didn't work. I'll try the second method and reply here.
After installing "Reserve_V1" via magisk, do I have to data-reset via twrp? Wipe internal storage? Or anything else?
Or
Just reboot after flashing the zip, and hopefully emojies are back?
Click to expand...
Click to collapse
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
Awesome, thank you so much. I'll try it and reply
Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
It seems I didn't pay attention before, but now I see that after twrp and root, my internal storage is not working properly. No apps are installing, can't download anything either.
Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
Reserve magisk worked wonderfully.
Thank you so much. Hopefully others can find this thread as well and root.
Im planning to root my op6, how do i not mess up the reserve partition??
bythelaw said:
Reserve magisk worked wonderfully.
Thank you so much. Hopefully others can find this thread as well and root.
Click to expand...
Click to collapse
Great to hear, glad that the Magisk module I shared was helpful. :good:
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
Antieco said:
Im planning to root my op6, how do i not mess up the reserve partition??
Click to expand...
Click to collapse
I'm actually not quite sure what causes the reserve partition to go missing. But from my own experience it seems that wiping the /data partition after a clean install of OOS with he MSM Download Tool causes this to happen. But I am not 100% sure this is correct.
The Reserve zip file worked very well. Thanks to the zip creator and guy refering to the zip file.
Now with everything fixed I wanted to use the font changer magisk module which I couldn't due to the above module blocking/overwriting it.
Reserve file containing all the fonts and emojis in system/fonts folder. Surprisingly almost all the files were already present in the phones system folder but containing 0kb data, which was the problem.
Extracted the Reserve zip file, copied files from system/fonts and replaced them in the phones system/fonts folder via file manager. Rebooted and everything was working. Now all the fonts and emojis are working as well as I'm able to change fonts using font changer module. Hope this helps
Mr.Hunk said:
The Reserve zip file worked very well. Thanks to the zip creator and guy refering to the zip file.
Now with everything fixed I wanted to use the font changer magisk module which I couldn't due to the above module blocking/overwriting it.
Reserve file containing all the fonts and emojis in system/fonts folder. Surprisingly almost all the files were already present in the phones system folder but containing 0kb data, which was the problem.
Extracted the Reserve zip file, copied files from system/fonts and replaced them in the phones system/fonts folder via file manager. Rebooted and everything was working. Now all the fonts and emojis are working as well as I'm able to change fonts using font changer module. Hope this helps
Click to expand...
Click to collapse
Absolutely not a problem! Glad it was somewhat helpful.
Great solution and tip for others who might run into the same issue. I'm sure that will be helpful for others who might run into this thread. :good: