PPCGeeks - Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

PPCGeeks (http://forum.ppcgeeks.com/index.php)

- CDMA TP Development (http://forum.ppcgeeks.com/forumdisplay.php?f=68)

- - Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible] (http://forum.ppcgeeks.com/showthread.php?t=64242)

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by lordshadowz (Post 838909)

No thats exactly what I'm getting. The jawbone physically connects and works fine but shows disconnected and will say passcode is incorrect.

Looks like this may be a Jawbone only related bug. Can anyone else please try ?

I just flashed for the 4th time so its not a flash issue.

Just tried it again for ya and as soon as I turn BT on they sync automatically. Stop flashing and try doing a Hard-Reset. Go to System>Settings>Clear Storage> 1234>Yes(Make sure you backup ur stuff). I got no problems with this great ROM. :headbang:

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

woohoo... huston we have liftoff..... nice job guys VZW boots ;)

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Does anyone know how to change the reply to address when using a windows live email? I changed it online but it doesnt take on the phone.

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by jdignazio (Post 839272)

ERROR [202, 204] : CONNECTION

This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.

ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR

When you see any of these error messages, close other running programs on the computer and run RUU again.

ERROR [208] : FILE OPEN
ERROR [210] : FILE READ

These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.

ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING

These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.

ERROR [220] : MAIN BATTERY POWER

This error message will appear when the device's battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).

ERROR [238] : FILE READ

This error message may appear when, for some unknown reason, the ROM image on the phone is corrupt. Download the whole RUU and try again.

ERROR [240] : FILE OPEN

When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.

ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY

One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.

ERROR [246] : DEVICE NOT RESPONDING

This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.

ERROR [248~260] : UPDATE ERROR

This error occurs when there is an ";open port error"; before upgrading the CE ROM image.

Solution: You can reset the device and run RUU again. If you still encounter an ";OPEN PORT ERROR"; again, reset your computer and try again.

ERROR [262] : UPDATE ERROR

This error occurs during the CE ROM code upgrade process.

Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.

Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.

ERROR [264, 274] : CONNECTION
ERROR [302~318] : UPDATE ERROR
ERROR [320~328] : INVALID COMMAND

These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.

ERROR [300] : INVALID UPDATE TOOL

This error message will appear when you use the incorrect RUU version to upgrade.

ERROR [330] : ROM IMAGE ERROR

This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.

Hope that helps!!!

Your phone is unlocked right?
Also, maybe a bad download or
Try flashing using a memory card.

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by bjhill2112 (Post 839244)

That is an issue in all 6.5 ROMs. So far all of the old phone skins just don't play nice. Give it time, someone will eventually figure out how to properly skin the dialer for 6.5 - until then, I'll just use the WM lock screen with the default dialer (even though it's not very pretty!)

oh yes, i wouldnt doubt that a 6.1 phone skin wont play well with 6.5. i love the new answer mechanism on the lock screen but the original WM skin is so outdated!

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by lllboredlll (Post 839384)

woohoo... huston we have liftoff..... nice job guys VZW boots ;)

glad to hear... lots of free ram for you too ;)

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by lilgrass71 (Post 839443)

oh yes, i wouldnt doubt that a 6.1 phone skin wont play well with 6.5. i love the new answer mechanism on the lock screen but the original WM skin is so outdated!

I am relieved that this issue was not happening just to me.. In a good way relieved...
I even had a hard time removing it from my programs. It would freeze my phone when I try to remove. I had to finally clear storage and re-install again.

Not going anywhere near SlideToAnswerWhite_CDMA.cab

But yes the lock screen is the best choice right now.....

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by Juicy47 (Post 839450)

glad to hear... lots of free ram for you too ;)

yes sir ty much :D

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by Mr_Sinister (Post 837826)

Is there a voice command cab floating around?

thanks!!

Quote:

Originally Posted by slopokdave (Post 837941)

Anyone figure out how to get opera as the default browser?

Quote:

Originally Posted by No1ustad (Post 837944)

2 regedits, search and you'll find out how.

Quote:

Originally Posted by slopokdave (Post 837985)

Did this, didn't work...

Quote:

Originally Posted by land2634 (Post 838005)

Same here. Tried searching for it for you since some people like to respond by telling you to search. Gets nothing accomplished but cluttering up the thread by the same people accusing you of cluttering up a thread.

Did a search, took roughly 9 seconds to find: http://forum.ppcgeeks.com/showthread.php?t=31906

Quote:

Originally Posted by superman426 (Post 838671)

Is it me or those some one else can get access to the gps? any idea on how to make the gps work?

Worked out of the box for me, made my first connection in a ridiculous 3-4 seconds. Maybe it's something you have installed?

Is anyone having problems using the hard keyboard to enter "!" or other characters that require the Fn key? I consistently have to repeat keystrokes to get these characters. If I'm the only one maybe it's because I've installed the Savage25rcracer TD2 Keyboard?

Small graphic bugs: Wifi info shows in the wrong place on Home screen, battery icon is not centered between speaker and task mgr.,

Re: Copper v.0.0.0.1 [6.5.21500 Build 21500] [16MBPP] [UC Compatible]

Quote:

Originally Posted by MX51 (Post 839377)

I'm very experienced with Roms. I always hard reset using clear storage after a Flash.

I'm not the only one with the issue so I'm not crazy. And again the headset works and syncs properly. Thats not the issue. What I keep saying is even though its connected and working properly the Bluetooth screen is showing it disconnected and when you select to connect it immediately says the password is incorrect.

Someone else with a Jawbone also reported the same exact issue. I'm trying to get people to check the Bluetooth screen to see if theirs shows its disconnected even though it is really connected. If not then its probably an issue with the specific Jawbone headset.

Thank You MX