[Q] help me.. - XPERIA X8 General

i've firstly root.ok.n then xrecovery.ok..but then when i want to enable JIT following this thread http://forum.xda-developers.com/showthread.php?t=877565,
my phone suddenly can't connect to wifi.and then the xrecovery cant be perform...and other things,how can i perform this operation?
(1: enable JIT (in a termnial or adb shell)
cd adb
adb shell
su
cd /sdcard/JiT-toggle-0.1
sh enable_jit.sh)
i connect the phone to pc an enable debug mode,run cmd,but pc says cant detect..watsoever..
can anyone help me?

If you followed all instructions for JIT and your wifi doesn't work means it wasn't the correct version of Busybox. I recommend you to install Titanium Backup hit Problems? and install busybox. Then, when you copy all files for JIT, don't copy busybox, because you have already the latest one. It should work. It happend to me, too. The nasty part is that you need to repair your Android with PcCompanion/ SEUS.

do i need to repair my phone first with pc companion or repeat again the step?
n how to run cmd?do i need to enable debug?i dont know how to do this instruction,1: enable JIT (in a termnial or adb shell)
cd adb
adb shell
su
cd /sdcard/JiT-toggle-0.1
sh enable_jit.sh

Well, if you have your phone rooted with superoneclick, then you got adb.exe. You need to access that folder into cmd. ex : c:\superoneclick\ and then with the phone connected (usb debug enabled) you can enter commands like adb shell and su. Try it. But wifi and xrecovery malfunctions are symptoms that something went wrong. Eventually repair with PcCompanion. Good Luck.

when i run the command prompt,it says 'adb' is not recognized as an internal or external command,operable program or batch file..is this because i didnt rooted my phone well?

Do you have adb.exe? Or superoneclick for root?

yeah.i have both.i downloaded superoneclick and inside ithave adb.exe..but when i click adb.exe,nothing happened.just a temporary command prompt about 2second and then its appeaered..

now open start-run->cmd and go to that folder. And only there you can run "adb shell".
So, in cmd you must be in that folder in order to input all commands.

go to that folder?what do u mean?open cmd from the folder?or open cmd and click to the folder?
sorry for the noob question..

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This should look like. using commands like " cd .." to exit folder and use ' cd "name of folder" ' to enter one. it should work.

thank god.finally i know how to run command.thanks a lot redpik

guys..help me.how am i to solve this command error?

Please follow this thread http://forum.xda-developers.com/showthread.php?t=877565 .
If you connect your phone to computer, make sure not to mount the sdcard. So, click on USB CONNECTION and select TURN OFF from the status bar. Make sure you have SUPERUSER application installed to grant access.
If it helps you, please consider pressing Thanks button.

sorry redpik..
i got big probs.. my homescreen and apps icon become smaller and i dont know whats going on.
is it brick or something else?
i try to use pc companion and seus,but it keep saying no update for my phone..
seriously,this small icon thing make me crazy..

I don't know what's with the screen, shouldn't have happened. Seus says no update, but Repair button is active so you can make it brand new. Then try again rooting and jit.

Related

Issues with adb shell, etc.

So for the first time I've set up my ADB since I will getting a MT3G tomorrow. Environment variables (PATH) set correctly, etc.
When I type adb shell in recovery model, it says *daemon not running. starting it now, daemon started successfully, error: device not found*
"Android Compsite ADB Interface" shows up in my USB devices. So what's the problem.
Then when I load up "emulator -data c:\", it starts up and gives me this error. msvcrt.dll? I've dealt with that .dll file before for other apps and it is in my system32 folder.
So what's going on here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try reinstalling the usb driver.
mine identifies as HTC Dream Composite ADB Interface.
did you install the usb driver that comes in the SDK?
what if you navigate to the location you have the sdk installed? does it work then? maybe the path is not set up as correct as you think? (i had this problem when trying to do fastboot. everything else worked fine except for fastboot. to get that working i had to navigate to the sdk directory.)
I sure did, and it reads exactly that.
Even adb devices doesn't bring a device up. Or adb remount.
Other thing is under Hard Drives Tree, the HTC Android USB Phone Device has a Microsoft driver. I tried to install drivers from the android/usb_driver/ and nothing. Do I have to do this in the Home Screen for the first time so it brings up the permission screen where I click on "Allow Always" for root? Cause I'm not getting that there, so I rebooted into recovery....nothing there as well.
i did have an issue recently where i couldn't get the usb driver to change over.
what i had to do to get it to change was disable and then re-enable usb debugging while the phone was connected to the computer.
it triggers a hardware change in windows and this allowed me to reinstall the correct driver.
uninstalling the current drivers might also help.
I've tried both things.
Same issue.
What Windows Services need to be enabled in order to get ADB to work? I did some tweaking of the services.msc for XP. I think that might be the reason adb shell isn't working.
Same problem I have:
I have TWO rooted G1s, Cyanogen 4.0.4 modified devices with identical Software releases.
The one (rooted by the Golcard Method) is recognized by ADB - the other one (rooted by the One Click Method) is not.
Troubled !
Oh Sorry -this is a Sapphire forum ... I apologize

How do I know that my phone (legend) is rooted or not?

hi firends
How do I know that my phone (legend) is rooted or not?
what are Symptoms for a rooted phone?
Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.
Liquid211 said:
Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.
Click to expand...
Click to collapse
1- how to install driver?
2- please see this picture and tell me what is wrong...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you haven't even installed ADB I don't know how you would think your phone is rooted? Did you buy it used?
Anyways. Download this ADB. Unzip to c: and run adb.exe shell from a cmd in c:\android-sdk-windows\tools
But make sure you install the driver first.
Go to Settings, Programs, Development and Tick Off "USB Debugging". Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.
thanks Liquid211 very much!
Liquid211 said:
... Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.
Click to expand...
Click to collapse
I have no such folder under "android-sdk-windows". I only see "add-ons", "platform" and "tools"...
just try a app that needs root rights.
for example many screenshot apps need su.
another way would be to look if u ve got the superuser app in ur app menu.
and ofcause a terminal like program could help to indicate if uve got root rights.
Simply download a terminal emulator from market and type 'su'...
Sent from my Legend using Tapatalk

Nexus 4 Not Recognized by ADB in Mac OS X

Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A
Try this command
adb kill server
adb start server
scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?

[Guide] How to install an app on any rooted device using terminal emulator

This is a guide on how to install an app using terminal emulator on a rooted device.
First make sure you have terminal emulator installed and root with su
Open terminal emulator and type in
cd sdcard
Press enter
Then type
Ls make sure the L is in lowercase
This will display the entire sd card contents
Then type cd "folder name" I.e Bluetooth or download so it will look like this
cd bluetooth
Press enter
Again type
Ls with a lower case L
Again you get a list of what's in the folder
Then type
su
Press enter
Then type this line
pm install "app name.apk"
So it would read like this in terminal emulator
pm install "root browser.apk"
You should get a message stating pkg name installing
Success
Exit terminal emulator and open your app drawer and search for the app you just install and open it
Congratulations on using command prompt with terminal emulator to install an app
I will be posting pics later for a visual walkthrough
If an app won't install try to rename the app to something smaller if you need to like if root browser app is named "root browser-233.apk" for instance just rename it to "root browser.apk" and then run the
pm install "root browser.apk" Command line in terminal emulator
It should successfully install some times an apps name is to long so it's invalid (I'm not positive on the exact error message offhand)
Hope this helps if you flash a ROM and don't have WiFi and need and app installed but only have terminal emulator like some aokp aosp and cm Roms do
I apologize for the pics on their sides before hand this phone sucks when it comes to pick can't wait to buy my galaxy s4 developers edition lol but anyway
OK as I promised to add pics for the walkthrough I used my titanium backup key.apk for an example
First open terminal emulator and type this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enter
To display the contents
Enter
The app I'm installing is in my apps folder so we do this
Enter
Type this to display contents of folder
Enter
Type this and accept su request
Type this line exactly as it looks with the quotes except use the name of the app your installing
If done correctly you should see this

[GUIDE][NO ROOT] ADB Bloatware removal Simple Guide for RedMi Note 5A.

Warning: I will not be responsible for any wrong doings that might occur with following this guide, this is my first Guide here, expect some errors. Any damage to any device that might happen by following then steps is responsiblility of particular user not mine. I recommend that you don't do anything you don't understand.
Disclaimer: I do not personally own a RedMi Note 5A device, I helped a friend to clean up some space on their device, as a part of which, I uninstalled some of the OEM apps that were not used by them.
If you use any of the apps, you should not uninstall them.
Difficultly level: Easy to medium.
Experience required: You should be familiar with ADB, Windows BatchScript (optional), Android file system.
As superuser access is not used in this process, root is not required, you can try this on Non-Rooted devices
Tested on : Redmi Note 5A, Android-8.x, MiUi v10.x
Should work on all device prior to Android 9.
Requirements: ADB installed on PC, supposedly windows. A proper USB cable, an Android Phone.
I'll assume you have already setup ADB via Android-SDK or minimalistic ADB tools, and not go into that.
1. Enable developer mode, USB debugging on phone,
2. Connect device to PC (in a USB 2.0 port, preferably).
3. start adb, "adb start-server"
4. Make sure device is available.
Now there is batch file in attachment for uninstalling and a text file with the list of apps I uninstalled. You can either replace the package name with those you want to remove or you can copy the command, make it a single line command and replace the package name directly into the prompt as I did
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Additional details are given in the attachment zip files, see below. You replace the package name with the app you want to uninstall and run the script/command in command line.
Same thing can in theory be achieved if "pm" command is readable by a third party terminal emulator apps like Termux, note that, on new devices, "/" is not readable, "/system/bin/pm" might be readable depending on ROM, thus ADB way should always work, but calling "pm" from on device apps is also possible.
Expected results: single word "success" on a new line.
If it says "device offline", restart adb with "adb kill-server" followed by "adb start-server" , if that doesn't work restart the smartphone, if that doesn't work check that USB port is v2.0( search on Google how to determine ), if that doesn't work, your cable would be faulty or some connection error.
Reserved.

Categories

Resources