Related
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 tried searching on the forum for a13 allwinners zeepad 7.0 but can't find anything.
I bought this from amazon,
Android version:
4.0.4
Model number:
A13MID
Kernel Version: 3.0.8
Can someone help me root this tablet?
Anyone? :|
Baoish said:
Anyone? :|
Click to expand...
Click to collapse
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
:good:
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
So, just install su and it will work?
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Yes there is A Solution To This Via A Simple App
meskes said:
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Click to expand...
Click to collapse
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
MikeG_MG56 said:
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
Click to expand...
Click to collapse
Sorry for bringing up an old thread, but I got the a13 and was wondering if anyone was making a cm9/cm10 rom for it as well. I have the a13. I tried to Google and can't find any info about any custom roms for this device.
I used kingRoot version 4.1 Any newer version would not root it.
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.
In our project we "lock down" the device and let only our homescreen app running.
therefore we remove all unnecessary apps, and wondering if we can remove superuser or supersu.apk
of course we need root rights, but we dont need the controlling app
we have tested it on many devices, there are a lot where we could remove supersu.akp and our app kept the root right, but on many other devices we lost the root when we removed it
is there anything we have to handle before we remove it, or how does it work?
thanks,
@oisiss, root is dependent on whether or not there are the su binaries existent in /system/bin (among other things). SuperSU is just a root management app, and its being installed does not affect the root access in the device.
ИΘΘK¡€ said:
@oisiss, root is dependent on whether or not there are the su binaries existent in /system/bin (among other things). SuperSU is just a root management app, and its being installed does not affect the root access in the device.
Click to expand...
Click to collapse
Hello, thank you for your reply, but i have to disagree:
1., to check whether the device is rooted or not is not as simple to check if the su binary exists in the /system/bin folder. even if that exists it can happen that our app (and of course many others: rootchecker, es file explorer...) doesnt get admin rights
2., if it would be so simple the root checker app in the google play wouldnt have 10M-50M downloads
3., in our app we also check if the device is rooted, for that we check 5-6 methods: if the su exists, remounting rw the system foder, run su command, create and delete file in a secured folder...
4., many threads talking about how to replace supersu with superuser. all is telling to install superuser first and only after remove the original supersu, so they never mention to remove supersu firts
we have in our lab aprx 60 devices, made many tests, and this is my question:
1., when there is a properly rooted rom, checked by rootchecker.apk
2., we delete supersu.apk from the system/bin and restart the device
3., we check with rootchecker.akk again and says unrooted
so is there any hidden settings somewhere where for example there are default setting for granting or denying root request? or why do we loose the admin righs
I think there is an aswer:
if the original root was not complete (http://su.chainfire.eu/), it can cause issues
the Install-recovery.sh has to be corrected before deleting the supersu.apk (su, daemonsu...)
can someone confirm this?
oisiss said:
Hello, thank you for your reply, but i have to disagree:
1., to check whether the device is rooted or not is not as simple to check if the su binary exists in the /system/bin folder. even if that exists it can happen that our app (and of course many others: rootchecker, es file explorer...) doesnt get admin rights
2., if it would be so simple the root checker app in the google play wouldnt have 10M-50M downloads
3., in our app we also check if the device is rooted, for that we check 5-6 methods: if the su exists, remounting rw the system foder, run su command, create and delete file in a secured folder...
4., many threads talking about how to replace supersu with superuser. all is telling to install superuser first and only after remove the original supersu, so they never mention to remove supersu firts
we have in our lab aprx 60 devices, made many tests, and this is my question:
1., when there is a properly rooted rom, checked by rootchecker.apk
2., we delete supersu.apk from the system/bin and restart the device
3., we check with rootchecker.akk again and says unrooted
so is there any hidden settings somewhere where for example there are default setting for granting or denying root request? or why do we loose the admin righs
Click to expand...
Click to collapse
Please notice how I phrased it like this:
NOOKIE said:
...root is dependent on whether or not there are the su binaries existent in /system/bin (among other things).
Click to expand...
Click to collapse
I am fully aware that root is not as simple as su being in /system/bin. :silly:
oisiss said:
I think there is an aswer:
if the original root was not complete (http://su.chainfire.eu/), it can cause issues
the Install-recovery.sh has to be corrected before deleting the supersu.apk (su, daemonsu...)
can someone confirm this?
Click to expand...
Click to collapse
Yes, this sounds right. :good: