Since updating SuperSU, it started requesting permission to "mksh (1000)". I deny it everytime it shows. It seems to have something to do with wifi. Everytime it connects to wifi that's when it pops up.
The file mksh is in \system\bin
Any idea what mksh is?
canpitt27 said:
Since updating SuperSU, it started requesting permission to "mksh (1000)". I deny it everytime it shows. It seems to have something to do with wifi. Everytime it connects to wifi that's when it pops up.
The file mksh is in \system\bin
Any idea what mksh is?
Click to expand...
Click to collapse
Other people seem to be having the same problem. All I can tell you is that the file exists for me, non-rooted, in '/system/bin/'. It might have something to do with shell/command line.
This is also being discussed at length in the SuperSU thread.
canpitt27 said:
Since updating SuperSU, it started requesting permission to "mksh (1000)". I deny it everytime it shows. It seems to have something to do with wifi. Everytime it connects to wifi that's when it pops up.
The file mksh is in \system\bin
Any idea what mksh is?
Click to expand...
Click to collapse
I took a look in my superSU app and it seems at some point I gave the mksh permissions lol, I don't remember it popping it, so I deleted it and am waiting for it to pop up again. No idea what the hell it is
andybones said:
I took a look in my superSU app and it seems at some point I gave the mksh permissions lol, I don't remember it popping it, so I deleted it and am waiting for it to pop up again. No idea what the hell it is
Click to expand...
Click to collapse
It happens for me when I'm connected to wifi and I either reboot or just turn wifi off and back on and let it reconnect. Happens everytime.
yeah, this just popped up for me as well on my evo lte, along with jackpal.androidterm, which google tells me is terminal emulator. so I'm guessing something got borked in the supersu update.
maybe, the dev may have done this on purpose to allow for my control over the device.
or it's a issue with the newest SuperSU update
Well I finally gave up on the latest Supersu (.97). Two things started happening after updating:
1. At home I use wifi. When I would leave the house the statusbar still showed I was connected to wifi. Even 20 miles away. (It was connected to mobile, just showed wifi)
2. After rebooting, the phone would not see the ext sdcard. Rebooting again would usually fix it. This didn't happen on every reboot, maybe half of the time.
The new update started asking for permission to mksh. I tried both granting and denying and it didnt seem to make a difference either way.
These did not happen before updating supersu, and after reverting back to version .96 these problems went away. I don't know what else to blame.
canpitt27 said:
Well I finally gave up on the latest Supersu (.97). Two things started happening after updating:
1. At home I use wifi. When I would leave the house the statusbar still showed I was connected to wifi. Even 20 miles away. (It was connected to mobile, just showed wifi)
2. After rebooting, the phone would not see the ext sdcard. Rebooting again would usually fix it. This didn't happen on every reboot, maybe half of the time.
The new update started asking for permission to mksh. I tried both granting and denying and it didnt seem to make a difference either way.
These did not happen before updating supersu, and after reverting back to version .96 these problems went away. I don't know what else to blame.
Click to expand...
Click to collapse
weird, I have it denied, and hasn't been a problem since.
andybones said:
weird, I have it denied, and hasn't been a problem since.
Click to expand...
Click to collapse
I'm gonna give it another shot today and deny it right from the start.
Anyone ever figure out what this is, idenied it, might be something to do with global??
Looks like it's the latest update from SU
Chainfire still suggests deny at this point.
http://forum.xda-developers.com/showthread.php?p=33550523
viperLTE 2.0.0 uses its own VenomSuperUser app, so no issues
Go to SuperSU , long press on mksh and on Notifications turn off. Is the and of Popup...
ninfaboy said:
Go to SuperSU , long press on mksh and on Notifications turn off. Is the and of Popup...
Click to expand...
Click to collapse
Didn't know you could do that, glad its now not nagging me
Thanks
mksh is the predecessor of pdksh/ksh. i think pdksh stands for public domain korn shell, and is pretty much used for migration to mksh. all are from the at&t ksh.
is it a symbolic link? wonder what the source looks like, is it possible to post it or its rc file?
Here i
Here i go Necormancing, but this is something every single android user should know:
MKSH is the default "posix compliant shell" of android as of jellybean, its part of the internal operating system.
Dont **** with it. Leave it alone. Give it all the permissions it needs
https://www.mirbsd.org/mksh.htm
In android, SH does in fact symbolically link to mksh. Ie, when you type sh in android, its really bringing up mksh
more on mksh and root
I’ve just summarised this in http://forum.xda-developers.com/showthread.php?p=52526690#post52526690 too.
mksh is used as system shell in Android, and just the “messenger” for another programm running a command as root.
---------- Post added at 12:19 PM ---------- Previous post was at 11:46 AM ----------
Sure, current summary here.
Related
I have been talking this over with Condemned Soul but wanted to see if anyone else has ran into this problem since he & I are both confused.
My fiances phone has been force closing a lot lately aka com.android phone not responding. I saw the first force close when I tried flashing Tazzs cm7 on his phone so thats when I first put on gsb 1.2
I switched his over to Sheds GSB on the 8th and it was great everything was fine but then I decided to try to improve on a few settings and when I restarted the phone it decided to start force closing.
I reflashed the rom and the gapps and everything seemed fine but then I wanted to put cs skull theme on his phpne since we had it on Kaos v9 but then when I restarted the phone after flashing the theme it force closed again.
So then I reflashed the rom and gapps again and got all his apps and settings all back how he had it and decided to do a Nandbackup so that we wouldnt have to keep reflashing the rom again and once I restarted the phone after the nandbackup it force closed again.
Long story short I reflashed the rom and gapps and now am in the process of getting his apps and settings back how he had it once again.
Am I doing something wrong to make it keep force closing? I would like to make a nandbackup at least for him so that we wont have to keep setting up his phone.
Thank you for any help
When you say you flash the ROMs, do you also do a wipe beforehand? If not, try doing a wipe and then install and see if that changes anything.
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
labnjab said:
Yes I wiped both the factory and dalvk sorry I thought I mentioned that. lol.
Click to expand...
Click to collapse
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
zerocool79346 said:
Its a problem that happens on certain ROMs with certain themes. Not sure there's a fix for it, I just got around it by not applying the phone.apk theme.
Click to expand...
Click to collapse
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
CondemnedSoul said:
phone.apk wasn't changed in the theme. Strange part is it's only on the one phone and haven't heard of it on any of the others.
Click to expand...
Click to collapse
That is odd.
Update:
This is still causing issues. Going to try and format the sd like tazz suggested, but moving my phone.apk to his didnt work, and yesterday he had to restart his phone and it did it again and needlessto say hes not very happy with his phone. Says its not reliable at all. If anyone else has anything else I can try it would be a big help. I have tried searching on google but dont find a whole lot of information. I just wish I could figure this out its got to be something I did or something stupid that I am missing.
There are a couple of next steps you can take.
If the problem is a software configuration issue, then it is possible that you will see the reason for the FC in the logcat.
The system logcat is designed as a "circular buffer" (in a way that it has a maximum size) - once you fill it to capacity, each new record which is added to the end causes information at the beginning to be lost. But, this also means that if a FC occurs, so long as you "dump the logcat" within a reasonable period of time after the FC happens, you will capture the moment in time that the FC occurred,
Generally, the "logcat" buffers get filled to capacity quite quickly at boot time (because there is lots and lots of "android" app activity), and quite a bit slower after the phone has been completely booted. If you are trying to capture a logcat event during the first boot, you need to continuously capture output to a file on your PC (it will be quite large) - but once the phone has completed booting, so long as you "run a logcat" within 5 or 10 minutes after a FC occurs, the relevant event(s) will be in the logcat.
If you want to capture it during the first boot cycle of a freshly flashed ROM, probably you ought to have a PC attached and dump the prodigious output to a file on the PC, as in
Code:
C:\MyWindozePC> adb shell logcat -v time > LogcatFileOnMyPC.txt
So long as the ROM you have flashed has "USB debugging" turned on by default, you can run the above command about 10-15 seconds after you see the 3 skating droids, and it will continuously place output into the local file on your PC. You need to interrupt the above command (Control-C) to get it to stop; you would usually do that a few seconds after you saw the FC, and then you would know that the log entries you are looking for at the end of the file.
(Note that logcat dumps are usually huge - don't bother trying to look at them with a text file viewer on the phone - they suck at handling large files... well, at least the ones that I have tried).
You could also instrument this on the BF's phone in a way where he can capture the info to the SD card anytime he is using the phone during the day with a couple taps of the screen, and then you could look at the logcat(s) later at your leisure - for instance by using Gscript Lite, and a simple script like this:
Code:
#! /system/bin/sh
_LOGDIR='/sdcard/logcats'
if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi
_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt
With this method, you just need to train him like a monkey to press the right keys after a FC occurs. If he's a clever monkey, you could even train him to send the logcat files to you via e-mail.
If the problem is due to an intermittent hardware issue with the phone, that will be tougher to identify. About the best you can do to make that determination is to return the phone software to stock and use the phone without installing any apps for a reasonable period of time and see if the problem continues to occur.
cheers
bftb0
Thank you for the detailed reply bfbt0 I was about to msg you when you responded.
I will have to give what you mentioned a try.
Is the gscript lite what I use for the adb shells or do I need another app as well. I have never done anything with adb or if I have it was something simple.
To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.
Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
labnjab said:
Update ~ Never mind I found you had to have android sdk on your pc Im downloading that now. I still may need help tho.
Click to expand...
Click to collapse
GScript Lite is a free app on the market. It was put together by XDA member "rogro", and he has a paid version as well if you want to throw a couple bucks his way.
Using the script above with Gscript (Lite or Pro), you don't need to be tethered to a computer nor set up the SDK and drivers. (Only when you want to capture a full first ROM boot do you need to use a PC (because the logfile grows so big in that specific case).
If you can force the FC to occur, then using the Gscript Lite script I showed above will capture the information you want.
bftb0
PS There is a brief outline of how you load a script into Gscript Lite in that "Universal Root for Dummies" thread over on AF.
cheers
Thank you I will try that tonight and hopefully can figure out what the issue is
labnjab said:
To clarify I would have to get his phone to fc again which is easy to do and then run a logcat. It sounds easy through the pc I just want to make sure I do it right. I would make a folder dedicated to where the logcats would be stored and then run it in the gscript lite? Meaning run the first code you posted.
Click to expand...
Click to collapse
That code I posted checks to see if a folder exists, and if not creates it - /sdcard/logcats
No need for you to do it manually; the first time the script runs it creates that folder
But, yeah - wait for the FC to happen and then run that script within the next couple of minutes (no real hurry). It is also useful to make note of the time the phone displays when the FC occurs - it will be easier to find things in the logcat file by timestamp if you do that.
bftb0
Thank you I will do that as well. Thanks also for taking the time to help me.
I did the code on my phone to make sure I did it right and it gave me an error
says cannot create/logcat_20110222-1558.txt read only file system
did I do something wrong, just want to make sure that I can get it right before attempting it on his phone tonight. Thanks in advance.
labnjab said:
I did the code on my phone to make sure I did it right and it gave me an error
says cannot create/logcat_20110222-1558.txt read only file system
did I do something wrong, just want to make sure that I can get it right before attempting it on his phone tonight. Thanks in advance.
Click to expand...
Click to collapse
If you typed that script in by hand, you made a typo.
I checked it by cutting and pasting it - and then I tested it afterward, and it worked.
Probably you bolluxed up the _LOGDIR variable, or you inserted a space in the logcat command where there should not be one.
I would suggest that you cut and paste, rather than type.
Hmmmm... it occurs to me that those little "scrolling CODE text boxes" don't render correctly on the phones browser. Here's the same script, but without enclosing it in [ CODE ] [ /CODE ] tags:
#! /system/bin/sh
_LOGDIR='/sdcard/logcats'
if [ ! -d ${_LOGDIR} ]; then
mkdir ${_LOGDIR}
fi
_tstamp=`date +%Y%m%d-%H%M`
logcat -v time -d > ${_LOGDIR}/logcat_${_tstamp}.txt
Thank you for all your help. I got it to work and come to find out I didnt even need to use that program because it hasnt forced closed yet. He said he wiped the phone a bunch of times the other day when he was trying to get it back up and running when it forced closed on him while at work and now i rebooted it and backed it up and that usually caused a problem, so far so good.
I am tho going to format the sd card and redo the rom again just to be sure this problem doesnt happen again. Thank you again for all the help.
On some builds (even though it shouldn't be required) it is necessary to wipe multiple times. On Tazz's earlier builds of GB, people reported having to wipe 3x or more to get it running smooth. Always make sure you do a nand backup before flashing in the future lol. Hopefully the phone stays running good! If not, people are always here to help!
Sent from my Ginger Tazz using XDA App
First, props to TeamWin, joel.bourquard, theintelligent, and maybe a few others I'm not aware of...
Second, these are Windows instructions. If you have another OS, you can open the batch files and type the commands inside (or paste them) one by one.
Third, keep in mind that the current temp root is NOT a full root even WHEN it is in place... so don't expect too much! This method has also been modified (by others) so that it does not "randomly" reset and it sticks until the next restart. As a result of how that works, however, even fewer apps recognize root with this method but some do!
Most of this is just other people's work: stuff from several different posts repackaged in a way that I found very easy to use. So I don't take credit for most of the contents, although I did modify the batch files to take care of a timing issue that was causing a fail on most machines. In the end, you should be able to use the attached prepare.bat file to prepare your phone once and then you can use root.bat after each reboot to restore temp root. Create a shortcut to root.bat on your desktop and you can just plug your phone in, click the icon, and you're (re)rooted in about 8 seconds.
The instructions are simple but I elaborate below to try to hit all the stumbling blocks. Basically you just run prepare.bat the first time you do this and from that point forward, you only need to run root.bat after every restart.
Here are the specific instructions:
THE FIRST TIME ONLY:
(1) Unzip contents of the attached ZIP to a folder you'll remember on your hard drive.
(2) Plug your phone in via USB and set it to "charge only" with "USB debugging" under "Settings", "Applications", "Development" turned on. It's best to do this after a fresh (full, not fast) boot. Your phone should be in this mode each time you connect it to root it. Trust me, if you've been using your phone for a while, reboot it first, then wait a few minutes for it to stabilize, THEN do this routine... saves a lot of headaches.
(3) Go to the folder where you unzipped the files in (1) and run prepare.bat. I prefer to do it in a DOS box but you should be able to just use Explorer and double click on the prepare.bat file.
(4) The first thing these batch files do is a check to make sure your computer can see the phone. If your phone isn't in the list, Ctrl-C and break out of the batch file. You'll have to correct the problem which will most likely be an issue with the HTC drivers. If your phone is not found, try these x64 drivers... or these if you're running a 32 bit OS. To install these, go to Control Panel and click on your Android device and do "Update Drivers" and browse to the location of the drivers you downloaded.
(5) Assuming your phone is on the list, everything should be ready to go. Press enter and the batch file will proceed and it will root your phone.
AFTER DOING THE ABOVE ONCE, AFTER EACH REBOOT:
(1) Attach phone and double click the root.bat file.
(2) Again, verify that your phone is on the list (proves your PC can see the phone). If so, press enter and the phone will be RErooted.
That's it! Works for me. Keep in mind that temp root is NOT a full root! Many apps will not run (won't see root) but that's just the nature of the current temp root. But some apps do work. Barnacle WiFi does for example: although sometimes it take two "start" presses to get it to connect as the first one sometimes produces errors. People say Titanium Backup and some other apps work: I haven't personally tested them. As temp root is really for dev and testing, test what you want and see if it works.
Hope this helps some of us to get a quick and easy temp root. If any issues are found, I'd be glad to modify this initial post and/or modify the batch files if any errors are found.
Mike
I can't get to the site to download the 64-bit drivers for windows. Anybody has an alternate links? Thanks.
Does this really work? How is this thread not blowing up??
vWvSTATICvWv said:
Does this really work? How is this thread not blowing up??
Click to expand...
Click to collapse
Really! Anyone out there? I expected to come back from lunch to find questions I needed to answer or maybe a suggested modification or two. This has been working for me for over 12 hours now. No restarts. No reverting to non-root. Barnacle Wifi Tether is still working. And the best thing is, if I have to restart the phone for some reason, I connect it to my computer, click, and 8 seconds later it is rooted again and I unplug it and go on my way.
Mike
can you run a wireless tethering app after temp root?
edit: see mikeyxda's post above this
I was hoping to be able to help some people with the Barnacle WiFi Tether app because a lot of people complain that they didn't get it to work and I suspect I got it to work with some combination of settings. Only problem is: I don't know how my Barnacle settings differ from those other people are using so I wanted to compare with others. Short on time right now but later I'll try to post my entire list of Barnacle settings. They work for me.
Edit: Oh Hell... I have a few minutes, here are my settings:
SSID: Evo 3D Tether
BSSID: <blank>
Wireless Encryption: not enabled (open)
Channel: mine is 6, probably doesn't matter
Custom Wifi Ad-hoc: none
Skip wpa_supplicant: NOT checked
Auto Associate: NOT checked
Access Control: NOT checked
New Client Actions: Notify Checked, nothing else checked
Local Mode: NOT checked
DHCP: Didn't mess with these
NAT: Didn't mess with that either
WAN: rmnet0 (whatever that means)
LAN: Blank
Mike
it seems like the link for the 32bit drivers is down also....
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
os10 said:
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
Click to expand...
Click to collapse
Try making sure fast boot is turned off and then power the phone down and power it back up. Then use the root.bat to reroot. Might not work the first time.
For those having trouble with the driver links, try this link. It's kind of a convoluted mess with countdowns, etc. but seems like the files are there. I haven't verified them yet though.
Mike
Gave it a shot, doesn't quite seem to be working for me.
johnsmusicbox said:
Gave it a shot, doesn't quite seem to be working for me.
Click to expand...
Click to collapse
What is it that isn't working: the rooting process itself or Barnacle? I was hoping to give enough feedback in this thread to get things working for the people who say "it doesn't work" because I've been watching other threads and most of these methods seem to be very inconsistent, meaning, they don't work for a lot of people. My intention was to find the kinks and get it working for the vast majority. If you can give me details like what you see during the process, whether any error messages display, and so on, we might be able to get a more reliable temp root.
Mike
Titanium backup is definitely not working with this.
So what's going on with this? Anyone got it to work?
OK, let's try this. This is a "cleaned up" version of a different method posted in another thread. Comes with 2 batch files. Run root-init the first time and then root-redo each time you restart after that. Let's see if this works better.
Mike
Ok...My guess is that people are scared and don't know exactly what they're flashing. Would you mind sharing the source of your find, Mike? If this does indeed work, I can't see people not using this method. HmMm
*EDIT* I found the source is from XHAUSX
*EDIT 2* IT WORKS!!
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
superdx said:
Every time I try to use it, it always renames the access point back to "Android AP" and wipes the password as well - anyone come across a fix?
I'm running the official 2.3.5 firmware.
Click to expand...
Click to collapse
I am not quite sure what your problem is.
Do you mean tethering?
And your phone does not keep the AP name and password for its own WLAN hotspot?
I am sure that there are some tethering apps on the Market.
Maybe one of them can help you to configure a customized AP name and password and saves it for later use.
Yep that's it exactly, tethering. The AP name and password keep resetting!
http://forum.xda-developers.com/showpost.php?p=18711488&postcount=128
clefster said:
This is because the permissions for the wifi settings got messed up so it can't write out your new permissions. The error handling isn't too good so it doesn't tell you about it
To fix, in a rooted terminal run this command:
chmod 770 /data/misc/wifi
Click to expand...
Click to collapse
After struggling with root, I tried your command and it doesn't work, says Operation not permitted
It looks like we have to move our discussion here, so I went ahead and started a thread.
As of now, there is root for the mediapad, but the only way to root the springboard is by flashing it with a rooted mediapad cust.img - which gives you root but loses your 4g.
So for us Springboard users, we either need root or a way to get 4g back if flashing it as a mediapad. Anybody with thoughts or leads or any know-how?
Finally,
Special room for Huawei Media Pad created,
Thanks to TS
I'm very glad,
Now i'm waiting the master in here to modified this device
cause i still newbie
Actually I Prefer The 3G More THan The 4G For Some Reason I Felt 4G Wasnt Stable Enough....So Im Enjoiying My Mediapad In 3G More Than My Springboard In 4G......
from the other thread, Rumbi wrote:
Yap, only thing you have to do is install Superuser and Busybox from Market and copy "su" from /hwcust/oversea_hk/preload/fixed/bin/ to /system/xbin (e.g. with ES File Explorer with root and r/w enabled), and you are ready to go
I've installed SU & BusyBox. I cannot move the SU file over to /system/xbin. A message tells me that I am not root.
However, when I run Root Check Basic I am told I have root.
I ran Root Check before & after I installed S7-301u V100R001C232B012(Root_version) and Root Check said I did not have root.
So the real question is, How do I really know if I have root?
*****
Actually I installed BusyBox Installer. I'm asked to pick a version to install:
1.19.3
1.19.2
1.18.5
1.18.4
1.17.1
None of these will install.
I also have the option to install a "Custom Tune" is there one? I'd gladly pay for BusyBox pro to get BusyBox running
*******
I powered off the device. Put my sdCard back in (the rooted firmware was removed from it). Then installed the SuperUser update from the market.
Ran that - it said everything was OK. Then I forced it to update - it crashed - so I force closed it. I then realized I could not run the original SuperUser app anymore.
Next, I opened up Root Explorer and was able to move the su file over to the xbin. But now BusyBox is not acting right - It said that it was having problems installing, and I'd need to reflash (or reload - I can't recall) the rom.
I'm rebooting, and going to try to install BusyBox....to be clear on which BusyBox..it's this one:
https://market.android.com/details?...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
*****
Just realized in Root Explorer, to tap the little gray box at the top. After you tap it it should read "Mount R/O"
Now you can long press a folder/file and change the read/write permission.
Rumbi,
You said to r/w enabled the su file....is that check ALL the boxes?...Read, Write, Execute Special?????
IIRC, i had some problems with busybox, too. Copy the file from the attachment to /system/xbin and try the installer again.
And i said to enable r/w support for the /system folder. There are two checkboxes in ES File Explorer. First checkbox is enable root permission for ES File Explorer and second checkbox is "Mount / and /system writable".
Now you should be able to copy whatever file you want to /system/xbin. That's how i have done it. If you have any further questions, feel free to ask. I'll try to explain.
PS. You don't ne to alter file permissions of the su-binary but mine are "rwx r-x r-x".
Rumbi, how do you feel about the High resloution mode, does it slow the tablet down? Have you had a chance to use any tegra 2 devices and if so how does the mediapad with the snapdragon compare when in standerd/high-res mode?
Nothing to complain about the Hi-Res-Mode but i don't have any Tegra2-Devices to compare, sorry.
Haven't tried any games in hi-res-mode but normal usage is just fine.
Thanks. Ill try this out. When i try to install busybox it hangs first, then i force close and run again. Then i get the message about reflashing Rom. But i know i have root. I installed connectbot and ran su and got #
Heres how i got root (im away from my pc right now so i try to be as accurate as possible) :
Installed Hauwei modified rom (its the one that says "(root) " in the file name.
Installed Root explorer
Installed Superuser
Install busybox
Install Connectbot
Put my microsd back in (with the firmware AKA dloa folder removed)
I could not get root explorer to allow rw permissions until i slid the sd card out and back in whil the device was on.
Then i ran connectbot as local and typed su hit enter then superuser popped up asking fo allow connectbot to access. Hit allow an type su hit enter an you should get # This took 3 reinstalls of the firmware to work wjthout errors. The first times resulted in superuser needing to be force closed.
I also ran superuser and went into settings and updated it eventhouh its not neede. There i got a read out saying that busybox is not installed, but it does say i have root.
Sent from my HUAWEI MediaPad using xda premium
Honestly i havent noticed a big difference between high resolution an standard.
The only issue with high res is the small icons and buttons are difficult to hit sometimes
Sent from my HUAWEI MediaPad using xda premium
Do i need to unzip this file first?....
.... Nevermind... I unzipped it and put the busybox file in th system/xbin folder.
I installed busybox installer by JRummy16. This time and it worked!!!!!!!
Now its on to figuring out 4G and tryiying to use it as a phone.
What is the xml file i need to edit?
Sent from my HUAWEI MediaPad using xda premium
Good, that you have worked it out now What exactly do you want to do? To get to the hidden menu, you have to open the calculator and type: ()()2846579()()=
To edit the XML-Files, you have to extract the cust.img... But now that you have root, yo can edit whatever is available via root explorer
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
after updating my mediapad to S301uV100R001C232B012, i have problem with 2x Client (RDP client) now, few second after conecting to rdp session, is app 2X client crashing, with error 2x Client has stopped unexpectedly (process com.tux.client), is here anybody with this problem? thanks...
Rumbi said:
€dit: To get 4G working again, maybe with someone with an original Springboard (not a flashed one) can copy the folder /system/lib/. This should be possible even without root. I think it has something to do with the ril-files...
Click to expand...
Click to collapse
How about this - link
I'll look at it, thank you And these are the libs from an unmodified Springboard, aren't they?
yes indeed. I broke the silly thing, so I haven't played with it much. guess I will have to call about how to get it fixed.
knoxjon said:
How about this - link
Click to expand...
Click to collapse
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
The *.so files are a bit like drivers for the internal components. I'll try to find differences between T-Mobile and Huawei so maybe we get 4G working again.
tedbone said:
Even though I have no clue of what to do with this, THANKS! I tried to open an .so file in notepad, but no luck, but I'm assuming that the geniuses here know what to do.
On an off-root topic - How do you take a screen cap? I accidentally did it yesterday while my MediaPad was lagging, but don't know how I did it.
The Hi Suite that comes with the device can do this, but require a computer and usb hooked up. Useful, but not as practical as doing it from the tablet itself.
Click to expand...
Click to collapse
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
knoxjon said:
I'm not sure how to screencap. It's so easy on CM that I've gotten lazy. Plus I rarely do it. I know there are a ton of apps for that, tho. But you could probably google "gingerbread screen capture" and find a better answer. But not with gingerbread. I'm blanking on the name for this version of android.
Click to expand...
Click to collapse
Honeycomb
I've been Googling searches like that, and end up with actual screen shots of Honeycomb os..I'll keep looking...
Tried this (from here), but no luck:
Screen capture
Android natively supports the ability to capture a screenshot by method of pressing both the power and volume-down buttons at the same time on an Android device. This native support was first included within the Android 4.0 (Ice Cream Sandwich) update, which is first seen on the Galaxy Nexus smartphone.[86] Previously, Android did not feature native support for screen capturing which would have likely been due to security concerns. Furthermore, prior manufacturer and third-party customizations as well as using a PC connection (DDMS developer's tool) were the only known methods of capturing a screenshot on Android.
I've looked through the *.so files and many of them are exactly the same, but some are different. One file caught my interest. I've attached it here for anyone who wants to try. Please only use it, if you have a T-Mobile Springboard with flashed root Firmware. Copy the content of the zip-file to /system/lib and overwrite the existing file. But make a backup first! After copying you have to set the correct file permission (rw- r-- r--) and reboot the tab. Hopefully 4G works again with this little trick.
Update 9/14/2013
A better solution has been released, please update using it.
http://forum.xda-developers.com/showthread.php?p=45598648
Warning: Don't attempt to use this on a device that isn't Motorola.
Lets break this sub forum open with a good one.
See: http://www.androidpolice.com/2013/09/12/exclusive-how-to-root-moto-x-ultra-mini-and-maxx/ for the story
Bounty payouts or donations can be paypaled to [email protected], or use the donate button to the left. If its for the bounty, please reply below with confirmation number or pm me.
These files are not to be mirrored elsewhere, no included in other packages. Its simple already, no need to repackage it.
Same APK should work for Maxx, Ultra and Mini. If it does not, I just need to rebuild it and need someone to test, it will work.
adb install -r <filename>
Run MotoRoot app
Press Setup
Install Supersu app
Phone will reboot, and you will be rooted as soon as device is fully booted.
Limitations:
Uninstalling the app will disable root until reinstalled
supersu is not able to update su yet, this will be fixed in an update shortly.
su is maintained in a ext4 img at /data/xbin.img and mounted over /system/xbin at BOOT_COMPLETE.
su is not available for the first few seconds of boot, im working on this.
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Unroot:
Two choices, factory reset, or press the unroot menu option in the app.
Problems:
Run into a problem? try hittung unroot then re-rooting
Credits:
We use two vulns in this app, first being 9695860 to gain system user, then a symlink attack of mine to get root from system.
xIndirect (nick) for assisting me from start to finish
Whoever originally found bug 9695860
Saurik for his description of 9695860
Ryan Welton for his 9695860 tool
Dave Kover for yet another kick butt icon
and Anthony Fox/Droid-Hive for great help with getting the device to me today
Very much appreciated.
PayPal transaction ID 4GK69936510343543.
Ignore everything I said, I will send my donation thank you
jcase said:
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Click to expand...
Click to collapse
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
jcase said:
su is not available for the first few seconds of boot, im working on this.
Click to expand...
Click to collapse
and dose this mean files cant be pushed with adb as a work around?
Confirmation number: 3FS7579230091290J
Thanks!!
Confirmation 17R58863KC726802C , I didn't pledge on the bounty thread.
Yes!
Worked like a charm!
Been waiting for this since day one. You are a god sir.
TheWhiteChallenger said:
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
and dose this mean files cant be pushed with adb as a work around?
Click to expand...
Click to collapse
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Thanks man!
Sent from my XT1080 using XDA Premium 4 mobile app
got adfree working, but you have to do it QUICKLY. remount /system as rw, then immediately press the update button on the adfree app. the changes will remain until reboot, but I hardly ever reboot
busybox mount -o remount,rw /system;
Thanks...didn't expect to have root so soon. Confirmation 7PD1555899342392B - pledged over on the Droid Ultra bounty page
Droid Mini Confirmed! Thank you!
Sent from my XT1030 using xda app-developers app
jcase said:
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Click to expand...
Click to collapse
ok kool, i dont mean to sound ungrateful thats just mainly what i use root for is fiddling with stuff of the system folder, so i was just wondering if i was permanently screwed of if was something that is atleast being working on, thanks again ill be sending my donation as soon as i remember my paypal pw, lol
Should USB Debugging be enabled?
is the "Transaction ID" the confirmation number?
Thanks! 8JG23957NE2435454
Posted from http://forum.xda-developers.com/showthread.php?t=2431005
Confirmation number: 4JK07192689429602
Thanks!
So this has to be installed by adb? What if in my haste and excitement, I "accidentally" installed it without ADB? I noticed I can't uninstall it. However, when I do Root Checker, it shows I'm rooted but I can't install SU it says "Installation Failed!"
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
I'm getting the exact same thing, if you push cancel it just closes the app.
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
Just don't open SuperSU once it's installed. Reboot one more time and you'll get regular prompts from SuperSU to allow permissions as apps request root.