Related
Hi Folks,
first thanks for the new rom. Here my experiences/questions.
First of all, the installation went quite smooth.
I am experiencing the following problems:
1) when starting the device I get the message the file screenrotate.exe cannot be opended. Ehter it is not signed with a trusted certificate or one of its components cannot be found. Same for sms_alert_fix.exe
2) phone link at the left bottom of the screen results in Shortcut Target Error opening the shortcut or locating the target filename
3) active sync with sbs2003 exchange and own certification authority results in The security certificate on the server is invalid. Contact you exchange server administrator or isp to install a valid vertificate on the server Support code: 0x0072F0D. I have downloaded the CA certificate as a file certnew.cer, copied it over to WM2005 and installed it. It is availiable under settings - certificates - root
4) Start - programs is has corrupted programs IA Album, IA Camera, xBackup
Any ideas how to work on these problems?
Tnx
What is the exactly name of the rom file you have downloaded to flash your device ?
XDA2_WM2k5_1.70a.96.WWE.zip ??? if this , it is a corrupted rom ...
try to flash http://tofclock33.free.fr/rom/Wm2k5_170.zip
Downloaded your link and still the same.....
OK, my mistake.
Did not read the installation instruction up to the end.
after modifying the boot options it appears that point 1,2 and 4 are solved.
But there is still the active sync problem.
OK, my mistake.
Did not read the installation instruction up to the end.
after modifying the book options it appears that pint 1,2 and 4 are solved.
But there is still the active sync problem.
Changed HKLM\Security\Policies\Policies\00001017 from 128 to 144
My Domain runs its own CA. So I went to
http://<certserver>/certsrv and downloaded "Download CA certificate", copied it over to XDA and doubleclicked on it.
I can see it now in the certificates
If I manually go to OWA using internet explorer I receive the message "The certificate was issued by a company you have not chosen to trust"
How can I trust it?
XDA2_WM2k5_1.70a.96.WWE.zip ??? if this , it is a corrupted rom ...
I have used the above file from day 1 and it was not corrupt!!!
OK, sorted out my last issue as well.
Besides installing the CA-Certificate I needed to install the Server Certificate as well.
This could be done by opening MMC, adding the Certificates snapin for local machine and exporting under personal certificates the servers certificate.
Copy the export to MMC and doubleclick on it. That's it.
i installed the wm2k5_170.zip
but have problems..
when trying to install any program..
most of the programs needs to be installed to local, but it seems i have 6 mb memory after installing the rom..
i have 32 mb storage memory and 1gb sdram.. but for example pocket plus wants to install itself to device memory.. and when trys to install it says that i dont have enough space..
A slightly strange ugrade problem
TofClock - thanks for the 1.65 and 1.70 upgrades. I've had a weird problem that's stopped me performing the upgrade. I thought I'd ask if it's something specific to your upgrades or some other problem:
I've got Buzz's 1.60c.00 with his 96Mb RAM disk on my Humalaya and it works like a charm. However, when I tried the 1.65 and 1.70 upgrades HimaUpgradeUt.exe failed both times with Error 101 - connection error. But my Himalaya IS securely in its cradle and seems to be communicating properly with the PC: ActiveSync, for example, seems to work perfectly.
The cradle is connected directly to a USB port on my PC and not through a hub, so I'm at a loss what's causing the problem.
Has anyone else had the same experience?
I have got
rom version: 2.06.00WWE
Rom date: 06/14/04
radio version: 1.18.00
protocol version: 1337.38
extended ROM version: xda2jopjo.v3.2zs
When upgraded to xda2jopjo.v3.2zs I had no problems. When I loaded xda2jopjo.v3.2zs it did tell me the all the information under "your Pocket PC software is about update from:", and then it loaded properly. However, with every version of 2005 it gives me none of the information on what I am updating from, and the only information he gives me I'm updating to is "ce image version: 1.70a.96.
And when I click on the upgrade button anyway it does try to upgrade, there is even some activity on the xda, but every time after about 10 minutes it tells me "the current software is now being erased from your PC", it tries a little longer and then tells me "there has been a problem while updating your pocket PC software. To continue the update please:
1 disconnect your Pocket PC and the USB cradle.
2 preform a normal reset by pressing the reset button as picture left show.
3 reconnect your Pocket PC and the USB cradle and run this pocket PC software update program again.
I've tried this several times, but it hasn't worked.
Can anybody help?
fk
Hello,
Okay, so I got my Kaiser 2 days ago, though it has a swedish HTC ROM, and I want the English HTC ROM.
I have the rom on the SD card, and when going to the bootscreen, it loads and checks the new rom, and than says "Not Allow".
I checked that out, and that means the CID is still on. But I can't get HardSPL on the device, as soon as it goes in the tri-color screen, I can't connect to the device anymore with usb, meaning I can't install HardSPL.
Anybody got a different way?
Try removing the Unknown device from device manager and re-plug your Kaiser while in bootscreen, it should install the driver again (you can find the drivers in Program Files/Microsoft ActiveSync/Drivers directory if not automatic)
Then it should work.
Can't find any Drivers directory in the activesync dir.
PS. Its windows Vista with mobile center
I would steer clear of trying to flash anything via vista....
Although it *may* work, most of the software tools were not designed with vista in mind. Don't want to brick you shiny new phone now do we?!
Turf out an old laptop or something with XP on if you want to flash.
RUU works fine in vista as does hard spl. I didn't have to do anything special other than run hardspl as an administrator by right clicking and selecting run as admin.
Nope still not working.
There's no other way to do it? Like from sd card or something like a normal rom update is possible
Well, found the Vista drivers. Not working, needed 64 bit.
Found 64 bit drivers, not working, unsigned.
booted the computer with disabled the security, WORKED! So now its flashed.
I am stuck in bootloader mode after trying to update to tomal mobile 6.
The screen on Imate jasjar says USB at the top and V 1.01 at the bottom.
The mobile device center does not allow USB since I checked it off.
When I execute MTTY1.42 usb is not given as an option.
When I execute MTTY 0.01 I get USB as an option However when I click on it I get the message "USB port cannot open"
By the way my screen says serial originally and then USB when I connect to my usb port.
I assume that if my screen says either serial or usb that it is in boot loader mode.
This is the second time that I had this problem after trying to update using Ranju's mobile 6 upgrade.
However the first time I was able to recover by starting with the MTTY 1.42 execution
Mobile device center suggests Vista. Most people would not dare these things without using XP. Suggest you do the same and disable activesync USB connection option before using MTTY
that is my next move. Go tto a computer with XP. although I was able to execute MTTY before this on my 64 bit vista computer.
Both my home computers run Vista 32 or 64.
Could there be a physical connection problem with my USB even if serial changes to USB when I plug my device into the USB port?
It is like I have apart USB connection but not complete. Or is there a software problem in the device with the part that handles the USB port? If so is there a way out?
If your device changes from serial to usb then you can start the upgrade... 8.5 seems to be the best so for with my experience..
Are you aware that I have a non background lit screen? That the device charge light does not come on? That it does not respond to soft reset?
It only reacts to hard reset and to the insertion of the USB cable?
When I try to run MTTY which I thought that I was supposed to to clear something I get the message that it cannot find a USB port.
Given this state can I do the upgrade that you suggested? or are you assuming that my imate jasjar is fully functioning
what do you mean by .......8.5 upgrade
Okay thats sounds good so far, i have been researching about that problem you have. when the serial changes to USB thats good, it means you are ready to run the update just ignore the recognition of the usb pop up message. did you down load the 8,5 Tomal's? if so run it i will do the same this side, i have been testing the 8.71 it tereble do not use it Tomal must try to put some time on it because he forgot some of impotant features. if the device shows usb then no need for MTTY. you just run the update rom. let us know what happens. Its normal that the back light is of just upgrade. Here is the link for the 8.5 upgrade screen shots; http://forum.xda-developers.com/showthread.php?t=454906 The download link; http://vidmes.com/xda/Uni/ROMs/Tomal...WM61_20764.exe
Looks like the download link will not work just scroll down on this link and download the special build rom. (window Mobile 6.1 V8.5 Tomal) http://forum.xda-developers.com/showthread.php?t=454906
Is your memory card slot in use? Remove memory card prior to using mtty or boot loader mode.
Yes the storage card is out
the sim card is out
the device is connected to the pc
the screen on the device shows USB
I run tomal version 8.5
I get the message
error CEROM update error
then I follow the recovery instructions
on recovery I get
RUU has stopped working
eroor 101 connection error
note
someone says
"U must remove the Memory card b4 upgrade, (Very impotant)"
Does that make sense
My problems started with
I had the crossbow Mobile on the system before.
I did a system restore
then tried install tomal 8.5
and from there things went off the cliff
I am now going to try things on a XP loaded computer as a last resort
swiching to my office computer and with active sync I was able to install TOML 8.5
Problem was with vista apparently
Mtty Help me Please..
Guys,
Please help me, every time I try to use mtty, it always like this attachment. What should I do, I allready follow the instruction, but still the same.
I would try on an XP computer
I did it on XP computer.
orb3000 said:
I would try on an XP computer
Click to expand...
Click to collapse
make sure your usb port in uni is not brocken. is active sync can running well?
have you un-check "allow usb connection" in connection setting before running mtty?
When I use activesynv v 4.5 it can connect correctly. Before use Mtty, already uncheck "allow usb connection". And the result is still the same. What's wrong?
indrastrid said:
make sure your usb port in uni is not brocken. is active sync can running well?
have you un-check "allow usb connection" in connection setting before running mtty?
Click to expand...
Click to collapse
irmanpribadi said:
When I use activesynv v 4.5 it can connect correctly. Before use Mtty, already uncheck "allow usb connection". And the result is still the same. What's wrong?
Click to expand...
Click to collapse
Now, there are only two things...
1. USB Sync driver in your PC is not functioning correctly
2. You have physical problem in USB port at your device
just my two cents.
irmanpribadi said:
When I use activesynv v 4.5 it can connect correctly. Before use Mtty, already uncheck "allow usb connection". And the result is still the same. What's wrong?
Click to expand...
Click to collapse
set your uni in bootloader i.e. press power button + backlight and reset using your stylus.
make sure you have disabled USB connections in AS
my two cents
So i got this error with a big "X" inside this red circle and next to it just says the word "Error" then nothing else when i tried sync using WMDC thats what happens. Btw im using a HTC Touch Pro and i tried plenty of solution from the Microsoft website this includes the following:
-Uninstalling the device driver and reconnect the device
-Disabling Advance Network Functionality
-Disabling firewall, antivirus software etc.
-Running WMDC on compatability mode
-Soft resetting device
-Hard resetting device
-Flashing a new ROM
Thanks in advance
[email protected]
[email protected] said:
So i got this error with a big "X" inside this red circle and next to it just says the word "Error" then nothing else when i tried sync using WMDC thats what happens. Btw im using a HTC Touch Pro and i tried plenty of solution from the Microsoft website this includes the following:
-Uninstalling the device driver and reconnect the device
-Disabling Advance Network Functionality
-Disabling firewall, antivirus software etc.
-Running WMDC on compatability mode
-Soft resetting device
-Hard resetting device
-Flashing a new ROM
Thanks in advance
[email protected]
Click to expand...
Click to collapse
what os?
try a new cable, or try plugging the cable into a different usb port.
i got the same problem. my pc:
Windows 7 with windows device center.
can not recognise my device.
i plug in the touch pro. i get the message to choos active sync diskdrive or share my internet.
i choose active sync.
then nothing happens in device center.
tried uninstalling rndis. after restart it installes the phone again and then it works for 1 time only. after that its the same.
i have searched forums saying that uninstalling device center does not solve the problem. also they say downloading the version on the MC site is another version that Windows 7 is shipped with.
Need help, wanna install another rom. i do have another pc, but i wished it would work on this pc.
any help would be very appreciated.
EDIT 24-10-2009
Also got this message at the properties of Microsoft Windows Mobile Remote Adapter:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hope that this could help me in some way
wishmaster86 said:
i got the same problem. my pc:
Windows 7 with windows device center.
can not recognise my device.
i plug in the touch pro. i get the message to choos active sync diskdrive or share my internet.
i choose active sync.
then nothing happens in device center.
tried uninstalling rndis. after restart it installes the phone again and then it works for 1 time only. after that its the same.
i have searched forums saying that uninstalling device center does not solve the problem. also they say downloading the version on the MC site is another version that Windows 7 is shipped with.
Need help, wanna install another rom. i do have another pc, but i wished it would work on this pc.
any help would be very appreciated.
EDIT 24-10-2009
Also got this message at the properties of Microsoft Windows Mobile Remote Adapter:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hope that this could help me in some way
Click to expand...
Click to collapse
You could just update to the latest HTC ROM from the official website if your phone is still under warranty, btw thats what i did but it didn't help. Note, that i'm running Windows 7 as my OS if anyone want to know this information to help solve the problem. Thanks in advance.
[email protected]
wishmaster86 said:
i got the same problem. my pc:
Windows 7 with windows device center.
can not recognise my device.
i plug in the touch pro. i get the message to choos active sync diskdrive or share my internet.
i choose active sync.
then nothing happens in device center.
tried uninstalling rndis. after restart it installes the phone again and then it works for 1 time only. after that its the same.
i have searched forums saying that uninstalling device center does not solve the problem. also they say downloading the version on the MC site is another version that Windows 7 is shipped with.
Need help, wanna install another rom. i do have another pc, but i wished it would work on this pc.
any help would be very appreciated.
EDIT 24-10-2009
Also got this message at the properties of Microsoft Windows Mobile Remote Adapter:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Hope that this could help me in some way
Click to expand...
Click to collapse
Settings-->Connections-->USB to PC and Uncheck Enable faster data Synchronization
I have the same problem.
in my situation i tried to recover usb-flash and flash a nokia phone. For both things programs installed their own drivers. Even after I deinstalled the software I probably still have their drivers on my pc. That's why I can't sync my phone...
is there a tool to manage installed drivers?
or the other way out is to reinstall windows 7
anyone willing to help?
This solution worked for me:
Thanks to Scubamike
copy and paste from
http://social.microsoft.com/Forums/...c/thread/7a6516e2-9a46-4e1f-b689-1aa7dc2bda64
I found a different solution that worked for me: On my phone I clicked start/programs/active sync/options and deleted all the old PC connections that were displayed. In fact, you could probably just delete ALL the PC connections displayed and start from scratch. You'll just have set up another sync partnership in WMDC when you plug it in. Let me know if this helps.
it is to easy! should work ALWAYS:
Make sure "Advanced network functionality" is switched off in the USB to PC settings then:
go to activesync, menu, connections, disable "connect via USB" off, press "ok" go back to connections, enable "connect via usb" press "ok" unplug and replug your cable. and all works.
greetings
i had trouble with a 6.5.3 rom i just cooked. had to uninstall, reboot, reinstall wmdc, then i synced okay.
I have the last original rom and win 7 and with removing all remembered connections on the pda, it connected immidiatly. Thank you for the help
i have been all over the microsoft forums to no avail. i recently updated my laptop to win7, and have a fuze running 6.1 mobile. when i connect my fuze to the laptop the laptop recognizes it as it begins to charge, but then nothing. i try to open win mobile device center and this is the error message i get C:\windows\system32\rapistub.dll is either not designed to run on windows or it contains errors. I have uninstalled and reinstalled 3 times and also tried different usb ports on my laptop. If anyone can help that would be awesome
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?