Quote:
Originally Posted by n1nj4Lo
Trying it now with everything directly on the card, no folders or anything... I also remembered to revert the startup.txt back to its original form.
Man I hope this works!!!
|
Hope it does too. You have giant cards too, 16gb and 32gb? What class are they? Believe it or not, class6+ is not recommended for the project... You can use them, but some have reported odd issues. Not sure if any have failed boots...
You're still on 1258 as well right? We can try adding another command to the startup.txt that fixes issues with SD cards, but with 1258 you shouldn't need it. Worse comes to worse, we'll add it.
Quote:
Originally Posted by Recursion
Actually, Sprint TP2s came with SIM cards pre-installed right out of the box. I don't know if Verizon & other TP2s did. Anyhow, I just wedged a piece of paper between the SIM Card and my phone's contacts & re-inserted the SIM. I lose too much chit.  |
Huh. Mine didn't, but it was a refurb... what is the SIM used for...? Certainly not to connect to Sprint's network...
Quote:
Originally Posted by Gremlin75
I hadn't...but I went back to his post and downloaded it. After installing it, I was able to connect to the phone and use MyPhoneExplorer to sync my Outlook calendar & contacts to the phone. Woo hoo!
I'm still getting the error messages about the CDC messages, and I've tried pointing the phone to both the USB Drivers directory as well as the PDANet directory. Can't locate drivers in either location. Seems to work just fine without them however.
Thanks for the help! Would definitely recommend this solution to anyone running Android and trying to sync to Outlook. 
I'd like to post a thread to provide instructions and links to the required files...crediting you & arrrghhh, of course. Do I have your permission to do so? |
Sure, I've always wanted to do an adb how-to but never got around to it. I was going to turn that thread I created into one in fact
.
As far as the other two devices you can ignore them. Just tell Windows to not prompt you about that hardware anymore. One is for USB mass storage, which doesn't work, and the other is... I believe for USB tethering which doesn't work either without using a 3rd party app like "EasyTether". So you can safely ignore the other two unknown pieces of hardware
.
Quote:
Originally Posted by ndno
I don't know but I think rel_path=blahblah needs to be PART of the set cmdline line before the "physkeyboard=rhod400" string... or does it not matter (someone once told me it mattered).
|
Doesn't matter where it goes, assuming that it's within the quotes and there's a space between each item. Order is meaningless as well...