Related
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
bamse said:
albetratz said:
i want update radio update but its locked at %10 then i restarted
and i want to enter bootloader but nothing come to screen. no power no bootloader!
how can i solve this problem...
Click to expand...
Click to collapse
You should have read the instructions before trying the upgrade. ROM upgrade goes first, then the radio stack. I don't know if there's something you can do yourself to fix your device, or if you need to have it reflashed by your supplier. Anyone else?
Click to expand...
Click to collapse
Hi,
Seems like you are another of the many victims who got problems
after trying to upgrading new ROM & Raidio stack. Hope you still
got that warrant and get it replaced with a new one. Otherwise
you might have to try what some crazy guys do here trying to fix
it by doing all sort of bootloader etc.. Hope those who are trying
to get the upgrade ROM and Radio stack be very careful and make
sure your device are from the same supplier or distributor where
you got the new upgrade. Otherwise it will be screwed. Dont learn
your lesson the hard way.
same problem here.
i've got the O2 NL XDA
downloaded the 3.15 and radio updates from O2 NL website
installed updates as per instructions
1st update went without a hitch
2nd update totally screwed my xda.
now it takes a long time to start up, and when it does it just displays a white screen with a blue taskbar.
tried the bootloader way of flashing the rom, but still no luck
luckily I can send it back in to O2 to have it fixed.
I may try to do it by backup up another XDA, and reflashing mine.
Same prob with me..
I've got exactly the same problem. I downloaded the Rom update 3.15 and the new radio update. First I installed teh Rom update and after a hard reset I "installed" the radio update.
While updating the XDA hang and I waited for about ten minutes to see if the XDA was really hanging. I gave the XDA a hard reset but then the XDA didn't work anymore (white screen and blue bar on top).
I can still access the bootloader. I installed a Rom from a XDA which still works. Still no difference. When I tried to write the Radio rom to a sd-card I got that message that I have to connect one or another RS cable.
The XDA still doesn't work anymore. I have contacted O2 but they told me that they couldn't help me because they can't find my IMEI number in their system. I contacted the company where we ordered all the XDA's but I still don't have an answer.
Thank you O2 for being so nice with not helping me out with my one week old XDA without any scratch. I hope my XDA could be replaced as soon as possible since the XDA will not sold anymore when O2 changes to Telfort !
If you can make the ROM update work, you should be able to install the corresponding radio as well.
Try this:
1. Make sure you have the latest version of ActiveSync (=3.6)
2. Make sure the battery is fully loaded.
3. Extract the ROM update and Radio update to different folders.
3. Connect the cradle to AC-adapter and computer.
4. Put the device in the cradle and make sure it connects to ActiveSync.
5. Run the ROM installation application. Should take 5-6 minutes.
6. Run the radio installation. IMPORTANT: When you are prompted to remove power supply, pull the power plug from the cradle. If you do not disconnect power, the update will fail. I think this update took a little more time than the ROM update, and the device may seem "dead" for a while.
Good luck!
Hy Guys.
Are there any news about the problem flashing the XDA?
Tried last night to update my XDA to the last Qtek-Versions (ROM 3.16.52.....)
ROM Update works fine, but after the RSU Update the phone didn't work any more.
Have the same white screen with the blue taskbar and the little keyboardicaon down the right side.
Entering Bootloader mode there comes the Error Message "GSM Error"
Nice screen is the qtek "Booting Screen".
It shows
G <empty>
R <empty>
3.16.52
Hope there are any other hints to resolv this problem.
Have anyone got some experiences with sending it back to O2 with an "unoffical" Softwareversion?
Or is there any posibility to change the ROM Version to an old (original) O2-RomVErsion?
Thanks for any help....
Regards
Stefan
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Regards,
Riccardo
Riccardo said:
Hi Stefan,
I would suggest to try upgrade you device with any XDA ROM version by bootloader's CE to SD backup/restore and after try again to upgrade RUU by PC.
I know that upgrading/degrading by bootloader is the more safety way to do it.
Click to expand...
Click to collapse
SD-Card Writer just orderd
But I don´t know if it will work. Since the Bootloader says GSM Error, I think there will be no other posibility to restore it.
Let´s wait for some days, hope and we will see.....
Stefan
My wife gave me an xda2 today,thought I'd use official 02 upgrade,so it's all perfect.Disaster....
Upgrade failed.Stuck in bootloader mode.
Eyes bleary from reading forum.Do I have to flash a new rom?If so which one.Please help.Thanks in advance.
Not much help to you now, but the ROM upgrade probably wasn't necessary as new XDAIIs have the most up-to-date ROM installed.
How far has the ROM upgrade gone? If it hasn't wiped the supplied ROM are you able to do a hard reset?
disaster.
Thanks for reply!
The rom on o2 site had higher number,so thought it more upto date.
Anyway,have tried hard reset,power button and soft reset .No better.
Just stays in bootloader mode,serial, or usb when attached.Think it needs reflashing,using sd card,but not sure to try image tool,or xradit,or another tool I forget,being new to this.
Also,am advised on forum to open upgrade and click on exe. file.Not sure which exe file. :?: Thanks in advance.
First of all THANK YOU all of the Great Minds of XDA Developers for all the support and great work you do for us!
a lot of your work, support and software and advice has been priceless help!
Any way no ass kissing here, just wanted to say thank you. ...and ask for help. As you probably know, there has been a lot of problems and issues with Prophet. (and very little or NO support and from manufacture and from providers. and there is not much available from xda developers forum users on this device. Though there has been great amount of support on any other devices. which has made me a happy user of Magician. But to cut it short, PLEASE HELPPPPPPP with Prophet!!! I can't reflash my XDA Neo with new WWE rom due to CID (vendor ID) error! It comes with german rom and I don't read german but love the phone! (and stuck with 2 year contract!) I tried aWisard utility numerus times in hopes that it would work despite the design for different device. I tried all kinds of roms available out there with no luck. and ofcourse HTC or O2 wouldn't help in any way! (different O2 support
techs said to me that I couldn't flash my Magician with WWE rom becouse it would kill the device! And I had it flashed in all the possible languages!) Any way, my magician is now a history (sold) and my new prophet is great pain in a ass!
Do you guys think you could help all of the xda community (and unlucky suckers) out here and help us overcome CID error so we can update/change our roms? (and screw the HTC, Qtek, Imate and O2 for such a poor support!)
I would greatly appreciate it! and it goes from all of us!
hi aleksandr
Just go the link below and follow the instruction to unlock the CID.
I just upgraded my 818 Pro to JAMin ROM, run very smoothly.
http://forum.xda-developers.com/viewtopic.php?t=37386
Hi, thank you very much for the reply! I did try this option but I have a little problem with Wisard program. I ran all the commands, enabled rapi,backed up my rom, ran unlock CID command, it returned "success" line, but when I try option -w- to write new rom into my prophet and get to "select OS rom file" where it saids to enter numbers only I don't know what to enter in the command line since the program doesn't have any roms listed in the command line screen. I've tried entering the rom release number, I even tried renaming rom to a number and I have placed the rom nk.nbf file in all the possible folders including "rom" in the program directory. but stil, once I hit enter, the command line window shuts down. could you advise?
and I did put the aWizard folder and rom file in the root directory on c:... tried d: too... stil, no result
Hi Alek,
Try this....
You now have a device that is CID unlocked, exit aWizard and locate the downloaded RUU update you now wish to load to your device. You should not need to use aWizard to do the flashing, just use the aWizard program to unlock the CID from the device.
I too have a Dopod 818Pro and I successfully flashed it to the new I-Mate JAMin ROM. All I used aWizard for was to unlock the CID on the Dopod 818Pro then exited aWizard and just used the downloaded RUU update.
Regards,
voyager
Thanks voyager, I guess you're very fast typist :lol:
Hi aleksandr,
Did you did an ActiveSync with your Prophet first then run the aWizard? For me I just run aWizard to enable RAPI and unlock the CID on my 818 Pro. Then I just double click on the latest JAMin ROM exe file, it detect my 818 Pro without any problem.
ualvoyager said:
Hi Alek,
Try this....
You now have a device that is CID unlocked, exit aWizard and locate the downloaded RUU update you now wish to load to your device. You should not need to use aWizard to do the flashing, just use the aWizard program to unlock the CID from the device.
I too have a Dopod 818Pro and I successfully flashed it to the new I-Mate JAMin ROM. All I used aWizard for was to unlock the CID on the Dopod 818Pro then exited aWizard and just used the downloaded RUU update.
Regards,
voyager
Click to expand...
Click to collapse
First of all thank you guys for getting involved and helping! I really appreciate it!
well, I tried just to CID unlock it with aWisard, got "successful" message and then I ran about 10 different upgrades from different providers, qtek, Imate, etc, and still got the wrong vender message!
hey mamakap,
you're right on the fast typing, my fingers are still burning...hee hee
voyager
mamakap said:
Thanks voyager, I guess you're very fast typist :lol:
Hi aleksandr,
Did you did an ActiveSync with your Prophet first then run the aWizard? For me I just run aWizard to enable RAPI and unlock the CID on my 818 Pro. Then I just double click on the latest JAMin ROM exe file, it detect my 818 Pro without any problem.
Click to expand...
Click to collapse
I usualy ran after sync, since the aWisard said it has to be fully ran. I will try it now!
Thank you! hopefully with all of your support I'll get the nedded results! Thanx!!
ok, just tried enable rapi with active sync off, the aWisard reopened and reastablished connection, but it still not finding the rom file.
wait a minute, does the rom file has to be in .nbf format or .nba?!
I'm looking right now for Extend Tool (64HTC Extended ROM Tool) and will convert the rom rom to nba file and see what happends.
man, I wonder how it worked for you just running unlock CID command and upgrading with the upgrade file!
Alek,
You already unlocked the CID from your device did you not? Your first post said you got a success message.
Put your device on the cradle or plug in the usb cable. Let ActiveSync do its thing then after the sync just double click on the RUU update you want to install. Follow the install wizard (NOT aWIZARD) of the RUU update. You do not need aWizard any longer to update the ROM, just use the RUU update you downloaded.
post if you need further help.
voyager
ualvoyager said:
Alek,
You already unlocked the CID from your device did you not? Your first post said you got a success message.
Put your device on the cradle or plug in the usb cable. Let ActiveSync do its thing then after the sync just double click on the RUU update you want to install. Follow the install wizard (NOT aWIZARD) of the RUU update. You do not need aWizard any longer to update the ROM, just use the RUU update you downloaded.
post if you need further help.
voyager
Click to expand...
Click to collapse
I've tried that several times and its still returnes the error!
Alek, one more thing ... you do realize that by doing this, you will wipe your device clean (hard reset) and you will need to load everything from scratch. If you use a back up program like Sprite or SPB backup YOU CAN NOT USE THAT BACKUP once you do this!!! You will be loading everything from scratch.
Just letting you know!!
voyager
OK Alek,
Tell me EVERYTHING you have done up to this point. I need to know what device you have, what ROM is currently on it and what ROM you want to flash with. Give me 5-10mins and I'll check back....lets try to get this resolved for you tonight.
voyager
yep! I do know this.. thank you though! I had an experience with Magician on that but I guess it's not much help with prophet though!
I haven't installed anything on this device yet.. just played with ExtRom, unlocked it and deleted O2 staff out of it just to see if I can do it But I do want to get the right OS in here first and then I'll worry about the rest of programs..
you guys wouldn't happen to have Extend Tool (64HTC Extended ROM Tool)would you? I'm visiting my family and I'm on my brothers PC dont have all my staff with me,and can't seem to find it on the XDA FTP
:?: What 64HTC Extended ROM tool are you referring to? If you're on your brothers computer do you have an ActiveSync connection to YOUR device? If so, is all synced up with your Outlook profile etc...?
First I need to know which Prophet you have (Dopod 818Pro, I-Mate JAMin or Q-Tek S200).
First let me say this, if you have a Q-Tek S200, I don't think you are going to be able to upgrade the ROM. I have seen several threads here that indicate that somehow Q-Tek S200 is permanently locked and that the aWizard program will NOT work on it no matter what, (or at least until some geneius here figures it out
Please let me know
voyager
ualvoyager said:
OK Alek,
Tell me EVERYTHING you have done up to this point. I need to know what device you have, what ROM is currently on it and what ROM you want to flash with. Give me 5-10mins and I'll check back....lets try to get this resolved for you tonight.
voyager
Click to expand...
Click to collapse
Hey, thank you so much! I really appreciate it!
ok, I have XDA Neo, German Version
rom 2.9.4.30 GER
rom date 2.14.06
protocol 413.1.03
ExtRom 2.9.4.120
First I have unlocked ExtRom with Wizards Utility
Then I tried to reflash the device to WWE rom with different upgrade utilities from different venders, tried Qtek s200,it didn't work, reterned wrong Vender ID error, then Imate- same result, then Dopod, using diferent RUU wizards, including Wizard Rom Upgrade Utility NoID.
still, no luck..
then I tried aWizard,
first I ran Rapi enable
second I made a back up of my own rom,
then Unlock CID,
then tried writing rom using aWisard, didnt work, aWizard doesn't finds any roms(and the program and rom are in the root directory of c
then tried just unlocking the CID and use Upgrade Wizards again, still, no luck!
tried praying, that didn't help either!
thinking about beer now! But I don't think that would help either
I did sync with PC and outlook.. activeSync4.1
I even tried flashing it with Danish rom, that I couldn't install it either..(I've read on XDA that flashing danish rom first than and only than I could try it to put WWE in to it. well, that didn't work either)
I tried running all possible rom upgrades that are available, and always got wrong vender id error.
even after aWizard reported that my rom was unlocked!
so I have no Idea what else I can try!
may be getting drunk and "sync it in the toilet"!
If we get this to work, you owe me a beer!!! OK, here's what I need you to do...
1) I tried researching this board for any signs of the O2 Neo being permanently locked like the Q-Tek S200, could find NOT anything. (edited, could NOT find anything)
2) Do you have a copy of the I-Mate JAMin RUU update on your brothers computer? If so great, if not, go get it. Try the latest one that came out yesterday.
3) Once you have this I-Mate JAMin ROM (save it to the Desktop for easy finding later) let me know.
4) Also, make sure you have ActiveSync 4.1 and it is set up and you have synced at least once with it. It doesn;t matter at this point what PIM info is on it since its going buh bye ina while, I just need it synced with a REAL partnership, not Guest.
Let me know when you have all these things done...
voyager
you've got the deal on bear! all you can drink! I'll bring you the german staff on my next visit to states!
any way, got it all! Imate jamin rom and sync has been done!
OK,
1) do a soft reset on the device. Once the device is fully up again, plug the usb cable in and let ActiveSync do its thing.
2) Open aWizard. Run the Rapi deal again. After that run the unlock CID.
3) If you get a success message after the unlock CID, CLOSE aWizard.
DO NOT UNPLUG THE NEO FROM THE USB!!! Let me know when this is done.
I found your 64HTC Tool:
http://buzzdev.net/component/option,com_remository/Itemid,100/func,fileinfo/id,196/
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
N1cholas said:
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
Click to expand...
Click to collapse
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
egzthunder1 said:
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
Click to expand...
Click to collapse
I'm running windows version 7. and no i didn't unlock the device. i just ran the installer application (i hadn't found a detailed install manual) i'm not entirely sure how i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
N1cholas said:
I'm running windows version 7. i'm not entirely sure i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
Click to expand...
Click to collapse
By bootloader, do you mean the three colored screen?
egzthunder1 said:
By bootloader, do you mean the three colored screen?
Click to expand...
Click to collapse
no, the screen that says serial/usb at top and 2.07 at bottom
I just wanted to make sure that we were on the same page
In my opinion (and this is just a theory), Windows 7 (since it is a beta) does not have the necessary drivers to recognize the "usb device". Hence, when you put it in the cradle, it just doesn't see it. Again, this is just a theory...
You may want to get a hold of a machine with XP (that is if you didn't make the one you are using a dual boot). You should be OK if you try to flash via XP.
If everything else fails, you can always use mtty and flash via SD card (the procedure can be found in the wiki).
I had the device synced up before the install. it's just having issues syncing while it's in the bootloader mode. The device actually appears in the usb devices, but doesn't sync. i was thinking that the device might have to be authenticated with local software(on the sx66) in order to sync. I'm using the windows vista drivers. I do have this machine dual boot, but it's not any other version of windows i'm using
Your device does not have to sync in order to up/downgrade. Think about it this way... the RUU will put the device in bootloader anyways.
Just run the installer of the stock rom (the upgrade from Cingular).
@N1cholas: Please correct me if I'm wrong. I'm just a little confused. Are you expecting MS Active Sync to show as it usually does when you are syncing your phone? If that is the case, it won't happen when on boot loader. Are you getting any error when trying to flash or you haven't tried to flash yet?
Advise:
1. Keep your hopes, don't get despert. Egzthunter is a master
2. Make sure you follow the guide... Step by Step to upgrade.
3. If it'll take you too long to complete the reading and flashing, reset your phone and put it to charge. You won't be able to flash with a dead backup battery. Main and Backup battery won't charge while on bootloader.
Edit: @Egzthunder: Sorry mate, while I was thinking, drinking coffee and writing you had already replied Like I said, your the help master. Once again, I encourage the MODS to propose you to be part of their teem. You're always there to help.
Mark
i'm going to head off to school, but it's not working. when i try to run any mods i get an error saying that it cannot communicate with device.
Yeah! Egz for MODS!!! Woohooo and Xplode too and someday..me! LOL (no i mean it!)
windows 7 uses the same drivers as vista
beakybal4 said:
windows 7 uses the same drivers as vista
Click to expand...
Click to collapse
Why do you think I don't trust it?
@N1cholas,
I apologize since I ended up going to bed yesterday night.
I think your best bet will be to find yourself a PC running XP and try the reflash in that since it seems to me that something is going on with the OS.
@red and mark
Thanks for the support, guys!!! But you guys are awesome as well!
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
N1cholas said:
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
Click to expand...
Click to collapse
You will not see the device in any type of sync software (call it ActiveSync, WMDC, etc). I hvae uploaded the SX66 stock installer from Cingular, so give that a shot
Here you go
SX66Update.exe
Like I said... XP computer. Also, for the SD flashing, you need to look for something called mtty and instructions on how to use it.
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
xplode said:
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
Click to expand...
Click to collapse
Hey xplode,
To be perfectly honest, I haven't flashed 2003 since 2006, so I would be lying if I told you. Feel free to add it to your database if you wish. FYI, this is the upgrade that Cingular Wireless used to offer when the SX66 was still available in the at&t website.
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
N1cholas said:
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
Click to expand...
Click to collapse
Did you try the update that I gave you?
i ran it, and it said it was trying to get the settings from the device, then it just disappeared lol. now when i run it, it extracts the install data to the temp folder on my pc, then just disappears
Hi,
Help me please just me and that happens to me the mistakes my God.... I had the original ROM version coming with my diamond2, put the upgrading and went well until the moment he arrived at 9% and restart the pda, re-install I think is normal, however the installation continued until k stopped in 18% and after a long time gave a notice of error (262) made the recovery as recommended and continues to give error ....
I do help me please
This just happened to me too
My phone was hardspl´d
It stuck at 18%, but no error message so far. Did you unplug your phone?
Read this:
http://forum.xda-developers.com/showthread.php?t=425913
I'm not sure. Have you flashed other roms before? Perhaps you have a bad download. I know the servers are overloaded from all of us geeks sucking down the WM6.5 rom... perhaps its bad.
What I normally do is put the phone in bootloader mode first by holding VolDown, while resetting the phone. This will give windows time to install the proper drivers and get situated. Once done, try flashing again.
I think 262 is a connection error. Probably driver related since you said you ran your stock rom. But check your cable. Make sure its secure and reliable. Next try another USB slot. If nothing else try a different computer... sometimes PCs just will not cooperate.
Thank you very much fighter, will try that.
I had Official 6.1 Asia WWE installed, HARDSPLed. Tried to upgrade to 6.5 on my computer and my laptop, nothing worked. Both stops at 9%, disconnects, comes back and stucks at 18% again. Had to go back to 6.1, this time it worked to bring phone to life.
My phone was bought in Taiwan.
Guess I am out of luck
I think the best way to upgrade is as follows:
1. Run the RUU_Topaz_S_HTC_WWE_2.16.405.4_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe on your PC/laptop to extract and get the RUU-signed.nbh.
2. Copy the RUU-signed.nbh to topaz SD card and rename to topaimg.nbh
3. Upgrade new ROM from SD card.
I had the same 262 error as well, screen went blank for a second at 9% and finally freezez at 18% with the error message. Heres what you need to do:
Update your HardSPL to 1.83
Flash 6.5 again
????
Profit!
Hello,
already did everything you say and nothing. I liked to tell me where I can get the former Rom wm6.1 because meeting.
help me please
duongla said:
I think the best way to upgrade is as follows:
1. Run the RUU_Topaz_S_HTC_WWE_2.16.405.4_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe on your PC/laptop to extract and get the RUU-signed.nbh.
2. Copy the RUU-signed.nbh to topaz SD card and rename to topaimg.nbh
3. Upgrade new ROM from SD card.
Click to expand...
Click to collapse
Would you be so kind as to enlighten me/us on how to extract the nbh file from the executable file.
Thanks
player911 said:
I'm not sure. Have you flashed other roms before? Perhaps you have a bad download. I know the servers are overloaded from all of us geeks sucking down the WM6.5 rom... perhaps its bad.
What I normally do is put the phone in bootloader mode first by holding VolDown, while resetting the phone. This will give windows time to install the proper drivers and get situated. Once done, try flashing again.
I think 262 is a connection error. Probably driver related since you said you ran your stock rom. But check your cable. Make sure its secure and reliable. Next try another USB slot. If nothing else try a different computer... sometimes PCs just will not cooperate.
Click to expand...
Click to collapse
How can u exit bootloader screen? Only by removing the battery or...?
Thanks!
I do not have with me the adapter card to do this
There is also a problem is that the pda now I do not go the menu with the three colors blue, green and red, until I have done a hardreset and nothing ....
at least I no longer ask the solution with the ROM 6.5 we only have as I had before ... and wanted my pda to work help me please
Little history for my friends with same problem here:
1. Bought Diamond in Taiwan with Chinese;
2. HARDSPL 1.33;
3. Install Asia WWE 6.1 ROM;
4. Try update Official WWE 6.5 ROM, no luck, remove battery and put back;
5. Reinstall Asia WWE 6.1 ROM, everything back to normal;
6. Update HARDSPL 1.83; Ask brother to donate
7. Install Duttys ROM or Official ROM works too
Hello,
I already installed the previous ROM with the 6.1 and everything was normal.
I tried to install again the OFFICIAL ROM 6.5 and the problem remains back to the error at 9% and 18% for the progress bar giving an error (262).
not understand some things as:
6. Update HARDSPL 1.83; Ask brother to donate
7. Install Duttys ROM or Official ROM works too
is there any solution?
can help me
Sorry:
1. install Hard-SPL 1.83.OliNex (http://forum.xda-developers.com/showthread.php?t=520312)
2. install 6.5 ROM or Cooked Rom.
It resets 9% again in Official ROM, but reconnects and go to 100% (no stop 18% again).
Dutty ROM no stop at 9% or 18%.
problem solved
thanks for the great help amazing
thank you very much
hello
the memory card is not me out with the official wm 6.5 ROM
what can I do to boot the card?? I have a diamond2
ah no problem of card pk started the card with the adapter to the PC and read it perfectly.
pesquisar
AntonyWatson said:
Would you be so kind as to enlighten me/us on how to extract the nbh file from the executable file.
Thanks
Click to expand...
Click to collapse
When you run the RUU, the RUU-signed.nbh will be extract temporarily to a folder in driver C:
(For me: C:\Users\Duongla\AppData\Local\Temp\pft51D9.tmp)
Just do a search and you'll find it.
And remember to HSPL to 1.83.
i have the same problem too
hello
i have a diamond 2
ihave olinex 1.83 from here http://forum.xda-developers.com/showthread.php?t=520312 and i can not install ANY wm6.5 rom!!! on the other hand EVERY 6.1 rom i have trie (5 different greek and english) work perfect?!?!??
any suggestions?
thanks
i had the same issue
i was running 6.1 (stock rom) which was hard spl'd
i had the same error kept going to 262 and haviong to be recovered
so i re hard spl'd with the latest one, and it worked fine after that,