I think i made a mistake.
After HardSpl i stuck in bootloader and now i have:
IPL 2.09.0001
SPL 2.G3
Did i HardSpl a G4 with a G3 rom?
I've tried every ruu i can find, even the original.
When i hard reset the Prophet i get "Format is Failed".
What can i do now?
Is there any way i can upgrade/downgrade SPL from Bootloader?
Thanks in advance.
Codix said:
I think i made a mistake.
After HardSpl i stuck in bootloader and now i have:
IPL 2.09.0001
SPL 2.G3
Did i HardSpl a G4 with a G3 rom?
I've tried every ruu i can find, even the original.
When i hard reset the Prophet i get "Format is Failed".
What can i do now?
Is there any way i can upgrade/downgrade SPL from Bootloader?
Thanks in advance.
Click to expand...
Click to collapse
As in my post in my signature, a basic solution = Don't Panic,
1. Try hardspl correctly referring to your model,
2. if no success, go to bootloader mode (3 color screen, see how to in my post 1), and flash PVtemp.
3. go all over again depends on your needs.
Enjoy.
dioxda2 said:
As in my post in my signature, a basic solution = Don't Panic,
1. Try hardspl correctly referring to your model,
2. if no success, go to bootloader mode (3 color screen, see how to in my post 1), and flash PVtemp.
3. go all over again depends on your needs.
Enjoy.
Click to expand...
Click to collapse
I've done that about 10 times.
No change.
I'm stucked in bootloader.
BTW how can i HardSpl from bootloader?
I thought you have to SoftSpl first...
Codix said:
I've done that about 10 times.
No change.
I'm stucked in bootloader.
BTW how can i HardSpl from bootloader?
I thought you have to SoftSpl first...
Click to expand...
Click to collapse
did you try to flash hardspl from the Bootloader mode?
1. enter bootloader( manually push buttons to enter, not the stuck screen,
2. plug and USB shows on the prophet,
3. flash Hardspl.....
dioxda2 said:
did you try to flash hardspl from the Bootloader mode?
1. enter bootloader( manually push buttons to enter, not the stuck screen,
2. plug and USB shows on the prophet,
3. flash Hardspl.....
Click to expand...
Click to collapse
Same
I think the problem with the device is that I can't hard reset it.
Everything is going well but it can't be hard reset.
I get the same message: "Format Is Failed".
BTW when i HardSpl from bootloader now, comes up a green screen with the same IPL and SPL on it.
Codix;1903274 said:
Same
I think the problem with the device is that I can't hard reset it.
Everything is going well but it can't be hard reset.
I get the same message: "Format Is Failed".
BTW when i HardSpl from bootloader now, comes up a green screen with the same IPL and SPL on it.
Click to expand...
Click to collapse
So~~~~~
Can you.....
copy the 3 files from the jumpspl.zip to and activate and then flash hardspl ??
1. copy then paste,
2. unplug,
3. execute SPL.lnk,
4. then ug back to PC,
5. Flash hardspl?
dioxda2 said:
So~~~~~
Can you.....
copy the 3 files from the jumpspl.zip to and activate and then flash hardspl ??
1. copy then paste,
2. unplug,
3. execute SPL.lnk,
4. then ug back to PC,
5. Flash hardspl?
Click to expand...
Click to collapse
No.
The device is stuck in bootloader, it doesn't do anything else, except when i flash the hardspl a green screen comes up and that's all.
The activesync can't connect.
I must change the SPL back to the original but only from the bootloader.
You HAVE to get back to a normal OS again before you can do anything else.
It is described in the WIKI, but I sum it up here for you:
* Find a complete NVID ROM RUU (there are several circulating, PDAViet Step1 for example)
* Put your Prophet in bootloader (3-colored screen)
* On your PC, in ActiveSync DISABLE the "allow usb connections" setting.
* Connect your Prophet to the PC using USB cable. ActiveSync shouldn't react, your Prophet is coneected as an ordinary USB device.
* Now run the NVID-RUU, it will take some time and it will look likes it stops at 80% and again at 95% but don't worry give it time and it will complete!
The result is a standard OS AND a standard SPL again.
GOOD LUCK!!
rondol1 said:
You HAVE to get back to a normal OS again before you can do anything else.
It is described in the WIKI, but I sum it up here for you:
* Find a complete NVID ROM RUU (there are several circulating, PDAViet Step1 for example)
* Put your Prophet in bootloader (3-colored screen)
* On your PC, in ActiveSync DISABLE the "allow usb connections" setting.
* Connect your Prophet to the PC using USB cable. ActiveSync shouldn't react, your Prophet is coneected as an ordinary USB device.
* Now run the NVID-RUU, it will take some time and it will look likes it stops at 80% and again at 95% but don't worry give it time and it will complete!
The result is a standard OS AND a standard SPL again.
GOOD LUCK!!
Click to expand...
Click to collapse
This 1 worked 4 me once, during flash electricity failure caused me headache but this method worked. I tried PDAVIET Step 1 rom.
Sad news
This is a post from Jesterz in another thread.
Sad news: no software solution for prophets with a wrong SPL (G4 SPL on a G3)
Hardware solution still possible, but we need to find the test points on the mainboard for a JTAG
email:
>> Hello,
>>
>> to be honest, we not have experience with a G4 bootloader on a G3
>> device but one thing is sure:
>>
>> Inside of the bootloader there are 2 functions to access the flash
>> chip (one to read and one to write). The G4 needs a complete
>> different sequence to access the flash. All operations (read: that's
>> why it can not start windows ce; and write: thats why you can not
>> flash another ROM) are using this 2 functions. So it doesn't matter
>> if you write the flash via bin or nbf file. The underlying flash
>> access functions are the same.
>>
>> The reason that your device still turns on is caused by the fact the
>> the IPL (the initial program loader) is still the correct G3 one and
>> has the correct flash loading mechanism inside to load the SPL
>> (secondary program loader) to RAM. Unfortunately the IPL does not
>> have any functions for reflashing. This is all inside the SPL (which
>> is now the bad one).
>>
>> The idea we have to fix the device is the following: We will start a
>> good G3 device from us in SPL then we will take out the G3 chip from
>> our device and place yours inside (device still on and having
>> correct G3 SPL in memory). Then we think we can flash your G3 with a
>> good G3 firmware. Finally place all chips back and it should be
>> working again
Jesterz you made my day.
Don't give up!
The Jester-mail descibes the "other-way-around" situation! Did you tried the suggestion I posted earlier? Iy worked for many others, why shouldn't it work for you? (Unless you are in need for a Prophet-shaped paperweight...)
rondol1 said:
Don't give up!
The Jester-mail descibes the "other-way-around" situation! Did you tried the suggestion I posted earlier? Iy worked for many others, why shouldn't it work for you? (Unless you are in need for a Prophet-shaped paperweight...)
Click to expand...
Click to collapse
Yes rondol1 i did what you told me but nothing.
My Prophet flashes all the roms succesfully and back to the bootloader, plus i can't hard reset it anymore.
Seems like i have one Prophet-shaped paperweight after all
Last try.....
Sorry to hear, I have just one option left:
I uploaded my saviour-ROM to rapidshare, give it a try. At least I know for sure that this one has everything onboard that would be needed.
http://rapidshare.com/files/90335584/wm50_RUU_Prophet_220734_2207114_026121_NVID.zip.html
And follow the steps I explained precizely.
rondol1 said:
Sorry to hear, I have just one option left:
I uploaded my saviour-ROM to rapidshare, give it a try. Atleast I know for sure that this on has everything onboard that would be needed.
http://rapidshare.com/files/90335584/wm50_RUU_Prophet_220734_2207114_026121_NVID.zip.html
And follow the steps I explained precizely.
Click to expand...
Click to collapse
Thanks man.
I will try it just now.
Perhaps a useless addition, but after the RUU finishes, don't touch anything, don't disconnect, just wait for your Prophet to restart.
rondol1 said:
Perhaps a useless addition, but after the RUU finishes, don't touch anything, don't disconnect, just wait for your Prophet to restart.
Click to expand...
Click to collapse
Actually i can't flash this rom.
ERROR[208]: FILE OPEN
I flashed a similar rom before but nothing.
Anyway thanks for everything guys.
I will send the Prophet to service in Monday.
I hope they will fix it.
I don't like it, but I have to admit I'm out of suggestions....
GOOD LUCK....
One suggestion left! Just noticed that in the ROM/RUU package I uploaded for you, somehow the RUUGetInfo.exe is changed to RUUGetInfo.txt.
Change the extension and it should work (at least here on my PC), that is, the RUU should run....
rondol1 said:
One suggestion left! Just noticed that in the ROM/RUU package I uploaded for you, somehow the RUUGetInfo.exe is changed to RUUGetInfo.txt.
Change the extension and it should work (at least here on my PC), that is, the RUU should run....
Click to expand...
Click to collapse
Now at 80% i get "INVALID COMMAND"
Codix said:
Now at 80% i get "INVALID COMMAND"
Click to expand...
Click to collapse
Sh****t... at 80% that is where the SPL gets installed, I think....
No Luck, no clues, no ideas left... sorry!
Related
Hi,
I've read and reread the thread at http://forum.xda-developers.com/showthread.php?t=350033 i.e. New WM6 Upgrade Guide.
Just a few questions:
1. After step 2 i.e. HardSPL is complete, what should be the status of the prophet? I mean.. at the end, would it soft reset? hard reset? the screen will remain blank? tri color? How would I know the step is completed successfully?
2. Step 5: Flash the nk.nbf. Ok.. now how should the prophet be connected? Will the prophet be in a wm5/6 setup stage, and a guest connection would have to be made thru activesynch, just like the previous process? What state would the prophet be in from previous step, and how and when to run the ROMUpdateUtility_NV_G3.exe? It is understood that my nk.nbf is in the same directory.
TIA.
J_Kirk said:
Hi,
I've read and reread the thread at http://forum.xda-developers.com/showthread.php?t=350033 i.e. New WM6 Upgrade Guide.
Just a few questions:
1. After step 2 i.e. HardSPL is complete, what should be the status of the prophet? I mean.. at the end, would it soft reset? hard reset? the screen will remain blank? tri color? How would I know the step is completed successfully?
2. Step 5: Flash the nk.nbf. Ok.. now how should the prophet be connected? Will the prophet be in a wm5/6 setup stage, and a guest connection would have to be made thru activesynch, just like the previous process? What state would the prophet be in from previous step, and how and when to run the ROMUpdateUtility_NV_G3.exe? It is understood that my nk.nbf is in the same directory.
TIA.
Click to expand...
Click to collapse
1. look the same (nothing change), only the digits was being changed while rebooting...
2. USB cable to connect, you can let it be in guess connection with the activesync or if problems occur, have a look to post 1 in my thread ( in my signature) for your reference..
Good luck....
again..... master rondol1 provides detailed answers, look below, enjoy~~~~~
J_Kirk said:
Hi,
I've read and reread the thread at http://forum.xda-developers.com/showthread.php?t=350033 i.e. New WM6 Upgrade Guide.
Just a few questions:
1. After step 2 i.e. HardSPL is complete, what should be the status of the prophet? I mean.. at the end, would it soft reset? hard reset? the screen will remain blank? tri color? How would I know the step is completed successfully?
2. Step 5: Flash the nk.nbf. Ok.. now how should the prophet be connected? Will the prophet be in a wm5/6 setup stage, and a guest connection would have to be made thru activesynch, just like the previous process? What state would the prophet be in from previous step, and how and when to run the ROMUpdateUtility_NV_G3.exe? It is understood that my nk.nbf is in the same directory.
TIA.
Click to expand...
Click to collapse
1. Your Prophet will restart to the same OS as you had before. There is no change other then the SPL replaced. You can check this on the second startup-screen, the one with the red informationtext. If things went fine, you should read: SPL 2.G3.4PDA or SPL 2.G4.4PDA. If not, don't continue flashing but try to install HardSPL again.
2. As the OS is still the same you used before, just connect your PPC using an USB cable. No need to connect in guest mode or anything different. When made sure that HardSPL is installed correct, the Prophet doesn't have to be in a special state. You have downloaded the RUU according to your devicetype G3 or G4. Download the nk.nbf ROM file of your choice and place it in the same folder with the RUU. Now just run the RUU and be patient. It seems to stop several time, but just don't react as long as you don't get an error. At the and the RUU will report it is finished and your Prophet will restart.
rondol1 said:
1. Your Prophet will restart to the same OS as you had before. There is no change other then the SPL replaced. You can check this on the second startup-screen, the one with the red informationtext. If things went fine, you should read: SPL 2.G3.4PDA or SPL 2.G4.4PDA. If not, don't continue flashing but try to install HardSPL again.
2. As the OS is still the same you used before, just connect your PPC using an USB cable. No need to connect in guest mode or anything different. When made sure that HardSPL is installed correct, the Prophet doesn't have to be in a special state. You have downloaded the RUU according to your devicetype G3 or G4. Download the nk.nbf ROM file of your choice and place it in the same folder with the RUU. Now just run the RUU and be patient. It seems to stop several time, but just don't react as long as you don't get an error. At the and the RUU will report it is finished and your Prophet will restart.
Click to expand...
Click to collapse
Thanks very much, rondol1 !!
dioxda2 said:
Thanks very much, rondol1 !!
Click to expand...
Click to collapse
Hahaha, why is it that we anwer the same questions at the same time so often??!
Thanks a lot rondol1 and dioxda2! your answers are just what i needed..
Ok a brief followup.. after downloading the update package from http://forum.xda-developers.com/showthread.php?t=350033&highlight=hard+spl and applying the G3 version of HardSPL, I see absolutely NO change on my prophet. The boot up shows SPL 2.20.0000 and not SPL 2.G3.4PDA as mentioned. I've tried it twice with same result.
Any suggestions?
J_Kirk said:
Ok a brief followup.. after downloading the update package from http://forum.xda-developers.com/showthread.php?t=350033&highlight=hard+spl and applying the G3 version of HardSPL, I see absolutely NO change on my prophet. The boot up shows SPL 2.20.0000 and not SPL 2.G3.4PDA as mentioned. I've tried it twice with same result.
Any suggestions?
Click to expand...
Click to collapse
did you try THIS TOOL on my Thread?
After Hardspl,
Try this "one step Jumpspl+Korand3.1(WM6.1)" tool (uploading), quite convenient.. to try this rom. ( clean, fast and stable)
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Update - I just tried this:
http://forum.xda-developers.com/showthread.php?t=326953
but without success. I get an Error [260] and the entire process stops.
Anubis1965 said:
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showthread.php?t=405814
lakeman said:
look here
http://forum.xda-developers.com/showthread.php?t=405814
Click to expand...
Click to collapse
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Anubis1965 said:
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Click to expand...
Click to collapse
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
If you see in bootloader mode ID showing somenting different than ATHE100 the solution is HERE http://forum.xda-developers.com/showthread.php?t=405814
I had the same problem! whell restart your pc and then connect the device to it. now start flashin an spl 1.20 rom. i did it and it worked! I hope i works for you too.
Cheers, Hirad
lakeman said:
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
Click to expand...
Click to collapse
Thanks - already tried!
When I reset/hard-reset the phone (tried many ways) I see a garbled boot image (with random pixels here and there)... It is definitively not the usual bootloader with the information about the various ROM components and the "USB" text at the bottom.
Anubis
Solution!
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
You are right and this is what sergiopi and I were referring to , specifically this post
http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
We were refering to the whole thread so you could learn the background.
However you are incorrect in your advice about how to enter bootloader
All you need to do is hold in the camera button and reset
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
Thanks - you are giving me some hope! I am on a business trip now and my Athena is at home, but I will try that as soon as I am back
Anubis
Ive got a "bricked" S200 G4 (I think)
Text in rainbow screen is
"ILP 2.20.0001
SLP 2.10.0001"
I dont know if the difference here matters.
Tried to upgrade with different ROMs, but no luck, upgrade stops in the process, different % every time.
But the latest Speedking 2 ROM I managed to install. Hopefully I softbooted and got the same rainbow screen.
Any advice?
Why didn't you hardspl your prophet ??
I did, but maybe wrong hardSPL? It is a jungle here, hard to find the right info I need because its so much.
hpn said:
I did, but maybe wrong hardSPL? It is a jungle here, hard to find the right info I need because its so much.
Click to expand...
Click to collapse
1. not 100% of our Prophet can be hardspl done ( like mine )
2. if so, just go straight ahean with my lazt_tool, too easy though....
3. hardspl is just a flashing process but only spend a couple of minutes unlike rom flashing, (from 5 - 10 minute.)
all you have to read in the sticky post on the top pf this forum
I recommend youto read post 1 of this thread....
http://forum.xda-developers.com/showthread.php?t=353547 as follow....
20080601added:
[size=+2]Lazy_Tool (thks YOUZII) is for flashing all nk.nbf, in win-xp PCs, ........[/size]
WANNA GO OLDER ROMS? READ THIS POST THOROUGHLY ^_^ )
P.S. You can just change / replace the nk.nbf inside the Lazy_Tool folder if you wish to flash other roms....
20080529 added:
Cloudyfa's 19213 clean rom + Lazy_Tool, simple, fast, error free, a new upgrade tool.
[size=+3] Additional RECOVERY steps for 3 colors screen boot-up after flashing...[/size]
a. Force Bootloader Mode MANUALLY (see below Point 4 for How To ), Then flash PVtemp or NVID for prophet( P.S. the boot up screen will be changed to Qtek...),
b. ( Optional) Use Lazy_Tool to upgrade to WM6.1 (default rom is Cloudyfa's 19213-clean, you may change if you want...)....^_^,
Click to expand...
Click to collapse
20080423 added: Alternative "Lazy_Tool"
some hints ~~
if error persists while upgrading with this tool,
Please ask yourself...
I. did I softreset yet? did I make the Prophet recovery? (remove battery and sim card),
II. will the USB port of my PC currently too heavy loaded?
III. did I restart my PC yet?
IV. any connection related software other than activesync is running?
V. did I try the rear panel USB ports?
V.I is my PC currently too busy?
VI. did I try other USB cable yet?
VII. did I try the force bootloader manually before upgrade?
VIII. Did I hardreset my prophet after new flash(if everything had done but no help~~~~ ) ^_^
**************************************
2008-02-18 added ***
NVID for prophet,
Click to expand...
Click to collapse
HARDspl
(OLD method is at the bottom of this post)
1: "DON'T PANIC",
2: 99.9999% CAN BE RECOVERED BY
DOWNGRADE TO WM5 WITH entering BOOT_LOADER MODE + flashing the PVtemp (old method step 1).
3: IF USB CONNECTION ERRORS, TRY REMOVE BATTERY FOR 1 MINUTE and try again.
4: FORCE BOOTLOADER MODE MANUALLY HOW TO = ....
4a. keep pressing the Commgr button and
4b. in the same time keep picking/sticking the bottom softreset button with stylus for one second,
4c. [size=+2][highlight] THEN ONLY ONLY RELEASE THE STYLUS[/highlight][/size] and wait for the screen
TO CHANGE to the three color screen (bootloader mode),
4d. then release all and go to step 10 below..... !!!
Click to expand...
Click to collapse
(remember to download and prepare all files you needed first, or you may have errors while in the upgrade process)
Click to expand...
Click to collapse
5. Execute the Rom Upgrade Utility (ROMUpdateUtility_NV_G3.exe ( or G4), in the
HardSPL folder that you had downloaded, all activities will only take 2-3 minutes to go and
nothing will be seen in the Prophet screen.
(P.S. if connection Error, NO PANIC, soft reset OR remove battery for half a minute and try again. )
6. after the flash completed, it will restart automatically.
7. done!! in your prophet, nothing will be changed VISIBLY EXCEPT the digits IN the reboot screen !!!!!
and while booting now YOU MUSTBE ABLE TO SEE information like: 2.G3.4PDA (FOR G3 PROPHET) or 2.G4.4PDA (FOR G4 PROPHET)
Prophet Hard SPL isn't yet completed until the SPL shows
"2.G3.4PDA" or "2.G4.4PDA". ^_^ !!!
Alternate way to Flashing / upgrading your Prophet to WM6,
a. ENTER BOOTLOADER (see how to at the upper part of this post) [size=+2]OR [/size]
b. DO THE JUMPSPL...(step 8-9 BELOW) [size=+2](you can force to bootloader mode instead of step 8 to 9)[/size]
8. copy the 3 files from the jumpspl.zip to the root directory of your Prophet and then unplug / disconnect Prophet,
9. Execute the SPL.lnk IN THE DEVICE (using the Total Commander is recommended), then you see Prophet in all bright or white screen,
10. Plug back to the USB port ( connect to rear USB panel of the computer - recommended) to the device,
11. Execute the Rom Upgrade Utility to upgrade to your chosen rom
(or put your NK.NBF to the unzipped WM6_Update_Utility folder), all activities will
only take 3-5 minutes, nothing will be seen in the Prophet screen.
12. Finally, after 100%, be patient, just wait, and Prophet will reboot automatically.
13. OF COURSE, after it auto-restart, [size=+2]better one more time HARD-RESET[/size],
ALL will be OKOKOK !!!
[size=+3]Tradition (OLD) method[/size].... (for ROM with OS.nb ),
1. Connect to PC, activesync now OK, Flash with [size=+2]PVtemp[/size] or NVID for prophet for step 1
WHEN FINISH,
2. TOUCH NOTHING, HANDS-UP !!! leave it alone, just don't touch your prophet...... ( WM5 wwe flashing now finished)
3. [size=+2]ACTIVE SYNC WILL POPS UP soon, JUST DON'T TOUCH IT (disregard it) [/size],
4. THEN RUN UPGRADE.BAT from PC to flash to WM6 (should be included in your old ROM package with OS.nb )
5. follow the on screen steps and YOU WILL GET WHAT YOU HAD EXPECTED THEN~~~~~
[size=+2]PLEASE REPLY IF YOU THINK HELPFUL ABOUT THIS MESSAGE !! ^_^ [/size]
Click to expand...
Click to collapse
I`m running Mac, with XP under Parallels. Upgrading Trinity is no problem on his config. But your reciepe include running command window. I cannot connect to the prophet from command window.
Trying to solve this somehow. Thanks for the link.
well, Hard-SPL is released now! sorry for delay, I got distracted elsewhere
[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]Donations are always appreciated to the big link in our signature ("elite project"). You can also donate via the link offered in the new Hard-SPL program. Thank you!![/size]
Preparations:
first an important note, if you want to flash more than one Iolite, contact cmonex for additional licenses via http://support.htc-unlocks.com. (the first license is transparently granted and free, so normal users do not need to worry.)
0) this package is for Iolite (Touch Cruise II/2009) devices. for any IOLI***** so far (SSPL loader checks this and gives a warning if needed), afaik there is no CDMA version so all the model variations should be fine.
1) if you have vista, WMDC update is recommended: http://www.microsoft.com/windowsmobile/en-us/help/synchronize/device-center.mspx
Instructions:
read this if unsure how to install Hard-SPL...
1) download latest Hard-SPL package (currently v1.10) from attachment, extract to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!!
3) NEW: internet access is required as the program checks online for updates and license.
4) run Iolite-Hard-SPL EXE on PC, make sure it's launched from a local drive (not through network drive, etc.). if you are on vista, launching as Administrator is strongly recommended, on XP administrator login is required. important: if your AV (norton/symantec mainly) warns about a virus, ignore it, it just doesn't like the packer I used to pack the program.
5) if possible, always use Automatic flash mode (for uses of Manual mode, see troubleshooting section)
6) it will ask you to wait while it prepares for the flashing, press OK. follow steps in the program and then in the RUU.
7) some notes: 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 thread, but this should not ever occur (as this means a really fatal error occurred).
more notes: when RUU says it will hard reset, do not worry, it is not going to do that. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
8) device should go to a tricolour screen now that says 1.09.C-SSPL, this is the SSPL version, which is temporary.
9) SPL flashes, device automatically reboots, job done.
10) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.09.OliNex, which is the Hard-SPL version.
NOTE: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, fully power the device off by long press of power key, then power on while holding the "volume down" key on the left side of the device. keep holding the volume down key until you see tricolour screen which is the bootloader mode, then release it.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs or radio packages. 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 will soon be posted in this post as well. 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 at the end of this post about how to reflash stock SPL.
NOTE 3: 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 (using OliNex custom cert, which is not public) will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or customRUU if you need to flash cooked ROM.
Troubleshooting:
- read the instructions above.
- read the instructions above.
- read the instructions above.
Manual flash mode for USB issues: you should usually go for Automatic flash mode; you must only attempt the Manual mode option if Automatic flash mode or SSPL-Manual.exe already put device in SSPL tricolour screen and you got USB issues. any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
ModelID checking:
- afaik no CDMA model, so doesn't matter but let me know if you got any problems.
nothing happens on the device, does not enter tricolour screen mode:
- anyone having problems with the device entering SSPL automatically, please make sure you watch the device screen if it asks about running files. also try unchecking advanced usb functionality in settings.
- if it crashes instead of entering SSPL, you need to use Automatic mode.
general usb connection error problems if you get connection error in RUU after the device goes to 1.09.C-SSPL screen:
- try manual SSPL: copy SSPL-Manual-Iolite exe to the device and run it, then when it went to 1.09.C-SSPL tricolour screen and shows "USB" at the bottom in this screen, use Manual option in the Hard-SPL program on the PC.
- make sure device was still synced via USB to the PC at the point of it entering SSPL (the 1.09.C-SSPL screen)!
- 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.
- also you can try unticking advanced network functionality in start menu / settings / connections / usbtopc applet.
- 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 and perhaps if you are on vista), then if RUU times out, but device still says "USB" on the tricolour screen, just leave it there and re-run the RUU when driver installation finishes.
- finally, you can try disabling antivirus or firewall programs on the PC.
other issues:
- if Enterbootloader.exe fails to run (says missing component or similar), try a hard reset of the device.
- if device reboots instead of going to SSPL screen (1.09.C-SSPL), contact us by PM'ing cmonex. do not PM OliNex user, that is not monitored frequently.
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. take the SPL relocker attachment, and run the EXE - this will flash 1.09.0000 stock SPL. simple as that!
2. flash
3. verify if it flashed by checking version in tricolour screen, it should say 1.09.0000.
credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> EXE program concept that runs on the PC, Hard-SPL concept, server code, maintaining licenses
cmonex -> new PC EXE & SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code)
---reserved post---
---reserved---
"IOLI100
SPL-1.09.oliNex
MicroP-Iolite(LED) v5"?
Has it released? It has appeared on the interenet.
Let me see see!
chenjun_conan said:
"IOLI100
SPL-1.09.oliNex
MicroP-Iolite(LED) v5"?
Has it released? It has appeared on the interenet.
Click to expand...
Click to collapse
yes, I've sent it to several people. I'm posting it here too in a sec.
edit: posted
Dan
OK
you are great.
Thank you so much.
Fantastish!
THANK U VERY VERY MUCH!!!
after HSPL and flashing to Rissian ROM it says "Your OS ROM isn' t customized for your hardware Please reflash the proper ROM code or contact the service center' .
In the internet i've read that taking out the battery for 10-15 minutes must help. But it doesn't. Please help!
Great job, big thanks!
@ cmonex was send you a PM, please answer me. Thanks!
Greetings
Baga12 said:
after HSPL and flashing to Rissian ROM it says "Your OS ROM isn' t customized for your hardware Please reflash the proper ROM code or contact the service center' .
In the internet i've read that taking out the battery for 10-15 minutes must help. But it doesn't. Please help!
Click to expand...
Click to collapse
try to flash WWE|Eng and post result here
Nice work as usual guys.
Thread stuck
Dave
After IoliteSPLRelocker, the HSPL' s not working, why? Please help
Thank you
Thank you so much for your hard work.
My Iolite can do do just about anything right now.
Baga12 said:
After IoliteSPLRelocker, the HSPL' s not working, why? Please help
Click to expand...
Click to collapse
You tell us? It what way doesn't it work?
Dave
I tried to test the IoliteSPLRelocker, it flashed correctly, then I again tried to flash the HSPL with mhile my device was in three color mode, but it stops at the 0%, not going more. Stupid of me, of course
So? what about WWE Roms? Does anybody flash them at new HSPL?
thanks very much . it's great'
Baga12 said:
I tried to test the IoliteSPLRelocker, it flashed correctly, then I again tried to flash the HSPL with mhile my device was in three color mode, but it stops at the 0%, not going more. Stupid of me, of course
Click to expand...
Click to collapse
Please help!
max_nya said:
So? what about WWE Roms? Does anybody flash them at new HSPL?
Click to expand...
Click to collapse
Once you have Hard SPL, you can flash any ROM's (Cooked or Shipped) to your device. So put on Hard SPL, find a WWE ROM and flash it .
Baga12 said:
Please help!
Click to expand...
Click to collapse
I've just checked the re-locked and it does contain the correct SPL.
Connect your phone to you PC using AS, and then run the re-locked, once done your SPL should be 1.09 (with the .OliNex) again
Dave
First of all, Hi!
Now, how do I clear my nike to the point where it has nothing on it?
I need to do this because I got stuck in the process of flashing it with HARDSPL 1.22 that I need in order to flash a new rom!
I tried everything, I followed the guide on how to do HardSpl, but got stuck at step 8 of the tutorial, the process bar is constantly at 0%, and followed by recovery steps!
I do not need them because everything works just fine, only with the original rom still on!
So I want to flash a rom, but am unable to!
Please help me!
Even if my solution is deleting everything ( I do not mean a Hard Reset- Did that 10 times ) and starting from 0!
But this is one thing I never did, and do not know where to start or what to do!
So any good soul out there willing to help, please do so!
Thanks in advance!
Ok let's try to help, can you tell us more details about your phone, model 16 or 20 keys, rom and radio.
If this is not clear just send me a pm
Regards Rataplan
Thanks, mine is a 16 key version.
Radio 1.65.28.25
Rom: 2.09.405.1
Rom date: 30.08.2008.
Protocol version: 25.98.40.07H
And I did the first few steps of flashing the HardSpl
and now it says SPL 1.22
and further more, on start up screen it says "TEST ONLY NOT FOR SALE"
BTW: I was looking of flashing your ROM but as I said, no can do!
HELP
Ok from what I see it looks to me that you already flashed a rom, just one question is it telling SPL 1.22 or SPL 1.22 Hard
just SPL
That is my problem!
Any solution!?
You need to start all over again, do you have a Niki, you can see that under the battery
Okay just read your post in the other thread, that cleared a lot of things, just do it all over again and use 1.15 instead of 1.22 maybe that will work for you, btw from what I can see you didn't do anything wrong, I also flashed directly the 1.22 and from me that works.
Just keep me informed how it goes.
Regards
The phone is niki100
There is no simlock!
What do I need to do?
Refer me to a tutorial, or just tell me everything here?
And thank you for the help so far!
Edit:
OK, I did what you said, and so far works!
But, could you please explain to me a couple of things!
1. download the attached files DONE
2. REMOVE SIM and SD CARDS !! DONE
3. connect usb cable DONE
4. copy sspl-1.16-nike.exe to your device and run it (usb cable must be connected!) DONE
5. after a few seconds "USB" appears on the display DONE
6. unplug and replug the usb cable DONE
(OPTIONAL, better to skip it! step 7. if you only want to test the sspl try flashing the attached splash screen by running ROMUpdateUtility.exe from flash-splash-niki) SKIPPED
8. you can now flash the hardspl-1.15mfg-nike.nbh by running ROMUpdateUtility.exe from flash-uspl-niki
AND NOW here is my question, in the file FLASH-USPL-NIKI there is a uspl-1.16-nike.nbh file, but here in this step it says to flesh the 1.15mfg(wich I downloaded), so do
i have to delete the 1.16 and replace it with the 1.15mfg or what?
9. after installing the hardspl you can flash any rom (rom cook project here)
Okay I think I kow what you mean, you must flash the 1.15mfg, do not copy it to your phone, you don't have to delete the 1.16.
EUREKA, it worked!
Flashed your F01-10 rom!
Now I only did the 1.15 HARD Spl
Please suggest to me a radio?
I tried flashing the Radio_1.71.09.01_25.75.40.02K and it got to 100% and then said FLASH WRITE ERROR, so I was stuck wit the old radio!
AND OMG, THE ROM IS WONDERFUL
Thank you so very very much!
I need help, i have flashed a rom but now my niki stops at the radio details. It doesn't boot to windows mobile.
How do i reflash a working rom now?
How long have you waited before taking out the battery?
It takes a while to load!
It takes a while to load yes, but 5-10 minutes is to long for it to start to boot.
It has passed 1 hour now.
Anyone knows how can i fix my niki?
2 die 4 said:
EUREKA, it worked!
Flashed your F01-10 rom!
Now I only did the 1.15 HARD Spl
Please suggest to me a radio?
I tried flashing the Radio_1.71.09.01_25.75.40.02K and it got to 100% and then said FLASH WRITE ERROR, so I was stuck wit the old radio!
AND OMG, THE ROM IS WONDERFUL
Thank you so very very much!
Click to expand...
Click to collapse
You're welcome for the rom, about the radio if you want to try the 1.71 radio you have to go back to an older radio before you flash the 1.71.
I suggest to use a 1.5.. radio, that will do the trick.
For now you can always put Hardspl 1.22 on your phone, some people are recommended that if you flash a wm 6.5 rom, personally I don't see any difference.
Btw The radio I use is 1.65.29.22
Regards
masterxiter said:
It has passed 1 hour now.
Anyone knows how can i fix my niki?
Click to expand...
Click to collapse
Hmm, that's a long time without a phone , did you already try a hardreset, just turn the phone off, and turn it on by pressing the power and the send and end key on the dame time, I think that will do it.
Just keep me informed.
Regards
Rataplan said:
Hmm, that's a long time without a phone , did you already try a hardreset, just turn the phone off, and turn it on by pressing the power and the send and end key on the dame time, I think that will do it.
Just keep me informed.
Regards
Click to expand...
Click to collapse
Yes it enters restore mode. If i have the usb cable, when the restore finishes, on the pc it says "unrecognized usb" / Unknown device. I reboot the phone and its the same.
masterxiter said:
Yes it enters restore mode. If i have the usb cable, when the restore finishes, on the pc it says "unrecognized usb" / Unknown device. I reboot the phone and its the same.
Click to expand...
Click to collapse
Hmm, okay this will be diffucult, I've read you flashed a rom and after that you get this issue, just a few questions did you cid unlock your phone, and is the bootloader still there. (that is the 4 coloured screen with the spl info)
masterxiter said:
Yes it enters restore mode. If i have the usb cable, when the restore finishes, on the pc it says "unrecognized usb" / Unknown device. I reboot the phone and its the same.
Click to expand...
Click to collapse
hey dude
y dont u flash the original rom of htc nike once and then retry?
Rataplan said:
Hmm, okay this will be diffucult, I've read you flashed a rom and after that you get this issue, just a few questions did you cid unlock your phone, and is the bootloader still there. (that is the 4 coloured screen with the spl info)
Click to expand...
Click to collapse
Yes i have both.
I allready change those 4 colors for an image, lol but ok i have the spl info:
M 04
B 04
R 1.65.28.25
G 25.98.40.07W
D 2.12
What happened was, i had an working cooked rom flashed in my phone. I was working with it for about a month.
yesterday i flashed with another one. It got me 100% rebooted and voilla doesn't pass the spl boot.
masterxiter said:
Yes i have both.
I allready change those 4 colors for an image, lol but ok i have the spl info:
M 04 R 1.65.28.25
B 04 G 25.98.40.07W
D 2.12
Click to expand...
Click to collapse
Ha ha yeah that would be nice if we could replace that for an image.
Okay, connect it to your computer when you're on the 4 coloured screen and see if it connect then, in the phone you see serial changing in usb, if yes just flash your original rom.