To aid in the use of the shell/console/terminal, the following page was started:
http://forum.xda-developers.com/wiki/index.php?title=Xperia_X10_Mini_Console
Only the method for the terminal emulator was described, if someone uses one of the other methods, feel free to update the wiki (press edit at the top).
Related
So I feel like a total Noob, which i am, but I cannot get this new Kernel to work for me. I do the following steps:
1) Open Terminal Emulator (install it from market if you don't have it).
2) Type "su" (without quotes) and hit enter.
3) Type "speedtweak.sh" (without quotes) and hit enter.
When I type in and I get speadtweak.sh and i get Speedtweak.sh not found... what in the world am I doing wrong?
when terminal boots up I get:
$ export PATH=/data/local/bin:$PATH
$
when your terminal boots up-
$ export PATH=/data/local/bin:$PATH
$
-- You need remember ALWAYS lower sensitive case characters
type su hit return
it will come up #
then
type speedtweak.sh hit return
There you will access the dialog output from speedtweak.sh.
Good luck
You have to install BusyBox. If you haven't it'll show up as "not found".
Having same issue. Busybox is installed even tried using adb shell. Any advice?
Did you install the kernel through Rom Manager or through Recovery? If it was through Rom Manager it could have been a bad flash.
Also, you can try this
I found this thread through google, searching for "speedtweak.sh not found." I dislike necroposting but I tried various suggestions found on multiple websites and none of them worked for me. I kept getting the same error code. Hopefully this will help someone else with the same issue. I don't know much about Linux/Unix so I am always extremely methodical about typing in commands precisely as they're posted, double-checking each step so I'm certain I did everything correctly.
I finally solved the issue for me by entering in the following in Terminal Emulator.
su
/sbin/speedtweak.sh
Typing in the full path for the speedtweak script worked for me. Perhaps someone with more experience can explain why that was necessary. Were we working in DOS, I'd know to add C:/sbin/ to the autoexec.bat path line... :silly:
Terminal emulator from the market had something changed in the last update so for some reason now you have to manually enter it or change the path in the settings.
Sent from my ADR6400L using Tapatalk 2
I've got a few questions about Gfree.
1. What is it?
2. Is it a part of Android SDK or do I get it as stand alone tool?
3. Do I use it on the phone or on the PC in the command mode?
thanks.
this may give you a clue:
http://forum.xda-developers.com/wik..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.7
if not try looking here: stfw
NO. I've been at that link already.
It does not explain what Gfree is.
It only says to use commands like this:# ./gfree -f -b hboot-eng.img -y recovery.img
No explanation.
And Google does not give any good links either.
bumping up.
G-free is an application to gain permanent root access to your phone. The commands are what determines what you want the application to do such as sim unlock, s=off and such.
Also it is a standalone tool but adb is used to push the file to the phone. Commands are done through terminal emulator on the phone.
lowandbehold - thank you very much.
So this is something like z4root or SuperOneClick -a stand alone rooting app...
It just needs commands through terminal emulator.
The same concerns Rage?
I'm not too savvy with this tech stuff but i figured if anyone could do it it would be you guy's here... i did not create this nor write it and since i am new i cannot post a link but its from our friends over at yumapk... so w/o further a due:
"Here is the tutorial of getting root access on NEC Terrain.
Before getting access on NEC Terrain, you need to prepare 4 tools:
Ⅰ：Android SDK
Ⅱ: The related drive of NEC Terrain
Ⅲ: cm-hero-recovery.img
Ⅳ: superuser.zi
The first step is to install USB drive:
Firstly, let’s come into this step. Find Setting-Application program-USB debugger button, then check the first option. Next, connect your USB line with PC, it will prompt you to install driver. If it is the 32 bit system, then you are supposed to choose “x86” document to install the drive. Whereas, if it is 64 bit system, choose “amd64” document to install the drive.
The second step is to prepare the software for NEC Terrain:
In detail, remove the “TMG” document in your software kit to the root directory in C disk, in order to give us the convenience of finding C:\TMG\
The third step is to examine adb.exe and fastboot.exe:
To begin with the third procedure, all we need to do is to ensure that we have the document of adb.exe and fastboot.exe in TMG. So we need to accomplish those procedures one by one.
The fourth step is to check the condition of drive installation:
Unplug your USB line, then shut down NEC Terrain, next press the backspace key. Go on pressing the power key to enter bootloader. Then connect NEC Terrain with PC, and fastbootusb will come out in NEC Terrain. Pay more attention that never press mount at this time.
Open Start-Run-CMD, then enter the order: cdC:\TMG
C:\TMG>_ will come out when the order runs successfully.
Then input the order: fastboot devices.
The fifth step is to start rooting:
Enter: fastboot boot cm-hero-recovery.img after C:\TMG>. Then NEC Terrain will enter the mode of recovery.
We will see seven options in this mode, they are the following ones:
[Home+Back]reboot system now\\restart
[Alt+S]apply sdcard:update.zip\\install update.zip in SD
[Alt+A]apply any zip fromsd\\install any zip file in SD
[Alt+W]wipe data /factoryreset\\delete all datas
[Alt+B]nandroid v2.2 backup\\back up
[Alt+R]restore late stbackup\\recover the final back-ups
[Alt+F]repair ext filesystems\\suggest backing up ROM in NEC Terrain, use the trackball to move the cursor to [Alt+B]nandroidv2.2backup, check it. If there is something wrong with your NEC Terrain, it can also recover.
Now start entering the order, an order is in a line. Pay attention to the small letters and the big letters and also the blank.
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
After rebooting, you will finally get root access on NEC Terrain."
if this works hopefully someone can make a script to make this more convenient for the others like me
-edit-
also please if it doesn't work, keep in mind I did not write this, and i made this account specifically to share this post because i cannot find any other info and so many people here know more about this stuff than I. NTM there are tons of people here looking for root just like me on this phone
holydude92 said:
Then input the order: fastboot devices.
Click to expand...
Click to collapse
Where did you find this guide? I'm guessing from some shady site where it changes phone name from google query in some universal rooting method and shows it to you.
To be honest I did not tried this guide, but when I was more optimistic about rooting NEC Terrain I tried a lot of different ones. I can tell you that at quoted step it fails, because NEC terrain doesn't have fastboot mode enabled. Sorry.
P.M. me a link to the site.
Good luck.
I am trying to Install apk and run it with command line
to Install apk
adb install myapk.apk
Now I am trying to run it with commands .. and after Googling I found something like
adb shell am start -n com.other.ProjectName/.MainActivity
How to know com.other.ProjectName and .MainActivity of an installed apk ..
any easier method will be helpful
U can use
adb pm list packages
command to view the packages installed in your device.
Regards,
Karthick
this command does not seems to work
how do i know and understand the logic of your.package/.YourActivity
stiphen said:
I am trying to Install apk and run it with command line
to Install apk
adb install myapk.apk
Now I am trying to run it with commands .. and after Googling I found something like
adb shell am start -n com.other.ProjectName/.MainActivity
How to know com.other.ProjectName and .MainActivity of an installed apk ..
any easier method will be helpful
Click to expand...
Click to collapse
Follow the steps below.
1. Install the attached .apk for ADW Launcher.
2. Open the Menu.
3. Swipe to the "Add" section of the menu and tap "Custom shortcut".
4. Now tap "Activities".
5. You will be presented with a list of all the apps you have installed; tapping on one of them will drop down a list of all of the packages available to launch for that app. Tapping on one of the packages will create a shortcut for it on the ADW Launcher homescreen.
Hope this helps! :good:
You can see in root/data/apps
Much easy if you use apk installer.exe. You can install apk, lunch, take screen short by singal click.
Sent from my Smartfren Andromax AD6B1H using XDA Free mobile app
thanks for all of your help .. got it
OK, I just got an Amazon Fire HD 6 for free from a friend brand new so I figured this would be a great thing to learn rooting android and other things. No cost = no loss if I screw it all up.
Basically my goal is jut to root it to get it to be more like a regular old android tablet and not to have all the Amazon crap constantly running in the background sending all my info to Amazon every minute of every day. From reading here this seems possible. Please tell me if It's not.
Background:
I know quite a bit about PCs running Windows since 3.0 and have dabbled with Linux and Apache off and on over the years but I am by no means an expert. Advanced amateur might be better.
The tablet is running Fire OS 5.1.2. I don't know what it had when I first turned it on but I had no idea what I was going to do with it so I let it update itself until it got to the current 5.1.2.
I tried reading some of the tutorials but they seem way over my head as they seem to assume a knowledge of certain acronyms that I am not yet familiar with.
This is what I think I know so far. Please tell me if I'm wrong...
1. It is not possible to root 5.1.2. I probably should have left it at whatever it was when I got it which was probably 4.5.x.
2. Because of #1 above the only way for me to root this is to downgrade to 4.5.x.
Do I have that right so far? Because if I don't have at least that right then I am way off, so let's start there.
My goal would be for this thread to become a real "how to root your HD 6" for real total newbs like me. Step by step on what to download, from where, what is a TWRP what do you use it for, what is an ADB and what do you use it for, from turning the thing on to ending up with a nicely rooted tablet.
In case anyone else wants to know what happened and how I accomplished all, the answers are in page 6 of this topic ...
http://forum.xda-developers.com/fire-hd/help/help-thread-question-noob-friendly-t3206776
Here is a full tutorial in one place...
First off these instructions are for the Amazon Fire HD 6 gen4 running Fire OS 5.1.2 only. Will it work on other things? Who knows. Will it work on another of the exact same tablet? I have no idea. Would it work on this same tablet if I had to do it over again? Could be ... but then again, ya never know. So proceed at your own risk. All I know is that it worked for me here today on this particular tablet at this time and I hope I never have to do it again.
All of these instructions can be found at the following link at about page 6 of that topic.
http://forum.xda-developers.com/fire-hd/help/help-thread-question-noob-friendly-t3206776/page6
1: First I installed the USB driver from Amazon at the following link:
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
and then I downloaded the ADB SDK tools from links from this tutorial:
http://www.howtogeek.com/125769/how...roid-debug-bridge-utility/?PageSpeed=noscript
After enabling USB debugging on the device I had ADB ability.
2. Downloaded the Kingroot version 4.8.5 apk from here and ran it:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Let it go to town doing it's thing. Afterwards it claimed success and said that I was rooted.
3. Ran the following commands given by DoLooper from above xda post to disable OTA update:
Open a CMD window from folder with adb.exe by right clicking in that folder and holding down the shift key. Then run these commands one at a time:
adb -d shell "su -c 'pm disable com.amazon.otaverifier'"
adb -d shell "su -c 'pm disable com.amazon.device.software.ota'"
adb -d shell "su -c 'pm disable com.settings.systemupdates'"
Tried to rename OTA file from DoLooper instructions using Simple Explorer with root priviledges (not ES) - fail - does not seem to want to rename the file for some reason.
So at this point I was successfully rooted. But I basically had a virus running on my tablet called Kingroot . I checked using another app and I saw that it was constantly connected to China. Bad? I don't know but certainly does not making me feel all warm and fuzzy so next step was to get rid of Kingroot. Problem is that if you uninstall it it sets you back to unrooted default. So ... read on.
4. Installed Terminal Emulator for Android from http://www.apkmirror.com/
6. Uploaded the 4 files from the zip file from wolfdroid from second link in sd_shadow post in that same topic. Can be found here:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
7. ran the 2 commands from wolfdroid website using terminal emulator.
This removed Kingroot and left me rooted. Then I found an updated version of SuperSU and updated it too. So now I have a tablet that is rooted and I can install apps that require root access. Also I was able to uninstall some Amazon apps, disable others and basically stop it from phoning home.
BTW, I didn't recommend disabling com.settings.systemupdates. They do this on the 2015 Fires, but I have not used it on either the 2014s or 2015.
Yes, I apologize. You are correct. You did not suggest that one. That one I did get from the other topic. However, I did it and I don't see any negative effects so far.
But you know more than I so is there any reason you could see toward not doing that one?