This has obviously been covered in DagentooBoy's thread - which is great.
http://forum.xda-developers.com/showthread.php?t=761045
But I tried it and it doesn't work, even with the SGS Unlocker, tried the WinXP (PC way) first.
The version I'm running is Android 2.1 update 1.
I get this when I try running it through the PC.
{
"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"
}
Sometimes when I turn my phone on I get asked to enter the SIM pin, but I hit DISMISS and get into the phone. The next screen says "Phone Locked", but I swipe and enter the phone.
Will buying an unlock code from one of eBay unlockers work or not?
I feel like I bought a brick here. lol
Anyways, any input would be greatly appreciated. I'm not looking to do anything else to it other than unlock and use it for now. While I'm fairly competent with doing this tech-stuff, the Android stuff is a step above for me, so I wanna take my time to learn this all.
It's my first smartphone after using a Nokia 6265i for the past 5 years.
http://en.wikipedia.org/wiki/Nokia_6265 lol
So for me this phone is a treat as is, if only I can get it unlocked.
Thanks for your help and input.
It's because adb can't get to the file without root. Happened to me too. I just manually copied the nv_data.bin over to my computer using the standard usb mass storage and ran sgux on it.
Code:
C:\androidsdk\tools>adb shell
/ $su
#cp /efs/nv_data.bin /sdcard
#exit
#exit
then mount the usb storage, copy over the nv_data.bin to the folder with sgux.exe in it (i put mine in c:\androidsdk), then:
Code:
C:\androidsdk>sgux nv_data.bin
and with any luck you'll have it.
chui101 said:
It's because adb can't get to the file without root. Happened to me too. I just manually copied the nv_data.bin over to my computer using the standard usb mass storage and ran sgux on it.
Code:
C:\androidsdk\tools>adb shell
/ $su
#cp /efs/nv_data.bin /sdcard
#exit
#exit
then mount the usb storage, copy over the nv_data.bin to the folder with sgux.exe in it (i put mine in c:\androidsdk), then:
Code:
C:\androidsdk>sgux nv_data.bin
and with any luck you'll have it.
Click to expand...
Click to collapse
Okay, I understand a bit. but I'm not sure what all the coding is all about and how/what to do. You copied nv_data.bin from your phone to a location on the computer?
I set my Vibrant to mass storage and while it's not showing on MyComputer anywhere, the only thing that pops up is the microSD card with the movie on it.
Correct... instead of androidsdk it would be wherever you saved it..
Having one hell of a time accessing my phone via the computer.
It's connected, but no icon to click open or anything of the sort (inside MyComputer)
Ok, this is what I have on my screen now.
No EFS folder, no nv_data.bin, anywhere in the folders.
You need to use root explorer or adb(maybe astro) for access to your internal system directories. Just pull the file using adb like chui mentioned. If you aren't familiar with adb then I suggest you read up in the Vibrant bible.
lralexl said:
You need to use root explorer or adb(maybe astro) for access to your internal system directories. Just pull the file using adb like chui mentioned. If you aren't familiar with adb then I suggest you read up in the Vibrant bible.
Click to expand...
Click to collapse
Wanna suggest a link to this almighty Vibrant Bible?
Well I just looked through it and there doesn't seem to be a thread specifically about adb file system actions.
Just open a command prompt and "cd" to your android sdk tools folder.
example: cd c:\sdk\tools
type:
adb shell
su
cp /efs/nv_data.bin /sdcard
exit
adb pull /sdcard/nv_data.bin /nv_data
that should get nv_data.bin into your tools folder under the folder nv_data. then just move the nv_data.bin into the sgux.exe folder
I'll try this now, thanks Iral.
Trying to type what you put, I can't remember for the life of me how to enter multiple command lines in command prompt. Hitting ENTER executes the first line. But I'm supposed to type all that out correct?
One line at a time
Well, I installed the SDK toolkit, updated Java, done everything possible.
Been diligent and patient with this, but this Galaxy phone is about to enter the Galaxy.
Just typing adb shell (the first command) and I get this.
koooba said:
Well, I installed the SDK toolkit, updated Java, done everything possible.
Been diligent and patient with this, but this Galaxy phone is about to enter the Galaxy.
Just typing adb shell (the first command) and I get this.
Click to expand...
Click to collapse
Post the output of ls err ...
Code:
dir
Not following LQ, sorry?
koooba said:
Not following LQ, sorry?
Click to expand...
Click to collapse
The screenshot you've taken when you executed adb, go to the same folder (tools) and execute dir in MS-DOS window.
Need to see if adb.exe is there.
I hope this is the one you mean.
I reinstalled SDK into c:\androidsdk and this was found in the \platform-tools folder
koooba said:
I hope this is the one you mean.
I reinstalled SDK into c:\androidsdk and this was found in the \platform-tools folder
Click to expand...
Click to collapse
what happens when you connect your device to the usb port (usb debugging is enabled i presume), open the command prompt on your pc and issue
Code:
cd c:\androidsdk\platform-tools
adb.exe devices
lqaddict said:
what happens when you connect your device to the usb port (usb debugging is enabled i presume), open the command prompt on your pc and issue
Code:
cd c:\androidsdk\platform-tools
adb.exe devices
Click to expand...
Click to collapse
This happens (seems like it's good)
Good,
now try
Code:
adb.exe shell
And what was the original post about ?
lqaddict said:
Good,
now try
Code:
adb.exe shell
And what was the original post about ?
Click to expand...
Click to collapse
lol ya.
Well it runs, but it seems to stop with a blinking cursor after the $
Related
Hey, did a search but couldnt find a solution. I'm having problems getting my device to pull up in adb remount on Ubuntu. When I try remount it says no command 'adb' found sometimes or permission denied when it does work, I have root and USB debugging enabled on the devices (a Nexus One and G1). When I try adb devices I just get ?????????????? unknown.
Also, and I don't know if it's related, but in Eclipse, I can't get the SDK location loaded, I have the directory right, but when I hit Apply or OK nothing happens, it just doesnt load. So if I try to start a project I have no Build Targets to select from.
Any help would be appreciated. I have everything running fine in Windows but I'm fairly new to Linux I haven't used it in years. I'm running Ubuntu distro if that matters. Thanks.
i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated
Hello,
The problem with linux having trouble with adb probably lies with a permission issue try adb kill-server && sudo start-server.
The other issue is most likely because you did not download any targets yet. goto windows in eclipse and select android sdk and adv, then at available packages or something like that download your target
i can't even get that far. i switch to my androidSDK/tools and then "adb devices" all i get is 'no command adb found'
I did the first couple times too, then I went to command and did:
su
<enter password>
cd
export PATH=${PATH}:<your_sdk_dir>/tools
then when I adb remount or adb devices it gives me the unknown device thing
but I think the next secret is here
http://forum.xda-developers.com/showthread.php?t=613217
in like the 3rd post. However I think the export PATH is a temp fix because the ~/.bashrc needs to be modified with the path settings and I have no idea how to do that. I just get lots of permission errors or file not found for everything I try, even with root. I'm just using Eclipse in Windows for now, and hopefully someone can help us out cause I'd like to work on roms but I guess I need to brush my Linux up first.
http://forum.xda-developers.com/showthread.php?p=5377103
i found some help elsewhere on the net, and posted it up at the end of this thread. they were having similar issues with the dream, apparently.
i also found this
that link there will probably get you hooked up
adb devices now has a readout!
and, you're right about adding the export PATH=${PATH}:<your_sdk_dir>/tools to
~/.bashrc
i think this command will do it. run in terminal
gksudo gedit ~/.bashrc
i just made a comment line that says
# android sdk export path
and another line underneath it that says
export PATH=${PATH}:/home/timmyd/androidSDK/tools
because that's where i have the extracted sdk
all good, i think. now, let's see what's going on ...
oh yeah, don't forget to enable usb debugging on the device itself.
settings>applications>development
allow usb debugging
screeny works at least
{
"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"
}
Cool, I'll try that out tomorrow.
timothydonohue said:
i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated
Click to expand...
Click to collapse
Hi all!!!!
I have a problem with my HTC Tattoo, can't connect the tatto with adb in ubuntu and eclipse Helios.
/android-sdk-linux_86/platform-tools$ ./adb devices
List of devices attached
???????????? no permissions
Thank you very much.
Hi, I have tha same problem with ????? and can't connect to eclipse my galaxy, so the solution is just use the instructions from the h**p://developer.android.com/guide/developing/device.html
I solve this problem with
1. Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
The USB Vendor IDs foreach manufacturer
Manufacturer USB Vendor ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Click to expand...
Click to collapse
Hope to help you!
Big thanks to tereg for the toolkit and the guys who rooted the EVO with a file write/chmod race condition exploit that gave me the idea for this.
jcase noticed that a race isn't actually necessary to exploit the chmod 777 on the file I've been working with, simplifying the script alot.
I used the files from the adb development pack that Tereg put together. Download them here. You don't need them for this root process as long as you have a working adb install.
THE SCRIPTS HAVE BEEN UPDATED MANY TIMES! Please be sure to re-download the new hack-v4.zip before you start if you a returning root seeker.
You will need adb access. Install the android sdk for your platform (macos, windows, linux) get it for your OS here.
If you don't know how to install the sdk, search xda, there are a ton of howtos for that.
Also, if you want to root and can't get your computer to talk to the phone or have some other weird computer related issue you can now try this method, which doesn't require a computer at all!
Unzip hack-v4.zip to somewhere, copy/move the files into your adb-sdk/tools directory/folder.
*updated files to hack-v4.zip @ 7-14-2010 10:43AM Central*
Files to download:
hack-v4.zip
A ROM file, I suggest EvilEris if you want to flash the whole phone OR EngTools.zip If you just want to be root. (Thanks jcase!)
Android SDK (skip if you have a working adb)
Instructions for linux/OSX. - Alternate instructions specifically for MAC
Have adb in your path, or move the files contained in hack-v4.zip into your sdk/tools directory so your pushes will work properly.
FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.
Do NOT have your phone in Disk Drive Mode, have it in Charge Only.
Open a terminal window in your /tools/ directory. Type this at the prompt.
Code:
sh runinlinuxfromtools.sh
This will take a few minutes, follow the instructions on your screen.
If you get adb: command not found, try
Code:
sh runinlinuxadb.sh
Some people get a permission denied error. Try
Code:
chmod +x ./runinlinuxfromtools.sh
./runinlinuxfromtools.sh
Instructions for windows (thanks tereg!)
Download the hack.zip file and extract it to the desktop. So, you have a folder on the desktop called hack. I would recommend moving or copying those files (EDIT: that are contained in the hack folder) to the C:\android-sdk-windows\tools folder. Why? Because the script runs "adb ____" commands, and unless you've set up adb to be able to run anywhere within the command prompt, the script won't run. So, it will universally work if the files in the hack folder are placed in C:\android-sdk-windows\tools
So, open a command prompt by pressing WindowsKey+R, or going to Start-Run (in WinXP) and typing
Code:
cmd
in the text box there and press OK
If you are in Windows Vista/Windows 7, go to the Start Menu, then type in
Code:
cmd
in the search bar in the lower right-hand corner of the start menu and press enter, and locate Command Prompt in the search results, or go to Start -> All Programs -> Accessories -> Command Prompt
Type
Code:
cd C:\android-sdk-windows\tools
and press enter
Now, I recommend pushing the ROM you want to flash to the SD card now. So, if you download EvilEris3.0 for instance, make sure you download it to the C:\android-sdk-windows\tools folder, and then execute
Code:
adb push EvilEris3.0.zip /sdcard
Replace EvilEris3.0.zip with the name of the .zip file that you choose to download.
Then, type
Code:
runindos.bat
to execute the script.
You might have to run it 2 or 3 times for it to work. If it fails, just reboot the phone normally, then run
Code:
runindos.bat
again once the phone is booted back up and you're ready.
----------(Thanks again tereg!)
If your device reboots into a new screen with options on it, you now have root in recovery mode. At this point you will be flashing your Eris's brains, so YOUR PHONE WILL BE BLANK AFTER LOADING A NEW ROM! All of your apps/numbers will be gone from the phone.
I suggest a nand backup first.
Download and copy one of these ROM's to your sdcard as update.zip and flash it with flash zip from sdcard by selecting "Install zip from sdcard".
The first boot after loading a new ROM takes quite a while to show any activity to the screen. Give it a good 5 minutes before you start wondering if it's ever going to come back.
Eris ROMS
More things you can now do.
Replace that hateful HBOOT 1.49, and get a rooted STOCK phone.
Donate of you luv me!
-----------------
And some love for tereg! Donate a bit to him too, if you're feeling generous.
Dude, seriously. Put up a donate button. I would donate for your effort. This is absolutely amazing.
I will suck yo thang if this works...brb
If this is confirmed I'm returning my eris with the ****ty trackball and rooting a new one >_>
I love you so much for running with our small shot
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Oh and btw
This should work on ANY HTC Android 2.1 phone.
{
"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"
}
cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile
wag3slav3 said:
crap, I'm kinda spaced out from glee right now. should be
/data/local/testfile
Click to expand...
Click to collapse
lol, same thing...
do you want us to do a cd command, because the cat command does not exist i believe. It may not help that i have absolutely no idea what to do in the first place
cptkrush said:
when doing
cat > data/local/testfile
I get:
System cannot find the path specified
Click to expand...
Click to collapse
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile
wag3slav3 said:
You're missing the first / in /data/local/testfile sir.
Yours cat > data/local/testfile
mine cat > /data/local/testfile
Click to expand...
Click to collapse
nope, that was just how i typed it out in the post, still not working.
How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?
ericFuels999 said:
How are we supposed to "run" the following?
/data/local/flash_image recovery /sdcard/recovery.img
reboot recovery
I keep getting "error opening /sdcard/recovery.img: No such file or directory", but I'm also not really sure if I'm missing something. I type it in EXACTLY as you put it, right?
Click to expand...
Click to collapse
cat is a unix command
we're on dos
dos doesn't have the same command
xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
I understand that, but that wasn't my question. Refer to my previous post.
xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
THIS EXPLAINS EVERYTHING, sorry for caps, but i got excited :3
any way to do this in DOS or am i gonna have to boot up ubuntu?
scratch that, wag3 got me covered.
xnatex21 said:
cat is a unix command
we're on dos
dos doesn't have the same command
Click to expand...
Click to collapse
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.
ahem... I get permission error when I tree to reboot **epic sadface**
I"M DUMB I HAVE TO LEAVE SHELL FIRST
Put run 'adb shell' in the instructions before 'then do this'. Not everyone is going to pick up on that.
wag3slav3 said:
You skipped the step where you do an adb shell.
You should be at the $ prompt on your phone for this.
Click to expand...
Click to collapse
you should add
"do: adb shell"
to the first post.
Did any tried to root ur Xperia Arc (2.3.2) using GingerBreak??
As per desc:
This App was tested on Gingerbread (2.3.3) but might also run on Froyo and Honeycomb.
http://forum.xda-developers.com/showthread.php?t=1045204
Sent from my R800i using XDA App
NielDK said:
http://forum.xda-developers.com/showthread.php?t=1045204
Sent from my R800i using XDA App
Click to expand...
Click to collapse
thanks but is it working for XPERIA ARC !!!??!!!
xperiax10.awesome said:
thanks but is it working for XPERIA ARC !!!??!!!
Click to expand...
Click to collapse
The title says Play, Arc and Neo
Well, it works for my Arc nice and perfectly
cool, finally I rooted my xperia ARC
these are very simple steps(copied from different threads):
1. Install the attached apk: Gingerbreak-v1.00
after installing most people getting this error - "could not extract assets".
TO OVERCOME THIS, just copy the attached ADB.zip and extract it on your laptop (windows)
say at
E:\mobile_Xperia\ADB
goto above path in your cmd promt and types these lines (your phone should be connected to laptop in debugging mode)
E:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
E:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
NOW JUST INSTALL THE apk file again and click on ROOT
xperiax10.awesome said:
cool, finally I rooted my xperia ARC
these are very simple steps(copied from different threads):
1. Install the attached apk: Gingerbreak-v1.00
after installing most people getting this error - "could not extract assets".
TO OVERCOME THIS, just copy the attached ADB.zip and extract it on your laptop (windows)
say at
E:\mobile_Xperia\ADB
goto above path in your cmd promt and types these lines (your phone should be connected to laptop in debugging mode)
E:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
E:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
NOW JUST INSTALL THE apk file again and click on ROOT
Click to expand...
Click to collapse
Last night I have rooted my device in this way. Now the question - how to integrate it into FlashTool, as well as Busybox and xRecovery ?
xperiax10.awesome said:
cool, finally I rooted my xperia ARC
these are very simple steps(copied from different threads):
1. Install the attached apk: Gingerbreak-v1.00
after installing most people getting this error - "could not extract assets".
TO OVERCOME THIS, just copy the attached ADB.zip and extract it on your laptop (windows)
say at
E:\mobile_Xperia\ADB
goto above path in your cmd promt and types these lines (your phone should be connected to laptop in debugging mode)
E:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
E:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
NOW JUST INSTALL THE apk file again and click on ROOT
Click to expand...
Click to collapse
I only keep getting: No such file or directory....
Cim_XII said:
I only keep getting: No such file or directory....
Click to expand...
Click to collapse
Extract the ADB.zip into any folder, then inside that folder shift + right click and select Open command window here. In the command window enter: adb shell rm -r /data/local/tmp/* and then restart the gingerbreak app.
Chainfire said he will update the app in the next release to fix this issue
mikrokiwi said:
Extract the ADB.zip into any folder, then inside that folder shift + right click and select Open command window here. In the command window enter: adb shell rm /data/local/tmp/* and then restart the gingerbreak app.
Click to expand...
Click to collapse
On a mac, it won't work like that.
Cim_XII said:
On a mac, it won't work like that.
Click to expand...
Click to collapse
Of course not, is it the osx terminal or adb that gives you this error?
mikrokiwi said:
Of course not, is it the osx terminal or adb that gives you this error?
Click to expand...
Click to collapse
Os X terminal, when I run adb I can't type any commands in the command/terminal window. So I have to use Os X terminal.
Cim_XII said:
Os X terminal, when I run adb I can't type any commands in the command/terminal window. So I have to use Os X terminal.
Click to expand...
Click to collapse
Well, the zip wont work for OSX since its a windows executable You should try to get adb to work on your system (Im sure there are lots of guides), or just wait for the next release of the app.
mikrokiwi said:
Well, the zip wont work for OSX since its a windows executable You should try to get adb to work on your system (Im sure there are lots of guides), or just wait for the next release of the app.
Click to expand...
Click to collapse
I know that lol...
I got all the files and tools for Os X, but when I run ADB it goes into Os X terminal anyway, so I have to use it I guess...
It worked for me, got root on my Arc
Im getting this what am i doing wrong
Getting :
{
"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"
}
use rm -r /data/local/tmp
Ok...this not work....and i don't know why
I put adb file in a new folder.
I do Shift+right and open cmd
i write "adb shell rmdir /data/local/tmp" but at this point nothing happen..like cmd was freezed.
what I must do???
Arc must be connected with debug ON but in wich way?
Media transfer? SD card? or nothing???
lollylost100 said:
use rm -r /data/local/tmp
Click to expand...
Click to collapse
Nice one that worked
I tried this it works for me, my ARC rooted.
C:\mobile_Xperia\ADB>adb shell rm /data/local/tmp/*
C:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
C:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
Then run Gingerbreak-v1.00.apk
cheer
James
I can only get the flashtool to recognize my phone is flash mode, anyone can chime in if they want to
HOW-TO
Open terminal alt+ctrl+T
Copy and paste each line separately
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jre sun-java6-plugin sun-java6-fonts
Then download the flashtool
http://androxyde.github.com/Flashtool/
Extract the file and save it in your home folder
Now you need to make a udev rule
Go in terminal and hit SHIFT+CTRL+T
2 tabs should be opened
Type
sudo gedit /etc/udev/rules.d/51-flashtool.rules
then go to the other terminal tab and type
lsusb
you should see a line that looks like this
Bus 001 Device 011: ID 0fce:612e Sony Ericsson Mobile Communications AB
copy the bold and italicized print into this line
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="####", MODE="0777"
Save that line into the rules file
Go to the flashtool folder
Click on the flashtool file
And run it but not in terminal
hi,
I got Macbuntu 10.10 here.
Downloaded & extracted flashtool 0.6.7
have java installed
have libusb-1.0 installed
how do I add the rule =>
(terminal?)
/etc/udev :
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
and then?
any help would be nice..
you will be in terminal, sorry im never on here. the command gedit will open the file where needed to make the rule
I'll redo install and take screenshots as I go
Jedidiah55 said:
you will be in terminal, sorry im never on here. the command gedit will open the file where needed to make the rule
I'll redo install and take screenshots as I go
Click to expand...
Click to collapse
that would be nice
I added this
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="615a", MODE="0777"
Click to expand...
Click to collapse
from lsusb
Bus 001 Device 005: ID 0fce:615a Sony Ericsson Mobile Communications AB
Click to expand...
Click to collapse
but I still get.
libusb couldn't open USB device /dev/bus/usb/001/007: Permission denied.
libusb requires write access to USB device nodes.
Click to expand...
Click to collapse
??
leona said:
I added this
from lsusb
but I still get.
??
Click to expand...
Click to collapse
Use sudo
leona said:
I added this
from lsusb
but I still get.
??
Click to expand...
Click to collapse
Oddly a restart seemed to cure it, even after I did restart a udev service, it needed to restart the PC.
Edit: Hum maybe not, just plugged phone while switched on and it seemed fine.
Went to do a firmware flash and it gave me the
Code:
libusb couldn't open USB device /dev/bus/usb/001/012: Permission denied.
libusb requires write access to USB device nodes.
Again
sorry ive been busy lately, job change, engine swaps, moving, buying new car, buried some family, etc.
ive also update to 12.4 ubuntu so ill see what i can do
Jedidiah55 said:
sorry ive been busy lately, job change, engine swaps, moving, buying new car, buried some family, etc.
ive also update to 12.4 ubuntu so ill see what i can do
Click to expand...
Click to collapse
Gosh you have been busy, I'm still on 10.04 LTS at the moment, as I have not got around to update my machine yet, as I can not stand the new UI.
I did the firmware flash in the end but using sudo as Mister J suggested which worked, but it would be nice to have it work it properly.
leona said:
Oddly a restart seemed to cure it, even after I did restart a udev service, it needed to restart the PC.
Edit: Hum maybe not, just plugged phone while switched on and it seemed fine.
Went to do a firmware flash and it gave me the
Code:
libusb couldn't open USB device /dev/bus/usb/001/012: Permission denied.
libusb requires write access to USB device nodes.
Again
Click to expand...
Click to collapse
Try opening up a terminal and typing:
"sudo nautilus"
Then, go to /dev/usb/001/012 and Right clicking on the file.
Click on the Permissions tab and change the drop down menu to read and write.
Like 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"
}
help
followed the steps as you mentioned. But when i click on the flashtool script file nothing is happening.
pls help
M4ST3R-V said:
followed the steps as you mentioned. But when i click on the flashtool script file nothing is happening.
pls help
Click to expand...
Click to collapse
Open terminal and run flashtool and you'll see what is wrong
Sent from my Xperia X10 using xda app-developers app
thank you
Tof37 said:
Open terminal and run flashtool and you'll see what is wrong
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
thanks for the tip. Yes i Opened it in terminal with sudo su permission and got the error. lsusb version error was the probem and there was a and additional update to the latestet version searched a lot to find it. this solved most of this :good:
good, but work only in root users.
because flashtool do not recognize, my x10? i can only flash. is a problem of linux version?
can i use with xperia Neo V?
Sorry for stupid question,but i don't know very well Ubuntu!
Thank you! Will come in handy later!
linux mint xfce 17 (ubuntu 14)
Hi, would be this guide work on my system too? I am newbee in linux. Help me please.
Sory, my phone is Elephone P9, MTK6592
help
sudo apt-get install sun-java6-jre sun-java6-plugin sun-java6-fonts
hi when i type this
show me in terminal this message:
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
please help me
hi. when i write this:
sudo apt-get update
terminal show me this text!
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
this is true?
I got this error everytime i run FlashTool as root.
I can run FlashTool if i run it as normal user, but the access to phones are denied by system ._.
Please help me
Well this my first own post on General Section
I am sharing how to use the (ADB)
which seem many of us should have some basic on it
(FASTBOOT) will be added later on.
-SIMPLE & EASY-
Is a proper way to tell what wrong's and bug you encountered by a log
Requirement :
Click to expand...
Click to collapse
-Adb Driver for Xperia X8 or This Universal_Naked_Driver
-Adb files (Repacked for you)
-Android Version 1.6-4.1.1
Click to expand...
Click to collapse
Set Up
Click to expand...
Click to collapse
Install the Driver For Adb for your device (Example :X8)
Unpack the Adb Files To A Folder (Named Whatever you like Example: Adb) on local disk C: (Recommend)
Turn on USB debugging on your phone: Settings>Applications>Development>USB Debugging
Go to Start Menu and Search for CMD (Command Promt) (Run as adminstrator)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Prompt CMD with the location you extracted the ADB Files (Mine at C:/adb)
Therefore key in this
Code:
cd c:/adb
{
"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"
}
Check Connected Device & Enable the Adb Server
Code:
adb devices
Wait for few seconds till the server is up and if you connection is working
Should show that the device name is there
If connection is offline should check whether build.prop has this line :
Code:
persist.sys.usb.config=mass_storage,adb
Add this line to build.prop if you need to do so
ADB Logcat
When able to have adb connection between device then you
can now do a pretty simple logcat
Code:
adb logcat > logcatfilename.txt
Replace "logcatfilename" with anything you like and shall log all over the text file
Can then stop logging just pressing Ctrl+C
Enable Access to System
If Encountered that your system not mounted
Code:
adb remount
If some still keeping error then need to boot cwm to adb
ADB Shell
Adb Shell Is A Little Advance So No Really Gonna Cover Up Here
Prompted by
Code:
adb shell
Checking Memory/Swap Progress
Code:
free
You can remove app/files by
Code:
rm -r /filelocation/filename.format
Replace " /filelocation/filename.format" with anything you want to remove such as latimime.apk so you replace with /system/app/latimime.apk
Adb Pull
Now You Should Know To Command using CMD
To Pull
Code:
adb pull /system/app/browser.apk
Replace "l/system/app/browser.apk" with location and file name you want to pull
Adb Push
Now You Should Know To Command using CMD
To Pull
Code:
adb push browser.apk /system/app
Replace " browser.apk /system/app" with file name(On the same folder of the adb files) & location you want to push that file into.
Adb Install
Should be same as pushing method but normally to data folder
Code:
adb install angrybird.apk /data/app
Replace "angrybird.apk /data/app" with file name(On the same folder of the adb files) & location you want to install into
Final :
I hope this Tutorial Is Clear Enough For Other's member which want to
learn adb.You can use this tutorial & i know there many more better adb tutorial
but i am just showing basic knowledge logcat and adb command that can easier
both developers and user.Any Comment & Suggestion can reply below.
I will fix/add if needed.Sorry for bad english & grammar
Credits :
Dev Whom Teached Me Basic Adb
1wayjonny For Universal Naked Driver
pswd
What password for ADB archive?
nikmaletz55 said:
What password for ADB archive?
Click to expand...
Click to collapse
steriod << Password Sorry for missed out
Fastboot tutorial when there's free time :cyclops:
I can't download the GingerLewa.
@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?
fastboot...i think we dont have fastboot
sgt. meow said:
@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?
Click to expand...
Click to collapse
fotak-x said:
fastboot...i think we dont have fastboot
Click to expand...
Click to collapse
i make this for adb for X8 & Other phone as well
i know there no fastboot but maybe usable for otheer phoness