Related
So, as I see there is many newbees here without experience in ROM flashing. Some of them need just ROM in another language.
Because there is really no simple guide for all who wants to flash their prophet to get at least WM 5.0 WWE (or other language) I will write my experience (this doesnt mean I can solve al problem!!!!, cos´in flashing about 50 devices already I really had no problems-just followed instrucions from this forum).
If you have a Prophet (S200, XDA Neo etc) and want ENG WM 5.0 ROM just follow next few steps, and it should works
1. Determine do you have G3 or G4 model
2. Download and install ActiveSync 4.5
3. Download ROM (my suggestion PVTemp) and unzip somewhere on desktop
4. If your device is locked-> unlock it using lokiwiz
5. Connect device to PC ( running WIN XP suggested) and sign as a GUEST!
6. Disconnect and go to bootloader mode -pres COMM button and after that soft reset with pen, relise pen in few seconds and your screen should show RGB colors. DEVICE BATTERY MUST BE ABOVE 50%!
7. Connect your PDA on PC (it will show USB on screen, down left)
8. Go to directorx and run ROMUpdateUtility_NV_G4.exe (if its G4) or ROMUpdateUtility_NV_G3.exe (if its G3)
9. Follow instrucions on PC screen
10. After some time (10min) PDA should finish and do a restart-it usualy stuck on 0% and 85%, but dont panic and wait, it sould continue!!
11. Enjoy new ROM!
That is it for now. I hope it will help, if I found out something I will edit the post, and at the end:
YOU CAN DO THIS ON YOUR OWN RESPONSABILITY;DO NOT CONSIDER ME RESPOSIBLE IF SOMETHING GOES WRONG.
Do as I do- read as many posts as you can considering flash and upgrade!!!
If someone want to add oppinion or suggestion (or just link to mentioned software) it will be great of course!
Also, if admin have a better idea (maybe to edit and stick post somewhere) it will be the best solution!!
Some solution from wiki:
If during an upgrade your Prophet fails to start properly or can only enter bootloader!
Hard reset
Hi,
Help needed to restore GSMFSS.NB0 cause flash stops with message,
"GSMFSS at 0x13000000
GSM Doesn't exist
Spin Forever
Use (format All) instead."
Is there a way to format all rom?
Thanx
If you have an original RUU (from either manufacturer or vendor), you could try that and see if you can flash an official rom. First thing would be if you can get into bootloader. If you can't, then I am afraid that you got yourself a pretty expensive paperweight.
However, if you can get into bootloader, there is still hope...
I am sorry but I cannot guide you through the bootloader process for your phone, but I do not own that device. However, this seems to be a way to possibly recover most phones I have seen so far.
Well if press "volume down+Left OK+Reset" i go into this main menu option, with Xand, Nand Format, diagostic,etc but when i press the respective key it does nothing... the GSMFFS error appears when i try to flash from the original RUU. So the device is comunicating, and i can access IPL- insert usb cable...
Can i access the device with rom with P525 Kitchen Tool?
Thnx
santosru said:
Well if press "volume down+Left OK+Reset" i go into this main menu option, with Xand, Nand Format, diagostic,etc but when i press the respective key it does nothing... the GSMFFS error appears when i try to flash from the original RUU. So the device is comunicating, and i can access IPL- insert usb cable...
Can i access the device with rom with P525 Kitchen Tool?
Thnx
Click to expand...
Click to collapse
Well, that is fairly good news... you can apparently access bootloader, so not all hope is lost. As far as the P525 kitchen, you always have to be extremely careful when using a program that was designed to work with a different device from yours.
Have you tried using the RUU after getting the device in bootloader mode? In other words, get it to this status, connect the USB cable to the computer (establish a connection), and then try to use the RUU. It could be that the GSMFFS error could be from the RUU not being able to put the device into bootloader.... It might just work... Good luck!
I got this out of an Asus Russian forum
"Proshivatsya in expert mode, though, and so like to ask
But if you do not return startanet through the expert mode
Hold down, press and hold OK (side button), tyknut stylus reset.
Wait for the appearance of the caption "IPL: Insert USB CABLE"
On the PC run P527FUU.exe, in the back left corner click on the program icon, choose the Expert Mode
Connect the cable and click Update
Do not guarantee the accuracy of keystrokes, but in the manual for the R527 is written that way. "
Here is the link for the site (already google translated)
http://translate.google.com/transla...earch?q=GSMFFS&hl=en&rlz=1C1GGLS_enUS310US310
Browse through some of the posts and see if you can come up with something. From what I have read the "Format All" is accomplished only via "Expert Mode" described above. If you can access that, then you might have a chance to restore the device.
egzthunder1 said:
Have you tried using the RUU after getting the device in bootloader mode? In other words, get it to this status, connect the USB cable to the computer (establish a connection), and then try to use the RUU.
Click to expand...
Click to collapse
Yup, the error appears just 5sec after pressing update button...
I guess the problem resides on the fact that gsmffs.nb0 file is missing from the rom, cause RUU log shows:
ClientDriver.dll Attach
g_Driver=0 g_RTimeout=0 g_WTimeout=0 g_DebugON=0 g_PurgeTx=0 g_PurgeRx=0 g_WaitRx=0 g_splitReadAck=0 g_splitReadAckSize=0
Client_QueueJob(): FeatureID=3, FileName=temp3, HeaderLen=0
Client_QueueJob(): Assumed flashing a Asset Data File because there is no header
Client_QueueJob(): FeatureID=3, FileName=temp2, HeaderLen=0
Client_QueueJob(): Assumed flashing a Asset Data File because there is no header
Client_QueueJob(): FeatureID=17, FileName=temp4, HeaderLen=0
Client_QueueJob(): Assumed flashing a Asset Data File because there is no header
Client_Initialize(): Model=(null), Language=0
Client_Initialize(): Skipping the model verification check
Client_Initialize(): Skipping the language check
Client_Initialize(): rebooting device...
Client_FormatDiskEx(): Type=3 Backup=c:\gsmffs.nb0
OpenComPort(): Wceusbsh
GetWceusbshDevicePreset
OpenComPort(): Wceusbsh \\?\usb#vid_045e&pid_00ce#5&1e9a0cb1&0&1#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
Windows Closing end
OpenComPort(): PC is XP plus
OpenComPort(): PC is XP plus
OpenComPort(): cto.RIT=0 cto.RTM=0 cto.RTC=0
OpenComPort(): cto.WTM=0 cto.WTC=0
OpenComPort(): sucessful
SendFormatDisk() cmd=3
GetEachROMSize(): GSM size=5242880
GetEachROMSize(): OS size=70254592
GetEachROMSize(): EXTROM size=1048576
SendFormatDisk():USBWritePacket
SendFormatDisk(): USBReadPacket
...
And then it hangs on the last command, it should return
SendFormatDisk(): receive format ok
ReadBackup(): Get a packet Remain=65536
...
I assume C:\ is on the pda not my computer right? I guess this file is missing. Very frustating since there's no tools available for my P527...
Look for a Rom dump from this device and see if you can find the missing file.
I think that the C:\ is actually in the computer. Even if the PDA is recognized as external storage, it would probably take a different letter (unless your HDD has a different letter assigned to it). But in bootloader mode, it is not recognized as storage.
Also, look for another RUU (for this device) and see if it works. Good luck
same problem
santosru said:
Well if press "volume down+Left OK+Reset" i go into this main menu option, with Xand, Nand Format, diagostic,etc but when i press the respective key it does nothing... the GSMFFS error appears when i try to flash from the original RUU. So the device is comunicating, and i can access IPL- insert usb cable...
Can i access the device with rom with P525 Kitchen Tool?
Thnx
Click to expand...
Click to collapse
hi santosru,
i am also having same problem were you able to solve it? where you able to select the options?
Ok, this may not work for everyone but it worked for me. I CAN NOT take credit for any of the work. I can how ever offer a very sincere thank you to developers who have brought 6.5 to the P527.
Download SCHIST 21864 from http://forum.xda-developers.com/showthread.php?t=506417
use the P527FUU that is included and check both OS and GSM.
set the OS path to ????/SCHIST_21864_clean\flash.dio.nb0
set the GSM path to ????/SCHIST_21864\EXT GSM(IND)\GSM.dio.nb0
now you need your phone screen to show the IPL: USB Cable message.
turn key lock on, press in on the scroll wheel (left side of phone), press and release the soft reset button with stylus, release the scroll wheel and press the left OK button. it may take a times to get it right but you should get the IPL: screen up. (I actually have to release the scroll wheel then move it down, release and then press the OK button)
insert the usb cable, click the ???? button in P527FUU this should "fix" you.
after it's complete even if phone hangs at the blue Asus screen you can download the correct Asus flash and use the installed included from Asus in advanced mode to restore your phone to WM 6.1 for your area.
if this helps anyone let me know.
IMPORTANT: I just learned that the computer you flash with has something to do with the bad flash. I needed to reflash the original 6.1 back to my phone and it locked up again on my computer, I tried my girl friends and it worked fine using the above steps.
Hello,
I upgraded my Kaiser 130 from Wm6 to Wm6.1 forseveral times, but at the end I restored Wm6.0, because I have never been pleased about Wm6.1.
Whenever I tried WM6.1, My device got freezed, or touch screen sensitivity decreased while in use, so I had to tap screen firmly sometimes.
I had HardSPL v1.0, is this the cause forsuch freezings or other problems? Should I flash higher HardSpls? Please help in this subject..
I want to use Wm6.1. But, after flashing My rom to Wm6.1, I restore back to Wm6.0..
Thanks in advance..
Best Regards.
Is not there any expert to help me?
what is my problem? why can't I get the best performance for Wm6.1 with my kaiser..
Still waiting for a logical reply,
aren't there any expert? Rom cookers?
Thanks in advance..
If you followed the noobs guide to flash to a T & then found the ROM you wanted and read the chef notes, then read fixes etc, should be fine.
Please be patient, i probably would have posted more if you was not bumping the way you are.....
lol good reasoning stylez
I would recommend upgrading your HardSPL, like this:
a. Download the Kaiser-HardSPL-3.29.zip from here and
extract them to a folder on your computer, for example: HardSPL.
b. Now download this file and
extract it to a folder on your computer, for example: JumpSPL.
c. Open the folder you extracted it to, and copy "kaiser_JumpSPL_pof_v1.nb"
and "JumpSPL.exe" (no quotes) to your device.
d. Power down your device, take out your SIM and SD card (if one),
then power back on the device. If it opens an emergency call screen
once restarting, just click the red End key button on your device to
exit and go to the today screen.
e. Open File Explorer, then open JumpSPL.exe on your device, then enter in: "0x00000000" no quotes, and then select kaiser_JumpSPL_pof_v1.nb
f. Now, if done correctly, you should be at a Tri-color screen and
it should say "USB".
g. Now disable USB connections in Activesync/Windows Mobile Device
Center. To do this, click on settings under Activesync or Windows
Mobile Device Center (depending on if you're running Vista or XP) and
UNcheck "Allow USB connections"
h. Unplug your device, wait 5-20 seconds, then plug your device back in.
i. Remember that folder that you extracted the SPL to? Well, on your
computer, open that folder, then run KaiserCustomRUU.exe.
j. Click Next, Next, then Update. Wait for it to finish, then click Finish.
k. Congratulations! If done correctly, you should have HardSPL flashed
on your device. To confirm this, press and hold the camera button on your
device all the way while pushing the stylus into the reset hole. You should
be at a tri-clor screen (called the bootloader). The second line down should
say "SPL-versionhere.Hard" (no quotes). If it does, you're ready to flash!
If it doesn't, please re-read all instructions.
good luck
mbarvian said:
lol good reasoning stylez
I would recommend upgrading your HardSPL, like this:
a. Download the Kaiser-HardSPL-3.29.zip from here and
extract them to a folder on your computer, for example: HardSPL.
b. Now download this file and
extract it to a folder on your computer, for example: JumpSPL.
c. Open the folder you extracted it to, and copy "kaiser_JumpSPL_pof_v1.nb"
and "JumpSPL.exe" (no quotes) to your device.
d. Power down your device, take out your SIM and SD card (if one),
then power back on the device. If it opens an emergency call screen
once restarting, just click the red End key button on your device to
exit and go to the today screen.
e. Open File Explorer, then open JumpSPL.exe on your device, then enter in: "0x00000000" no quotes, and then select kaiser_JumpSPL_pof_v1.nb
f. Now, if done correctly, you should be at a Tri-color screen and
it should say "USB".
g. Now disable USB connections in Activesync/Windows Mobile Device
Center. To do this, click on settings under Activesync or Windows
Mobile Device Center (depending on if you're running Vista or XP) and
UNcheck "Allow USB connections"
h. Unplug your device, wait 5-20 seconds, then plug your device back in.
i. Remember that folder that you extracted the SPL to? Well, on your
computer, open that folder, then run KaiserCustomRUU.exe.
j. Click Next, Next, then Update. Wait for it to finish, then click Finish.
k. Congratulations! If done correctly, you should have HardSPL flashed
on your device. To confirm this, press and hold the camera button on your
device all the way while pushing the stylus into the reset hole. You should
be at a tri-clor screen (called the bootloader). The second line down should
say "SPL-versionhere.Hard" (no quotes). If it does, you're ready to flash!
If it doesn't, please re-read all instructions.
good luck
Click to expand...
Click to collapse
Thank you mbarvian I flashed my Hard SPL, And checked it by pushing Reset&Camera button, it is 3.29.
So can you say that this is the most important cause of the freezings or decreasings in touch screen sensitivity in WM6.1? If I flash Wm6.1 rom, do these problems appear?
Thanks in advance.
stylez said:
If you followed the noobs guide to flash to a T & then found the ROM you wanted and read the chef notes, then read fixes etc, should be fine.
Please be patient, i probably would have posted more if you was not bumping the way you are.....
Click to expand...
Click to collapse
Thank you expert, but I say that, I got such problems even if I flash my device with official Wm6.1 ROMs..
Thanks again..
preface for the people not reading ... some quick answers:
- our page on this Hard-SPL is always here: http://rhodiumw.htc-unlocks.com/hard-spl.php
- license: you will just have to run the program on the PC with phone connected, normally you will not notice anything about the licensing, it is totally free for personal use!
- if you need help with license issues (when it says you already unlocked a device), you can send your message at: http://support.htc-unlocks.com
[SIZE=+2]Hard-SPL Release Time!!!! [/SIZE]
[SIZE=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/SIZE]
[SIZE=+2]NOW UPDATED -> if you already installed HardSPL, you will not need this update. but if you are going to HardSPL only now, it applies to you (package will lead you to update link anyway).[/SIZE]
Preface: okay, it was released only this weekend! but trust me the wait was worth it as it works really great and smooth now!
Licensing information: it's like with previous Hard-SPL unlockers - every user gets one free use of the Hard-SPL, further use is subject to paying a small amount per device.
however, if you are a private user, you can have other uses free on request if needed, such as using it on a replacement device.
the license is valid forever and all this works as transparently as possible, so for normal users nothing is noticable; while businesses who need to unlock more devices than that, can use the link inside the program to send payment or contact cmonex or Olipro if you want to discuss bulk unlocking.
contact info is: via support link at our site
IMPORTANT: please do not use this contact info for asking help for problems unrelated to licensing unless you are a paying customer. other messages will not be answered - instead you can use this thread to post about your issues!!!
Preparations:
0) this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
1) if you have Vista / Windows 7, WMDC update to 6.1 (or whatever is latest) is recommended.
Instructions: read this if unsure how to install Hard-SPL... if you are an experienced user then you'll probably not need to read most of this but if you are unsure or run into an issue, then you should read the following!
Steps:
1) download newest RhodiumW Hard-SPL package and extract this to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!! the device needs to be connected to Activesync or WMDC via USB cable. and it must not be in Flight/Airplane mode (i.e. the phone part should be on).
3) internet access is required as the program checks online for updates and for the license.
4) run Rhodium-HardSPL.exe on your PC, make sure it's launched from a local drive (not through network drive, etc.). running it on XP requires Admin logon, and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, so allow it please.
important: if you get an antivirus warning, please ignore it, it contains no harmful code (just used a packer to compress it). if you encounter DEP errors, then add it to the exception list in DEP settings.
5) follow steps as prompted in the Hard-SPL program. if this is the first run of Hard-SPL on a device after hard reset, you must select Automatic flash mode (the first button in Welcome screen).
notes: you should usually go for Automatic flash mode; the Manual flash option is only to be used as noted below - any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
6) it will ask you to wait while it prepares for the flashing, press OK.
7) now it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the forums, but this should not ever occur (as this means a really fatal error occurred).
at this point the device did hopefully went to a black screen. this is the SSPL version, which is temporary. then RUU (Rom Update Utility) will instantly launch.
9) some notes: when RUU says it will perform a hard reset and cause data loss, do not worry, it is not going to do this. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
10) SPL flashes, device automatically reboots, job done.
11) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.00.OliNex, which is the current Hard-SPL version.
More Notes:
NOTE 1: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, you need the following key combination: Power Button + Volume Down + Reset Button. means, do a soft reset while holding the "volume down" key and power key on the side of the device. hold these keys until you see a special tricolour screen which is the bootloader mode.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs (except of course some Radio roms). also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted on our site. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps in the next post about how to reflash stock SPL.
NOTE 3: anyone having USB connection problems with the device after it already entered SSPL mode, please copy SSPL-Manual-Rhodium.exe from SSPL-Manual-RhodiumW.zip (available on our site), copy it to the device and run it. then once the screen has gone black, run the Hard-SPL package on the PC and you must select Manual flash option. *important*: make sure that the USB cable is plugged in and device is synced to Windows Mobile even if doing manual method.
NOTE 4: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or a customRUU if you need to flash cooked ROMs.
NOTE 5: supported OS versions: both 32-bit and 64-bit XP, Vista, Windows 7RC and later. Windows 2000 was untested, and pre-RC win7 (lower than build 7100) is explicitly not supported. also, the program may be unstable or not work on Virtual systems, so it's recommended to try outside Virtual OS software.
Troubleshooting: and Step by Step on reflashing stock SPL: are in next post below!
Credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> concept of EXE program that runs on the PC, Hard-SPL concept, server-side license code and maintaining the licenses.
cmonex -> HSPL package on PC, SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code),
[SIZE=+3]Donations are always appreciated, the Hard-SPL program will provide you with a link at the end of the process to make it easier. any little helps!!! Thank you![/SIZE]
and now enjoy!
-continued from first post-
Manual SSPL download: (added soon)
Troubleshooting:
firstly:
- read the instructions above.
- read the instructions above.
- read the instructions above.
nothing happens on the device, does not enter black screen mode:
- anyone having problems with the device crashing instead of entering SSPL, make sure you've used Automatic flash mode before to put the device in SSPL (if you hard-reset your device, you have to repeat Automatic flash mode at least once).
- please make sure you watch the device screen if it asks about running files (it probably won't, I made sure of that, but just in case, check, for example it can warn about model incompatibility).
- also you can try unticking advanced usb/network functionality in settings on the device. exact location of this will probably be: start menu / settings / connections / usbtopc applet.
general usb connection error problems:
- if you get connection error in RUU after the device goes to black SSPL screen: make sure device was still synced via USB to the PC at the point of it entering SSPL (the black screen) and do not try replugging please, that will probably just crash SSPL.
- it will take a few seconds for the RUU to detect the device, but do not worry, as soon as the USB connection is established in SSPL, RUU will see device. if not (happens very rarely), wait for RUU to time out (or wait a few minutes). then remove back cover, reset, it will boot OS again, then you can retry unlocking process.
- anyone having problems with the device entering SSPL without functional USB port ("ERROR 260 CONNECTION" RUU error), you can get SSPL-Manual-Rhodium.exe from attachment in this post, copy it to the *device* itself and run it. then once the screen is showing black, run the Hard-SPL package on the PC and select Manual flash option. please do not use Manual flash option for any other purposes
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time it needs to do that), then if RUU times out, but device is still in black screen, just leave it there and re-run the Hard-SPL package when driver installation finishes - you must use Manual Flash option in such a case. I recommend to wait for Windows to take its time searching for the USB drivers, then click Next in RUU only when they are installed.
- finally, you can try disabling antivirus or firewall programs on the PC.
ModelID checking: if SSPL loader says it's for a different model or device, please make sure you are using the correct HardSPL package. currently this SSPL accepts only RHOD400, RHOD500 modelids i.e. the CDMA-GSM worldphone version, but if we get notified of another compatible RhodiumW version, we will instantly modify it to allow those models. check modelid by entering SPL tricolour screen manually and note what it says (RHOD400, RHOD500, or something else). note: RHOD1xx, 2xx, 3xx are not going to be compatible at all!
other issues:
- if device reports that Enterbootloader.exe fails to run (says missing component or corrupt signature or similar), try a hard reset.
- if device reboots instead of going to SSPL screen (black), which is very unlikely to happen, then contact us by PM to cmonex. do not PM OliNex user, that is not monitored frequently (and PM's to it are disabled now anyway).
- if none of the above help, read thread for further suggestions, if still nothing, make a post in thread describing all details about the exact situation.
how to reflash Stock/Shipped SPL: - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. download the Relocker by clicking here, extract the zip and run the EXE on your PC
2. if you wish to replace RUU_Signed.NBH that got extracted, feel free to do so, but not necessary (this Hard-SPL will only allow overwrite with a SPL made by us). the included one is the 0.63.0000 stock SPL. 3. flash
4. verify if it flashed by checking version in tricolour screen, it should say 0.63.0000, not 1.00.OliNex.
About UPDATES:
-new release coming soon, fixes a specific problem for a small group of people-
-more troubleshooting tips soon-
Consider yourself... sticky
Thank you Olinex. Great WORK
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
buggs1a said:
thank you! can someone please tell me what this does for my vzw tp2? thank you so much .
Click to expand...
Click to collapse
In a nutshell, this basically will allow you to flash custom made roms and other assorted customizations.
Hey, thank you.
Does using this and then not putting a custom rom on it right away do anything bad? Like waiting for a 6.5.1 rom or something. Sorry if this isn't the right place. Forgive me please.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
You can wait as long as you want to flash another rom, custom or carrier. So no worries in holding off.
Thanks so much for answering.
Here's something.
Crashes on vista x64 sp2 home premium. as soon as I click to open the hard spl exe it crashes.
I just tried. I don't get it.
My mcafee doesn't have a trust app add feature that i can see so i turned off real time scanning to extract the file and then run it. Then the hard spl crashes when i try to run it. I hit auto flash and immediately it crashes.
What specific error message(s) are you getting?
Nothing specific. It just crashes and the windows app crash pops up. That's all that I can remember. Should I try again and look for something specific?
Also I would like to say that I connected the phone to my pc via usb cable and that's it. On phone opened the disk mode or active sync selection but I didn't touch anything in time then it disappeared. The phone showed up as a hard drive in explorer. I didn't do anything else when trying to run the hard-spl exe. Should I have?
Thanks a million.
You need to make sure you're connected to your computer and sync up with ActiveSync. Once that's all connected properly, then you can run hspl.
but how do i do that? i noticed just now i reconnected phone and active sync was selected on the phone, but nothing comes up on windows vista except the auto run and it says synch with media player or open to view files or do nothing.
Oh, Vista. Right. You'll need to use Windows Mobile Device Center then. Install that, reboot, then sync up with that (it's ActiveSync's replacment for Vista and Windows 7). Then you should be able to run hspl fine.
That you very much Oli, and to all the people who worked so hard on this! I just put it on my Verizon Touch Pro 2 and it went like a snap, but what software from you doesn't A nice donation is coming yer way me matey!
thanks. that did it.
i got to the part where it said make sure the battery has 50% or more. i said cancel and now my phone is off and won't come on. I disconnected usb and tried to turn it on and nothing happens. reconnected phone and tried to do this again and it told me i need to active synch again. but i can't turn on phone right now. I don't know what to do now.
Have you tried taking out the battery of the phone, reinserting it and turning it back on?
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
buggs1a said:
trying now except i dont know how to open it. ok my bad. had to remove stylus. it's on now.
Ok sweet. It rebooted the phone. Success I suppose. Now to find a rom.... But then I dunno what to look for. hmm...
lol
Click to expand...
Click to collapse
Glad you got it figured out. Have fun finding a good rom that suits you.
edit: since we don't really have much of a CDMA TP2 selection just yet, I'd recommend checking here. He makes a great ROM. Just be sure not to discuss ROMs in this thread.
I posted this at PPCGeeks also, but here is a problem I am having while trying to unlock in Windows 7 x64 using WMDC.
1. Ran the .exe
2. Screen pops up "Preparing to flash, press ok to wait. I press ok.
3. The screen goes black (like it's supposed to), Active Sync DISCONNECTS, and a box pops up: "Welcome to the ROM update utility...". I check the box "I understand the caution..." and click next.
4. The next box pops up "Follow the instructions..." and I check the box "I completed the steps..."
5. A box pops up: "Verifying the information on your PDA phone...please wait..."
6. About 30 seconds go by, and an error box pops up: Error [260]: Connection...
7. The screen remains black and the phone non-functional. I have to soft-reset the device at this point.
When I soft-reset in #7 above, the computer dink-donks like when you disconnect the UBS cable, so there's still some sort of connection the PC is recognizing. I tried a second time after installing the enablerapinew.cab (using auto mode) and got the exact same errors.
Any thoughts?
hi.
I'v got loox n560 that was upgraded to WM6.1-6.5 servel times without any problem.
the last time i did update, i did it accidentally with a bad firmware file(uncompleted download).since then, the device wont boot(just a white screen).and the pc wont recognize it.
any way to save it? or i made myself a nice paper weight?
thanks.
I think there was a way to put the N560 in bootloader mode by pushing some keys and soft-reset hole manually (the "monkey grip" it was called or something similar...) and with the file of the rom to be flashed in a SD card... perhaps you can google for information on this ancient -and more unsure that the cable one- flashing mode. Worth to try it better than have a paperweight...
Good luck!
I give you more information (shame that FIRSTLOOX information is not there anymore)
For manual bootloader mode: press On-Off button + left side button (voice recording) + stylus soft reset (for some seconds). Keep pressed On-Off and recording untill the dolphins appear.
I can't find references to flash from SD card. Anyway, for incomplete flashing, Newplowe gives this procedure:
"You should close process "wcescomm.exe" on PC in task manager. Then hold button record, power and puch reset after that you will come in boot loader. Run the program mtty.1.42 and select usb connect. If You will see the any error just start again mtty. Put command l c:\os_213u.nbf (You should put correct flash file in c:\ or use correct path to os_213u.nbf, l - like L but small). When it will done You should start PocketLOOX5xxFlashTool.exe and flash you PDA."
I got this reference from "http://forum.xda-developers.com/showthread.php?t=429148&highlight=flash+n560+card".
Good luck anyway.
this is very interesting...
i was able to put the device into boot loader mode and ran the command "L c:\os_213u.nbf" ("l" didnt work, but L did).
it did something to the device, a progress bar till the end of the screen.but the device didnt reboot.when i try to run POCKETFLASH program it couldnt connect to the device.
i runing windows 7, so i guess it the problem(ACTIVE SYNC is a XP PROGRAM).
i'll try installing XP on another computer and try this again.
thansks.
almost...
i have installed Windows XP just for this, and everything seems to go well, i connect with MTTY, put the l c:\os_213u.nbf command and the device respond.
the next stage i to flash with PocketLOOXN560FlashTool.
when i start it, i receive connection error, and then i go to recovery mode.the program try to communicate with the device, but i get at the end error that the ROM language is different than the language on the device.it says "(ENGLISH)" and there are also empty
()
Click to expand...
Click to collapse
at the end.
i doubled checked this with the original WM5 English rom, and its the same.
is there a way to change the language with MTTY?
any other ideas? its a shame to stop now after i can get a response from the device...
thanks.
The only idea I have is to check if after the failed flashing your N560 is still an "english" one. Perhaps the defective rom has changed the language of your device to something else...
If your device respond to communication with the XP computer, perhaps you could make a rom dump (in newplowe's page you can got tools for doing that) and check in the dump file with an hex editor which language actually has. You can always check newplowe's blog and forum (with google translator ), or ask him
Sorry i didnt post an update.
i have fixed the rom language.it had a gibberish mark at the end of the ENGLISH, after i have fixed that, .the device was flashed correctly and its working!
thanks for thelp guys