My Xda mini was fine for a little while.. and then the phone just dead suddenly.
when I reset the device, there is NO GSM at the start up screen (the O2 logo).
Then i tried to upgrade the rom using JAM 1.06, and qtek 1.11 and the upgrade failed at the step 1. UPGRADING RADIO.
Now the xda wont start, just a screen with serial v.1.00.. tried and tried and nothing works.
It seems that the radio wont upgrade because there is no gsm.. i'm not sure what to do now.
Sounds like you may need to call tech support to have it repaired
Likely ur problem can be resolve
screen with serial v.1.00
Click to expand...
Click to collapse
The above message means the Mini is in "boot loader" mode. Try to reflash again. It should work. Take away the other 2 .nbf file and left the "radio.nbf" in the same folder which you going to flash. Retry the same thing (when the Mini shown with "Serial 1.0" if nothing is connected, it'll show on your screen the message "USB 1.0" if the sync cable is connected). Good luck and god speed .
cheers,
cyberjaya
Related
As I have read through the threads in this forum, I am not the only one with this problem, but for some reason none of the solutions make sense to me.
Earlier today, I was trying to use the "Prophet AKU2.3 pdamobiz customized rom released [G3 Only]" to downgrade and didn't notice that my XDA NEO is 4G (the tool is for 3G only). Now after each boot the screen is stuck with the Boot Page showing:
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS 1.0.13.21
I am so pissed at myself and so frustrated.
I have tried hard-resetting and the problem still persists. I am able to get into the Bootloader by holding the camera button and pushing soft-reset. I am just not sure where to go from here. I connected the phone per usb to the computer. The phone indicates that it's connected to USB. Every ROM upgrade file I have tried gives me an update error, since they are all expecting the phone to be connected to the computer through ActiveSync.
I bought this phone in Germany and currently live in the US, so it will be tough to send it back for repairs. Plus, I don't even know if I have the original receipt anymore.
Any help would be greatly appreciated.
pengo said:
As I have read through the threads in this forum, I am not the only one with this problem, but for some reason none of the solutions make sense to me.
Earlier today, I was trying to use the "Prophet AKU2.3 pdamobiz customized rom released [G3 Only]" to downgrade and didn't notice that my XDA NEO is 4G (the tool is for 3G only). Now after each boot the screen is stuck with the Boot Page showing:
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS 1.0.13.21
I am so pissed at myself and so frustrated.
I have tried hard-resetting and the problem still persists. I am able to get into the Bootloader by holding the camera button and pushing soft-reset. I am just not sure where to go from here. I connected the phone per usb to the computer. The phone indicates that it's connected to USB. Every ROM upgrade file I have tried gives me an update error, since they are all expecting the phone to be connected to the computer through ActiveSync.
I bought this phone in Germany and currently live in the US, so it will be tough to send it back for repairs. Plus, I don't even know if I have the original receipt anymore.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Extract the rom file you are using to flash your phone, to a folder on your pc, than Extract the file i attached ("ROMUpdateUtility-NoVendorID.zip") into this folder. than connect your phone to pc and double click on "ROMUpdateUtility-NoVendorID.exe".
cross your fingers.
reboot the computer first
I guess the trick was to reboot the computer first. After the reboot, I was able to use the provided No_Vendor_ID Updater to reflash again. Now it's all set. Thank you very much for the advice.
pengo said:
I guess the trick was to reboot the computer first. After the reboot, I was able to use the provided No_Vendor_ID Updater to reflash again. Now it's all set. Thank you very much for the advice.
Click to expand...
Click to collapse
cool, any time.
Hi,
I have tryed to upgrade my rom to a new version (Prophet WM5 AKU3.2 v3231). Followed the stept correctly, however my phone does not boot anymore. It gets stuck in the qtek logo (when it displays the AKU version i´ve got) and the sceen gets all shacky.
An addictional problem is because it is stuck at that point it does not connect to my computer....
What can I do to fix this, any good suggestions
Thank,
Sebastiaan
You should be able to enter bootloader mode by pressing and holding the camera button while you power on your phone. On the bottom left, you should then see "USB" - connect it to the PC and flash it again.
Had to do this yesterday after flashing failed.
Mike
thanks it worked
Sebastiaan
Error [296] Upgrade Only
Hello
I have same Trouble & I Make Bootloder from USB but Always I get This Error
ERROR [296] UPGRADE ONLY
This NBF file connects used for your PDA Phone. Please get newer NBF file.
Note: I try to Upgrade to 2006-11-12_Prophet_WM5AKU2.3_lvsw_edition but my Phone Stack So I reset as say after 30 m
Now I trying to back to Old Software from I-mate
Also I try to upgrade to 2006-11-12_Prophet_WM5AKU2.3_lvsw_edition but no Connection....
Please help me I with out Live (Phone)
I know it sounds strange but i used a different USB port and then it did connect. Now that everything is back to normal i can use the old one again.
maybe it works for you as well
I tried doing that, but for some reason my computer doen't recognize the device...pls help!
1st off I DID use the search button.... 2nd HELPPP ME!!!
Waaah :'( I have a most intriguing problem I was running pdaviet 4.0.0.6 Touch for almost 2 weeks now without a single glitch.. the phone fell on my carpet and went to bootloader screen and eversince then it has never recovered I tried a hard reset it didn't work when I was pressing the send button it did nothing I did some forum searches and tried putting back the nvid RUU and it said that the update was succesfull and the progress bar on the phone moved accordingly but it went back to the bootloader screen ... then I tried pdaviet temp rom that was in the package still no go I can tell it works somehow because the USB lights up in the bottom left when I plug the usb cable and the progress bar that moves, but I'm getting desperate IPL and SPL info is in my sig...
same same... but i dropped mine before flashing the new PDAVIET touch rom.. still went fine..
now, it still flashes... RUU says its successful.. but PDA just reboots back to bootloader..
i can charge my phone fine in bootloader.. i can see the USB come on when i connect it to my computer.. other than that, can't do anything...
i've tried everything the past 2 days.. looks like i'll have to send it back to dopod.. will let u guys know what happens... probably something got damaged..
struck at bootloader
I tried WM6 (4.0.0.6 touch) from WM5 AKU 2.2 but it failed in between with some write message,which was bit strange as I didn't touch any key on laptop during that time and no program was being run at that time. (I am using VISTA Home premium). I got my phone into bootloader but it does not connect to my laptop...so cant upgrade back to AKU 2.2. In Windows Mobile Device Center, I cant see my device connected. So is it particular to Vista or my phone got bricked?
I am yet to try on Windows XP, which I have to arrange.
Please advise.
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
charliess said:
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
Click to expand...
Click to collapse
I tried the same but when I run ROMUpdateUtility_No_VenderID, I get a message 'Update Error, 260' which tells further that PDA is not connected to laptop., although it is very much connected. However LED on PDA does not blink as well.
When I plug in this phone to Wall adaptor, LED does show up.
'USB' appears at Bottom Left corner of PDA when connected to laptop and certainly its getting recognised by Vista as it starts installing Driver as soon as this is connected to laptop.
Please suggest.
I am stuck in the same situation, although I have a G3, running 2.20 on IPL & SPL
Working now
I tried on XP (I was trying on vista before)..I had to install Active Sync as it was not installed on that PC, then run RUU update for AKU 2.2 and update was successfull. Now will try Touch 4.0.0.6 again but this time on XP.
Hope this time I wont have any problems.
Hello. I just got an HTC Touch Pro, and I want to upgrade the ROM, but when I try to upgrade to Hard SSP I lose the connection to my PC, and the device hangs and has to be reset. I tried copying SSPL-Manual.exe to my device and running it from there, but it also crashes the device. What can I do to fix this?
Thanks for any help.
Regards,
Jim Crutchfield
Long Island City, NY, USA
jdcrutch said:
Hello. I just got an HTC Touch Pro, and I want to upgrade the ROM, but when I try to upgrade to Hard SSP I lose the connection to my PC, and the device hangs and has to be reset. I tried copying SSPL-Manual.exe to my device and running it from there, but it also crashes the device. What can I do to fix this?
Thanks for any help.
Regards,
Jim Crutchfield
Long Island City, NY, USA
Click to expand...
Click to collapse
did you follow these instructions exactly:
from hardspl thread by rapheal elite team:
1) download Hard-SPL package from attachment, extract to an empty folder. make sure it's launched from a local drive (not through network drive, etc.)
2) you must Have Phone Synced with PC in Windows Mobile!
3) run RaphaelHardSPL-Unsigned_190_1_3.exe,
4) follow steps in the RUU, check device for prompts after PC shows loading bar.
5) it should go to black screen now.
6) SPL flashes, device automatically reboots, job done.
7) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.90.OliNex.
source:http://forum.xda-developers.com/showthread.php?t=410150
Thanks for the help, but I followed the instructions exactly and it still hung and gave me "Error [260] connection". Windows Mobile Device Center closed and I had to reset my phone. I've also tried copying the SSPLManual.exe file to my phone and running it from there, and it also hung. I did a hard reset, but that didn't help. Any other suggestions?
Has anybody come up with a solution for this? I see on other forums that other people are having the same problem. I'd really appreciate some help. Thanks!
Best,
Jim Crutchfield
Long Island City, NY, USA
after your screen goes to the boot launcher you have to go to unplug and uncheck allow usb connections in activesync (and then replug of course) The installation should then continue
I haven't read up on your particular device but that is pretty standard for hard spl (the unplug-replug)
Thanks, but my screen never gets to the boot launcher--it hangs at the Today screen with the little "please wait" wheel, which stops turning.
see if this helps:
http://forum.xda-developers.com/showpost.php?p=2639344&postcount=202
Hey i had the same problem, the circle thing would spins and stop and hangs.
http://forum.ppcgeeks.com/showthread.php?t=42503
this file did it for me hope it works for you, gl and happy flashing.
if you have Sprint, Telus or Alltel or Bell, flash default package (Raphael_CDMA_HSPL_037.zip).
Thanks! I'll give it a try and report back.
dear all,
first at all: I´m completely new here, so hello.
I finished reading the Wiki twice, also the guide from 'mskip' (Flashing your First GSM Raphael Rom (For Noobs)). very good and sounds very easy.
now I downloaded this file: RaphaelHardSPL-Unsigned_190_1_3
when I´m trying to flash, it results in a "error 202: connection". could the windows mobile device manager be a reason, because here is just an explanation with activesync. as I use win7 64bit, activesync will not run.
I also checked lots of posts here, but did not get a right answer which could lead to a solution.
btw I have the "MDA Vario IV"-version.
greetings, tris
EDIT:
Update: Now I downloaded "TAEL ROM v6.28244 RC2".
Connected mobile to PC, waited until it is connected via 'windows mobile device manager'.
Proceeded with the update (my image is 1.69.111.6) until the screen turned black and a progress bar is shown (0%). now error 262 appeared. have to unplug USB cable, reinstall battery and restart. old system is still working. what am I doing wrong? btw, same error on my laptop with win7 32bit with fresh installed 'windows mobile device manager'.
EDIT2: okay, and same on my other laptop with winXP and activesync.
You need to flash hard spl before doing anything else. Try putting the phone into bootloader (hold volume down, then soft reset), then connect it to your PC once it's in the tricolor screen and run the hard spl exe.
After that, just flash roms off your sd card. Make sure it's FAT 32 format, rename the ruu_signed.nbh to RAPHIMG.nbh, put it on the sd card root, and then go into bootloader and follow the instructions.
volume down and reset done. phone switched to tricolor screen. then I started 'RaphaelHardSPL-Unsigned_190_1_3', phone switched to gey screen with progress bar. 30 seconds later after 0% progress: error 262 appeared
EDIT: also when trying to update via bootloader, my image (1.69.111.6) will be left blank, I can´t see the version number which is currently installed.
I just hope you have a GSM TP/RAPH...
RAPH300 -> "T-Mobile MDA Vario IV"
but why do you ask? do I have the wrong software?
Just hear of those bad incidents with CDMA phones and GSM ROMs is all...
What does it display on the bottom of the screen when you boot into the tricolor screen/bootloader before you connect it to your PC and then after?
first serial, later USB
oh my god! *facepalm* okay for all the noobs out there: look at your phone. if you use HardSPL for the first time, you have a short timeframe to confirm "unsigned access to bootloader" via touchscreen. if you don´t do so, you will result in connection error 202 / 262.
thank you all, it works