I tried to install the 6.5 rom from Allshadow.com. I got installation errors which allowed me to go through the recovery process. At about 50%, I got a "file open" error that only allowed me to "Exit". I did so and attempted to reflash the rom again. Activesync wouldn't recognize phone anymore (I've been through the advanced connections and checked "allow USB connection") and the screen isn't the green/red/black error screen but rather it is the Windows 6.5 Splash Screen.
Any suggestions?
Email to:
[email protected]
[email protected]
Thanks.
Related
NEED HELP!!!!! ERROR 264: CONNECTION
when making update the rom of qtek 8010.
They help me please.
Debtor,
Marco Cardoso - Portugal
Same here
ANY HELP?
I figured it out!!!!!
figured it out!
I went to a blank computer and installed the T-Mobile Apps from scratch then the first thing I did after the reboot from the ActiveSync install...was rand the ROM upgrader (CUSTOM_RUU_Prodigy_2170702_217_20710_TMO_US.exe)
....PRESTO.....
What I saw was the driver used when the phone goes into the Boot Loader screen (RED, GREEN, BLUE). It stated "USB Device" as the driver was loading in Windows XP...after it stated device ready to be used....it started!
I would suggest unistalling ActiveSync and reinstalling it from the T-Mobile Disc....this should work!
PM me if you have any problems.
So got my Dopod 838pro running windows mobile 5 and will upgrade it to windows mobile6 with any luck, at the moment im trying to upgrade the boot loader to SPL (Bootloader) version 2.10.Olipro (HardSPL v7) and im following this very handy guide http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=30&Itemid=27
however i get to the very end where its supposed to flash the new boot loader and it sits there for a while until the updater utility comes back with ERROR [260] Update Error.
Which informs me that i should check to see if the phone is connected to the computer via usb, which it is.
It must connect to the phone cause it actually starts the process of trying to update the boot loader, i see it on my phone. It goes to a red, green and blue screen. Which says:
Herm1000
IPL-SSPL by Des
Herm100
SPL-1.09.ds
USB
The only option i have here is to press exit on the updater utility, and start again.
Nothing else happends after this.
Im running Windows Vista 64bit, have also tryed this guide
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
Still no solution.
Currently i have:
IPL 1.01
SPL 1.06
Have also restarted my computer in between trying different things.
Anyone ever had this problem or know a fix?
Thanks in advance.
error 260 is an open port error. try a different usb port, disable antivirus and firewalls, or if avaiable try on a different pc, xp if possible.
heh, works on my XP machine.... >< Thanks.
Edit:
I tried a differeny USB port on my vista machine and that didnt work. I also closed absolutely everything and that didnt work either.
Error happen
Read below for more information
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I got this when I first installed the standard DFT ROM, i found that by remving the accept USB connections in activesync resolved it and I was able to install. I then tried to install a different ROM and failed, I tried another and the same. I was initally getting RAPITOOL errors, dll not found. Reinstalled activesync and I am not getting those errors anymore but ROM still wont install. With error above.
Reinstalled Mag ok so bootloader installs still ok, anyone any ideas?
FECK, my NAND Android build has gone as well...
What helped for me:
- If USB is connected: right click on USB -> safely remove MAGLDR USB device
- remove MAGLDR USB driver from PC
- restart pc
- connect phone again via USB and let driver install
Should work fine again now. Guess something can go wrong in the USB driver sometimes.
mag does not show up as a device to remove, i will reboot and try again.
I think activesync reinstall resolved it as it worked after a rebooted, didnt reboot prior to that, thanks for your help anyway.
I spoke to soon, well managed to flash another ROM, didnt like it so flashed again, got half way through and then came up with error again, tried again, back to square one. Anyone ideas what is causing this?
rebooted, still the same, reinstalled activesync and rebooted, all ok again. Why is activesync required, cany anything else be used, anyone any idea what is happening here?
you can install magldr, radio or roms with ruu in 3 color mode in hspl...
get there with wol down key and end call button pressed
when magldr is already installed boot up your phone with pressing end call button until magldr menu appears
and then start you android flashing procedure the way cotulla explained it!
I had the 723 error too and what helped for me was executing the daf.exe with password secured admin rights (your profile on computer has to have admin rights and has to be password secured)
t3g said:
you can install magldr, radio or roms with ruu in 3 color mode in hspl...
get there with wol down key and end call button pressed
when magldr is already installed boot up your phone with pressing end call button until magldr menu appears
and then start you android flashing procedure the way cotulla explained it!
I had the 723 error too and what helped for me was executing the daf.exe with password secured admin rights (your profile on computer has to have admin rights and has to be password secured)
Click to expand...
Click to collapse
Hi, thanks for info but I am passed that point. I have already installed mag and tested my first ROM, I am having this problem when trying to flash new ROMS. I have now go another ROM on by reinstalling activesync and rebooting again, I am hoping someone is aware of this issue and let me know how to resolve it as I dont want to have to go through this rigmarole everytime I want to flash - as I am still at the stage of settling on a ROM and are trying all the current set.
In a much happier place right now. don't have to stress over winmo 6.5 anymore. Thank you all for your help. Lovin' Android on my HD2. So fast.
Try this http://forum.xda-developers.com/showthread.php?t=918698
And this might be helpful, too
deckoff said:
And this might be helpful, too
Click to expand...
Click to collapse
cheers but problem now solved after using android_install.exe rather than daf.exe
Hello...
I have a SD-bootable Android on a Dutty Windows ROM 6.5 with a working radio and HSPL 2.08. All perfectly working.
Now i want to go NAND and want to install MAGLDR. I start it as administrator, then i can select update and my phone goes straight from windows to bootloader. But after that i get the message that my workstation can't connect to my phone (althought boot loader says "USB"). I tried it directly from boot loader too and that too doesn't work (from there i can't even get the Update selection).
Could there be an issue with the Dutty ROM or has anyone else an explanation for this kind of behavior?! And is there anything i can do... maybe erase the whole ROM (HOW???) or anything?
Regards
Elmar
Is the error message by any chance "USB init failed"?
What version of Windows are you running? Also, do you have a firewall or antivirus application running? I have seen them interfere before and you could try temporarily disabling / deactivating them.
I have an antivirus (AVG), but it is only on Android, which i am not accessing when updating. As i said i tried from windows (6.5) and the update took me to the boot loader but then the windows application is trying to connect and then gets no connect and this error message appears :
"Error (260)
Check the following :
1. PDA Phone is connected via USB
2. USB cable is connected to the workstation"
And it is connected, which you can the on the fact, that the update is running my phone into the bootloader, but then i get stuck on 0% and after that the error message appears.
What you want to do is try disabling the allow usb option in active sync. Do this after you install magldr but before you try to flash the rom. This seems to fix the problem.
Sent from my Wimax infested cm6.1.2 SuperSonic
Hello again...
I am so sorry to have bothered you with my nonsense.
From the workstation i tried (which i strangely flashed all other ROM's before and had no problems) there had been missing the driver for the boot loader which pretty simple explains my problems here (Do'h).
Tried it from a workstation with internet connection and eureka, the driver installed and i could install magldr afterwards.
Thx for all your support and sorry for my homer-like thinking for not checking that before.
P.S. Any of you any recommandations for a good NAND ROM. I think i am going to try MDJ's CyanogenMod7. Or has anyone tried various and come to another good ROM?
Regards
Elmar
Hi, I need some help from you guys. I flashed WP7 for my HD2, everything was good. But I accidentally unregistered my phone by 'Windows Phone Developer Registration'. And I failed to register it again.
'Error communicating with the developer portal. Please set the correct data and time on the phone, check the Internet connection and try again later (ErrorCode:0x64)' was the error message.
And I failed to flash the ROM or reinstall the MAGLDR113 once again on my phone.
'Error Description: USB init failed; Info: .\RSPL\RSPL.cpp(1198)' was the error message when I tried to flash the ROM again.
How can I fix my problem?
zhaoch25 said:
Hi, I need some help from you guys. I flashed WP7 for my HD2, everything was good. But I accidentally unregistered my phone by 'Windows Phone Developer Registration'. And I failed to register it again.
'Error communicating with the developer portal. Please set the correct data and time on the phone, check the Internet connection and try again later (ErrorCode:0x64)' was the error message.
Click to expand...
Click to collapse
Similar problem here.
I flashed my HD2 with a custom ROM that already had the jailbreak baked into. Yesterday I purchased a developer program membership and thought I might legally register the phone.
I startet the registration tool from the Windows Phone Developer Tools and it said the phone was already registered. I managed to successfully unregister the phone but then, when trying to reregister it using my Live ID, I got the same error message (ErrorCode:0x64).
A lot of people at the developer forum on MSDN are complaining about this error as well. A couple of them said the registration tool wouldn't work on 64bit Windows. Some of them installed Windows 7 x86 on a virtual machine and tried to register their phone from there and it worked.
I am going to give it a try, too.
Did you have any success in the meantime?