I have installed Google Nexus 7 Toolkit on my PC.
When it runs and I select YES to check for new update I get the following message:-
"Starting ADB ... daemon not running: starting it now on port 5037 daemon started successfully Do you want to check if an Update is available [type yes or no]? checking update availability. Update server cannot be located. Check your internet connection and try again. Continuing normal toolkit operations."
My internet connection is fine.
I need to update as I am running 4.2.2 on my Nexus 7 and 4.2.2 does not feature on the toolkit list.
I am happy to donate which I have tried but that does not work either.
Thank you.
Related
Hi!
I have (had maybe) officail Android 2.1 with sense. Yesterday an OTA update showed up, so I updated the system and the phone is now down.
System doesn't start at all... Only HTC logo shows up, I can't flash any official HTC rom.
Errors:
140: wrong bootloader version, 131: wrong client ID
the only error information from HTC phone is... as I show on picture... very informative and descriptive
I've tried 6 offficial update rom's from HTC.
The phone error statement is red error sign...
Graphic, no text :/
I attached a photo with this
All the thing is quite recent, any ideas?
Cheers!
Paweł Lipko
What you need to do is download the android recovery system, see my sig (RA-hero-v1.7.0.1 Recovery). Install that and then let us no when you have. This will enable you do do other things and then we can go from there.
Hi again!
At the beginning I would like to say thanx for help
Ok following "RA-hero-v1.7.0.1 Recovery" thread I've downloaded SDK with ADB.
To be correct with the timeline, I'll tell that this PC already has got HTC drivers coming with HTCSync software. Probably I write too much, but it's better to have too much of information than too less
Before the problemm which we are trying to solve here - phone worked fine with windows. Now XP says, that "device hasn't been recognized succesfully and the gear could not work correct. (I don't know english version for that, Polish Windows I have )
Next - ADB doesn't see the phone:
\Android SDK\tools>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Restarting windows - doesn't help
Trying to list devices in ADB - none
restarting AB daemon - doesn't help
Removing HTC Drivers and HTC sync (it was old version for android v.1.5 and 1.6. Still it worked before disaster with 2.1 )
Rebooting XP
Installing HTC Sync for Android 2.x. This include: HTC BMP USB Driver 1.0.5375 (32Bit), HTC Driver Installer 2.0.7.018
After installation new HTC Sync, XP says that it recognized the phone correctly, but still I have no access to SD Card storage. Only drive letter shows up. Lets take it as progress
still yet ADB gives output:
\Android SDK\tools>adb shell reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've tried to puty the same command with FastBoot and HBoot - but - nothing new comes with that...
At this level I think I'm stuck.
knock knock - any ideas?
What operating system are you running? Definatly a driver issue.
Windows XP SP3 Polish ver.
HTC Drivers as I wrote earlier - latest from htc.com
As for now I'm downloading HTC Sync also for older Androids - 1.5 and 1.6.
I'll try to remove this HTC Sync for And 2.1 with drivers and install that for 1.5 & 1.6.
If You say, it's a drivers issue - maybe there is a mess on my PC, I'll try using another one or two with both HTC Sync versions and give You a reply.
But when the disaster happened I tried to flash Hero with official ROM and I've had only info's like error 131 or 140 - as I mentioned at the beginning.
And it was other PC, with brand new HTC Sync, so the driver problem could be... no the clue...
I'll post when I'll try to install HTC Sync on other PCs.
Cheers!
Paweł
Shadow_82 said:
Windows XP SP3 Polish ver.
HTC Drivers as I wrote earlier - latest from htc.com
As for now I'm downloading HTC Sync also for older Androids - 1.5 and 1.6.
I'll try to remove this HTC Sync for And 2.1 with drivers and install that for 1.5 & 1.6.
If You say, it's a drivers issue - maybe there is a mess on my PC, I'll try using another one or two with both HTC Sync versions and give You a reply.
But when the disaster happened I tried to flash Hero with official ROM and I've had only info's like error 131 or 140 - as I mentioned at the beginning.
And it was other PC, with brand new HTC Sync, so the driver problem could be... no the clue...
I'll post when I'll try to install HTC Sync on other PCs.
Cheers!
Paweł
Click to expand...
Click to collapse
ah in that case error 131 or 140 is nothing to do with drivers, for error 140 as far as I know the ROM is not compatible. You will need to try find a version that is suitable. try the HTC website for updates.
Hmm.. You say that it's not drivers problem?
Well...
I already tried to flash these ROM's listed from XDA Developers:
[ROM] Official HTC Hero RUU ROM + Radio Links
WWE: (World Wide English)
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_ NoDriver.exe
RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe
RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe
RUU_Hero_HTC_WWE_2.73.405.61_WWE_test_signed_NoDri ver.exe
RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe
I've tried also ROMs from official htc.com website.Europe website and Polish website - still its the same, but when something doesn't want to work...
ROM version 2.73.405.5
All of them gave me errors:
140: wrong bootloader version,
131: wrong client ID.
All of these ROM's weren't able to say which version currently is installed on my HTC Hero...
Total HTC Hero Eclipse
I'll try to flash them once again, right now I take my pendrive, I'll go to my friend and let's roll
God damn it - another Q - by the way
How I'll be checked to be able to post external links?
Should I ask some moderators?
Or it'll happen just like that in a month or year?
ok.
another PC, completetly not known to this HTC Hero.
first windows told me that it doesn't recognize the phone. It's ok. it doesn't have any drivers.
I've installed latest HTC Sync with drivers - the one for Android 1.5 and 1.6, filename:
_HTC Legend_HTC_Sync 2.0.40.exe
Rebooting windows and...
Windows still doesn't recognize the phone
Trying to flash it with one of official ROMs
Yup - error 170 - no connection with phone
adb devices - no devices...
next: uninstalling this HTC Sync
rebooting windows
installing new one for android 2.1
filename: _HTC Wildfire_setup_3.0.5422.exe
rebooting windows
once again windows doesn't recognize the phone
Trying to flash it with official ROM
filename: RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
Connection error... damn...
ADB:
\HTC SDK\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
After some fight with USB I managed to make Windows recognize the phone, a drive letter shows up, but I can't acces data on SDCard.
ADB after restarting it's daemon doesn't see the phone
Another try to flash it with official ROM
ok. there's any progress - RUU App sees the version on the phone
trying to flash the phone
and... error 140 - wrong bootloader ver.
ADB: error: device not found
I'm starting to be confused...
Any ideas?
SuperOneClick v1.7.0.0
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
error: closed
FAILED
theskipshow said:
SuperOneClick v1.7.0.0
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
error: closed
FAILED
Click to expand...
Click to collapse
you have pdanet installed?
You need too use soc 1.5.5 with rage
Sent from my Dell Streak 7
theskipshow,
Here are some suggestions
Hi,
i struggled with the same problem, but at the end i found a solution.
First of all, you have to install 2 app from dell.com
Navigate to dell.com, go to drivers & downloads, then choose Support for home users and choose your device.
You get a list of 4 files. what you need is:
- Dell Aplication - Dell PC suite for Android 1.6
- Dell Driver - Dell mobile sync powered by nero for Android 2.2
Install both of them - one will "take control" of the phone when off, the second when its turned on (you will see later )
Turn off your phone, then start superoneclick, it will start the daemon and when it says waiting for device, simply turn it on and wait for a minute. When it will be booted to a state super one click will continue.
If you dont have the old driver from 1.6, superoneclick will not even start the daemon as it will not see your phone...
PS: this is a solution that works under Vista and win7, where the proprietary ADB driver is loading automatically, but our beautiful, wonderfull, adorable Dell shxt does not work correctly with it.
theskipshow said:
SuperOneClick v1.7.0.0
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
error: closed
FAILED
Click to expand...
Click to collapse
Make sure you have selected development under applications.
Turn streak off leave plugged in.
Start one click select rage against the cage
Wait till you see waiting for device
Start the streak
It will root during the boot process.
Big Thank you!!
Just wanted to say thanks for the hand holding. Would never have got it done. Rooted and all is good with the android world today
I followed the instructions in this thread and opened the file to confirm the changes (0x54c) was there, but my Sony S1 still isn't showing up in my Android Device Chooser when I run my applications. Rebooted computer, Eclipse, Tablet...
If I can't get it to show up, I'll be sending it back for a Galaxy 10.1, so bit of a time window here. Any ideas greatly appreciated.
Sorry for posting this here, but I'm not allowed to comment in the dev threads yet.
So I made it to the Sony Android Developer Program site and download and downloaded the development kit. Followed instructions in the very poorly made guide... no dice.
Talked with Sony support who said I should talk to Eclipse. At my wits end here, might just send it back and get a Galaxy Tab.
Those of you who have gotten the Tablet to connect with Eclipse - what version of OSX are you on? I'm on Lion and it seems some others have had similar issues since upgrading.
Ok, so I finally got it working! After adding 0x054c to your adb_usb.ini I had to kill ADB and restart it. However ./adb kill-server and then trying to ./adb start-server was giving me errors and refused to start. I had to do ./adb nodaemon server ADB_TRACE=ALL
After this, the tablet is FINALLY showing up in Eclipse.
Hi,
I initially started out debugging with GDB and got to a point where I wanted to be able to step into an android module/device driver. I could never successfully do it with it GDB so I did lots of searching and found out about KGDB which from all accounts is supposed to be the preferred way of debugging the kernel and modules in Linux based machines. I went through the exercise of getting KGDB cross compiled and inserted on my device and that part went ok. When I try to communicate to the device via GDB (target remote /dev/ttyHSL0) I get a device not found error message even though the file is there when I look at it via adb.
(gdb) target remote /dev/ttyHSL0
/dev/ttyHSL0: No such file or directory.
After doing more investigation and thinking about things a little we know that the way to communicate via an Android handset is with adb so this in itself is probably an indication as to why it's difficult to communicate to the device via KGDB.
Does anyone have any up to date or successful instructions on how to connect to a handset using KGDB?
Thanks
basically im trying to recover data on this phone but the tenorshare app requires rooting.
so i have tried rooting and failed. it got stuck and windows forced close.
* daemon not running. starting it now on port 5037 *
* daemon started successfully
i had enabled debugging. what is wrong ? i am rooting for the 1st time ever