I've been working on a step-by-step CLOSE-UP VIDEO guide to Flashing a ROM, including how to HARD SPL, to make available to users here. Here are things I'm still not clear on.
(These were posted recently to the Guide written by mskip in the Kaiser forums. He answered some questions, but these are still unanswered. )
Flashing via ActiveSync with USB Lead
2. Pull out the battery and reinsert it (this step IS important) *DONT turn phone back on yet*
Click to expand...
Click to collapse
** When is this step necessary & required (whether during initial HARD SPL or FLashing a ROM post-HardSPL) , as opposed to simply "Best Pratices"? What is this step accomplishing?
8. After a few seconds the tri colour screen will appear on the phone and "USB" will be displayed at the bottom
9. Unplug the usb cable for 30 seconds and then Replug (phone will not re-sync but still says "USB" on the screen)
Click to expand...
Click to collapse
** Please explain #9, what it is accomplishing & thus why recommended?
"Active Sync" vs "USB connection"
Please tell me if this is accurate or not:
(1)When installing via PC vs installing via Storage Card: After data has been backed up to PC by way of "Active Sync", thereafter, when performing any ROM updates (HardSPL or flashing a new ROM) the app "Active Sync" is technically no longer involved in the flashing process, but rather, what's necessary is simply having a USB connection from device to PC, correct? Is the distinction that Actice Sync can foul up the basic data connection from phone to PC necessary to flash a ROM. I want to be very clear. Is this accurate?
10. Right click on the Activesync icon in the bottom corner icon on the computer, goto connection settings, deselect "Allow USB connections" and click "ok"
11. Microsoft ActiveSync icon will now have a red cross in it and the program will say "Connection Disabled"
12. Run the ••••••RUU.exe file on your PC thats in the same folder as the HardSPL .nbh file and follow instructions (ticking boxes and clicking Next) *DO NOT reenable USB Connections in Activesync*
Click to expand...
Click to collapse
** same as above: Are these just more compensations in order to disable MS's incorrect assumption that the insertion of a USB cable always equals "launch an Active Sync session" ?
15. Unplug USB cable from phone then REPLACE SIM & SD CARDS !!
**Remember to re-enable "Allow USB connections" in Activesync connection settings after a successful flash**
Click to expand...
Click to collapse
Why, exactly, is it required to unplug the USB cable? Is it, again, a "Best Practices" precaution to prevent any kind of accidental read/write of data?
A few questions re entering Bootloader mode, various scenarios:
1. In some older guides, even for when flashing a rom to phone device from your PC , sometimes a step is specified to "enter Bootloader mode by holding & pressing the xxxx and xxx keys on your phone, and then xxxxx".
2. But if you have an RUU folder that includes the Bootloader.exe app, along with the RUU.exe and .nbh file, then by running the RUU.exe app, the entering bootloader mode is handled automatically, sending the commands to phone, which automatically place the phone into the tri-color screen mode? -- as opposed to one having to manually press xxxx and yyyy on phone to enter bootloader mode? Correct or not?
3. If correct: then, does it matter on which screen or in which mode your phone is currently on in order to begin the flash-ROM process? Could I just as well be on a Total Commander app screen or on a TouchFlo Today screen?
4. Some guide-writers recommend users hard reset their phones before starting a new flash-rom session, just for "best practices". Others consider this superfluous & irrelevant, and what matters most is a Hard-Reset be run immediately AFTER flashing a new ROM. ... Any opinion on this?
Flashing Via ActiveSync
<snip; this is deep into the flashing process >
2. Turn phone back on and wait until it syncs with your PC
Click to expand...
Click to collapse
** Would it be more accurate to say here "until your PC confirms it has a USB connection to your phone"? (You're not looking to run a sync session, but rather just getting a USB connection for files to be transferred from PC to phone.) I think the term "Active Sync" often creates more confusion than helpfulness in this whole realm of moving files from PC to phone. )
Question re RUU.exe file on PC:
From what I have seen in the ROMS I have used in years 2008-2009, the extracted ROM folders I've downloaded from the chefs have typically all had the file " Bootloader.exe " within the RUU folders, and that (in the case of mskip's Flash Guide for Kaisers) KaiserCustomRUU.exe calls the Bootloader.exe app which sets the phone into bootloader mode from the PC, without one needing to manually set the phone into bootloader mode.
But this is your response from your initial quick-reply, which confuses me"
The customRUU automatically puts the phone in bootloader mode thus there is no need for the seperate file (bootloader.exe).
Click to expand...
Click to collapse
** This confuses me. I am principally trying to distinguish between when one needs to manually set phone into bootloader mode -- and when this step is handled by the PC's RUU.exe process. In the older (around year 2007) "How to flash" guides, users were often told they needed to create a folder, make sure they have the correct RUU.exe file inside it, make sure they have the correct .nbh file, make sure they don't have files that are there for those with soft SPL phone, etc. And as far as I can recall, in those older Guides, this bootloader.exe file was not included. And thus users were instructed to manually put their phones into bootloader mode...
The difference being that for the past year or more, chefs currently are now providing the whole contents of the RUU folder in the .rar file, so that if you've hard-SPL'd, then that .rar file has eveything you need, and all you need to do is launch the RUU.exe -- never having to set your phone manually into bootloader mode.
Yet you are saying
Quote:
thus there is no need for the seperate file.
Click to expand...
Click to collapse
I'm not a coder, but I don't get this. Why would bootloader.exe be inside practically every RUU Folder nowadays if it were unnecessary to set the phone into bootloader mode to initiate the flashing process? You were saying the RUU.exe app itself would contain some method of setting phone inot bootloader mode without even needing that bootloader app present in the folder.
Could someone please clarify.
And secondly: Does it matter one bit of difference which screen your phone is on when you commence with running RUU.exe ?
And third : If users happen to be confused, and think they must manually set their phone into bootloader mode, as part of running RUU.exe, and they do manually set their phone inot bootloader mode and get the tri-color screen: Does that conflict with or hamper in any way the running of the RUU.exe program from the PC? Or does the RUU process just simply proceed, and send an "enter bootloader mode" instruction to the phone, which then causes the phone, already in tri-color screen, to be reset again into bootloader mode (and there is no problem that the phone was already in bootloader mode) ?
After New Rom is Completely Installed and You Have Customized Your Phone:
** I think it in dutty's guide where he says "after customizing your phone, power down your phone, then power it back up". Is this power-down/ power-up cycle equivalent to just doing a soft-reset? What is the difference as it pertains to that specific step after customization?
Quote:
Flashing Via MicroSD Card
<snip>
3. Goto the Roms Folder and rename the .nbh file to KAISIMG.nbh
4. Copy the KAISIMG.nbh file to your MicroSD Card
Click to expand...
Click to collapse
** Where does one get the correct 4-LETTER CODE for their phone if one has a DIFFERENT phone than Kaiser and wants to flash via MicroSD card?
-----
Thanks to anyone who can please clarify these points
2. Removing the battery is not required in any level of flashing a ROM. removing the battery for Hard-SPLing is not required on all devices. For instance, my polaris doesn't require removing the battery.
9. Not sure why you need to do that but it IS necessary (you can pm Olipro about it) but i'm pretty sure it has to do with updating the connection between the PC and the PDA since while in Bootloader the PDA doesn't act as a plug-and-play device.
11. I don't recall this being an important step as I flashed hard-spls and roms without changing the AS state. you HAVE to have an activesync connection with your PC in order to flash (doesn't have to be synced, but the PDA has to be recognized by activesync, hope this is clear).
15. Yes, it is not a MUST. you can flash roms and spls while leaving the cable connected.
---------------------------------------------------------------------------------------------------
2. Yes, if you have the full library containing bootloader and everything you can flash without entering bootloader manually prior to flashing.
3. flashing doesn't require a specific state. you can start the process whenever.
4. Hard-reseting before MIGHT make a difference... in some cases which i'm not familiar with. maybe there's an app which can disturb the flashing process.
Hard-reseting after is pointless as flashing a rom performs exactly that WHILE switching the OS.
-about the syncing.. yeah, you don't need an actual sync-session. a usb connection is enough (AS LONG AS the comp identifies the hardware of course)
-it doesn't matter if you have the bootloader.exe file inside or not (I assume it depends on your device as well.. but not sure). RUU runs bootloader automatically. about HARD-SPL.. yeah, i haven't seen a hard-spl which doesn't contain bootloader.exe.. (i again suggest you pm olipro about this)
-again, it doesn't matter which screen you're on when running the ruu
...
-about the phone codes for flashing... you can find all codes for all phones in the forum
for instance,
Polaris -> POLAIMG.nbh
Hermes -> HERMIMG.nbh
Blackstore -> BLACIMG.nbh
Diamond -> DIAMIMG.nbh
Raphael -> RAPHIMG.nbh
Trinity -> TRINIMG.nbh
yada yada...
you can search, and i'm pretty sure not ALL devices have this option..
the wifi also contains info about flashing from SD card.
also, wonderful initiative and i hope you will agree to post this in the GUIDES thread.
Related
While a lot has been written, the following should provide an easy-to-follow guide.
Flash the new ROM
1. Backup your pocket pc using Sprite Backup and backup your original ROM using the SD card method http://forum.xda-developers.com/viewtopic.php?t=19500&sid=446b03c5f2a384e62c7905557ddcb450 .
2. Download the appropriate “shipped-rom.exe” file, such as ftp://xda:[email protected]/MA_DANG_WWE_10600_115_10500_SHIP.exe . DO NOT run it directly.
3. Right click to use winzip (or winrar) to unzip all the files into a directory of your choice.
4. Download MaUpgradeUt_noID.exe from http://www.ce4you.cz/forums/downloa...les/forums/cz/0000053752/MaUpgradeUt_noID.exe and save it in the same directory.
5. Disable USB in ActiveSync.
6. Set your ppc to bootloader mode (keep pressing both camera and on/off switches while resetting).
7. Connect pocket pc through USB.
8. Run MaUpgradeUt_noID.exe on your PC.
9. Don't get panic when the screen of your pocket pc goes dark. Use a torch and you can see the wording "USB ....".
10. On completion, hard reset your ppc (keep pressing on/off switch while resetting).
Follow-up Procedure:
1. After hard reset, you may choose to skip the installation of the Extended ROM files (especially the Default_Patch_bthusb.CAB file which might cause occasional bluetooth malfunction) by soft resetting the ppc, after the screen alignment routine and before the "in 3 seconds" message disappears.
2. You can re-install the splash screen of your choice by downloading the appropriate cab file. ftp://xda:[email protected]/Magician/Splash Screens/
3. You might have to re-install all softwares one-by-one, unless you are experienced in using the advanced features of Sprite Backup.
4. Copy the appropriate autoconfig files to get the right GPRS settings. For example, if you use CSL1010 in Hong Kong, download from ftp://xda:[email protected]/Magician/Extended-roms/O2_Mini_HK_Chinese/ : 11O_ALL_CHT_103170.sa.CAB, CAB-Customization-Magician-O2Asia1010-06Jan05.CAB, and AutoConfig.txt into the windows directory of ppc and run autoconfig.
very clear guide but how do i unzip the MA_DANG.......SHIP.exe file it says no archives found ? :?
dont unZIP them; if youre using winzip forget about it. get yourselfwinrar, right click on exe and 'extract to...' and youre done man!
regards,
Quappo
i followed your instructions..however when i run MaUpgradeUt_noID.exe it states "checking the information on your device" and thats it. it doesnt do a thing. any advice?
Topazworm said:
i followed your instructions..however when i run MaUpgradeUt_noID.exe it states "checking the information on your device" and thats it. it doesnt do a thing. any advice?
Click to expand...
Click to collapse
the same here...
ik looks like my downgrade (yes, a downgrade from iMate 1.06 to 1.03) starts and after 30 seconds it says it's ready, but notting happend!
Re: Summary of the USB MaUpgradeUt.exe methold of ROM Upgrad
Talents said:
While a lot has been written, the following should provide an easy-to-follow guide.
Flash the new ROM
.....
5. Disable USB in ActiveSync.
.....
Click to expand...
Click to collapse
How can I disable USB in ActiveSync?????????????
Tnks,
Ale
Click to expand...
Click to collapse
Re: Summary of the USB MaUpgradeUt.exe methold of ROM Upgrad
AX3L said:
Talents said:
While a lot has been written, the following should provide an easy-to-follow guide.
Flash the new ROM
.....
5. Disable USB in ActiveSync.
.....
Click to expand...
Click to collapse
How can I disable USB in ActiveSync?????????????
Tnks,
Ale
Click to expand...
Click to collapse
under connection settings, just uncheck allow USB connection,
Click to expand...
Click to collapse
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?
Hey everyone.
Last year I taught myself, how to Flash Samsung software.
After I learnt everything I needed, I made a step by step guide in my notes in case I need to do it again.
I posted that step by step guide in another discussion and it seems to have got a lot of views and hopefully helped.
As its at the bottom of a forum I thought I would post it in the next comment so people can get better access and I can help more.
Hope it helps.
Notes Before The Method
the cable you are using to connect to the pc should be the original charging cable. (If you don't have the original then use the one your using and see if it works)
Your phone needs to be at least at 60% battery.
Older phones sometimes don't work with newer versions of Odin so if this is happening download a older version.
If it's a new phone and you want to personalize it from scratch then no need to back up and restore any data.
Remove your SIM card to prevent it from being SIM locked to one network. ( I read it somewhere, not sure how true this is but I do it and seems to work)
After removing your memory card, plug it into your computer using a memory card extension and copy photos to your computer. Just in case the phone formats the memory card when entered back in to the phone, after the firmware is installed.
Method
1. Go to Sammobile via Google chrome in incognito mode. (If you don't do this they will re-direct you to a sign up page, everytime you press download)
2. Download Firmware, find this by picking the lastest firmware thats with your network and match the Baseband version or the last part of build number. (found in system info in the settings)
3. Install the latest version of Odin and install Samsung secondary device drivers on your pc/Laptop.
4. (On your mobile) back up your data in the samsung cloud.
Setting>Cloud and Accounts>Samsung Cloud>Backup settings> Back up.
If you have a memory card, move all your photos ect to it and remove it from your phone.
5. Go into setting and tap build number 7 times to unlock developer options. After unlocking it, enter developer options and enable usb debugging.
Setting>developer options>USB Debugging.
6. Once the firmware file has stopped downloading on your pc extract it and send it to your Downloads File.
7. Open Odin and load each part of firmware in the right box e.g. AP with AP, BL with BL, CSC with CSC ect (Do not load up Home CSC this is used for when your moving a branded device to another brand, E.g. EE to 3)
8. Before you plug your phone up to the computer. Turn your phone off and enter Odin mode(Download mode). Each device has a different way of doing this so just google how to do it on your specific samsung device.
9. Once your phone is in download mode plug it into the computer and press start. This should take a couple of minutes but some files may take longer.
10. Once the Odin confirms the process is done by showing the pass sign unplug your phone and turn it on. First time you turn it on May take a minute or two to load.
11. Enter your google email and password, and restore all your data on google.
12. Then enter your Samsung user and password, after that press restore and choose the date you backed up on before you flashed your phone (at point 4)
13. Enjoy all done.