Hi there so heres my story shortened:
>for some reason was getting en error on google play store "insuffient space to install apps" despite having 2gb free space
>saw a root only app they claimed to fix this.
>managed to root device by going down to 10.5.a.0.230 rooting with ezroot then back up too 10.5.1.a.0.292 and was successfully rooted.
>then attempted app that claimed fix didnt work
>tried to sign into banking app i use daily didnt work because they dont allow rooted devices
>since the fix didnt work and i now longer could access my banking app i decided to unroot using SuperSU's interal feature
>then could only access google play store on 4g wifi came up with "check your connection and try again" which you can fix via having root access i believe and changing the hosts file
>at this point i was unrooted, banking app still wasnt letting me in though
>tried same process to reroot, but its not working, in ezroot is says success but flashtool tells me the device doesnt have root access and i cant seem to edit the hosts file so i guess its right
>playstore still isnt working, tried to reroot about 5x and have even done a complete backup and restore in pc companion and it changed nothing.
been trying to fix this for hours and im so frustrated please help
Aizon said:
Hi there so heres my story shortened:
>for some reason was getting en error on google play store "insuffient space to install apps" despite having 2gb free space
>saw a root only app they claimed to fix this.
>managed to root device by going down to 10.5.a.0.230 rooting with ezroot then back up too 10.5.1.a.0.292 and was successfully rooted.
>then attempted app that claimed fix didnt work
>tried to sign into banking app i use daily didnt work because they dont allow rooted devices
>since the fix didnt work and i now longer could access my banking app i decided to unroot using SuperSU's interal feature
>then could only access google play store on 4g wifi came up with "check your connection and try again" which you can fix via having root access i believe and changing the hosts file
>at this point i was unrooted, banking app still wasnt letting me in though
>tried same process to reroot, but its not working, in ezroot is says success but flashtool tells me the device doesnt have root access and i cant seem to edit the hosts file so i guess its right
>playstore still isnt working, tried to reroot about 5x and have even done a complete backup and restore in pc companion and it changed nothing.
been trying to fix this for hours and im so frustrated please help
Click to expand...
Click to collapse
Flash C6603_10.5.1.A.0.292_Generic_NCB.ftf using Flashtool.
It should solve all of your problems.
As for rooting, I suggest that you follow the guides in this forum because they are already verified to work with Xperia Z.
Aizon said:
Hi there so heres my story shortened:
>for some reason was getting en error on google play store "insuffient space to install apps" despite having 2gb free space
>saw a root only app they claimed to fix this.
>managed to root device by going down to 10.5.a.0.230 rooting with ezroot then back up too 10.5.1.a.0.292 and was successfully rooted.
>then attempted app that claimed fix didnt work
>tried to sign into banking app i use daily didnt work because they dont allow rooted devices
>since the fix didnt work and i now longer could access my banking app i decided to unroot using SuperSU's interal feature
>then could only access google play store on 4g wifi came up with "check your connection and try again" which you can fix via having root access i believe and changing the hosts file
>at this point i was unrooted, banking app still wasnt letting me in though
>tried same process to reroot, but its not working, in ezroot is says success but flashtool tells me the device doesnt have root access and i cant seem to edit the hosts file so i guess its right
>playstore still isnt working, tried to reroot about 5x and have even done a complete backup and restore in pc companion and it changed nothing.
been trying to fix this for hours and im so frustrated please help
Click to expand...
Click to collapse
you
Its easy dude...if u want ur banking app to work on rooted device...just use. ROOT CLOAK. APP...
Hope this helps.
I know it's been said 1000x and I've def been there before. But again, if you've never rooted a device, do yourself a favor and take some time to at least know what you are getting into. It's not for everyone. But just knowing the basic pros/cons, would of helped avoid or solved all of these issues, even prior to rooting. There is a ton of info that's super easy to find on xda that'll save yourself from a headache and hours wasted.
BlackBradPitt said:
I know it's been said 1000x and I've def been there before. But again, if you've never rooted a device, do yourself a favor and take some time to at least know what you are getting into. It's not for everyone. But just knowing the basic pros/cons, would of helped avoid or solved all of these issues, even prior to rooting. There is a ton of info that's super easy to find on xda that'll save yourself from a headache and hours wasted.
Click to expand...
Click to collapse
And I might add, if you cry when you lose it, back it up.
Such a shame. Hope you don't lose too much data, op!
Update: decided to plug my phone into flashtool and
Try and fix again it said somethint about sony RIC
Now disabled, root access granted.
Managed to edit hosts file, all fixed shame i lost all my apps
Despite backup kept all music, settings and images tho.
Thanks for all your advice
Got lucky somehow.
Related
I accidently deleted a folder containing photos, I tried downloading DiskDigger, Undelete and Hexamob...all for root which I have. When I opened them they ask for root and I allow, then you are supposed to be able to choose which device you want, but there is nothing there. It says if there isn't anything there than you don't have root...but this seems to be a recurring problem after I updated my D4 using the OTA update, that even though I am rooted, a lot of the programs do not work anymore.
Does anybody know of a way I can attempt to recover those pictures I accidetly deleted??!
svrnmnd said:
I accidently deleted a folder containing photos, I tried downloading DiskDigger, Undelete and Hexamob...all for root which I have. When I opened them they ask for root and I allow, then you are supposed to be able to choose which device you want, but there is nothing there. It says if there isn't anything there than you don't have root...but this seems to be a recurring problem after I updated my D4 using the OTA update, that even though I am rooted, a lot of the programs do not work anymore.
Does anybody know of a way I can attempt to recover those pictures I accidetly deleted??!
Click to expand...
Click to collapse
Did you use something like rootkeeper when you took the OTA? If not then the OTA to ICS probably caused you to lose root. You'll need to root your phone again.
Sent from my D4 - AOKP JB
I don't think you have root if most of your programs that required root in GB no longer work after you upgraded to ICS. You need to use OTA Rootkeepr to keep root after an upgrade. So your only choice now is to root and to run those programs to try to recover the photos.
I actually flashed back to orig non-root GB before I updated because I had changed too many things and OTA would fail. I used the droid for win tool and flashed GB system to my phone then went to settings system and got the OTA. After that I rooted. since then most root programs work like rom toolbox, titanium backup for root, root explorer etc. but some programs just don't work anymore, like Droidsheep or Wireless Tether, I believe they just aren't compatable with ICS...I know that a lot of people on google play are saying that after they did their ota wireless tether would not work anymore..everything works on it except it won't switch into AD-HOC mode , which is what I'm guessing changed in the OTA.
I tried using some recovery program for mac but it didn't work, right now I'm downloading riplinux and a couple other recovery distros. since the files were on my removable sd card I am just going to plug it in and try and recover from a computer....does any one have any methods that work best?
When you pull the files off your SD card let me know which program worked for ya... please and thank you
Sent from my DROID4 using xda app-developers app
Hello there everyone, total noob here.
I have tried to "root" my S3 LTE using this method: http://forum.xda-developers.com/gal...-cf-root-cwm-recovery-ported-supersu-t1914394 (or more likely this: http://forum.xda-developers.com/showpost.php?p=45291825&postcount=306 ). Everything went great, Odin has shown a pass and it was successful while installing CWM, then I installed Supersu through CWM (only thing I did differently was putting a supersu zip file on internal storage) and that was a success too. I did everything like it said, even without plugging out my phone. After rebooting everything went down...
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Now, I dont have root AND internet access.
Other info that might me useful:
Android 4.3
Null IMEI: no
Baseband: i9305XXUEMK1
I have performed factory reset, still no use.
Any help regarding repairing wifi, getting root access or bringing back state before "rooting" would be appreciated.
Regards,
Maziu92.
Maziu92 said:
Hello there everyone, total noob here.
1. Knox is blocking SuperSU, someone reccmmended that I should have tried to disable it by installing supersu.apk manually, but then it has shown a popup that supersu doesnt have access to binary files. I have checked with root checker and it said that device isnt rooted...
It wouldnt bother me much, because having root isnt necessity for me, but...
Click to expand...
Click to collapse
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Maziu92 said:
2. I cannot access internet via wifi. It connects to router, signal is pretty decent, but still, when I try to use a build-in browser/chrome it just doesnt connect. Nevertheless, I can connect via 3/4g with no problems at all.
Click to expand...
Click to collapse
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
tharinduwijewardane said:
Just download the "SuperSU version 2.02" apk and install it. Its provided in this thread. (its newer than whats currently on Google play)
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
It will ask to disable KNOX. select YES.
Click to expand...
Click to collapse
Oh, I did it, that's why it said the binary was missing. But I did it other way around:
1. I have flashed CWM like it said in second link provided in first post
2. Installed SuperSU 2.02 from zip file on internal card though CWM instead of file provided in thread (I could have installed remove-boot-recovery too, but I didnt notice that I needed that. Anyway, I did that later)
3. Rebooted and tried to turn on - supersu was still blocked by knox :/ BUT!
4. I have installed manually supersu.apk, then opened it via installator (important! Dont tap 'done' but 'run'!) and next I didnt get the "missing binary" popup but if I want to disable KNOX. Well, yeah, I do, so I tapped OK and it looped and looped... http://www.reddit.com/r/galaxys5/comments/2a92qq/supersu_stuck_disabling_knox/cisq087 found this soulution and it worked (reboot phone and start supersu again). Sorry about my short memory, but I think I needed to install supersu.apk manually again and tap disable once more time, but disabling KNOX took a few seconds.
5. And then I went to the settings in Supersu and tapped option 'install supersu into /system', rebooted and it worked fine!
5.a To make sure it really works I downloaded (via 3g ) Root checker and it said it is rooted.
So now I have root, yaay, but still no Wifi access :/
tharinduwijewardane said:
The best thing i can suggest you is moving to the new 4.4.4 Stock Rom
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Use Odin v3.07
and then (if u want) root it using "CF-Auto-Root-m3-m3zh-gti9305.tar.md5."
and install "SuperSU version 2.02"
Click to expand...
Click to collapse
I have been using odin 3.07.
Really, It is the only way to get back wifi? Are there any other options apart this?
Nooby questions:
-will it work with my phone? It says that its "MODEM: I9305XXUFNI3" and mine is XXUEMK1.
-in the meantime I have read about efs files/folder, what are they for and should I somehow backup them?
-while flashing 4.4.4 it is possible that my IMEI will go null?
-will it be possible to go back to 4.3?
I dont want to brick it or anything, thats why I am asking.
And of course, thanks for your help, Tharinduwijewardane ^^
Edit:
Actually, I have managed to repair my WIFI connection without flashing new rom etc.... So what was wrong, you will ask? Me.
I have downloaded adblock (before factory reset) and it asked to connect via proxy, so I did. And then I have disabled it because it was blocking SuperSU along with KNOX. And my phone tried to connect with internet via proxy, but it couldnt, because of this configuration.
Found this by complete coincidence (my GF told me to check if I get connection though Chrome and it said that it cant connect because of proxy settings). It is strange that this configuration was still there, even after factory reset.
Oh well, case solved, thanks again for helping and even everyone else for checking this out^^
glad to hear u got it fixed.
:good: :good:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam
johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.
Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s
johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM
I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.
Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?
KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Disable OTA
Dmriskus said:
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Click to expand...
Click to collapse
1. Disable updates, link one post up
2. Root in TWRP
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.