[BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes

[ndno]

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 go ahead... wait for arrrghhh's response.

[arrrghhh]

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.

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...

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 .

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...

[n1nj4Lo]

Originally Posted by arrrghhh

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.



Huh. Mine didn't, but it was a refurb... what is the SIM used for...? Certainly not to connect to Sprint's network...



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 .



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...

It's a class 2, and bring on the new cmdlines... No luck yet so far... Grrrr! LMAO

I don't wanna be a bother, but I suppose it's helping everyone out and making progress and evolution with the project.

[arrrghhh]

Originally Posted by n1nj4Lo

It's a class 2, and bring on the new cmdlines... No luck yet so far... Grrrr! LMAO

I don't wanna be a bother, but I suppose it's helping everyone out and making progress and evolution with the project.

Hrm, and the same command just keeps repeating in the terminal...? I wish I could see what's going on during the boot process .

It doesn't seem like this will fix it, as usually people get a "Waiting for SD card" error or something similar when the problem is the SD... but here it is:

msmsdcc_1bit msmsdcc_fmax=14000000

^^ just paste it anywhere within the quotes after the cmdline=. Again, just make sure there are spaces between each item within the quotes...

[n1nj4Lo]

Well I'll add this discovery for the newbs

In order for Gen.Y Boot (Dual Boot App) to work..
YOU Must have the contents of whatever android folder all rooted directly onto your card. So no main folder and then all the others inside that folder, everything inside the main folder can't be in a folder like frx04 or andboot (Whatever name of kernel/distro)\ >then xdadroid files >, it all has to be directly on/in the main base location of your card.

[arrrghhh]

Originally Posted by n1nj4Lo

Well I'll add this discovery for the newbs

In order for Gen.Y Boot (Dual Boot App) to work..
YOU Must have the contents of whatever android folder all rooted directly onto your card.

Not true, you can change a registry entry within WinMo and you can direct Gen.Y to any directory... .

Feel free to peruse the Gen.Y XDA Thread.

[n1nj4Lo]

Originally Posted by arrrghhh

Not true, you can change a registry entry within WinMo and you can direct Gen.Y to any directory... .

Feel free to peruse the Gen.Y XDA Thread.

Yea it looks like it is the same error, then every once in awhile it'll change the n go back to the same old error...

Wish there was a way I could record this or take a screen capture, to post what it's doing.

Also yea I'm still using the updated kernel.

[arrrghhh]

Originally Posted by n1nj4Lo

Yea it looks like it is the same error, then every once in awhile it'll change the n go back to the same old error...

Wish there was a way I could record this or take a screen capture, to post what it's doing.

Also yea I'm still using the updated kernel.

I'm... pretty baffled. I need to know what error the phone is spitting out.

Did you change anything about the build, or just extract it to the SD card and move the startup.txt file? Do you have adb setup? Have you ever been able to boot before?

[Recursion]

Originally Posted by n1nj4Lo

Yea it looks like it is the same error, then every once in awhile it'll change the n go back to the same old error...

Wish there was a way I could record this or take a screen capture, to post what it's doing.

Also yea I'm still using the updated kernel.

Just to be sure, you DID remove your SIM Card, right? That error message you posted was similar to the one I got when my SIM Card was in.

[manekineko]

Originally Posted by cganesh75

i had the same issue. it was complaining some MDP_BUSY or whatever and also something that ended with "4 out of 4 times" or something. went back to tiads version and it works. both of them after a clean format of the 8gb sd card

I believe your problem is that you don't have a calibration file, and you're using one of the recent kernels that are busted for calibrating the screen. There's a prompt for you to be touching some squares to calibrate your screen is what I think is going on, but that prompt and the squares are covered by text, which is a bug in the 1253 kernel, so then it just sits there apparently not doing anything. You can solve this in one of three ways:

1) Go to arrrghhh's first post, and download the calibration file that he has attached, and stick it in your Android folder.
2) Start by booting with either 1258 or one of the kernels numbered 1234 or less I believe it was. Then you should be able to see the calibration squares you're supposed to be tapping.
3) Calibrate blind. 5 squares are going to come out, first in the top right, and then top left, then bottom left, and then bottom right, and then center I believe. They're about 1 cm from the corners of the screen. Just tap even though you can't see them, and your boot should continue. This approach is probably a bad idea.