Hi All,
I have screwed up my android which was perfectly fine with a perfect root. Please help me to restore the root access !!!
Here is my problem description:
I have a Sony Xperia Miro which was perfectly rooted.
Model : ST23i
Android : 4.0.4 ICS
Build : 11.0.A.5.5
The root verification using app 'root checker basic' was successful.
Now I had few of my company apps and bank apps which wouldn't work in rooted device. But I never wished to lose my root status. So I was searching for the ways to hide root access from these apps. I even came across apps exclusively built for this purpose (hidemyroot/OTA root keeper) But due to some bad comments about these apps, I decided to try manually
The idea was to fool the apps when checking the root access.
At first I renamed the super user apps at the location /system/apps. to some invalid file(super.txt)
This did the trick for couple of apps which weren't working before in my mobile. However couple of apps were still failing.
The next thing I did was renaming .su to ku in the below location /system/bin/.ext
Then I verified Root Checker Status, still it displayed "u have root access"
Then I went to /system/xbin and renamed the following.
.su to ku
.busybox to busyboxk
.dexdump to dexdumpk
Then I tried Root Checker Basic again. And got the message "device don't have proper root"
But still my apps were not working. Then I did the most foolish thing which was restarting the device.
BAM.. !!!! I lost my root access permanently. Now I don't have superuser app. And I m not able to use 'Root explorer', to rename back the files to its original state.!!! And most ironic thing is my company app still saying I have root access. I tried after deleting its cache and data. The result was same !!
How can I restore my root access ? Please help
one update
Since I renamed the superuser and superSu applications, I couldn't use them.
Today I installed both of them using package installer.
But they doesn't seem to work as they can't find su binary installed
See the attached
appviz said:
See the attached
Click to expand...
Click to collapse
Do you have a Custom Recovery setup and if so did you make a backup after root?.
keifus.rahn said:
Do you have a Custom Recovery setup and if so did you make a backup after root?.
Click to expand...
Click to collapse
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
appviz said:
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
Click to expand...
Click to collapse
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your device. The same thing happend to me awhile back :/ If you want to save your apps use titanium back up or app backup & restore and add a custom recovery like cwmr so if this happens agen you wont have to reroot. if you are still having problems with your apps for work boot your phone into recovery and go to advanced then fix permisions if you have any other questions or any problems just let me know.
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
keifus.rahn said:
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
Click to expand...
Click to collapse
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
appviz said:
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
Click to expand...
Click to collapse
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
keifus.rahn said:
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
Click to expand...
Click to collapse
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
appviz said:
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
Click to expand...
Click to collapse
That's Awesome :highfive: I'm glad the hear that you got everything working correctly and with your company apps too. :victory:
Thank you for sharing with me and everyone. You never know if some one out there is having the same problem and this could really help them out one day.
Related
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.
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does 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, Ok so i updated my Huawei u8650 to android 4.4.2 and something went wrong with my root. I can open superuser and it shows my binary and all that and it says im rooted but when i go to a app that requires root access like terminal emulator for example and i type in the command su. nothing happens it just goes to the next line. and i tried to mount my SD card partition in link2sd and it said that the script cant be created because its not allowed to su.
I thought it could be that superuser just wasn't allowing permissions but i open superuser and theres no apps, no logs or anything. I checked my settings and they're all fine and i even tried to use SuperSU instead and i still got the same thing. There's no prompt to allow access either. I dont know if the apps are just not trying to get root access or what? No app can get root permission and i need to get this fixed so i can fix some bugs on the rom. Please Help.
Thanks to all who attempt or do help. Ill be sure to hit thanks for u.
Please Help!!!
brewsterj98 said:
Hey, Ok so i updated my Huawei u8650 to android 4.4.2 and something went wrong with my root. I can open superuser and it shows my binary and all that and it says im rooted but when i go to a app that requires root access like terminal emulator for example and i type in the command su. nothing happens it just goes to the next line. and i tried to mount my SD card partition in link2sd and it said that the script cant be created because its not allowed to su.
I thought it could be that superuser just wasn't allowing permissions but i open superuser and theres no apps, no logs or anything. I checked my settings and they're all fine and i even tried to use SuperSU instead and i still got the same thing. There's no prompt to allow access either. I dont know if the apps are just not trying to get root access or what? No app can get root permission and i need to get this fixed so i can fix some bugs on the rom. Please Help.
Thanks to all who attempt or do help. Ill be sure to hit thanks for u.
Click to expand...
Click to collapse
I really need help to figure this out. Someone please help ie been trying to fix this problem for 2 days now and have gotten no where.
Hello everyone!
I would like to ask you something and i REALLY HOPE someone will be able to help me out.
I have a samsung s5 sm-g900f with Android 6.0.1 and i'm trying to root it.
Actually it was supposed to be rooted when i got it -it's my bf's phone. And...aaam i don't know if it's called "rooted" when it just have custom recovery and rom? I just call it that way-. Yesterday i installed root checker and Super SU and the Super SU keeps saying that "There is no SU binary installed and SuperSU cannot install it" and that if i have Android 5 i should re root manually and stuff.
I have tried like everything i have found on the net since yesterday, flashing with Odin, changing recovery from twrp to cwm, and all the time the steps are made by letter, all seems fine, i see the red pirate android after the recovery reboot and all that, have tried to install the UPDATE-zip and the BETA-zip and all i could find. I tried to install Kingroot but i couldn't figure out how. My recovery nor Odin can see the file to install it and then i try to do it manually, like all apps, it says could not be installed. :crying:
I got really tired and i cave in to ask for help here. I hope the post is in the right place and if it's not please move it where it should be!
Thank you in advance!
CloeNi said:
Hello everyone!
I would like to ask you something and i REALLY HOPE someone will be able to help me out.
I have a samsung s5 sm-g900f with Android 6.0.1 and i'm trying to root it.
Actually it was supposed to be rooted when i got it -it's my bf's phone. And...aaam i don't know if it's called "rooted" when it just have custom recovery and rom? I just call it that way-. Yesterday i installed root checker and Super SU and the Super SU keeps saying that "There is no SU binary installed and SuperSU cannot install it" and that if i have Android 5 i should re root manually and stuff.
I have tried like everything i have found on the net since yesterday, flashing with Odin, changing recovery from twrp to cwm, and all the time the steps are made by letter, all seems fine, i see the red pirate android after the recovery reboot and all that, have tried to install the UPDATE-zip and the BETA-zip and all i could find. I tried to install Kingroot but i couldn't figure out how. My recovery nor Odin can see the file to install it and then i try to do it manually, like all apps, it says could not be installed. :crying:
I got really tired and i cave in to ask for help here. I hope the post is in the right place and if it's not please move it where it should be! Thank you in advance!
Click to expand...
Click to collapse
Since you can flash custom recovery then your bootloader is already unlocked so....
Do a search for "flashing SuperSU.zip Galaxy S5" or you might need to search for "flashing SuperSU.zip in systemless mode galaxy s5". Flashing one of those should give you root and su binaries, after flashing, boot the device and open the SuperSU app and update the su binaries then reboot the device. Then after rebooting, you need to go to system settings>developer options>root access and set it to "apps and adb", then install a file manager that has a root explorer such as ES File Explorer, then open it, tap the menu button, go to the "TOOLS" tab, find "Root Explorer" and turn it on, then when you see the next menu, tap "Mount R/W", then set all listed partitions to "rw".
If you can access your SELinux profile, make sure it's set to "permissive" mode.
If you can get all of that set then you'll have access to modify and control pretty much anything you want about the device.
I DO NOT PROVIDE HELP IN PERSONAL MESSAGE, I DO NOT TAKE REQUESTS IN PERSONAL MESSAGE, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
thank you!!!
i wont be able to try it for a few days but i'll try it as soon as i can and give you feedback on this!
So i'm trying to follow your instructions right now. I guess it's ok if i install recovery upon recovery and SU upon SU without first removing the "faulty" one?
Cause i have done the first steps a lot these days
edit: i flashed again aaaaaand nothing new happened. The SU binary is nowhere to be found :/
some say it could be a problem of the cable or the computer?
Should i try from a different pc and cable? I do not really understand it but i'll give it a try later
edit 2: i retried from another pc and another usb cable, the same happens. Does not install the SU through the recovery
I installed the SuperSU (actually enebled it again and updated it) from playstore and opened it and it says the sme thing again. Can't find su binaries and stuff.
What should i do? Is format a solution or can avoid it?