Okay heres my problem i have been floating around on the forums for a while and been after flashing my win Mo 6.1 X1 to 6.5 or use any of the many custom roms on this site.
However i have many many memory sticks for vairous phons for the last 5 or so years, but i dont own the required type for this phone and i refuse to buy a MS just to freekin upgrade my rom.
does anyone know of a way to update the rom on the phone via PC like place the custom rom / win mo file son a place in the main phone storage and update form that ?
i can't for the life of me find away to do this, thnx in advance
can write but can't read ?
http://forum.xda-developers.com/showthread.php?t=446070
Seems you can't read also i said without using a memory stick. . . i need a way to do this without sticking the rom file on the root of a memory stick
Download the attachment, unpack and put the ROM in the same folder.
Connect your phone to your pc with active sync
Run CustomRUU to flash your phone
Lokatho said:
Download the attachment, unpack and put the ROM in the same folder.
Connect your phone to your pc with active sync
Run CustomRUU to flash your phone
Click to expand...
Click to collapse
Thanks very much for your help, have a gold star from me
HUmmm okay this method of running the ROM from the same directory as the .nbh file is failing i get past the 4 colour boot screen and then to the 0% bar and then i get an error [26] update error
i have tryed this with two diffrent customRRU.exe and one supplyed with the rom i am trying to install ( X2 rom with win 6.5 latest release ) and nothing just crashes and re boots in ( yes the phone has had hardSPL used on it, as it was unlocked fromvodaphone network ) any ideas ???
Try connecting your phone to your pc when in bootloader, and wait until your pc has installed the drivers for it (don't run CustomRUU).
When the drivers are installed, reset your phone, connect to your pc with ActiveSync (or Windows Mobile Device Center, if you have Vista or Win 7).
Run CustomRUU when connected...
renamed to ruu_signed.nbh? kovsimg.nbh is only for sd method, just asking
Related
Heloo every one ... i'm tired from this pda p3600 ... since 4 day's i wanna to upgrade my rom from wm5 to 6 & the upgrade process didn't work ... i try everything .... but non is work ...
first i was trying to make upgrade through windows vista home premium but didn't go well & this is the photo for my problem :
http://www.freewebtown.com/Haitham/CIMG0511.JPG
http://www.freewebtown.com/Haitham/CIMG0512.JPG
http://www.freewebtown.com/Haitham/CIMG0513.JPG
http://www.freewebtown.com/Haitham/CIMG0514.JPG
http://www.freewebtown.com/Haitham/CIMG0516.JPG
then i try to upgrade through my freind windows xp ... and also didn't work good .. the error message say that the phone is unable to upgrade do u rom flash or something like that ... so i try to instal the unlock & also same message ....
i'm in **** mood ...
any one can help me please
Until the new version of WMDC is released with fixes, I suggest you use XP computer to do upgrade.
New WMDC v.6.1 coming soon: http://windowsvistablog.com/blogs/w...ows-mobile-device-center-6-1-coming-soon.aspx
The XP computer needs to have Active Sync 4.5 installed. Reboot xp computer before starting, to clear any existing syncs. Delete current sync profile on Trin. Connect to pc via usb as usual, let ASync run, but cancel when it tries any profile, you are left as: Guest sync
You should be connected now. Upgrade rom file should be extracted in explorer, e.g., so you can see all files. Run RUU wrapper or ROMUpgrade exe, depending on rom you're using.
If you go through process, & get error message. Don't disconnect Trinity. Close that page & start again. It should work the 2nd time. When it's working, you will see the boot screen, color bars & at bottom usb notation. (If it says serial, you'll have to, unhook usb connection, reboot computer, re-sync to guest status, & start again.) Then the update screen on Trin will show % bar, if process is working correctly.
If you still get error message, then check Trinity Wiki info as rom upgrade problem FAQ is there. I'll assume your Trin is unlocked. Check boot screen on Trin to see boot loader info. Wiki explains how.
Also: Use SSPL software Bootloader solution from "Des" - this loader ignores the CID and the upgrade will work also with wrong CID. See also http://forum.xda-developers.com/showthread.php?t=293632
If you still have problem, come back here & give info:
1. What rom is currently on Trin? What radio?
2. Did you buy an unlocked Trin? Exactly, what device do you have?
3. What wm6 rom do you want to upgrade to?
I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Drake008 said:
I was performing the radio update on my MDAIII and now he hangs in the bootloader with USB in the upper middle und 2.08 in the under middle. All resets won`t bring it back to life. If I try to reinstall the update all I get is a blank message screen (update from version to version) in my Vista. How can I get out of there.
I did everything what was stated here
The original BAUpgradeUT won`t find my device. The MAUpgradeUt_noID.exe gives me the blank screen with the update from to screen.
Click to expand...
Click to collapse
I'm using a Vista PC.
After the Radio update to 1.15 the error described above is not to go away yet.
What to do, I'm nearly in tears.
Finally I got it back but with an old Romupdate from T-Online. Is there someone who got the QTC 9090 update (latest one)
That was fast..
im glad you solved your problem.
i think someone here has it.
just post what you need and make it as a title for others to read in the digest.
Im not a expert but is vista the problem??
Most likely.
Failed MDA II flash with vista notebook
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
mda3newbie said:
Hello everybody,
I just read this thread in hope to find a solution for my problem, which is quite similar to the one described here initially.
I got a used MDA III with T_Mobile ROM. Since I'm a customer with O2, I wanted to change the ROM to O2 as well. I followed the directions given in an other thread here (don't have the link just now) and during the flashing, the flash application suddenly had no connection to my MDA III anymore. It was securely settled in its craddle an connected to my laptop via USB. Now my MDA III is stuck in Bootloader Mode with USB v2.07 displayed on the screen.
Each retry of installing either the O2 or the T_Mobile ROM now meet with the error 101: no connection. I read here that you managed to update successfully with a vista pc. Thus I wanted to ask, how you did that since I just don't seem to find the reason for the connection failing each time.
Here is what i tried to establish connection so far:
* disabled virus scanner & firewall
* unplugged the mda III and plugged it in again. It was recognized as a new device but that didn't help the connection issue
Could you please post what you did to make the update work under vista? Help would be greatly appreciated
Click to expand...
Click to collapse
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
mda3newbie said:
thankfor the tipp and sorry for my late reply. Since I have no XP PC available i tried the mtty1.42.exe on my vista notebook. When i run it however, it only lists com port 1-3, no usb port. Do i have to make a special configuration on vista for it to work?
Thanks in advance,
mda3newbie
Click to expand...
Click to collapse
In vista i dont know...sorry for my late reply too.... in XP u must kill ActiveSync process called wincecom.exe. in vista, maybe u have to kill the Windows Mobile Device Center....i dont know...
Dont forget, put the Qtek 9090 in Boot Loader Mode (Pressing Power Button + Record Button + Reset), maybe will appear USB and u can format the device.
If this does not work, try on Windows XP....Find a friend with Windows XP and ask him to use his PC only to do that.
Maybe somebody in forum have the Windows Vista and can help u....
Sorry my terrible english....
Sjogos said:
Try on computer with Windows XP and kill activesynk (wcecomm.exe on taskmanager/processes)
Maybe it will work. If u cant flash O2 ROM try to use "MaUpgradeUt_noID.exe". On my Qtek 9090 allways flash using this APPS and allways work.
U can try too format device first, put it on candle and use "mtty1.42.exe". On XP, kill active sync, and open mtty1.42.exe and select port USB and put OK. Do "Enter" on command and should appear USB>. After this write Task 28. This will format all your PC. Try install SO after this. This command delete all files on PPC. I have attach files that you maybe need.
Click to expand...
Click to collapse
hi guys I tried the step by step process and when im enterin( Task 28 ) then pressed Enter -
Invalid command : Task28
For a help screen, use command ? or h
does any one know where the problem is??
Try this
Downlaod the XDA IIs .exe file and run it - no need to put into USB mode
http://www.o2online.ie/wps/wcm/conn...es+&+accessories/Xda+Range/Software+upgrades/
this should reset to factory default (o2)
it runs on vista too
I am not 100% sure it will work but worth a try
diesel_dog said:
Im not a expert but is vista the problem??
Click to expand...
Click to collapse
Yes, i know my reply is late but the problem ist 100% Vista! i Tryed 2 ours with vista...then i decided to format my pc and to install XP. At the first try it worked!
hello guys, as i have posted in other threads but no one gave me any soultion to my problem so im starting this thread.
ok i have xperia purchased from UK.
im trying hard to use jack's rom 1.07.
i have done hard spl..i started X1_HardSPL, some message showed on xperia i click yes, it restarted my device. and X1_HardSPL gave me error that it cant connect to my phone...i put my device in bootloader mode and it was showing this on colour screen:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-787
then i used the sd card way..i put the jack's rom file in the card after formatting it with fat32 format..i put the device in bootloader and after the colour screen it shows LOADING and i waited for an hour but nothing happen..
2nd way i used was i ran hardspl file again in a folder, it created some temporary files, i renamed the jack's rom to RUU_Signed.nbh and overwrite the file in hardspl folder.....it again restarted my device to bootloader and after coloured screen it showed LOADING and thats it..nothing else..and hardspl file running on pc gave me 260 or 262 error i cant remember..
so anyone kindly tell me what im doing wrong?and how to fix this
thanx
najaf363 said:
hello guys, as i have posted in other threads but no one gave me any soultion to my problem so im starting this thread.
ok i have xperia purchased from UK.
im trying hard to use jack's rom 1.07.
i have done hard spl..i started X1_HardSPL, some message showed on xperia i click yes, it restarted my device. and X1_HardSPL gave me error that it cant connect to my phone...i put my device in bootloader mode and it was showing this on colour screen:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-787
then i used the sd card way..i put the jack's rom file in the card after formatting it with fat32 format..i put the device in bootloader and after the colour screen it shows LOADING and i waited for an hour but nothing happen..
2nd way i used was i ran hardspl file again in a folder, it created some temporary files, i renamed the jack's rom to RUU_Signed.nbh and overwrite the file in hardspl folder.....it again restarted my device to bootloader and after coloured screen it showed LOADING and thats it..nothing else..and hardspl file running on pc gave me 260 or 262 error i cant remember..
so anyone kindly tell me what im doing wrong?and how to fix this
thanx
Click to expand...
Click to collapse
did you do this (prefereble on an XP machine)
Phone Synced with PC
run X1_HardSPL.exe
follow on screen instruction, including after getting the drivers installed on you xp or vista machine installed, so the hardSPL will make the phone in bootloader and make sure it says 100% done on you xperia. and XP VISTA
then put inte bootloader holding down volyme button and power until tricolor screen is shown, and make sure that the imgage.nbh file is named correctly.
'
then it should work.
the most common failure is that the hardspl isnt installed correctly.
najaf363 said:
hello guys, as i have posted in other threads but no one gave me any soultion to my problem so im starting this thread.
ok i have xperia purchased from UK.
im trying hard to use jack's rom 1.07.
i have done hard spl..i started X1_HardSPL, some message showed on xperia i click yes, it restarted my device. and X1_HardSPL gave me error that it cant connect to my phone...i put my device in bootloader mode and it was showing this on colour screen:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-787
then i used the sd card way..i put the jack's rom file in the card after formatting it with fat32 format..i put the device in bootloader and after the colour screen it shows LOADING and i waited for an hour but nothing happen..
2nd way i used was i ran hardspl file again in a folder, it created some temporary files, i renamed the jack's rom to RUU_Signed.nbh and overwrite the file in hardspl folder.....it again restarted my device to bootloader and after coloured screen it showed LOADING and thats it..nothing else..and hardspl file running on pc gave me 260 or 262 error i cant remember..
so anyone kindly tell me what im doing wrong?and how to fix this
thanx
Click to expand...
Click to collapse
DO NOT I REPEAT
DO NOT
use the hardspl custom RUU for flashing roms.
this is from the 1st post of the HARDSPL thread.
http://forum.xda-developers.com/showthread.php?t=431218
NOTE 4: do not use this RUU to flash anything else! this is only intended for flashing the Hard-SPL. use Xperia CustomRUU to flash other ROM images. for example this version: http://rapidshare.com/files/164933503/X1_CustomRUU.zip
Click to expand...
Click to collapse
IF you have finished hard-spl properly it should say 0.72.Olinex, I'd suggest doing hardspl all over again
thanx bro for replying...during hard spl process it never asked for any drivers, i will try this on xo machine and see what happens,
and i dont understand about customs roms, jack's rom is a custom rom right? so which hard spl file do i need ?
najaf363 said:
thanx bro for replying...during hard spl process it never asked for any drivers, i will try this on xo machine and see what happens,
and i dont understand about customs roms, jack's rom is a custom rom right? so which hard spl file do i need ?
Click to expand...
Click to collapse
do the SD WAY, but remember to rename xxxxx.nbh to kovskimg....nbh otherwise it wont load it, se sticky post here in ropm section.
the driver issue is for XP AND VISTA when still in tricolor screen thn vista will install driver needed for hardspl to work (to recognise the device), as i stated the most common is that the hardspl isnt correctly installed.
hope you got it bro..
It sounds like you're getting confused between RUU and NBH
Ruu is the process for upgrading your phone with a new rom.
RUU stands for
Rom
Upgrade
Utility
nbh is the actual rom
there's only one Hard SPL available in the hardspl thread.
Run that again and let it complete, it should work from booloader mode on your phone.
when that is finished and your device in bootloader says 0.72.olipro then you can flash a rom.
If you use the SD Card method the whatever ROM file you choose must be called KOVSimg.nbh and be in the main section (root) of the SD card.
If you want to flash from desktop take the SD card out first.
Download the RUU I linked to in my last post. Extract that and make sure the nbh rom is called RUU_signed.nbh put it inthe ruu folder then start the RUU process.
smaberg said:
do the SD WAY, but remember to rename xxxxx.nbh to kovskimg....nbh otherwise it wont load it, se sticky post here in ropm section.
the driver issue is for XP AND VISTA when still in tricolor screen thn vista will install driver needed for hardspl to work (to recognise the device), as i stated the most common is that the hardspl isnt correctly installed.
hope you got it bro..
Click to expand...
Click to collapse
one too many ks in kovsimg there mate.
thanx guys for replies. i have managed to install the drivers and then i run the hardspl and now its showing :
KOVS110
SPL-0.72.0LINEX
MICROP1-787
MICROP2-707
now i hope it should upgrade it.before doing somthing i want to know after upgrading to jack's rom, the XPERIA logo that comes when starting the device will keep on showing right? the new rom will not remove it?
thanx
najaf363 said:
thanx guys for replies. i have managed to install the drivers and then i run the hardspl and now its showing :
KOVS110
SPL-0.72.0LINEX
MICROP1-787
MICROP2-707
now i hope it should upgrade it.before doing somthing i want to know after upgrading to jack's rom, the XPERIA logo that comes when starting the device will keep on showing right? the new rom will not remove it?
thanx
Click to expand...
Click to collapse
you have windows vista or xp ???
i cant solve this problem with xp
malik bro i have vista, what i did is i connected my device to pc, and without running the hardspl i restarted in bootloader mode (while connected) it automatically installed the drivers when it was in bootloader mode...
after that i restarted my device then i did the hardspl
and now i finished upgrading to jack's rom..job done.!!
now i have 2 problems.
first the panel is gone...how to install it?
2nd the xperia logo what comes in start is also gone...how to install it bcz i need it very much.
thanx
najaf363 said:
now i have 2 problems.
first the panel is gone...how to install it?
2nd the xperia logo what comes in start is also gone...how to install it bcz i need it very much.
thanx
Click to expand...
Click to collapse
read #2 post @ jack's ROM thread
Some cabs and extra files you may need.
1. X1 Panel package to add panel back (divided into sub cabs)
extract the .rar file then it'll show you the panels cab
install Jack Sony X1 Panel Main.cab first then u can install other panels
sorry cant help you with the xperia logo
ok i want to get back to my stock rom..is there anyway to do that?
how to remove this rom so i can install the orignal rom, by connecting with SE software update utility?
this rom is fast stable but its not only me how use this device.so others dont like the way programs and startmenu are showing.
Usb-driver
I have the same problem when trying to flash with XP. I have tried two different computers but have the same problem. It seems that there is some usb-drivers missing. One time i got an error in XP when rebooting the X1 that the usb-device not working correct.
Can not flash by computer
Can not flash using card
The problem occurs when trying to install ROM
Result: When running RUU. Reboot= OK, Tricolour =OK, Process freeze after "loading" apperas (when *.nbh is supposed to start loading.) SPL never finish.
Anoyone knows which driver i need?
don't forget to disable any firewalls and possibly antivirus... This was the problem for me when using Hardspl and Zonealarm suite... So switched off Zonealarm and Hardspl just worked.... [oh and any windows firewalls]
Will try again tonight without FW and antivirus...
However... i have successfully upgraded ROM using SE Update software earlier... The USB worked fine at that time.
najaf363 said:
ok i want to get back to my stock rom..is there anyway to do that?
Click to expand...
Click to collapse
Yes. Just download the generic ROM from the ROM thread and follow the exact same steps as for a custom ROM. Also, look for answers yourself before asking questions that have answers stickied
Spiff76, SE update uses a different way to access your phone. hardSPL can be considered a "hack", which is why antivirus etc. might detect it.
Hmmm... turned of FW and antivirus but same result. RUU freezes after reboot and tricolour. When phone is supposed to start loading new ROM it just freezes and i get a connection-error message.
I believe it has to do with the usb-connection but i can not figure out how to solve it. Have also tried ti install via card without any luck. Same problem remain... i can not get the SPL to finish.
Have any one experienced similar problem and how was it solved. It can not be a biggie but it is really ***.
As said, running this on XP. USB works fine with active sync and in usb to PC-mode.
Spiff76 said:
Hmmm... turned of FW and antivirus but same result. RUU freezes after reboot and tricolour. When phone is supposed to start loading new ROM it just freezes and i get a connection-error message.
I believe it has to do with the usb-connection but i can not figure out how to solve it. Have also tried ti install via card without any luck. Same problem remain... i can not get the SPL to finish.
Have any one experienced similar problem and how was it solved. It can not be a biggie but it is really ***.
As said, running this on XP. USB works fine with active sync and in usb to PC-mode.
Click to expand...
Click to collapse
Most probably YOU HAVE NOT DONE THE HARD-SPL FLASH FIRST
Please CHECK your tricolour screen: the world "olinex" must be there, which means you correctly flahsed the "olinex HARD-SPL" to your device
READ again. It's all written there (sticky posts)
First of all why should i ASK if there WAS AN ANSWER TO BE READ???
I have:
1. Tried to flash using exact intructions in:
http://forum.xda-developers.com/showthread.php?t=431218
Yes, the STICKY POST!
2. I have tried to flash from card whit hard_SPL:
http://forum.xda-developers.com/showthread.php?t=445662
Yes, again the STICKY POST!
And of course:
http://forum.xda-developers.com/showthread.php?t=446070
I have changed cables, ports. The flash seems OK, it says "olinex" in boot-loader but it has never finished.
Have searched the forum for other similar problems and found this thread.
I do not feel the need of repeating myself. Was hoping for some help and answers...
I am running windows mobile device center on a Vista 64 bit laptop.
I have a t-mobile wing that I got second hand. The wing has OpenTouch V7.6 BP WWE.
Here is the problem,
I am trieing to flash the rom to the latest T-Mobile update. When the flash starts the activesync connection drops and it never gets to even 2% done.
I have also tried to flash to different Ver. of OpenTouch and same thing.
Is this a problem with the phone or yet another Vista Issue...........
ANYONE !!!!!!!!!!!
omg! we have the same problem dude i wanted to flash the latest t-mo wing rom but then activesny drops and never installation progress never reach 2%.... will sum1 pliz help? i think this is not a small issue here pliz some1 help
I flash from vista 64 all the time run flash as Administrator
i can flash HERALD.ASerg.Clean2.WM61E.WWE and also HERALD.ASerg.9.WM61E.WWE.6pp(which i am currently using) but i cant flash the t-mos really need help pliz
Solution for flashing from Vista 64bit and postin only once
I do have the solution for your issues (specially looking the amount of posts you have done since your incorporation to XDA-Dev's):
1) Go to the top of the page, near to your username
2) Look the third link in the brown menu bar, from the right (LogOut, QuickLinks, ...)
3) That's right: this one which says "Search". Click on it.
4) Write "Flashing from Vista" in the combo which appeared
5) Read the issues with Vista and specially with Vista 64 bit or even XP 64 bit
6) You'll have the solution, and you'll have found it by yourself. That's to be proud !
6b) In some cases, you'll find it's too hard to flash from Vista and you need XP or the use of SD card ;-p
thanks buddy but actually i am using xp32. so now?
is your phone Hard spl?
wingmanbill said:
I am running windows mobile device center on a Vista 64 bit laptop.
I have a t-mobile wing that I got second hand. The wing has OpenTouch V7.6 BP WWE.
Here is the problem,
I am trieing to flash the rom to the latest T-Mobile update. When the flash starts the activesync connection drops and it never gets to even 2% done.
I have also tried to flash to different Ver. of OpenTouch and same thing.
Is this a problem with the phone or yet another Vista Issue...........
ANYONE !!!!!!!!!!!
Click to expand...
Click to collapse
That's not Win XP 32bit...
On the other side, if you use Win XP 32 bit, did you hard-SPL ? Can you put all the data about your device ? (SPL, Radio, etc.) so that we can know what is happening ?
afn691 said:
That's not Win XP 32bit...
On the other side, if you use Win XP 32 bit, did you hard-SPL ? Can you put all the data about your device ? (SPL, Radio, etc.) so that we can know what is happening ?
Click to expand...
Click to collapse
I too had trouble flashing the default ROM on my Wing. The secret is actually to open up the official RUU application, then search your Temp folder for two NBH's, the RUU_signed.nbh, and the SPL.nbh. You need to then copy them into the RUU folder of Flash Center, run that as administrator, and make sure to flash without SD card. That's the way that I used to restore mine to stock from Hard-SPL.
I synchronize my phone using ActiveSync. After flashing wizzard my rhodium wanted a driver. I didnt find it and now I'm standing in the tricolor.
Somebody help me please what to do !!!!! :-(
In the tricolour screen (the bootloader), does it say "USB" at the bottom ? If so, you should still be able to flash it ok. Though if there is a missing driver on your PC, it might just come up with an error and not be able to flash it. You could still try flashing from SD card in that case.
I did a soft reset and my old ROM was boot. Driver is missing. I have to install it. Thx
Wihtefaust said:
I did a soft reset and my old ROM was boot. Driver is missing. I have to install it. Thx
Click to expand...
Click to collapse
if you want to obtain the missing driver, you shouldve left the phone on the tri colour screen, and now this is my question, what OS are running? Win7 or XP? if youre on Win7 its going to search for the drivers on the internet and it should take 5 mins, as stated above if the drivers are installed it should say USB on the bottom and should be ready to be flashed, this happens to me once in a while when i flash a ROM, i just leave it on that screen and let the computer do the work and sometimes the RUU which is the program u use to flash a ROM will have an error, thats fine, just re run the RUU and should be fine from there
My OS is win XP, but this computer is adjusted using XP lite. One of important component is removed (maybe drivers support... idk). I did not know that I have these problems during the flashing on this computer.
Wihtefaust said:
My OS is win XP, but this computer is adjusted using XP lite. One of important component is removed (maybe drivers support... idk). I did not know that I have these problems during the flashing on this computer.
Click to expand...
Click to collapse
If you have the ActiveSync drivers it should be automatic. If you were able to Sync with ActiveSync, you can flash. Just let it install the drivers by itself or download ActiveSync again and install and try again.
or flash from memory card.... no need for drivers.
Wihtefaust said:
I synchronize my phone using ActiveSync. After flashing wizzard my rhodium wanted a driver. I didnt find it and now I'm standing in the tricolor.
Somebody help me please what to do !!!!! :-([/QUOTE
Copy RHODIMG.NBH (you can take from any Rom, sometimes it has another name, rename it rhodimg.nbh) to your SD card using a card reader form your computer
Put it in your phone than start. It will ask you to push start button to begin flashing.
After flash restart phone with red button under battery cover
Click to expand...
Click to collapse
Have you tried doing a Windows update while the phone is hooked up to your computer? Your computer probably just doesn't recognize the phone. I had that problem when I did my first flash. Windows update just found the drivers and installed them and I was good to go.
I think what he was trying to say is that he used N-Lite to strip down his XP install and removed some critical driver or possibly PNP pieces..
hx4700 Killer said:
I think what he was trying to say is that he used N-Lite to strip down his XP install and removed some critical driver or possibly PNP pieces..
Click to expand...
Click to collapse
I understood that but if ActiveSync works, then flashing should work as they are the same driver. Probably needs even less components than ActiveSync.