Related
Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator
This has been solved! Check at bottom for solution!
I have been looking around to find a way to unlock it simply, but nothing was possible.
I've enabled all development settings, it's SEMC SIMLOCK, it's still on R, I've even moved to other rom to try it to make it work, disabled AV, firewall, installed drivers, everything but NOTHING worked.
Here are logs (Flashtool 0.6.7.0 and generic msm7227 cmd file):
Code:
18/010/2012 01:10:57 - INFO - <- This level is successfully initialized
18/010/2012 01:10:58 - INFO - Flashtool Version 0.6.7.0 built on 2012-01-15 22:00:21
18/011/2012 01:11:06 - INFO - Device connected with USB debugging off
18/011/2012 01:11:06 - INFO - For 2011 devices line, be sure you are not in MTP mode
18/011/2012 01:11:08 - INFO - List of connected devices (Device Id) :
18/011/2012 01:11:08 - INFO - - USB\VID_0FCE&PID_2138\4342353131534C4E5235 Driver installed : true
18/011/2012 01:11:08 - INFO - - USB\VID_0FCE&PID_2138&MI_01\6&1A726446&0&0001 Driver installed : true
18/011/2012 01:11:08 - INFO - - USB\VID_0FCE&PID_2138&MI_00\6&1A726446&0&0000 Driver installed : true
18/011/2012 01:11:08 - INFO - List of ADB devices :
18/011/2012 01:11:09 - INFO - - 4342353131534C4E5235
[B]18/011/2012 01:11:09 - INFO - - emulator-5554[/B] [I]< What the hell is this!?[/I]
18/011/2012 01:11:09 - INFO - List of fastboot devices :
18/011/2012 01:11:09 - INFO - - none
Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Waiting ...
error: more than one device and emulator
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights
.
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Waiting ...
error: more than one device and emulator
Getting ROOT rights.
error: more than one device and emulator
Waiting ...
error: more than one device and emulator
Writing patched semcboot. Two step process
First, we need get access to semcboot area
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Second, we need to write semcboot ;)
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Press any key to continue . . .
I really want to know how to fix this damn thing because I've wasted 5 HOURS ON THIS and NOTHING WORKED.
Here's solution: Run CMD, and run adb -e reboot (forces all emulators to reboot), and make sure you don't have any other emulators by running command "adb devices". You'll have to check 3-4 times to be sure by terminating idle adb.exe in task manager.
Lets just go straight to the point :
Make sure that you've :
- Downloaded and extracted 'DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)' (ref : http://forum.xda-developers.com/showthread.php?t=1321582)
- Installed Android SDK to enable you to run ADB shell
- Enabled 'Unknown Sources' in your phone
- Enabled 'USB Debugging' in your phone
Step 1 :
- Open command line as Administrator and go to 'android-sdk/platform-tools' folder
- Run this command :
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf
- Leave the cmd windows open
Step 2 :
- Go to DooMLorD folder
- run 'runme.bat'
- press 'Enter' once and then once more
VOILA!!
p/s : You can close the 'cmd' windows now
Superoneclick method is better which dosent need android sdk installed
its just another way. no biggie
I rooted my O1 with Superoneclick and I recommend it , fast and safe
Sorry, where can i found superoneclick?
i have O1 with last ginger update, it's compatible?
kyrulamri said:
Lets just go straight to the point :
Make sure that you've :
- Downloaded and extracted 'DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)' (ref : http://forum.xda-developers.com/showthread.php?t=1321582)
- Installed Android SDK to enable you to run ADB shell
- Enabled 'Unknown Sources' in your phone
- Enabled 'USB Debugging' in your phone
Step 1 :
- Open command line as Administrator and go to 'android-sdk/platform-tools' folder
- Run this command :
adb devices (after this command you should see your device id)
adb shell
echo 1 > /data/local/lge_adb.conf
- Leave the cmd windows open
Step 2 :
- Go to DooMLorD folder
- run 'runme.bat'
- press 'Enter' once and then once more
VOILA!!
p/s : You can close the 'cmd' windows now
Click to expand...
Click to collapse
Superoneclick has zergRush exploit in it and more.
Anyone wanting to root their phone or flash baseband go into my guide, link is in my signature
Hi mates¡
First of all, sorry for my english.
I didnt want open a thread for my issue but i cant find anthing thath work for me. I began to comment the issue at Pandemic's thread (it's the guide that I below to flash). When I read the answers is like my problem is so weird...
Well, my setup:
* Neo Mt15i with 0.62 stock
* Pc with a clean installation of Ubuntu 12.04
* I installed Java JDK with this Guide:
http://forums.team-nocturnal.com/showthread.php/772
* I installed ADB with that:
http://forums.team-nocturnal.com/showthread.php/773
After that, I add tu /udev/rules/ with my IDVENDOR and IDPRODUCT (I get it using the terminal using "$ lsusb". I readed it from a guide at XDA but cant find now, later I will edit this and add the link ) the line from flashtool web:
Add these rules to /etc/udev :
SUBSYSTEM=="usb", ACTION=="add", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="*", MODE="0777"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
* Download Flashtool 0.6.9.1;M check Md5 (OK) and extrac in home folder (my user folder)
* Download 2 differents files of firmware 0.42 GLOBAL for MT15i; I cant find the MD5 of those
PROCESS
Well, doing all of that Flashtool can recognise my Neo ON with Usb debbuging ON; third applications ON; MSC ON
FLASHTOOL LOG:
02/058/2012 11:58:14 - INFO - <- This level is successfully initialized
02/058/2012 11:58:14 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:43:11
02/058/2012 11:58:14 - INFO - You can drag and drop ftf files here to start flashing them
02/058/2012 11:58:19 - INFO - Device disconnected
02/058/2012 11:58:28 - INFO - Device connected with USB debugging off
02/058/2012 11:58:28 - INFO - For 2011 devices line, be sure you are not in MTP mode
02/058/2012 11:58:29 - INFO - Device connected with USB debugging on
02/058/2012 11:58:30 - INFO - Connected device : MT15
02/058/2012 11:58:30 - INFO - Installed version of busybox : N/A
02/058/2012 11:58:30 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
Click to expand...
Click to collapse
Afterthat click flash; select Firmware (on fw folder) and connect the phone on FLASHMODE when the prompt order and thats its my LOG:
02/058/2012 11:58:54 - INFO - Device disconnected
02/059/2012 11:59:10 - INFO - Selected MT15i_4.0.2.A.0.42_Global.ftf
02/059/2012 11:59:10 - INFO - Preparing files for flashing
02/059/2012 11:59:12 - INFO - Please connect your device into flashmode.
02/059/2012 11:59:17 - INFO - Device connected in flash mode
02/059/2012 11:59:17 - INFO - Phone ready for flashmode operations.
02/059/2012 11:59:17 - INFO - Start Flashing
02/059/2012 11:59:17 - INFO - Flashing loader
02/059/2012 11:59:19 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : NOT_ROOTABLE
02/059/2012 11:59:19 - INFO - Flashing adsp.sin
02/059/2012 11:59:23 - INFO - Ending flash session
02/059/2012 11:59:39 - ERROR - Transferred 41472 bytes of 65536
02/059/2012 11:59:39 - ERROR - Error flashing. Aborted
02/059/2012 11:59:40 - INFO - Device disconnected
Click to expand...
Click to collapse
I must to unplug the NEO because it dont work. When I do this LOG its the 10 time i tried, and never works, even I wait for half hour. Thats because I didnt wait this time, always its the same...
I will update that with SCREENSHOTS later... For a easier understanding.
* I must use a virtual machine to install SEUS or PCCOMPANION, because of that I create that with VIRTUAL BOX and install winXP. I try flashtool here too.
I installed JavaJDK; SDK; DRIVERS from drivers folder of Flashtool.
No works either...The same result
I think to create another VM with win7 to try on that but i will do it later.
Thats all my problem, i dont know what more I can do...Could you help me??
Many many thanks for all those wath read the long text and dont get tired of my english.
Your udev rules is flaky, flashtool is a more than just adb.
Use the one from here
http://forum.xda-developers.com/showthread.php?p=25511424
Also don't connect the phone till it tells you
Sent from my MT11i using Tapatalk
Thanks for the fast answer.
In the link that you wrote before there are another link of minus,and those are dead links...
My android rules in udev have more info, I copy that of the link I posted before about install ADB. At final of these links I write that one of FLAHTOOL web. I found another three lines to write here but im not at pc and I havent the links here... This three lines was writed for a Spanish xdader at a thread its the only thing I remember.
Later I will post the link and my android rules.
Any idea for now?
Sent from my MT15i using XDA
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Sorry men, its true, I check ir fast and didnt think too much...tomorrow I will try them on pc.
I will search info about these files because I dont know anything,
There are another thread talking about them, or an howto install them?? Im not at pc and search here its worth....
Im so noob at linux too
But I learn fast when something its interesting to me, and ubuntu surprise so much to me.
Many many thanks for your help
Sent from my MT15i using XDA
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
mpiekp said:
The link is not dead, click standard view, then back then refresh it will work
Sent from my MT11i using Tapatalk
Click to expand...
Click to collapse
I change my android.rule file, I put yours one. Continue cant flashing, and when I connect with the phone ON Flashtool recognise it, and ADB too (with "$ adb devices").
The first one I have was three lines (one/conecction mode) which I get from this thread:
http://forum.xda-developers.com/showthread.php?t=1612273
Thats one is my actual 99-android.rules
http://tinypaste.com/91108a48
yacloo said:
which language installed on your ubuntu is it non-english
exactly flashtool have some issues on non-english OS
you can put this line on flashtool executable file
export LANG=en_US.UTF-8
than flashtool will work fine
EDIT:flashtool was updated to 0.7.1.0 you can get it from here
Click to expand...
Click to collapse
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
I see now that always that I unplugg the phone flashtool first say that is in Usb debuging OFF and then says thats its ON,,,I saw it on other thread (which i cant found for now)
With the new version of Flashtool i have always the same problem:
04/000/2012 05:00:01 - INFO - <- This level is successfully initialized
04/000/2012 05:00:01 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/000/2012 05:00:01 - INFO - You can drag and drop ftf files here to start flashing them
04/000/2012 05:00:01 - INFO - Device disconnected
04/000/2012 05:00:11 - INFO - Selected MT15i_4.0.2.A.0.42_Vodafone.ftf
04/000/2012 05:00:11 - INFO - Preparing files for flashing
04/000/2012 05:00:11 - INFO - Please connect your device into flashmode.
04/000/2012 05:00:16 - INFO - Device connected in flash mode
04/000/2012 05:00:17 - INFO - Reading device information
04/000/2012 05:00:37 - INFO - Start Flashing
04/000/2012 05:00:37 - INFO - Flashing loader
04/000/2012 05:00:37 - INFO - Ending flash session
04/000/2012 05:00:37 - ERROR -
04/000/2012 05:00:37 - ERROR - Error flashing. Aborted
04/000/2012 05:00:37 - INFO - Device disconnected
Click to expand...
Click to collapse
With olders flashtools have same issues that before, starts but stops randomly...nothing changes after all...for now I hope.
The ways off today:
* 3 FTF 0.42 global and vodafone for MT15i
* 3 versions of FLASHTOOL (all with md5 OK)
* Repeat after fail, dont use before SEUS
* Ubuntu and Winxp on VM
Thanks for all the support
pollolpc said:
Thanks men, I have spanish language installed on Ubuntu, and i havent any idea of where I have to put that line of code when I open it with gEdit.
could I change my language now for that?
Click to expand...
Click to collapse
open FlashTool file and your file must look like this
#!/bin/sh
export BASEDIR=$(dirname $0)
export system64=$(uname -m)
export LANG=en_US.UTF-8
if test -z "${JAVA_HOME}"
then
if test "${system64}" = "x86_64"
then
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre64
else
export JAVA_HOME=${BASEDIR}/x10flasher_lib/linjre32
fi
echo "JAVA_HOME not set. Using default value : ${JAVA_HOME}"
fi
chmod 755 ${BASEDIR}/x10flasher_lib/adb.linux
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.linux
chmod 755 ${BASEDIR}/x10flasher_lib/adb.mac
chmod 755 ${BASEDIR}/x10flasher_lib/fastboot.mac
if test -e ${JAVA_HOME}/bin/java
then
$JAVA_HOME/bin/java -Xms128m -Xmx512m -jar x10flasher.jar
else
echo "No Java in specified path in JAVA_HOME=${JAVA_HOME}"
echo "Set the variable to a valid Java installation"
fi
Click to expand...
Click to collapse
Because I didnt knew how insert that line in FLASHTOOL i tried to do other thing; change language on a terminal wich will run flashtool....i dont have idea if this is stupid....but i tried, nothing to loose i thinked....
"change the language with that :
$ export LANG=en_US.UTF-8
Click to expand...
Click to collapse
I copied the info give me the terminal, i didnt know if this could be helpful...
Post at tiny paste for a cleaner post:
http://tinypaste.com/38e38b82
yacloo said:
open FlashTool file and your file must look like this
Click to expand...
Click to collapse
Ok many many thanks, i give a try richt now
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
pollolpc said:
Didnt work bro, try to start flashing but stops suddenly without flash any file. Before didnt try flash, stops at READ DEVICE...
Heres the log:
http://tinypaste.com/37c68abc
Thanks a lot for your attention
Click to expand...
Click to collapse
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
yacloo said:
I think you are using 64-bit ubuntu
Check that libusb-1.0 is installed. On 64bits system, both 64bit and 32bit should be installed
hope can work
Click to expand...
Click to collapse
Im usin 64 bits, yes. I think I installed them...I check Synaptics:
Uploaded with ImageShack.us
Both ticked from bottom no?
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
yacloo said:
I think only 64bit libusb installed
You can get it those files for 32 bit from packages.ubuntu.com
Both files are same low versioned one for old applications
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
You could install the 32-bit packages for these libraries:
$ sudo apt-get install libusb-dev:i386 libX11-dev:i386
Note, however, that this will remove the 64-bit versions. Probably it's better to use a chroot (e.g. with cowbuilder or pbuilder) or Qemu image for this kind of thing. E.g. create the file ~/.pbuilderrc-precise-i386:
# Set this to the distribution you want to build for
DISTRIBUTION=precise
# The architecture you want to build for
ARCHITECTURE=i386
# The directory in which to store the chroot base image
BASEPATH=/var/cache/pbuilder/base-precise-i386.cow
# The repositories to be enabled in the /etc/apt/sources.list
COMPONENTS="main universe"
# If you want to speed things up with ccache, enable these options
export CCACHE_DIR="/var/cache/pbuilder/ccache"
export PATH="/usr/lib/ccache:${PATH}"
# List here all packages you need to build your software
# (e.g. build-essential, libusb-dev, libX11-dev, etc.)
EXTRAPACKAGES=ccache
# List here all directories from you system that should be visible inside the chroot
BINDMOUNTS="${CCACHE_DIR} ${HOME}/projects"
Then install cowbuilder and create the base image as follows:
$ sudo apt-get install cowbuilder
$ sudo cowbuilder --create --configfile ~/.pbuilderrc-precise-i386
Lastly, enter the chroot and finish configuring it (copy over configuration files:
$ sudo cowbuilder --login --save-after-exec --configfile ~/.pbuilderrc-precise-i386
You can exit the chroot using Ctrl+D or using exit. Now you have set up your base-image. In the future, don't use the --save-after-exec flag any more when entering the chroot. This ensures that all the modifications will be discarded after you leave the chroot, ensuring a clean build environment for future builds.
Now you should be able to enter the chroot and build your software:
$ sudo cowbuilder --login --configfile ~/.pbuilderrc-precise-i386
% cd $HOME/projects/foo
% # build project foo
Note, however, that the files created in this way will be owned by root. Hence, out-of-source builds are a very good idea.
Click to expand...
Click to collapse
I dont know what to do
pollolpc said:
Im reading about this, i found that if I install 32 bits package, uninstall 64 bits....that isnt a problem? ... I found this in another forum:
http://askubuntu.com/questions/127701/gcc-m32-cannot-find-libraries
I dont know what to do
Click to expand...
Click to collapse
That was ia32 lib issue install both files and ia32 lib file other 64 ones will not be removed
Sent from my MT11i using XDA
I check that with this: $ dpkg -l libusb\* and I have this versions:
||/ Nombre Versión Descripción
+++-==============-==============-============================================
ii libusb-0.1-4 2:0.1.12-20 userspace USB programming library
ii libusb-1.0-0 2:1.0.9~rc3-2u userspace USB programming library
un libusb-1.0-0-d <ninguna> (no hay ninguna descripción disponible)
un libusb0 <ninguna> (no hay ninguna descripción disponible)
ii libusbmuxd1 1.0.7-2 USB multiplexor daemon for iPhone and iPod T
Click to expand...
Click to collapse
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
...I have an update avaiable ny OTA....The 0.62...and my about section sqy 0.62 too..:banghead:
Sent from my MT15i using XDA
pollolpc said:
I check that with this: $ dpkg -l libusb\* and I have this versions:
0,1.4 is 32 bits or im wrong again?
The last version of flashtool say that:
04/015/2012 07:15:07 - INFO - <- This level is successfully initialized
04/015/2012 07:15:07 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:14
04/015/2012 07:15:07 - INFO - You can drag and drop ftf files here to start flashing them
04/015/2012 07:15:08 - INFO - Device connected with USB debugging on
04/015/2012 07:15:09 - INFO - Connected device : MT15
04/015/2012 07:15:09 - INFO - Installed version of busybox : N/A
04/015/2012 07:15:09 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
04/015/2012 07:15:09 - INFO - Phone in recovery mode
04/015/2012 07:15:09 - INFO - Root Access Allowed
WTF? Im still at 0.62 on "about"
Sorry for be worried
Click to expand...
Click to collapse
download those files and install via dpkg -i *.deb
libusb-0.1-4_0.1.12-20_i386.deb
libusb-1.0-0_1.0.9~rc3-2ubuntu1_i386.deb
and you have to search on synaptic for ia32-libs and ia32-libs-multiarch
than install those packages
if doesn't work switch to 32bit ubuntu or 32bit windows for better compatibility
It's working fine here on 64 12.4
If the above doesn't work, I'll post a list of installed packages, should sort you out
Sent from my MT11i using Tapatalk
These are the Qualcomm CDMA Technologies MSM Windows Vista 32-bit drivers for those of you who are having trouble installing the drivers. I have only noticed this problem on Windows Vista, and therefore I have created this thread.
I have only tested the below procedure on Windows Vista 32-bit.
Please note that I am not responsible for any damages caused to your windows system as a result of wrongly in putting the codes below.
Also note that following the installation of the drivers by this method may result in Test Mode being displayed on your desktop wallpaper.
Let’s get started:
1) Download, extract and place the Qualcomm folder on your desktop.
Installing the certificate:
2) Double click on “qcusbtest.cer” and open it.
3) Click on “Install Certificate.”
4) Select “Place certificate in the following stores”
5) Place the certificate in “Trusted Root Certification Authorities.”
6) Click Next, then Finish.
7) Follow steps 2 to 4
8) Place the certificate in “Trusted Publishers”
9) Click Next, then Finish.
10) Run Command Prompt as administrator (Start>Type “Command Prompt”>Right-click on command prompt and select “Run as administrator”)
In the below steps replace the red [insert] boxes with the relevant configurations of your system.
Next:
11) On command prompt type:
Code:
cd C:\Users\[COLOR="Red"][Insert Your Windows Username Here][/COLOR]\Desktop\Qualcomm CDMA Technologies MSM\Drivers
12) Then type:
Code:
PnPUtil -i -a msmdm.inf
13) You should receive a success message.
14) Repeat for the other .inf files type:
Code:
PnPUtil -i -a qcmdm.inf
and then type:
Code:
PnPUtil -i -a qcser.inf
15) Reboot your PC
Now you should have the Qualcomm CDMA Technologies MSM drivers installed.
What is it for?
ybregeon said:
What is it for?
Click to expand...
Click to collapse
How to install Qualcomm Drivers for people who are having trouble installing the drivers.
Just explain that you mean the PC drivers. Some might get confused and think you mean Qualcomm bootloaders in the phone.
Sent from my Lumia 800 using XDA Windows Phone 7 App
for xp??
ok i am with nokia lumia 710 and i am trying to write new os,but it wants this drivers "qualcomm cdma technologies msm" pls help,i am on xp,my phone have unlocked qualcomm bootloader
info
hi.
I succeeded in no way, unfortunately the third already does not settle. but Windows 7 64 bits of my system yes. May this be the trouble?
PnPUtil -i -a msmdm.inf (installed o.k.)
PnPUtil -i -a qcmdm.inf (installed o.k.)
PnPUtil -i -a qcser.inf (not installed, platform compatibility problem. )
i very sad! i flashed (my lumia 710 prototype rainbow rom with lumia 710 douwnloader. the rom is okay, but i have no call sound!!!! i want the original firmware . but nss not see the lumia help
Adrammelech said:
PnPUtil -i -a qcser.inf (not installed, platform compatibility problem. )
Click to expand...
Click to collapse
looks like you need x64 drivers...
Worked on x64 Windows 7. Thanks very much for this
hasn't worked for me, still shows up as drivers not installed in Device Manager. When I point towards the files it doesn't accept them or if I do a computer/internet search. Just says driver cannot be found.
Any ideas?
---------- Post added at 10:07 PM ---------- Previous post was at 10:03 PM ----------
RHodgett said:
hasn't worked for me, still shows up as drivers not installed in Device Manager. When I point towards the files it doesn't accept them or if I do a computer/internet search. Just says driver cannot be found.
Any ideas?
Click to expand...
Click to collapse
I should say I am running Windows 7 64bit.
Confirmed that work on Windows 8 dev preview and customers preview with Vista drivers (x86)
Hey, I've done the commands you gave.. All drivers installed correctly like you said.. But When I plug in my lumia 800 windows says it can't find the drivers
What can I do?
Yours sincereley,
Shabo09 said:
Hey, I've done the commands you gave.. All drivers installed correctly like you said.. But When I plug in my lumia 800 windows says it can't find the drivers
What can I do?
Yours sincereley,
Click to expand...
Click to collapse
does your phone come up as a flash disc in restore mode if it doesnt then you dont have a unlocked bootloader regardless if its a qualcomm, there were 2 versions from what i can gather one allows nand access and one doesnt sounds like you have the one that does not
rob:good:
I have problem only with the installation of this....
PnPUtil -i -a qcser.inf
When i try to install this, receive this message:
Can not install the drivers for any of the devices in the system: exhausted the available data (translated from italian)
I need only of this driver for flash, I have an unlocked NAND
OS Windows 7 x64
bombolo85 said:
I have problem only with the installation of this....
PnPUtil -i -a qcser.inf
When i try to install this, receive this message:
Can not install the drivers for any of the devices in the system: exhausted the available data (translated from italian)
I need only of this driver for flash, I have an unlocked NAND
OS Windows 7 x64
Click to expand...
Click to collapse
you dont need the drivers to flash put the phone into nand mode vol+ and power short vibration then plug usb, either flash in linux or in nss
rob:good:
moaster7 said:
These are the Qualcomm CDMA Technologies MSM Windows Vista 32-bit drivers for those of you who are having trouble installing the drivers. I have only noticed this problem on Windows Vista, and therefore I have created this thread.
I have only tested the below procedure on Windows Vista 32-bit.
Please note that I am not responsible for any damages caused to your windows system as a result of wrongly in putting the codes below.
Also note that following the installation of the drivers by this method may result in Test Mode being displayed on your desktop wallpaper.
Let’s get started:
1) Download, extract and place the Qualcomm folder on your desktop.
Installing the certificate:
2) Double click on “qcusbtest.cer” and open it.
3) Click on “Install Certificate.”
4) Select “Place certificate in the following stores”
5) Place the certificate in “Trusted Root Certification Authorities.”
6) Click Next, then Finish.
7) Follow steps 2 to 4
8) Place the certificate in “Trusted Publishers”
9) Click Next, then Finish.
10) Run Command Prompt as administrator (Start>Type “Command Prompt”>Right-click on command prompt and select “Run as administrator”)
In the below steps replace the red [insert] boxes with the relevant configurations of your system.
Next:
11) On command prompt type:
Code:
cd C:\Users\[COLOR="Red"][Insert Your Windows Username Here][/COLOR]\Desktop\Qualcomm CDMA Technologies MSM\Drivers
12) Then type:
Code:
PnPUtil -i -a msmdm.inf
13) You should receive a success message.
14) Repeat for the other .inf files type:
Code:
PnPUtil -i -a qcmdm.inf
and then type:
Code:
PnPUtil -i -a qcser.inf
15) Reboot your PC
Now you should have the Qualcomm CDMA Technologies MSM drivers installed.
Click to expand...
Click to collapse
---
Hello
Does anyone know why I get the following error?
Processing inf : qcmdm.inf
Adding the driver package failed : Access is denied.
Adding at least one driver package failed!
kian1234 said:
---
Hello
Does anyone know why I get the following error?
Processing inf : qcmdm.inf
Adding the driver package failed : Access is denied.
Adding at least one driver package failed!
Click to expand...
Click to collapse
Are you the admin or have the administrators rights to install drivers.
check that 1st.
I got the same 800 with Qualcom CDMA technologies MSM ... so can I flash and full unlock my 800????
I still get Certificate issues after installing your certificate.
Start command prompt as admin and type "shutdown -o -r -t 0"
disable driver signatures
Now installed drivers fine, going to restart now hope it works
Using windows 8 x64
After installed this drivers NSS pro didnt recognize my lumia 710
before driver
when i click on "READ INFO" it answer me correct
now
Checking selection...Supported(USB) interface selected.
Init connection...Done.
----------------------------------------------------------------------
Phone details:
-----------------
NCSD Version: N/A
SW Version: N/A
HW Version: N/A
IMEI: N/A
Product Code: N/A
Basic Product Code: N/A
Module Code: N/A
Production SN: N/A
Battery life: N/A
Number of Nams: N/A
Number of Mins: N/A
ESN: N/A
ESN Decoded: N/A
PRL Version: N/A
Battery Charge Capacity: N/A
Battery Full Capacity: N/A
Battery Cycle Count: N/A
Battery Temperature: N/A
Battery Voltage: N/A
Battery State of Charge: N/A
Battery Average Current: N/A
Battery Flags: N/A
Battery Standby Current: N/A
Battery MaxLoad Current: N/A
Battery Health State: N/A
Battery Nominal Capacity: N/A
Battery Remaining Capacity: N/A
any suggestions?
regards
moaster7 said:
These are the Qualcomm CDMA Technologies MSM Windows Vista 32-bit drivers for those of you who are having trouble installing the drivers. I have only noticed this problem on Windows Vista, and therefore I have created this thread.
I have only tested the below procedure on Windows Vista 32-bit.
Please note that I am not responsible for any damages caused to your windows system as a result of wrongly in putting the codes below.
Also note that following the installation of the drivers by this method may result in Test Mode being displayed on your desktop wallpaper.
Let’s get started:
1) Download, extract and place the Qualcomm folder on your desktop.
Installing the certificate:
2) Double click on “qcusbtest.cer” and open it.
3) Click on “Install Certificate.”
4) Select “Place certificate in the following stores”
5) Place the certificate in “Trusted Root Certification Authorities.”
6) Click Next, then Finish.
7) Follow steps 2 to 4
8) Place the certificate in “Trusted Publishers”
9) Click Next, then Finish.
10) Run Command Prompt as administrator (Start>Type “Command Prompt”>Right-click on command prompt and select “Run as administrator”)
In the below steps replace the red [insert] boxes with the relevant configurations of your system.
Next:
11) On command prompt type:
Code:
cd C:\Users\[COLOR="Red"][Insert Your Windows Username Here][/COLOR]\Desktop\Qualcomm CDMA Technologies MSM\Drivers
12) Then type:
Code:
PnPUtil -i -a msmdm.inf
13) You should receive a success message.
14) Repeat for the other .inf files type:
Code:
PnPUtil -i -a qcmdm.inf
and then type:
Code:
PnPUtil -i -a qcser.inf
15) Reboot your PC
Now you should have the Qualcomm CDMA Technologies MSM drivers installed.
Click to expand...
Click to collapse
seem to be having a problem while installing those inf files through cmd
getting the following message -
Adding the driver package failed : Invalid INF passed as parameter.
Total attempted: 0
Number successfully imported: 0