There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary
I just flashed the latest Omni Rom 4.2.2 and found it generally great however one issue I cannot seem to fix. Device is rooted with busybox however when I ran root validator it says "you may have root but permission was not given. Did you allow root when prompted?" or words to that effect...
The issue seems to be that when I run a process / app that requires root access I do not get the prompt to allow root access therefore it can't be given. I even set root to always allow and this didn't fix it. I opened SuperSU and the apps says binary needs to be updated but the update always fails in normal mode. I tried updating via TWRP but the device doesn't boot to recovery and update the binary either.
I have tried unintalling and reinstalling SuperSU and this has no effect.
Another thing, the hardware keyboard is enabled every reboot... but this is easy to get around and may be unavaiodable at this stage. I'm not super concerned about this as sure to be fixed eventually.
Also no photosphere available in stock cam and pano did not work at all (no image captured from cam although it does TRY to make a pano, but with no input from cam it cannot work).
Any ideas how to fix?
originaldigga said:
I just flashed the latest Omni Rom 4.2.2 and found it generally great however one issue I cannot seem to fix. Device is rooted with busybox however when I ran root validator it says "you may have root but permission was not given. Did you allow root when prompted?" or words to that effect...
The issue seems to be that when I run a process / app that requires root access I do not get the prompt to allow root access therefore it can't be given. I even set root to always allow and this didn't fix it. I opened SuperSU and the apps says binary needs to be updated but the update always fails in normal mode. I tried updating via TWRP but the device doesn't boot to recovery and update the binary either.
I have tried unintalling and reinstalling SuperSU and this has no effect.
Another thing, the hardware keyboard is enabled every reboot... but this is easy to get around and may be unavaiodable at this stage. I'm not super concerned about this as sure to be fixed eventually.
Also no photosphere available in stock cam and pano did not work at all (no image captured from cam although it does TRY to make a pano, but with no input from cam it cannot work).
Any ideas how to fix?
Click to expand...
Click to collapse
Try flashing SuperSU zip through recovery manually, instead of using the app itself. The SuperSU app requires root to already be fully functional in order for it to install its binaries via normal mode. I don't know about the keyboard and panorama, but I do know that photosphere requires gyro sensor, which the Tab 2 does not have.
Fixed!
putr4s said:
Try flashing SuperSU zip through recovery manually, instead of using the app itself. The SuperSU app requires root to already be fully functional in order for it to install its binaries via normal mode. I don't know about the keyboard and panorama, but I do know that photosphere requires gyro sensor, which the Tab 2 does not have.
Click to expand...
Click to collapse
Worked perfectly. Thank you!
Help. Looking for root method for Hannspree SN14T71 on 4.2.2.
Please any help is appreciated.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm in the same boat
tennisjunkie said:
Help. Looking for root method for Hannspree SN14T71 on 4.2.2.
Please any help is appreciated.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi! I bought the Hanspree 13.3 and noted that when I bought it one of the reviews said that it came rooted from the factory. Sure enough, I downloaded Root Checker and it says that I have Root. Unfortunately when I went to install Superuser Pro it installed but then says I need to update the binary (and I've done this multiple times on my Android phones or other tablets, it's a hobby what can I say?) it fails to update. I tried getting the binary direct from Sterickson and installing it through Recovery but that failed too. Busybox won't install because it says SU is screwed-up or I don't have root..
I was just hoping to find some ROM that could take advantage of this large screen, out of the box it boots and looks like a tablet for the sight-impaired (no offense) because all it does is display these huge icons and huge text (even after reducing text size to small). From all that I have seen today it looks like nobody is developing for this device. I guess we should be happy that we got 4.2.2 out of the box, at least we're ahead of most others..
Anyone have any ideas???
Chris R.
Ok. I have had the same experience and I found out the "solution" I believe. Did you try superSU? Because I tried to install superuser and it failed also but supersu did not. Try that and let me know.
Sent from my SCH-I605 using XDA Premium 4 mobile app
same wish here
Mine doesn't seem to be rooted. Any fail safe way to check if it is rooted or not? Want to speed this thing up and get the programs off of the RAM. I end up with only 300-400 mb available.
crodgers79 said:
Hi! I bought the Hanspree 13.3 and noted that when I bought it one of the reviews said that it came rooted from the factory. Sure enough, I downloaded Root Checker and it says that I have Root. Unfortunately when I went to install Superuser Pro it installed but then says I need to update the binary (and I've done this multiple times on my Android phones or other tablets, it's a hobby what can I say?) it fails to update. I tried getting the binary direct from Sterickson and installing it through Recovery but that failed too. Busybox won't install because it says SU is screwed-up or I don't have root..
I was just hoping to find some ROM that could take advantage of this large screen, out of the box it boots and looks like a tablet for the sight-impaired (no offense) because all it does is display these huge icons and huge text (even after reducing text size to small). From all that I have seen today it looks like nobody is developing for this device. I guess we should be happy that we got 4.2.2 out of the box, at least we're ahead of most others..
Anyone have any ideas???
Chris R.
Click to expand...
Click to collapse
It has a version of SU in xbin, but that doesn't mean that it is rooted really....
I have tried to get ADB to work, but so far no luck with that. I believe that I could get root to work if I could get ADB to work, but that is just a circular argument.
As to the screen, I use an alternate launcher. Apex in my case. It allows me to set the grid size and scales the icons to fit. Others like other launchers better, but I prefer Apex and purchased the pro version.
All around I like it, even without root. Still, I would like to be able to use GL to SD, Titanium Backup, and the host of other root reliant apps I normally install to get around certain deficiencies.
I'm also trying to root this device.
After a lot of digging, it looks like the su in xbin has different permissions (at least as far as I can tell), when comparing it to the su in my rooted s3. I used root checker pro. The permission of su on my s3 is -rwsr-sr-x root root 113036, while the permission for su on my SN14T71 is -rwsr-sr-x root root 67080.
The funny thing is root checker pro says that root ownership is present and is properly configured. The only thing I can think of is the permission isn't set right.
Now without adb (which I can't seem to get to work either, even though there is a debugging option in the android settings), I don't see a way to change the permissions. Anyone have any ideas?
My usb file transfer doesn't even work on this device. When I try to use usb to transfer files it remounts the internal memory and crashes the tablet, and I have to shut down and reboot to fix it.
I think that they messed up remote usb access period, and that might be why adb doesn't work.
I can use usb file transfer just fine. It only works through the OTG port, not the "regular" port, or whatever you want to call it. In fact, I have no idea what the regular port is even there for, if file transfer only works through OTG. My computer (running ubuntu 12.04) doesn't even detect the tablet using lsusb when connected to the non-OTG (regular) port.
And yet, ADB doesn't work with either port. They definitely did something wrong here, I just can't figure out what.
I can only transfer files via the OTG port and a flash drive. Connecting to a computer, and I have tried windows 7/8/8.1, only causes it to crash. We may only be able to hope that it is fixed in the next update...
Both external usb storage (OTG) and my computer work fine using the OTG port. Still can't figure out what the other port even does right now.
Are they still going to release updates? Hannspree's "news" section hasn't even been updated since 2012.
Ha. Your guess is as good as mine...
It is still my favorite tablet though. The Price/Performance ratio is good, and I love the huge screen even if I have to use the upside down tablet trick for better viewing angles. Mine does have the overheating bug though, which is primarily what causes crashes and wifi failure...
Rooting Hanspree SN14T71
I hope this helps.
I am usually a lurker and don't post but I wanted to pass this info along.
I was able to root my Hanspree SN14T71 by installing Mobogenie.
Install the Mobogenie PC App from mobogenie.com/en-us/download.html
then download the ADB drivers from here mobogenie.com/drivers-download.html
Put tablet into debugging mode.
Connect to pc then run the Mobogenie PC app click on the My Phone Icon in the upper left and from there you should be able to click the OneClick Root icon and root your SN14T71.
I have verified root access and have installed and run apps that require the tablet to be rooted.
Try at your own risk but this did work for me.
Good luck.
I've only had it for a few days actually, so I really haven't had enough time to figure out what all of it's quirks are. I actually got it to hang up on my fridge for the calender, shopping list, recipes, pandora, etc. It's attached using velcro so I can take it off if I need to.
Well I guess I'll work on getting it rooted occasionally when I feel like it, unless someone cracks it before me.
EDIT: I'll try that out wcbellaz. I'll report back if it works.
So I tried the one click root with mobogenie, and while it definitely did something, it didn't give me root access. Using the one click root, it actually moved the su from /system/xbin to /system/bin, but still doesn't give me permission to use su. Setuid attribute is there, and the root ownership is there, so theoretically, I should be able to use su. Then again, I should have been able to with the original su file, which also has setuid and root ownership.
One thing that is strange when comparing it to my rooted galaxy s3 is under the "root user is and group id status" in root checker pro, the contents are different. On the hannspad, it says the su binary isn't found or isn't operating properly. On my GS3, it says the uid and gid are both root.
When I unroot it with the one click root, it removes the su file entirely.
So I know this mobogenie app can in fact get root privileges, as it did mess with the su file. I just wish I knew how it was doing it so I can do it myself.
Masterjuggler said:
So I tried the one click root with mobogenie, and while it definitely did something, it didn't give me root access. Using the one click root, it actually moved the su from /system/xbin to /system/bin, but still doesn't give me permission to use su. Setuid attribute is there, and the root ownership is there, so theoretically, I should be able to use su. Then again, I should have been able to with the original su file, which also has setuid and root ownership.
One thing that is strange when comparing it to my rooted galaxy s3 is under the "root user is and group id status" in root checker pro, the contents are different. On the hannspad, it says the su binary isn't found or isn't operating properly. On my GS3, it says the uid and gid are both root.
When I unroot it with the one click root, it removes the su file entirely.
So I know this mobogenie app can in fact get root privileges, as it did mess with the su file. I just wish I knew how it was doing it so I can do it myself.
Click to expand...
Click to collapse
That is really odd. I just got my Hannspad in the last 3 weeks. When I would run Root Checker it said the device was not rooted. I have heard some say that the device would report as rooted but in fact was not.
If there is anything I can do to help let me know.
I am pretty much a novice at this but I had to root my Hannspad because I did have enough space in memory left for apps, and needed to install Link2SD. In my opinion the only major drawback to this device is the 1GB memory. But for the $226 that this tablet was offered on Amazon was too good a deal to pass up.
Tried Mobogenie, and it seemed to install the correct driver and the driver pack was not needed - I had already started the install on the drivers though...
Sigh...
Got root, it uses a root app that I have never heard of - Kinguser - so I mistakenly installed SuperSU, which then asked me to update the superuser binary...
I am now in the process of restarting to find out if I messed up my root access.
Sigh...
Update:
Apparently I didn't lose root, so I have installed some of my root requiring favorites to see how they work.
The oneclick seems to update the su in xbin, and they put a link to it in bin with full permissions.
I have tried three apps that successfully report gaining su permissions, Root Explorer, Titanium Backup, and GL to SD.
I want to try the move updates to system option in TB, to free up some space, but I am currently too chicken.
Sigh...
Whelp, Titanium Backup works anyway...
Update 2:
I installed SuperSU ( re-installed it actually ) and did the normal binary update. Then I uninstalled Kinguser manually by using Root Explorer to delete its apk in SYSTEM ( superuser ). Then I restarted and deleted all traces of Mobogenie and its daemon as they were slowing down my tablet, and the daemon died hard ( I can imagine that it was tied into all sorts of things ).
I have confirmed that I still have root access, and I just didn't like all that Mobogenie stuff on my tablet.
Happy now
RageAgain said:
Tried Mobogenie, and it seemed to install the correct driver and the driver pack was not needed - I had already started the install on the drivers though...
Sigh...
Got root, it uses a root app that I have never heard of - Kinguser - so I mistakenly installed SuperSU, which then asked me to update the superuser binary...
I am now in the process of restarting to find out if I messed up my root access.
Sigh...
Update:
Apparently I didn't lose root, so I have installed some of my root requiring favorites to see how they work.
The oneclick seems to update the su in xbin, and they put a link to it in bin with full permissions.
I have tried three apps that successfully report gaining su permissions, Root Explorer, Titanium Backup, and GL to SD.
I want to try the move updates to system option in TB, to free up some space, but I am currently too chicken.
Sigh...
Whelp, Titanium Backup works anyway...
Update 2:
I installed SuperSU ( re-installed it actually ) and did the normal binary update. Then I uninstalled Kinguser manually by using Root Explorer to delete its apk in SYSTEM ( superuser ). Then I restarted and deleted all traces of Mobogenie and its daemon as they were slowing down my tablet, and the daemon died hard ( I can imagine that it was tied into all sorts of things ).
I have confirmed that I still have root access, and I just didn't like all that Mobogenie stuff on my tablet.
Happy now
Click to expand...
Click to collapse
Awesome.
You lost me on the binary stuff.
In your opinion should I uninstall the Kinguser as you did and install SuperSu. there seems to be no difference to me in performance after the Mobogenie root. I really don't want anything on this tablet other than the stuff I have to have.
wcbellaz said:
Awesome.
You lost me on the binary stuff.
In your opinion should I uninstall the Kinguser as you did and install SuperSu. there seems to be no difference to me in performance after the Mobogenie root. I really don't want anything on this tablet other than the stuff I have to have.
Click to expand...
Click to collapse
The Kinguser seems to work fine, I just like using what I am used to and I couldn't find much info on Kinguser superuser app ( in english anyway ) so...
It does have a lot more configuration options than SuperSU, which could be a good thing. Your guess is as good as mine...
Hold the phone. Kinguser? I have never heard of this, nor has it been installed on my tablet by the one click root.
I did install SuperSU and tried updating the binary (without success) before trying mobogenie to see if I could get it to work. This wouldn't have screwed me over in any way, would it?
EDIT: Just to be sure, you both are running the latest OTA update, right?
Masterjuggler said:
Hold the phone. Kinguser? I have never heard of this, nor has it been installed on my tablet by the one click root.
I did install SuperSU and tried updating the binary (without success) before trying mobogenie to see if I could get it to work. This wouldn't have screwed me over in any way, would it?
EDIT: Just to be sure, you both are running the latest OTA update, right?
Click to expand...
Click to collapse
Version 1.1.4 dated 11/23/2013
I used a laptop running windows 7, and installed Mobogenie ( I also, perhaps unnecessarily, installed the adb driver pack ). I then connected my tablet and Mobogenie reported a connection - it reported the available memory both internally and on the sd card and it could see my installed applications, after which I used the one click root. The Mobogenie app and daemon were installed along with an updated su and the Kinguser superuser app.
As far as I know trying to install SuperSU previously shouldn't have any effect on the process since I did that too.
Hey guys,
This is the wrong place forum, but I like you guys, so I will ask you a question
Say there is an app that requires root (in this case Cisco AnyConnect rooted version), but I do not want to have root access enabled from within Android OS. Is there a way to install the app with automatic root access? E.g. by flashing it from within the recovery?
Thanks,
Su
Do it need root access or system permissions ?
If it needs root, you must have "su" in android OS.
If it needs system permisssions, you could push it in /system/app/ or /system/priv-app/ (more access than /system/app/)
Hmm, from the description, it seems like root access... ah well, from the CM11 SuperUser settings, seems like it is possible to automatically deny root access to all requests, and only allow selected apps.
Perhaps this is a better way to set up the device...
Sumanji said:
Hmm, from the description, it seems like root access... ah well, from the CM11 SuperUser settings, seems like it is possible to automatically deny root access to all requests, and only allow selected apps.
Perhaps this is a better way to set up the device...
Click to expand...
Click to collapse
every app that wants SU permission should be prompting you the first time to allow or deny it.
if any app gets SU permission without you allowing it, something is wrong.
what i dont understand is, you said the phone is NOT rooted, then mentioned cm11. if you are running cm11, your phone is already rooted.
****EDIT****
Please see http://forum.xda-developers.com/showpost.php?p=56539897&postcount=9 for the Answer
*************
Hi all ,
I'm wanting to use NowTV (like SkyGo) on my OnePlus , however they are using a type of Root check that most root hiders cannot bypass.
Therefore I'm looking for a way to temp unroot and then root back again with ease.
just wondering if there are any tools or easy to follow guides?
thanks
Disable Superuser in SuperSU settings.
zoro25 said:
Hi all ,
I'm wanting to use NowTV (like SkyGo) on my OnePlus , however they are using a type of Root check that most root hiders cannot bypass.
Therefore I'm looking for a way to temp unroot and then root back again with ease.
just wondering if there are any tools or easy to follow guides?
thanks
Click to expand...
Click to collapse
Or if you are on a Cm nightly you can turn them off in the developer option
Disabling super user doesn't work, their detection method is unknown and they check more than the su binary.
I might try the nightlies, however I need stability.
Thanks for the responses so far
Outside of the nightly wing if you want stability use the M releases, they are designed to be more stable than the nightly branch
zoro25 said:
Disabling super user doesn't work, their detection method is unknown and they check more than the su binary.
I might try the nightlies, however I need stability.
Thanks for the responses so far
Click to expand...
Click to collapse
The problem isn't really the SuperSU as such, it's CM. They flag CM as a rooted ROM, it'll even happen if you're on stock un-rooted CM11S.
Transmitted via Bacon
I'm pretty sure that I saw an xposed module that could hide superuser completely. Might want to give that a try
skyguy126 said:
I'm pretty sure that I saw an xposed module that could hide superuser completely. Might want to give that a try
Click to expand...
Click to collapse
As per my post right above yours, it isn't SU that's the problem, it's that the ROM is CM.
Transmitted via Bacon
Timmaaa is correct and that's the info I wanted, I had tried the xposed modules but none worked and now I know why.
I'll contact sky and see if I get anywhere
****EDIT****
So it seems that Timmaaa is NOT correct as there is NO CyanogenMod or any ROM check, it's all to do with the the name of your Root App
Short Version is unroot and uninstall SU app for this to work (removing SU Binary or removing Root alone is not enough)
So we need to have a new Root app with a new AppID and name , and also the SU binary to be identified as something else for this to possibly work.
I now have NOWTV working , and it's on an Unrooted One+One with no SU App installed after running full Unroot (however my SUPro app is still installed)
Note that SUPro does nothing really and just gives extra functionality when the main SU app is installed.
Thanks for everyone help and input on this.
So it seems that you would have to
1)Full UnRoot (Which also uninstalls the main SuperUser app)
2) Watch what ever you wanted to on NowTV or SkyGO
3)Go through the Rooting process again as if it were a new device. (which will again stop NOWTV/SkyGo) from working.
Do steps 1 and 2 again to watch.
This would have to be done everytime you want to watch NowTV
zoro25 said:
Timmaaa is correct and that's the info I wanted, I had tried the xposed modules but none worked and now I know why.
I'll contact sky and see if I get anywhere
****EDIT****
So it seems that Timmaaa is NOT correct as there is NO CyanogenMod or any ROM check, it's all to do with the the name of your Root App
Short Version is unroot and uninstall SU app for this to work (removing SU Binary or removing Root alone is not enough)
So we need to have a new Root app with a new AppID and name , and also the SU binary to be identified as something else for this to possibly work.
I now have NOWTV working , and it's on an Unrooted One+One with no SU App installed after running full Unroot (however my SUPro app is still installed)
Note that SUPro does nothing really and just gives extra functionality when the main SU app is installed.
Thanks for everyone help and input on this.
So it seems that you would have to
1)Full UnRoot (Which also uninstalls the main SuperUser app)
2) Watch what ever you wanted to on NowTV or SkyGO
3)Go through the Rooting process again as if it were a new device. (which will again stop NOWTV/SkyGo) from working.
Do steps 1 and 2 again to watch.
This would have to be done everytime you want to watch NowTV
Click to expand...
Click to collapse
This is just a theory... may be wrong:
Can't you move the SuperSU app into /system/app instead of /data/app. Or does the NOWTV app have perms to check the integrity of /system also. Or can you change the app id of the SuperSU app with a simple decompile tool.
I did that while using cm11s. But still had problems trying to watch skygo. In the end I had alter my buildprop to a phone which supports skygo as at the time it didn't support oneplus one. Then full unroot etc to watch then root back to get root access again.