Does anyone know were I can find a command line program that will work on wm2005, I tried installing pocket cmd , that worked on ppc 2003, but it did not work on wm2005,
thanks cheers
any update???? I wnat the CDM and telnet too!!!!
me too!
How can they take such an important piece 'out'.
I know it's not exactly out, since you had to put it into earlier versions of windows-mobile your self by downloading the "Windows Mobile Developer Power Toys"
a link here:
http://www.microsoft.com/downloads/...d6-1dcc-47aa-ab28-6a2b006edfe9&DisplayLang=en
i tried to install this anyway for wm2005, yet no success -- i might have overlooked something though.
i want this shell to play with ruby (a programming language) on my vario (htc wizzard).
lets hope it will show up soon!
cies breijs.
tried even more
i tried to install (on a Wizard; windows mobile 5) the following:
PocketConcole (only a drive or something)
http://www.symbolictools.de/public/pocketconsole/index.htm
plus
CMD (form here):
http://www.symbolictools.de/public/pocketconsole/applications/cmd/index.htm
and
PocketCMD:
http://www.symbolictools.de/public/pocketconsole/applications/PocketCMD/index.htm
i also tried the PowerTool CMD as mentioned earlier again.
NO SUCCESS.
i just want a little terminal window for starting Ruby!
(and i hate windows, MCF, programming)
still hoping!
cies breijs.
Any success with TelnetD & Console?
Hi!
Did anybody have any success with TelnetD running on WM 5.0? I have also tried Symbolic Tools' packages with no success. But I would still like to have access to the device through telnet & command line.
Cheers,
Ondrej
http://forum.xda-developers.com/showthread.php?t=275019&highlight=console
havent gotten it to work myself but havent made that much of an efford yet
PocketCMD OK on WM6...
Following the solution I posted a while ago (link in post above), I confirm this is still working on WM6/Wizard.
First install pocketconsole, reboot, modify registry, install pocketcmd, nettools and telnet.
Verify de change in registry is still there...
Cheers,
Hal
Pocket CMD and Nettools
Hi Hal, can you give me a url where I can download the Nettools for pocket console, just try to simbolyc.de but the site is not available
thanks
draguz
draguz said:
Hi Hal, can you give me a url where I can download the Nettools for pocket console, just try to simbolyc.de but the site is not available
thanks
draguz
Click to expand...
Click to collapse
Dear Draguz,
Have you found the Nettools for pocket console ? I'm searching for it too, but without success
Thanks for your answer !
http://www.google.dk/search?hl=da&q="Nettools"+pocketpc&btnG=Søg&meta=lr=lang_da|lang_en
´`?
Rudegar said:
http://www.google.dk/search?hl=da&q="Nettools"+pocketpc&btnG=Søg&meta=lr=lang_da|lang_en
´`?
Click to expand...
Click to collapse
Hmm... Thanks Rudegar ! But I was searching for nettools for pocketconsole, to use with pocketcmd in order to have the "route" command.
Fortunately, I found it : nettools_arm_setup.exe on http://ftp.linux.in.th/pocketpc/net/
Thanks for your answer.
Regards,
HUGE BREAKING NEWS!!! THIS JUST IN:
May 12th, 2008
ENTER "FrankenKaiser"
For the past several weeks, I've been working with Jocky on unbricking devices with nuked SPL's as a result of task 2a MTTY commands. Last week the amazing Jocky found a way to exploit OEMSBL & to Security Unlock a BRICKED device via dload mode. That's right, you heard correctly, Jocky Security Unlocked a bricked device, giving me access to all of the OEMSBL, Radio Boot Loader commands!!!
Subsequently, Jocky has written a tool that will then use this exploit to load a new SPL via Dload mode into ram & do some device initialization. After three chalenging & frustrating weeks, we were able to load a SPL into ram, get the spl to stick & voila.....I now have the first ever Kaiser recovered from being a nuked SPL brick!!!!
I won't give to many details, as this is really Jocky's baby & it's his place to share the information as he sees fit, but I'll tell you that this tool may be the start of something huge! It will allow you to test SPL versions & recover from bad SPL flashes. I believe this tool is also going to be the center of fixing the locked AT&T radio's.
I can take no credit for this tool, I was really nothing more than a brave & willing guinea pig, that occasionally floated theories, & remembered some of the little stuff.
Jocky did let me name the tool, based on the first thing I thought & said when we were talking about the theory behind the tool, which was "Oh my God, It's alive, it's aliiiiive!!!!", so the tool has been named FrankenKaiser!
If you have a Bricked Kaiser, Let me know, post it here in this thread until Jocky start a thread specifically related to this new tool. Please don't overwhelm Jocky with requests & PM's, as the tool must be moddified for each & every different OEMSBL version. If you have a task 2a or other bricked Kaiser, please PM me or post the info here on this thread & depending on the type of brick you have, someone will let you know if this tool can help you.
Okay, it's true I've put my Tilt thru hell & back trying to help out the noobie. I have done partial flashes, radio & rom, to recreate their problems in an effort to guide them thru the solutions.
I've alway been able to recover......Until now!
A WARNING TO ALL USERS FROM OTHER DEVICES NEWLY COMING TO THE KAISER!!!
After countless trips to hell & back for my device, it finally, It is totally dead. After doing a few MTTY task & info calls while assisting a noobie I decided to format my device & the nand storage to start afresh. Now I am stuck in OEMSBL.
Should you try and format or dump bad blocks as previously possible on some older devices using the task 2a command. There are several thing you need to know. Firstly, you'll need to immediately flash a new SPL BEFORE soft resetting. Otherwise, your device will not boot period. You will find that the service LED light stays green like it is fully powered, & the "GREEN" light will come on whenever you hit the power button, but when you plug it into the USB port on your PC, it will only be seen as new hardware & will add the following new devices: a NMEA GPS Device, a Qualcomm Data Device, an Qualcomm Diagnostic Interface, a Baseline Modem, Baseline Storage Device, etc. But A/S will not run & MTTY cannot communicate using standard commands nor can it be used thru the USB port.
The reason this happens is becauser you have just completely formatted the NAND, essentialy killing the Boot Loader or SPL.
As of this time, there is no known recovery for this type of brick. Several people are working towards a fix, but unless your device is security unlocked, there will be no miraculous recovery.
ALWAYS EXCERSIZE EXTREME CAUTION WHEN COMMUNICATING THRU MTTY WITH SPL OR WITH OEMSBL. DO NOT ASSUME THAT THE SPL COMMANDS ARE STATIC> THEY CAN & DO CHANGE BETWEEN DIFFERENT SPL VERSIONS & DEVICES.
As an example, Tilt Devices with the 1.56SPL can execute the boot command, whilee HTC 1.93SPL devices cannot & require a task 8 to reset.
If you do not know what SPL is, or have no idea the available commands & their effects, do not use them.
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Laurentius26 said:
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Click to expand...
Click to collapse
Laurentius is right; it would surprise me if the Flash from SD-card would not work for you!
Good luck,
Edward
sorry to say that but it is a true brick now, it is recognized by windows because there it falls back to qualcomm diagnostic mode (which will not help you at all) I had exactly the same situation and you won't be able to flash it, send it to htc for repair
No, The screen will not turn on & when plugged in it now acts as accessories or hardware for my PC.
The chipset inside the device is still getting power, & it is a chipset that is powerful & used for many, many things. So, it's no suprise that it sees the modem, the Basecom Interactive, Basecom NMEA device, etc...What it doesn't see is all of it integrated into a package & it actually creates 6 or 7 port connections thru XP Hardware Wizard for each "accessory".
What I believe has happened is that the unit has been completely formatted meaning the actual Windows CE has been destroyed, formatted, removed, kaput...
The only way to revive I think would be to reload CE into the device the way Mfg's & OEM's do.
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Da_G said:
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Click to expand...
Click to collapse
nope, there is now way to do that
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
GSLEON3 said:
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
Click to expand...
Click to collapse
sorry, that's a misunderstanding my post was referring to the use of pst software/mtty and usb connection, and I reckon that it's cruel to give the man hope, though you can always buy yourself a piece of software built based on jtag, special serial connector and a book how to to that but given the sources you mentioned I reckon you haven't read much about the problem yet, my kaiser is about two be back from service this week and if there was no breakthrough on the internet about that with last 2 weeks then there is no know way how to talk to qualcomm diagnostic software directly using usb.
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
_Alex_ said:
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
Click to expand...
Click to collapse
yes Alex, also SPL (which is the real problem here), and you can't use pdocwrite unless you could actually talk to the device which in qualcomm diagnostic mode you can't with this software as it will not accept any commands other than specific to that mode, I have flashed windows mobile device for about 4 years now and that's actually the first time I ended up with a real brick but of course htc can easily fix it (they did it in 1 day, most likely in less than 30 minutes) but they have equipment to do that which I don't and only few users on xda have that kind of equipment, to get more info about it you could look in the search for task 2a there were bricks like this before us
Alex,
Yes CE, Radio, SPL, OS... All see to be completely wiped with the task 2a command. I don't think pdocwrite will work as its still needs a medium to connect to my device. That medium is what I have yet to find. The first step would be to somehow restore boot loader. I am currently trying to see if I csan use qpst to push linux to the device. I haev found some CE restore utilities for reverting from linux, but first I need to be able to at least boot to SPL or another Bootloader.
Whats about Windows CE and KITL Mode?
The device stays in OEMSBL. If you use the MotorolaQ drivers, you will be able to connect to the right COM port and issue radio bootloader commands. You will probably be able to unbrick it depending on what problem it has. First try the easy one:
* Execute "setboot 0" and "cego" commands.
If this does not work, then probably your SPL has been erased in NAND, you can check that by dumping radio memory address 0 right after executing "cego" command. (commands: "cego" and "mb 0 40000").
If it's all 0xFF then your SPL has been erased. Here's how to fix that:
1) Issue command 'setboot 1' (with the default 0, the application ARM is hang because it tries to execute 0xFF), this way it keeps the SPL in memory after reset.
2) Copy a full SPL at address 0 by issuing 256K times 'mb <address> 1 <byte>' (i've written a small app that does this for you...)
3) Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader, in my case (OEMSBL version 1.27.12) the patch was 'mw 901708 1 0000a0e1' you'll have to figure it out yourself if you have a different OEMSBL version.
4) execute 'cego' and see the bootloader 3color screen appear again (keep the bootloader keys pressed if you have not used a patched SPL in step 2)
5) Flash HardSPL.
6) Connect to OEMSBL again and execute "setboot 0".
7) See the device booting OS
Thanks pof!
setboot 0 returns ARM9BootMode:0, so it is communicating. However, I get invalid command errors with the cego & mb commands. You think there is a way to flash an spl.nbh using OEMSBL thru pnewbootloader? I believe you're right on the money & from what I've learned playing around today is that the task 2a command indeed formats the NAND. So bye bye bootloader. I think it's now just a matter of finding a way to flash spl back. That said however, I can figure things out given a lot of time, but I'm definitely nowhere near a bright bulb on the XDA X-mas tree, so to speak. So you'll have to forgive me if the meaning of "Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader" escapes me.
Thanks again!
When I used to work @ symbol we used to interface with our devices directly in IPL mode using hyperterminal (included in windows). I wonder if you could accomplish something like that?
From there we used to use IPL commands (I dont remember them because this was a long time ago)
GSLEON3 said:
Thanks Oli!
However, I get invalid command errors with the cego & mb commands. Also, where can I find the spl patch app you've written? I searched high & low.
Thanks again!
Click to expand...
Click to collapse
I think POF is talking about JumpSPL correct? I am surprised it didn't work after what POF recommended his right on 99% of the time!
I believe s right. I just think the cego command isn't correct for my device. I think maybe this command has changed just as spl commands can change between versions. The mb command also returns an invalid argument.
But it's definitely down the right path.
GSLEON3
I really wish I could help you out man. You have done alot on this forum for alot of people. Unfortunately I'm about as lost in here as a hooker in a pecker patch. Sorry bro, wish I could help.
pof's method only works if your device is security unlocked
1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks
Shame you didn't spend some of that two days reading the site rules and the fact that not only is there Q&A section but also try posting in the ADB threads that are littered around these forums.
Catch me on irc, link in sig and I'll see what can be done.
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
So what does helping you get adb setup help android G1 Developmet?
Sent from my HTC Dream using XDA App
lolmensch said:
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
Click to expand...
Click to collapse
fastboot uses fastboot.exe, not adb.exe. Adb works while in recovery or while booted.