Hey guys, I wound up digging around wanting to add Google's Car Home app when I flashed a couple different ROMs and lost the similar app that came from Samsung. It wound up being pretty simple to do and it's been working great on my S3.
I wound up writing it up on my blog, you can find it here:
Manually Installing Google's Car Home App
The steps I wrote aren't necessarily specific to the S3. I had success with a few other Android devices too.
I haven't tried your version yet, but with previous versions on my VZW SGS3 Google Car Home loads and runs fine, but as soon as I customize it (add / remove apps), it no longer loads and FQs.
Have you noticed anything like this with your setup? Thanks!
bradys said:
I haven't tried your version yet, but with previous versions on my VZW SGS3 Google Car Home loads and runs fine, but as soon as I customize it (add / remove apps), it no longer loads and FQs.
Have you noticed anything like this with your setup? Thanks!
Click to expand...
Click to collapse
No, I haven't noticed anything like this at all. That seems weird to me (although, I imagine there's a reason that Google doesn't list many devices as compatible in the Market).
I would recomend trying the version I've got out there and then also maybe installing it as a System App to see if that fixes your FQs?
Neckhole said:
No, I haven't noticed anything like this at all. That seems weird to me (although, I imagine there's a reason that Google doesn't list many devices as compatible in the Market).
I would recomend trying the version I've got out there and then also maybe installing it as a System App to see if that fixes your FQs?
Click to expand...
Click to collapse
I used TB to pull com.google.android.carhome.apk (v2.2.1) and com.google.android.cardock.apk (v2.2) off my Thunderbolt running 4.0.3 (I can't even remember what rom it's running now). After installing both to my GS3 (4.1.1 stock), Car Home seems to be working fine. Good thing, too, because all the alternatives in the play store suck.
mobilejohn said:
I used TB to pull com.google.android.carhome.apk (v2.2.1) and com.google.android.cardock.apk (v2.2) off my Thunderbolt running 4.0.3 (I can't even remember what rom it's running now). After installing both to my GS3 (4.1.1 stock), Car Home seems to be working fine. Good thing, too, because all the alternatives in the play store suck.
Click to expand...
Click to collapse
Any way you could post those APKs?
Hi, rather new here so I can't post in the thread on the developers board. Thought I'd try here. I recently flashed Tiny's latest CM 10.1 nightly rom and I really like it so far. There are a couple of issues but after messing with it for a while, it's mostly smooth and works well. My biggest beef, aside from those couple issues is Netflix. The app loads and I can select a show, but when I try to load a video, I just get the red loading screen that goes on forever until I hit the back button. I tried an older apk, and it wouldn't load, period (1.5.2), which I guess is to be expected when running Android 4.2. I tried 2.1 and I got the same issue with the red loading screen. Tried loading it in the browser and I got the usual page that tells me I need a certain browser for it to work. The app worked just fine in the official CM 7.2. Is there an option in settings I'm missing or something or does it not work on this rom (which I don't see why it wouldn't)?
Other naggy issue is epsxe. It works alright but if I press a volume button, it either increases or decreases all the way and all buttons freeze. Nothing works. Home, menu, power button, touch, etc (yet the emu keeps going and the music keeps playing). Sometimes when I press an on-screen button to move, it's like the button gets stuck and the character keeps moving in that direction. I have to remove the battery to reboot. Did not have this issue in cm 7.2.
Other than that, awesome rom and thanks, Tiny, for working on it.
EDIT: Well, I just tried using epsxe again and it even worked when using the volume button. Not sure why it worked except that I let the game load for a bit before pressing anything. After that, it worked just fine. So, I guess it may be even an app issue on 4.2, rather than the rom. Hope Netflix is as easy to get working.
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
omniatic said:
Netflix hasn't worked on JB or ICS. Known issue since day one. Probably won't be fixed as it's not a high priority in the overall picture.
...sorry...I was on the phone...
Click to expand...
Click to collapse
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Kaepernick said:
Well, that's disappointing. I really like this this rom but Netflix was one of the biggest reasons to keep using this device. It's mainly used as a tablet now and I don't want to buy anything else right now. Funny thing, Netflix was the only reason I didn't switch from Windows 7 to Linux. I figure, if I'm paying them every month, I should be able to play their vids on any device I please and it irks me that I can't even get it working in the android browser. Oh well. Thanks for the quick response.
EDIT: Well, I did some research and found that Netflix 1.81 seems to work to an extent. I get sound and subtitles but no video. Going to look into it some more.
Click to expand...
Click to collapse
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
It works on better supported devices on ICS and JB. The issue here is the codecs and hardware support / drivers which will not be fixed for now. Just confirming its not androids fault or Netflix's.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Kaepernick said:
So no amount of tinkering with older apks and workarounds (to make it so the app uses older netflix video players) will work because the rom/hardware simply doesn't support playback? I was looking at some other threads and google and a lot of people seem to be having trouble getting Netflix to work on 10.1 and Android 4.2 in general. Seems when the app detects Jelly Bean, it uses its newest video player, which has some problems on some devices. Forcing it to use an older player seems to work for some people. Adding a line to the code to make it use player "6" instead of "10" or something. Haven't actually applied anything to the app to try it because I'm a complete novice at this.
You're the expert and I assume if there was an easy method that wouldn't screw anything up in the CM 10.1 build, you'd apply it. I do appreciate the work you and others are putting into these roms and other than this Netflix issue, it rocks. I may go back to CM 7.2 after a bit but I'll definitely keep an eye on your updates and try them out.
Click to expand...
Click to collapse
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
That may just work. I'm kind of a newb at smali but it may be worth a shot. I haven't heard of this workaround before. In theory it should work under software.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Kaepernick said:
Well, that gives me some hope, at least. Here's one of the threads I was looking at.
http://forum.xda-developers.com/showthread.php?t=2101525
On the last page, someone posted the code that enabled it to work on theirs.
EDIT: I tried the Xposed app workaround, by the way, which did not work for me, using 1.8.0 (thought it was 1.8.1 but wasn't. Plan on trying that next) or the newest version. I realize that these are different devices, but I'm hoping there's a way to get it to work on ours. I wonder if there's a way to trick it into thinking it's Gingerbread instead of ICS (in the thread) and using the player that works on CM 7, if it would work?
Click to expand...
Click to collapse
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
tiny4579 said:
I don't have a netflix account currently (had it and didn't use it), so I can't do much testing but based on the link you showed me, the app should work fine. Try the init.d script linked in the github in the thread you posted. Are you familiar with pushing files to your device? You just need to copy it to /system/etc/init.d and add execute permissions. Usuaully I use read-write-execute for user and read-execute for group and other.
Click to expand...
Click to collapse
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Kaepernick said:
The xposed_init file under assets? Can't say I've ever tried this before. I know how to add files to that folder, but no idea how to copy it to a file or whatever that would work. Don't know how to execute permissions either.
Looking things up, I can't just add a file to my sdcard and use ES File explorer to add it to the init.d folder? I copied one of the files on my desktop and opened it up with notepad. It sadly didn't help me. Like I said, total novice with android here or this stuff in general. Would like to give this a shot though. Do I add the text to notepad and then delete the .txt or do I need to make a .js file? As for permissions, do I just add r rw and x to the file?
Click to expand...
Click to collapse
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
ealassi content
tiny4579 said:
Yeah, you can add it to notepad and remove the .txt at the end but it uses different line breaks in Windows than what Linux uses so the script may not work right. I'm not sure though. The worse thing that can happen is nothing. Android doesn't use .js which is Javascript. For permissions, yes that will work.
Click to expand...
Click to collapse
Tried it. Not sure if I did it right. Most likely not. lol But in any case, it doesn't work. Getting a bit tired, so I may just relent. I'm sure many who are more experienced have tried already.
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
MysticCobra said:
Just curious: If your primary use for your old Dinc is as a portable Netflix viewer, then why not just flash back to a stable GB-based ROM and enjoy?
Seems that would be a lot simpler than trying to get Netflix to work on JB, especially if you're not doing anything with the phone that requires JB.
Click to expand...
Click to collapse
I like Jelly Bean. I like how it looks and feels. It's a more mature Android. Plus, I like keeping up to date with software. It's kind of nice to have 4.2 running on the aging, yet good o'l Dinc, when some newer devices don't even have 4.1 yet officially.
Also, I got it working, by the way! Before, when I downloaded the newest one onto 10.1, it would just continuously load when picking a video and not work. After tinkering, I got it to play sound but no video. I could tell that the video player was different than the one I used on 7.2 (also, the newest app). I switched back to 7.2 for a bit and downloaded my apps. I backed everything up using Clockwork mod so I could go back to it whenever. Then I backed up all the Apps with Titanium Backup. I switched back to Tiny's 10.1 and restored the apps. I tried out Netflix and it worked. It was using the same player it used on 7.2. I don't know if it detects Jelly Bean when you download it from Google Play or if it does it when you sign in to your account. When I restored it, I was already signed in, so maybe that's it. At any rate, it works.
Well, I spoke too soon. It did work for the first few videos but then stopped. I tried uninstalling and reinstalling with the Titanium Backup, but when I try to choose a video, it says I've been signed out. I sign back in and I'm back to the forever loading red screen. So yeah, I think it detects which OS I'm on as I sign in. Just a guess though. Just shows that it has nothing to do with your ROM aside from their newest player not working properly on it. It can indeed be fixed via the software with some tinkering.
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
tiny4579 said:
Can you check the value for int name="nflx_player_type" in /data/data/com.netflix.mediaclient/shared_prefs/nfxpref.xml from a working Netflix in Gingerbread? Easier yet, pull that file from your Netflix backup from Gingerbread for me. Check for passwords in the file and clear them out before giving it to me for security.
Click to expand...
Click to collapse
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Kaepernick said:
Here you go. Says It's using Player 9. I have read that 10 is the newest player. At least I believe so.
Edit: just checked that file on 10.1. It says player 10. That means it switched when I signed back in.
Click to expand...
Click to collapse
Hmm, if you edit that file back to 9 and open Netflix does it work?
tiny4579 said:
Hmm, if you edit that file back to 9 and open Netflix does it work?
Click to expand...
Click to collapse
Yes and it didn't work. Then I tried "6". Didn't load. I tried 9 again and for whatever reason, it loaded. It works just fine now, using the same player it did in 7.2. The kicker is that I check the XML file again and it changed somewhat. It now says "6" and it looks different. I believe the Player line used to be before the Logged in line. Now the logged in line is last. If there was some way to force it to use 6 every time, even when logging in, we'd have a working netflix app on your rom.
Maybe "old app version=17" is the key, I don't know.
EDIT: Exited the app. Still works. Rebooted the phone. Still works. There's no log out button, so I assume to log out, I need to clear data, which I assume would just put me back at square one. Seems to be working fine now, as long as I stay signed in. If I somehow have to sign in again, I'll check the xml file.
Attached the file. Just edited the user id part.
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Watching this with interest, if you guys figure it out please post a guide and link to it because you're not alone. My Netflix stopped working when I upgraded to 10.1 as well (interestingly it worked fine on my ICS One-Click ODIN Rom that I got last June, not CM) and this was the first thread to pop on my google search as I've started looking for answers.
*UPDATE* Got mine working using the directions in this thread: http://forum.xda-developers.com/showthread.php?t=2101525
Hope this helps!
Kaepernick said:
Well, it was working. Then it quit. I checked the xml file and it had switched to 10. Didn't sign in or out or anything. Tried the 6 file and it immediately switched back to 10. So, I uninstalled and then installed 1.8.1. Replaced the nfxpref file with the one I backed up and it worked. Funny thing, it's actually using an older version of the player. I believe that may actually be "6". In cm7.2, it said "9" and was using a newer version of the player (newer than the one I'm using now). It seems to work well so far. Haven't tried updating from this yet, to see if the newest one works by updating, but I doubt it would work anyway. I did notice that in the shared prefs folder, there's only one other file with the nfxpref file. In the newest version, there looked to be about six or seven other files.
Click to expand...
Click to collapse
I would like to ask here for any help getting any (Other than FFIII) games to run on my nexus 7. I have been unable to run them, both the paid for (And I can't get a refund on the 2 i purchased yet) and I've also tried the 'cracked' pirated versions way, and in all cases, the game will not run(screen blinks for a second, returns me to previous screen, or it opens a black screen and sits and does nothing)
The only game I've been able to run was FFIII and sadly, the PAID version would NOT run (I had to use a cracked/pirated version) and I would like to know what I am doing wrong (And considering I've seen a LOT of others with same issue but no 'fixes' yet the issue seems totally random not dependent on the type of device, if the device is rooted or not, or the game in question, I think its something to do with me.
My n7.2 is rooted with the wugfresh toolkit(I had it rooted before another way and had exact issue so I'm not sure its this) and ive also tried after factory resetting the device and same issue.
So can anyone here give me some insight on to what I can try next to enjoy the games I've paid for at least?
Edit: as a test I tried the chaos rings I and II and II installed and played fine yet I did not, both were, if it matters, 'cracked' games and I have no interest in playing either. But added this just in case there's something about them which may help reach a conclusion.
hmm guess nobody else has had this issue. Oh well. Thanks for looking.
IMO I would install a PS emulator and just run the games that way. If you bought them originally on the market legally, obtaining a copy of the ROM for a PS emulator wouldn't be illegal technically as you've already purchased the media rights.
Sent from my Nexus 7 using xda app-developers app
Square is picky about their games. I haven't played the FF games on my N7 but Chaos Rings works. Sadly I paid for it and don't really get into it.
Sent from my Nexus 7 using XDA Premium 4 mobile app
AtmaDarkwolf said:
I would like to ask here for any help getting any (Other than FFIII) games to run on my nexus 7. I have been unable to run them, both the paid for (And I can't get a refund on the 2 i purchased yet) and I've also tried the 'cracked' pirated versions way, and in all cases, the game will not run(screen blinks for a second, returns me to previous screen, or it opens a black screen and sits and does nothing)
The only game I've been able to run was FFIII and sadly, the PAID version would NOT run (I had to use a cracked/pirated version) and I would like to know what I am doing wrong (And considering I've seen a LOT of others with same issue but no 'fixes' yet the issue seems totally random not dependent on the type of device, if the device is rooted or not, or the game in question, I think its something to do with me.
My n7.2 is rooted with the wugfresh toolkit(I had it rooted before another way and had exact issue so I'm not sure its this) and ive also tried after factory resetting the device and same issue.
So can anyone here give me some insight on to what I can try next to enjoy the games I've paid for at least?
Edit: as a test I tried the chaos rings I and II and II installed and played fine yet I did not, both were, if it matters, 'cracked' games and I have no interest in playing either. But added this just in case there's something about them which may help reach a conclusion.
Click to expand...
Click to collapse
I had the same problem. FFIII and FFV work, but not IV or Dimensions. I dunno, I'm guessing a fix will come eventually. We own a popular device.
Send an email to support, let them know your issue and solution. The piracy should get their actions in gear.
3 and 4 work for me, no go on FFI. It connects to server then hangs on "checking license..." Willing to forgive them if they release FFVII for Android (and if, y'know, it works lol)
Sent from my Nexus 7 using Tapatalk 4
dimebagdan65 said:
Willing to forgive them if they release FFVII for Android (and if, y'know, it works lol)
Click to expand...
Click to collapse
Don't hold your breath. All FF games run good for me on my Flo.
AtmaDarkwolf said:
I would like to ask here for any help getting any (Other than FFIII) games to run on my nexus 7. I have been unable to run them, both the paid for (And I can't get a refund on the 2 i purchased yet) and I've also tried the 'cracked' pirated versions way, and in all cases, the game will not run(screen blinks for a second, returns me to previous screen, or it opens a black screen and sits and does nothing)
The only game I've been able to run was FFIII and sadly, the PAID version would NOT run (I had to use a cracked/pirated version) and I would like to know what I am doing wrong (And considering I've seen a LOT of others with same issue but no 'fixes' yet the issue seems totally random not dependent on the type of device, if the device is rooted or not, or the game in question, I think its something to do with me.
My n7.2 is rooted with the wugfresh toolkit(I had it rooted before another way and had exact issue so I'm not sure its this) and ive also tried after factory resetting the device and same issue.
So can anyone here give me some insight on to what I can try next to enjoy the games I've paid for at least?
Edit: as a test I tried the chaos rings I and II and II installed and played fine yet I did not, both were, if it matters, 'cracked' games and I have no interest in playing either. But added this just in case there's something about them which may help reach a conclusion.
Click to expand...
Click to collapse
Do you have xposed framework installed? That was my problem. Ffiii worked fine, but ffiv and ffd would not work for me. Not sure about ffv, as I had xposed disabled before trying it.
Someone else here posted some info. Check on your sd card for a file named either "__57d5__.log" or something similar. It should say what is causing the issue.
It might also be a dpi issue. Others have had issues with trying to run ffi at 200 dpi, but it works at 240.
Sent from my Verizon Galaxy Note 2 using Xparent Skyblue Tapatalk 2
Hey,
Got a nexus 7 2013. I bought Modern Combat 3 for it a while ago, and never got it to start. I had the same problem for my Galaxy Nexus, but I fixed it by installing a previous version of the app through an apk. Whilst it worked flawlessly for my Gnex, when installed on my N7 it tells me that my device is incompatible. I know this is not true as I downloaded the app from the playstore and installed it no problems; running it was the issue.
So I need to ask if changing the device name in the build.prop, letting the game install then putting it back has a possible chance of causing a brick. Either way, please let me know asap.
If there is a different way to get the game working, or to make the app think I have a compatible device, please also let me know.
I'm rooted, running stock 4.4.2 with Xposed.
Thanks,
-Riku
For the most part anything under ro.build and ro.product is safe to edit, they're generally for display purposes or for market to do app compatibility checks like what you might be having issues with.
The exceptions are
ro.product.cpu.* (I simply have not tested changing these)
ro.board.platform (this will definitely break booting if you change it)
Whether or not this actually helps you though, I dont know.
TheManii said:
For the most part anything under ro.build and ro.product is safe to edit, they're generally for display purposes or for market to do app compatibility checks like what you might be having issues with.
The exceptions are
ro.product.cpu.* (I simply have not tested changing these)
ro.board.platform (this will definitely break booting if you change it)
Whether or not this actually helps you though, I dont know.
Click to expand...
Click to collapse
This is useful and I will apply that to future questions, but i just want a solid answer. If you have a N7, would you main testing it and seeing if it still boots? If you don't, is there a way you could confirm an answer for me?
Your help is greatly appreciated.
-Roku
So i'm trying to figure out what would work the best for my 10.5 tablet,
Main thing's i'm wanting is it Rooted, Basic enough design that work's pretty good, and has the Samsung app, not sure if i can get this off google play or not but. will obviously find that out soon. lol
but yeah, if anyone can give me their suggestion's for what i'm after (Might be looking for better performance as well) that would be awesome.
Damob99 said:
So i'm trying to figure out what would work the best for my 10.5 tablet,
Main thing's i'm wanting is it Rooted, Basic enough design that work's pretty good, and has the Samsung app, not sure if i can get this off google play or not but. will obviously find that out soon. lol
but yeah, if anyone can give me their suggestion's for what i'm after (Might be looking for better performance as well) that would be awesome.
Click to expand...
Click to collapse
I think you would get a more valuable response if you stated why you want root. I've just upgraded to a Tab S from a rooted Nexus 10 and so far have not found a "must have" reason to root and loose my warranty. That does not mean I'll never root though. I've already replaced the launcher with Nova launcher and changed the icons with an icon pack but neither required root. The one root apps I miss are Viper4Android and GMD Gestures but Nova Launcher provides an acceptable alternative to GMD for now.
So what do you require root for?
Sent from my SM-T800 using XDA Premium HD app
Im mainly wanting it for a couple of apps that use it, one for modding a game, another for moving apps to sd, full files and all not just a 16th of the app. Just tried an app called kingroot but unfortunately it didnt work.
Damob99 said:
Im mainly wanting it for a couple of apps that use it, one for modding a game, another for moving apps to sd, full files and all not just a 16th of the app. Just tried an app called kingroot but unfortunately it didnt work.
Click to expand...
Click to collapse
What model tab s do you have? Kingroot V4 rooted my kitkat t805 just fine. Doesnt work on lollipop though.
Sadly did it on my normal tablet before having any root access what's so ever without installing another rom on it. lol. wanted to test it to see if it would work, sadly it didn'. i have a Galaxy Tab S SM-T805Y.. it's the 10.5 samsung tablet.
Damob99 said:
Sadly did it on my normal tablet before having any root access what's so ever without installing another rom on it. lol. wanted to test it to see if it would work, sadly it didn'. i have a Galaxy Tab S SM-T805Y.. it's the 10.5 samsung tablet.
Click to expand...
Click to collapse
Sometimes it takes more than once. Did you let it reboot and then continue?
Yes and unfortunately it didn't want to work.