Quote:
Originally Posted by NFSFAN
Problem fixed by reflashing 2.31 bootloader coKe. It appears it was corrupt for some reason.
|
I had this issue when cooked Verizon ROM and my .rgu had "first boot time zone fix"
;*** First Boot Fixes ***
;================================================= =====
[HKEY_LOCAL_MACHINE\Software\Microsoft\Clock]
"GMT_OFFSET"=dword:00000168
"AppState"=hex:11
"TZIndex"=dword:00000004
"HomeDST"=dword:00000001
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"NITZEnable"=dword:00000001
[HKEY_CURRENT_USER\CONTROLPANEL\PHONEEXTENDFUNCTION \CDMA]
"SyncSystemTime"=dword:00000001
it syncs to pacific
This made a conflict with 1 of the Verizon's provxmls (they had entries to sync to eastern time zone)
That conflict made my phone acting strange (touch responce driver worked strange too),I couldnt flash even shipped exe ROM(same error 262-connection,and there is nothing wrong with connection),and only coke 2.31 ruu helped me
(extracted coke 2.31 to empty folder and ran ROMUpdateUtility.exe of that folder).just like flashing any custom ROM,only this time it was flashing coke 2.31 unlocker.Process takes 3-5 sec to upgrade from 0% to 100% and no more 262 errors.
Sorry if wrote too much.That way first time flashers can understand what I was trying to say...