OK, challenge for you. I have been saying how brilliant this site is, so a colleague has given me his prophet to fix.
It is stuck in the bootloader screen and only says "IPL 2.10.0001" and "SPL 2.G3" - yes I have identified the problem here as it is a G4 device...
However, I can't get the PC to recognise the device through the USB cable, so I'm not sure what else I can do. I have hard reset the device and got activesync running on the PC, but now I'm stuck...
Ramsfan_Jim said:
OK, challenge for you. I have been saying how brilliant this site is, so a colleague has given me his prophet to fix.
It is stuck in the bootloader screen and only says "IPL 2.10.0001" and "SPL 2.G3" - yes I have identified the problem here as it is a G4 device...
However, I can't get the PC to recognise the device through the USB cable, so I'm not sure what else I can do. I have hard reset the device and got activesync running on the PC, but now I'm stuck...
Click to expand...
Click to collapse
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
OK, I've been through that thread http://forum.xda-developers.com/showthread.php?t=353547 in full (I admit I stopped reading the first time when it said use Activesync).
I also discovered it only seems to flash from USB ports on one side of my laptop and not the other?!
I downloaded and tried PVTemp: I get ERROR [300] INVALID UPDATE TOOL
I tried http://v-dog.net/XDA/RUU_Prophet_220734_2207114_024721_NVID.zip NVID for Prophet: I get to 80% updating, then it stops with ERROR [326]: INVALID COMMAND - This NBF file cannot be used for your PDA Phone. Please check you NBF file.
I tried Upgrade HardSPL_G4: I get ERROR [300].
I tried RUU_Prophet_220734_2207114_024721_NVID utility. I get to 80% again - same problem ERROR [326].
Any more ideas?
Ramsfan_Jim said:
OK, I've been through that thread http://forum.xda-developers.com/showthread.php?t=353547 in full (I admit I stopped reading the first time when it said use Activesync).
I also discovered it only seems to flash from USB ports on one side of my laptop and not the other?!
I downloaded and tried PVTemp: I get ERROR [300] INVALID UPDATE TOOL
I tried http://v-dog.net/XDA/RUU_Prophet_220734_2207114_024721_NVID.zip NVID for Prophet: I get to 80% updating, then it stops with ERROR [326]: INVALID COMMAND - This NBF file cannot be used for your PDA Phone. Please check you NBF file.
I tried Upgrade HardSPL_G4: I get ERROR [300].
I tried RUU_Prophet_220734_2207114_024721_NVID utility. I get to 80% again - same problem ERROR [326].
Any more ideas?
Click to expand...
Click to collapse
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
dioxda2 said:
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
Click to expand...
Click to collapse
Is there a reason for this? Just to aim my understanding, the device has presumably at some point been flashed with incorrect software (there is no known hardware issue), so shouldn't it just be a question of re-flashing with the correct software?
I am used to working on mainframe and PC software, so pardon my ignorance when it comes to mobile technology. Isn't it just a case of rebuilding the operating system somehow?
dioxda2 said:
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
Click to expand...
Click to collapse
I'm in the sames circunstances than the post before.
Heart transplant the only solution? Some new updated proccess for recovery?
I'm very worried.
hi,
Yesterdayi I was dealing with the same problem.
I've got i-mate Jamin.
I solve it by flashing my pda with thisrophet_PV_Temp.
http://rapid+share.com/files/156034341/Prophet_PV_Temp.rar.html
Your pda will turn to wm5 rom. Than you can upgrade to wm6 Roms.
Hope this can be helpfull.
Note: rapid+share = rapidshare
Related
Hi,
I started a new thread because on my previous post I did not receive that much reactions so I try a brand new one.
A few months ago I bought this, in my eyes, really cool HTC Trinity, aka the P3600. One of the main reasons I bought this device was because I read on some forums that this device had GPS functionality, but at that time it was not supported/ebabled yet by HTC but properbly would be in the future. Off course I could not wait, so I tried to install a Dopod version which should enable GPS functionality. Unfortunately I've got a Dutch version of WM5 running on my PDA, so a ROM upgrade was not possible, unless the CID lock is removed. In order to accomplish that I downloaded the tool SSPL, installed it, and executed it on my PDA. After that I tried to install the Dopod ROM, but during the upgrade it froze up. After rebooting, the device frooze up during the startup (when it is display the MS logo for push mail). After that I retried the to run the update, but unlucky me, it stucks at 1%, then device reboots, and I receive the "ERROR [294] : INVALID VENDER ID". on the screen of my PC. My PDA is now worthless because it still freezes up during tje startup.
I' m still able to access the bootloader menu however but none of the ROM updates that I have at my dispossal are working. Unfortunately I do not have the Dutch ROM in my possesion and a quest on the Internet lead to nothing. However, this week I will receive a Trinity at my work (exactely the same). Is it possible to make a backup of this ROM and then restore it back to my nearly dead PDA? Or should i deal with this dead PDA in anoter way to bring it back to live again.
Any help is more the welcome
Follow this thread to CID unlock then just re flash. This should take care of your invlaid vender issue.
http://forum.xda-developers.com/showthread.php?t=293957
RebelShadow said:
Follow this thread to CID unlock then just re flash. This should take care of your invlaid vender issue.
http://forum.xda-developers.com/showthread.php?t=293957
Click to expand...
Click to collapse
JolietJake's Trin is not booting to OS, he can't run SSPL
stepw said:
JolietJake's Trin is not booting to OS, he can't run SSPL
Click to expand...
Click to collapse
Yep, that's right... If I only could
You may have to suck it up and pay for the unlocker from IMEI-check. I may be wrong, but I think you run that from your pc and only have to connect your trin via usb. I'm just not sure if you need a valid activesync conncection to use it - as you probably can't get that with a "zombie" trin.
Do a little research first if you are going to try.
If you try it, good luck!
http://www.imei-check.co.uk/m700unlock.php
psargent said:
I'm just not sure if you need a valid activesync conncection to use it - as you probably can't get that with a "zombie" trin.
[/url]
Click to expand...
Click to collapse
I indeed need an active sync connection, which I have.....
....during 10 seconds or so (only just after I rebooted the TRIN)
I also tried to use this tool in Bootloader menu. It's able to set up a connection through USB, the screen on my PDA goes gray and the message ".....ERROR" appears on the screen of my PC. After that the TRIN reboots and freezes up again . Fortunately I did not pay for the tool yet, i just downloaded it)
However I appreciate your help very much!
psargent said:
You may have to suck it up and pay for the unlocker from IMEI-check. I may be wrong, but I think you run that from your pc and only have to connect your trin via usb. I'm just not sure if you need a valid activesync conncection to use it - as you probably can't get that with a "zombie" trin.
Click to expand...
Click to collapse
Too bad, it's the same story, it needs OS/ActiveSync to be running to re-enter boot and flash SPL.
My friend's jamin when he tried upgrading with smart1 wm6
after the flashing process finished it gives the 3 colors of boot loader
the screen flickers continously with the 3 colors
no way to hard reset the device
and activesync doesn't feel it
I searched all the forum for a problem like this but I didn't find any
any suggestion please, or any help?
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
NetrunnerAT said:
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
Click to expand...
Click to collapse
Please how can i flash with the activesync doesn't notice my device and where's NVID Rom
Ok. I'll search for it but please help how can I flash it to the device which doesn't recognized or felt by PC
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
divxmaniak said:
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
Click to expand...
Click to collapse
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
must use NVID rom. maybe qtek nvid one from here? http://wiki.xda-developers.com/index.php?pagename=Prophet_ROMs
hasanemara said:
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
Click to expand...
Click to collapse
If the problem still there, Try to release the battery for 1-3 hours and put it again to the device, go to the boot loader and pray. Hopefully it could work. Actually, this way worked on my Himalaya and Prophet.
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
ekto said:
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
Click to expand...
Click to collapse
I shall try and tell you the result
error 260 this is the result
i have a slight variation problem like this...
1. i was upgrading my O2 Neo to the latest WM05 & the phone went to bootloader mode & the upgrade started searching for the phone as normal..then some error & it stopped upgrading while the phone was in bootloader mode..
2. at that time,i got an urgent call & had to leave the phone in bootloader mode...
3. when i came back..the phone was dead & now it wont startup at all.. not even in the bootloader mode.
4. Maybe the batteries dead...so i charged it (Over night)..nothing happened in the morning..
5. kept the battery removed for about 5-6hours & still nothing happens..it simply does not startup.
6.I've tried holding the camera button & resetting, but it wont go into bootloader mode.
7. i;ve tried holding the connections button + camera button _ reset but it wont hard reset...
can anyone help me here...
what can i do???
hasanemara said:
error 260 this is the result
Click to expand...
Click to collapse
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
ekto said:
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
Click to expand...
Click to collapse
No I didn't change any and I can connect my o2 xda mini to the same cable
I want to ask few technical question
HOW CAN A SOFTWARE DAMAGE THE DEVICE?
CAN A SOFTWARE FOR EXAMPLE BURNS A PROCESSOR OR SOMETHING LIKE THIS?
If So there will be a big problem with those types of devices
a virus for example can destroy my device's board or processor!!
Yesterday My friend went to an I-mate customer service who tel him that
the board had been destroyed by the bad software !!!!!!!!!
Please Give me technical advice about this problem
and is there a web site for him to buy this board (i-mate jamin)?
I've tried everything... even tried it on my desktop... but my phone just wont turn on now. i've kept the battery removed for more than 8hrs now... i've even charged it for more than 8hrs non-stop..nothing happens..
maybe i should get hold of a charged battery & try it with that battery...?
Any clue how to get my phone started??
got it working !!! PHEW... i used my HP battery which was charged & put it into it..now i've got my bootloader & i'm installing the new OS as we speak... 15% done.... keeping my fingers crossed
done.. got my HP Ipaq battery , which was charged & my new started up in bootloader more.. PHEW !!!
66% done... keeping my fingers crossed
ok, installed...now, one more problem..my touch screen's not working...???
Any idea what to do?
i installed "Prophet_PDAViet_Step1"
I dragged my Mini s out of the draw thinking it dead for the past few months, after using the battery jump start trick got her up and running again. now, after using mobile 6 on my other HTC i wanted to upgrade on this one, nothing fancy just bog standard mobile 6. its an O2 G4 model, I also checked it with the wizard service tool. I then used the hard SPL G$ tool to unlock it, that went fine. the device repowered and worked. I then tried to load in windows mobile 6 from this thread
http://forum.xda-developers.com/showthread.php?t=355591
after its started the flash I got an error message saying "error 300 invalid update tool" please get a newer tool, I have tried to run it again and now get the message " error 2641 cannot connect " and now all I have is an XDA with a red, green and blue screen showing IPL2.21.0001, SPL 2.21,0lip and "usb" in the bottom left corner
is it bricked? can I recover it, I will be gutted if it is bricked as I followed the instructions to the letter
btw I havnt disconnected it from the USB at all, just leaving it there until I get somne advice from here
update, bit the bullet and unplugged, soft reset and its all as it should be, on windows mobile 5.
so my question now is why didnt the Rom update in the link above work? or am I just a noob doing it wrong...
try downloading another rom and flash it again...even if it isn't connected in activesync ignore that and flash away...if that still doesn't work try your original rom wm5 and then flash a wm6 again...it's not bricked(see below)
stevescoots said:
I dragged my Mini s out of the draw thinking it dead for the past few months, after using the battery jump start trick got her up and running again. now, after using mobile 6 on my other HTC i wanted to upgrade on this one, nothing fancy just bog standard mobile 6. its an O2 G4 model, I also checked it with the wizard service tool. I then used the hard SPL G$ tool to unlock it, that went fine. the device repowered and worked. I then tried to load in windows mobile 6 from this thread
http://forum.xda-developers.com/showthread.php?t=355591
after its started the flash I got an error message saying "error 300 invalid update tool" please get a newer tool, I have tried to run it again and now get the message " error 2641 cannot connect " and now all I have is an XDA with a red, green and blue screen showing IPL2.21.0001, SPL 2.21,0lip and "usb" in the bottom left corner
is it bricked? can I recover it, I will be gutted if it is bricked as I followed the instructions to the letter
btw I havnt disconnected it from the USB at all, just leaving it there until I get somne advice from here
Click to expand...
Click to collapse
Download this RUU ,extract it and replace all the files in the folder with the RUU files in the Rom and run the RUU,it'll flash successfully .
stevescoots said:
update, bit the bullet and unplugged, soft reset and its all as it should be, on windows mobile 5.
so my question now is why didnt the Rom update in the link above work? or am I just a noob doing it wrong...
Click to expand...
Click to collapse
Your ROM Update may not have worked because, maybe it was not built for the G4 Wizard. so try anyother ROM
xda2_hasseb most of the WM6 roms available for download on xda-developers are G4 safe as they don't conntain ipl and spl flash....so you can safely flash a Windows Mobile 6 rom without bricking your Wizard
'XDA Mobile 6 Release 5 FINAL' is the latest custom build wm6 rom,build for both the devices,it can be flashed to both the devices G3 and G4 safely,its one of the most favourite roms.
Thakx xardas_90, i knew they didnt had the IPL and SPL with them but i didnt knew that it was IPL & SPL not the ROM it self that caused the Bricking of the G$ WIzards i thought Windows ROM for G3 and G4 were different but THANKS for the info. TC
Thanks for the advice, got it done and works a treat, except no data transfer or sms or net conncetion, still soldiering on, at best it will work, at worst, well i guess my son gets a hand me down lol
stevescoots said:
Thanks for the advice, got it done and works a treat, except no data transfer or sms or net conncetion, still soldiering on, at best it will work, at worst, well i guess my son gets a hand me down lol
Click to expand...
Click to collapse
You need to get GPRS/MMS settings configured,get these settings from your carrier,only then you'll be able to connect to internet/SMS/MMS, or check out the 'XDA Mobile 6 Release 5 FINAL' rom thread,you might find the appropriate GPRS/MMS settings there of your concerned network.
I'm new in these forums as well I'm new with flashing ROMs so obviously I messed up flash process and my device stuck in bootloader (tri-color) mode. This post I address to those unfortunate like me .
# Symptoms #
- ROM flash started and stopped at 17%. After recovery flash process stucks at 0% and pops Connection Error 262. Device is stuck in bootloader mode not possible to flash anything, hard reset does not help, flash from SD card does not help either.
# Possible cause for that #
1. In bootloader mode device shows:
Code:
Pola100
SPL-1.25.0000
CPLD-2
means that Hard SPL was not flashed before flashing ROM file (if Hard SPL was flashed then in second line will be written SPL-2.20.Olinex.).
2. Connection between ActiveSync and device was not established when flashing ROM file.
Before to go any further please take your time and read Polaris Wiki to get familiar with glossary and acronyms used here.
PROCEED ONLY if flashing original ROM does not help, hard reset does not help and flash from SD card does not work.
# Solution #
1. Download MTTY software.
2. Kill ActiveSync (Press Ctrl-Alt-Del and stop rapimgr.exe and wcescomm.exe processes).
3. Plug Polaris into usb port (Plug directly not through hubs).
4. Start MTTY after chose USB from PORT dropdown list (if it is not listed there then ActiveSync processes were not stopped).
5. in window type: set 16 0 (enter cmd mode)
6. after type: task 8 (this will format phone)
7. after type: task 0 (this will restart phone. Not always necessary)
8. soft reset
This procedure can damage your phone. Use it as last resort.
Official source in french here.
Now before flashing any ROMs read carefully how to flash (not install!) Hard SPL.
# P.S. about install and flash termins #
This error with flashing happened to my due misunderstanding between notions of installing something on your device and flashing. In my opinion those are completely two different things. As for first I understand of running some cab or exe directly on device. So problem comes when people sees install Hard SPL en device as they try to find some cabs or exes to install directly on device or they just copy all files to device. To make things clear Hard SPL "installation" actually is ROM flash process which must be done with maximum caution, but those who did not read Wiki won't understand it.
Cheers, whitealien
BiG THX @ Whitealien.
works to 100% on my Touch Cruise.
I flashed under Vista Ultimate...
# Solution # ... addition from me for Vista users!
....
2. Start Windows Mobile Device Center and Deaktivate USB Connection and then start Task manager end kill
Process wmdc.exe.
Rest of whitealien. and have fun!
Thank you!!!!
I had given up on this, and was sure my only option was a warranty repair :O
always welcome
Thanks, you've saved my Polaris.
Mine didn't want to react anymore to the soft reset, so I replaced your instruction 8 with:
Cmd>boot
and that did the trick.
whitealien said:
1. In bootloader mode device shows:
Code:
Pola100
SPL-1.25.0000
CPLD-2
means that Hard SPL was not flashed before flashing ROM file (if Hard SPL was flashed then in second line will be written SPL-2.20.Olinex.).
Cheers, whitealien
Click to expand...
Click to collapse
I had exactly the same problem, for whatever reason went back to original SPL before HARD SPL.
I solved my issue by using back the original original HTC RUU_signed.nbh and flash it using the CustomRUU.
Thereafter, repeat the entire HARD SPL and flash the home cooked ROM.
Cheers.
For unbricking your HTC Polaris, you can try also a hard-reset (if it is related to a software error):
http://www.hardreset.eu/htc_touch_cruise_polaris_hard_reset_soft_reset.html
Thank you very much
you really helped
thank you again
mrfone2003 said:
Thank you very much
you really helped
thank you again
Click to expand...
Click to collapse
you are welcome.
Seems people are still falling for this error.
I'm has this error.
Solution (with SPL-2.20):
- kill ActiveSync (process, not uninstall)
- cable to USB on motherboard
- hard reset on phone
- connect to cable
- flash OFFICIAL rom
Two time I revive my Polaris.
help me please
hi.I have a big problem with my htc touch cruise when I installed a hard spl htc dedicate a Diamond.donc I had a white encrant after I did a hard reset since my htc no longer I have a black encrant are neither green nor orange but when I connect with the pc I am data interface and it does not recognized my htc. In my pay is not qualified repairman three non réparé.aidé unable to please me I tried the commands mtty.exe but does not c I do not really know how it works.
thank you for your patience and for help
thanks for the support
Thanks dudes for the great help you gave to recover my htc dual from bootloader screen. I am very happy to have my phone back. Thanks for everybody for the help they have provided generously. I appreciate alot. infact thousands times.
I think i have really messed up my phone. When opening mtty i select USB and press ok, then it says "can not open USB Port"
please help me, i have all the symptoms you explain. Stuck in bootloader, POLA200 SPL-1.25.0000 CPLD-2
i cant flash any roms and the original rom stops at 39%, i have redownloaded it countless times so its not the rom.
aaront1988 said:
I think i have really messed up my phone. When opening mtty i select USB and press ok, then it says "can not open USB Port"
please help me, i have all the symptoms you explain. Stuck in bootloader, POLA200 SPL-1.25.0000 CPLD-2
i cant flash any roms and the original rom stops at 39%, i have redownloaded it countless times so its not the rom.
Click to expand...
Click to collapse
Did you follow all steps from 1st post?
Did you kill all running ActiveSync processes?
I did indeed, i'm on vista so didnt have those particular processes going but followed the step from Aeroman and it still doesn't want to play. Any ideas?
managed to find a working XP machine and it worked a treat. Thank you so much.
thanks,this solved my pb
please help
Im having the same problem, im stuck in the bootloader but i didnt do anything for that to happen....this happened all alone withount any try to flash or do anything
it is saying
POLA100
SPL-1.28.0000
CPLD-2
when this happened i tried sodt reset and unpluging the battery b4 reading and searching here.
now i tried the steps showing in the first post and step by step .... the devise restart to the same bootloader like i did nothing ((( oh god im so upset please help me .... what to do ((((
wesram said:
Im having the same problem, im stuck in the bootloader but i didnt do anything for that to happen....this happened all alone withount any try to flash or do anything
it is saying
POLA100
SPL-1.28.0000
CPLD-2
when this happened i tried sodt reset and unpluging the battery b4 reading and searching here.
now i tried the steps showing in the first post and step by step .... the devise restart to the same bootloader like i did nothing ((( oh god im so upset please help me .... what to do ((((
Click to expand...
Click to collapse
What did you do to get there?
whitealien said:
What did you do to get there?
Click to expand...
Click to collapse
hey, im sorry for the late reply. it didnt notify me and now after posting several times asking for help in many threads by accident i bumped into this thread again to see that u answered and thank you so much.
now, what i did? this is the wierd thing, i didnt do anything, i went and back to see my phone stuck in bootload .... after this i tried almost everything i can find. from ur solution to flashing original rom to hrd spl to .........
now all gave an error except the original rom (polaris.1.28.415.2), it did went to 100% and device restarted to take me to my nightmare .... another bootloader screen am i suppose to search for polaris 1.28.0000?
i still have now the same writing shown.
please help me with this, its a nightmare .... is it totaly dead???
i managed to catch what it is saying b4 bootload screen (only when SD card is in place) it says no image file was found!!! in a very fast way and go to bootloader. in case the sd is not in place nothing happens and it goes straight to the bootloader
I have received one elf with is stucking on calibration menu,everytime that i press all the 5 positions again it keeps on asking for it and i cant get to the phone.
Phone is detected by activ syn ,i want to upgrade the rom but as i'm having this problem i cant upload cert and enabl files.I cant do hardspl nothing.
Is there anyway i can repair this phone.It has got 2.26.00 spl.
Regards
I had the same problem.... but I just hard reset my phone with the styles and started my phone again and then pu it fast on my computer and started the upgrade to 2.28 and the my phone worked correctly.
Maybe I've made some mistakes but that's because im 13 and I live in Holland
I hope its good information for you!
hi sonkar read this thread http://forum.xda-developers.com/showthread.php?t=445666
i agree with marcbrug .. try to do a hard reset .. that is by holding the End & the Call Buttons and soft reseting the phone.. when the confirmation msg appears press the "Middle" (the largest) button..
hope that helped...
I have already done the hard reset,it's the first thing i did but still facing same problem.
sonkar said:
I have already done the hard reset,it's the first thing i did but still facing same problem.
Click to expand...
Click to collapse
It's happened to me a couple of times. I just re-flashed the ROM (hard reset did not work).
Can you explain how i can flash the rom?
Cos as the phone gets stuck in calibration i cant install cert and cab files in the phone.So i cant do hardspl and neither flash the rom.My spl is 2.26.00.
Regards
sonkar said:
Can you explain how i can flash the rom?
Cos as the phone gets stuck in calibration i cant install cert and cab files in the phone.So i cant do hardspl and neither flash the rom.My spl is 2.26.00.
Regards
Click to expand...
Click to collapse
You could probably still install it manually if you are able to connect to ActiveSync during the screen calibration.
First, try installing "myMobiler" which allows you to access the phone from your PC (like in Remote Desktop). See if you can get any further than the calibration screen with that.
Otherwise, download the "itsutils" package from here:
http://www.xs4all.nl/~itsme/projects/xda/tools.html
Then, use "prun" to remotely launch the CAB file from the DOS window:
e.g. C:\> prun.exe \Windows\myfile.cab
I have never tried this command with CAB files but it worked with Windows Mobile EXE files.