HI,
Anyone tried revert back to Stock-SPL trough MicroSD?
I did, wel... the SPL is back, but i'm getting this screen:
RUUNBH
RAPH100
SPL-1.90.000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
Upgrade ROM code error
Please try again
Serial.
this is in the TRI-COLOR screen and i'm not getting a USB connection (this is the problem why i reverting back to stock SPL, USB is not recognized)
Please help!
Possibly re-flash your ROM? But I'm no expert on this.. so don't trust me fully.
Already tried... nope
Flash hard spl and start over. Try reading the instructions on reverting to stock-there are plenty of resources here. Do the spl over usb, and do it last.
My USB isn't working!
Other updates doesn't work
Follow these steps:
# Download mtty.exe from here: http://taeguk.co.uk/xda
# Disable activesync (connection settings -> uncheck "allow usb connections")
# Kill the following two processesto stop active sync; rapimgr.exe and wcescomm.exe (Ctrl+Shift+Esc, select from the list of processes).
# Connect your Kaiser to PC using USB cable.
# Open mtty, select USB port and click OK.
# Hit ENTER twice, you should see the "Cmd>" prompt.
# type "set 16 0" (without quotes) and press ENTER.
Reboot.
Ta
Dave
DaveShaw said:
Follow these steps:
# Download mtty.exe from here: http://taeguk.co.uk/xda
# Disable activesync (connection settings -> uncheck "allow usb connections")
# Kill the following two processesto stop active sync; rapimgr.exe and wcescomm.exe (Ctrl+Shift+Esc, select from the list of processes).
# Connect your Kaiser to PC using USB cable.
# Open mtty, select USB port and click OK.
# Hit ENTER twice, you should see the "Cmd>" prompt.
# type "set 16 0" (without quotes) and press ENTER.
Reboot.
Ta
Dave
Click to expand...
Click to collapse
this is the problem why i reverting back to stock SPL, USB is not recognized
Click to expand...
Click to collapse
It's staying SERIAL
binky11 said:
It's staying SERIAL
Click to expand...
Click to collapse
I don't think you can remove RUUNBH just from the SD card.
You posted the SPL is 1.90. this is a stock one IIRC.
Dave
DaveShaw said:
I don't think you can remove RUUNBH just from the SD card.
You posted the SPL is 1.90. this is a stock one IIRC.
Dave
Click to expand...
Click to collapse
When i try a ROM, RADIO ROM or SPL it stays on Loading...
It's really frustrating..
binky11 said:
When i try a ROM, RADIO ROM or SPL it stays on Loading...
It's really frustrating..
Click to expand...
Click to collapse
It will, the RUUNBH flag is stopping it.
As I said before, the SPL you posted is 1.90 and doesn't say Olinex, so I'm guessing it's stock. Why can't you return the device?
Dave
I don't think that's warranty?
binky11 said:
I don't think that's warranty?
Click to expand...
Click to collapse
Unless it says Olinex I'm pretty sure it's stock. From what I've heard HTC are on the lookout for the "OliNex" mark in the bootloader, which you don't have.
I cannot see any reason it would be rejected (unless you still have a custom ROM and they somehow get it to boot).
That's just my opinion, but I can't think of any way to get it to boot WM without USB working again.
Dave
DaveShaw said:
Unless it says Olinex I'm pretty sure it's stock. From what I've heard HTC are on the lookout for the "OliNex" mark in the bootloader, which you don't have.
I cannot see any reason it would be rejected (unless you still have a custom ROM and they somehow get it to boot).
That's just my opinion, but I can't think of any way to get it to boot WM without USB working again.
Dave
Click to expand...
Click to collapse
I tried the lastest Vodafone ROM from UK. It's says Not Allow..
So i'm on the lookout for the Dutch version (the one on the wiki doesn't work)
binky11 said:
I tried the lastest Vodafone ROM from UK. It's says Not Allow..
So i'm on the lookout for the Dutch version (the one on the wiki doesn't work)
Click to expand...
Click to collapse
This is what hey says with the Vodafone UK ROM
Loading...
Checking...
00028002
Not Allow
DaveShaw said:
I don't think you can remove RUUNBH just from the SD card.
You posted the SPL is 1.90. this is a stock one IIRC.
Dave
Click to expand...
Click to collapse
RUUNBH can be removed by flashing a valid image that 100% completes the flash. even if it is done via SD
DaveShaw said:
It will, the RUUNBH flag is stopping it.
As I said before, the SPL you posted is 1.90 and doesn't say Olinex, so I'm guessing it's stock. Why can't you return the device?
Dave
Click to expand...
Click to collapse
yeah, I'd like to know that myself.
binky11 said:
I don't think that's warranty?
Click to expand...
Click to collapse
is the ROM on the device stock? I'm asking because they can get it booting if they really want to. the question is of course whether they wish to go to that trouble just to check as the SPL itself is stock so it looks nice
so anyway let me know if it's cooked or not
cmonex said:
is the ROM on the device stock? I'm asking because they can get it booting if they really want to. the question is of course whether they wish to go to that trouble just to check as the SPL itself is stock so it looks nice
so anyway let me know if it's cooked or not
Click to expand...
Click to collapse
Well.. as far as i know it's stock.. i downloaded the Dutch Vodafone ROM from the WIKI.
Hope that helps
stock voda ROM
did it work ?
http://www.vodafone.nl/Vodafone/wg20/software/RUU_Raphael_Vodafone_NL_1.90.172.4_Radio_Signed_Raphael_CRC_52.33.25.17_1.02.25.19_Ship.exe
this is the stock ROM on the voda NL website
Related
Dear All,
I've tried to upgrade to ROM Hermes_1.18.416.1_1.18.416.101_1.14.00.10_WWE_Ship
and unluckly cable loosen and I reset the phone.
Since it's in the middle and can't success enter the Windows Mobile,
but the bootloader was updated to 1.06.
Now I can't flash any ROM either
HER_DopodAsia_1237074_1060010_WWE_SHIP or the new one.
The tools on "imei check" even can't recognize my phone.
Any one can help me on this issue, please?
Thanks in advance.
Try the steps here, let us know the results:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you don't fix it with the proposed solutions attach USB Monitor capture in text format as explained in the bootom of the page.
I have the same issue, and sent it to service, and now I have the phone back and they could not fix it, so got no radio or imei number, so none of the FAQ will work for me.
So I have an expensive paper weight.
Hi,
ME TOO!!
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
I have also tried imei without any joy.
the PDA part of my M3100 still works but the phone is dead. I have been told that if you can get the latest radio installed then you satnd a chance of the phone part working.
We need a hack to get bootloader 1.4 back on the phones.
Please help.
Thanks
My one now is a photo frame which one show "HTC" or "Windows Mobile",
at least your one is a PDA.
There are nothing in "info 2" and so nothing can be flash into it.
Is it possible to have something written CID and IMEI to phone in mtty
and let the flash rom success?
i am in the same situation like yhlee. Pof, i have reply your pm and ready to upload the result file to FTP. where should i upload to?
Thanks
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Thanks.
rnc1688 said:
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
Click to expand...
Click to collapse
This can be fixed by bootloader commands 'set 14 0' and 'task 8', will reboot your device and boot into OS again (but no GSM yet!)
yhlee said:
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Click to expand...
Click to collapse
Upload it to xda-developers ftp:
ftp://xdaupload:[email protected]/Uploads/Hermes/
USER: xdaupload
PASS: xda
POF, file have been uploaded, file name= rnc1688
Thanks
'set 14 0' and 'task 8' didn't work
@rnc1688: It starts the flashing process, but you get a "CID not allow (255)" error because your CID is corrupted and you are in bootloader 1.06.
Is not booting WM5 after "set 14 0" in mtty.exe? If it's not booting WM5 you'll not be able to flash bootloader 1.04 and bypass CID checking.
so i guess my unit is bricked now.
I've upload the file which named yhlee.txt.
However, I'm going to send the unit for service.
Hope they can fix.
Any way to make it show the bootloader screen on start-up
everytime?
"set 14 1" doesn't work after push the RESET button.
Thanks.
@yhlee: U're getting exactly the same error as rnc1688. Device in bootloader 1.06 which has corrupted CID, however you say you can go into OS, so it would be possible for you to downgrade the bootloader so it does not enforce CID checking.
yhlee said:
Any way to make it show the bootloader screen on start-up everytime? "set 14 1" doesn't work after push the RESET button.
Click to expand...
Click to collapse
Try "set 1e 1" and then "set 14 1", you'll boot stright into bootloader.
@rnc1688: If you want to go WM5 try this:
"set 1e 1" and then "set 14 0", you should be able to boot stright into OS.
no luck either
grrr!!!... command "set 14 [0|1]" is working fine in 1.04 here to switch boot into WM5 or boot in bootloader mode... probably different in 1.06??? I don't have a 1.06 now to test
Mine one is just showing "Windows Mobile" but stuck there,
but seems rnc1688 one is a PDA but my one is nothing.
I've sent to distributor for service.
Thanks you pof.
yhlee said:
I've sent to distributor for service.
Click to expand...
Click to collapse
Let me know when they fix it... i'm curious about if they will fix it with 1.06 or they will downgrade to 1.04 first.
I got a correct message back from the service company, and they will not fix a bootloader 1.06 unless the original rom has been release with it, I was told that is HTC policy on this.
Hi,
went to imei-check.co.uk and got my CID unlock key. IPL & SPL are still showing X.XX.0001
Is the device unlocked, or not?
Ghostzapper
My G4 Wiz still displays the versions as you show, and it's unlocked.
I guess my answer is: I dunno.
the xx.0001 is not an indication of CID locked or not. It is an indication of the version (i.e. G3 or G4) your Wizard is. There is no easy way to check your CID status, other than flashing it. However, from what I can see so far, it doesn't seems to be beneficial to flash it all (i.e. CID-unlock) when ShellTool can do a very good job in a CIDlocked Wizard.
ghostzapper said:
Is the device unlocked, or not?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=295038
Thx @ all
Will see into this.
I unlocked the phone and tried to install NBD 9. Update process stuck at 52%. Managed to reflash original Vodafone ROM. Have restored my Data via SPB Backup and will try again after trying the Wizard Support Tool.
Gonna keep you informed
Ghostzapper
The "CID actions" includes a report on the CID lock status .. good luck!
There is an easy way to check if the device is CID unlocked:
Kill active sync (taskmanager kill wcescomm.exe)
Start wizard in bootloader (reset and hold voicedail butten untill red/green/blue window)
Open mtty.exe
select connection \\.\WCEUSBSH001 and press ok
in the new window type:
set 32 2
and press enter.
then the following will appear:
Code:
Cmd>set 32 2
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x3C8C0000 Bytes
g_cKeyCardSecurityLevel = 0
HTCE
Cmd>
The g_cKeyCardSecurityLevel is the key!
if it is set 0 then the device is CID unlocked, else its locked.
Best regards,
EquinoXe
This is great information.
Possible to get a sticky or to add to the wiki?
Cheers!
Huckleberry88 said:
This is great information.
Possible to get a sticky or to add to the wiki?
Cheers!
Click to expand...
Click to collapse
haha no one's stopping you from adding it
Hi,
the-equinoxe said:
Open mtty.exe
Click to expand...
Click to collapse
where the heck can i download mtty.exe? Typed my fingers bleedy last night...
Ghostzapper
Got it.
Huckleberry88 said:
http://forum.xda-developers.com/showthread.php?t=295038
Click to expand...
Click to collapse
Thx.
The Tool tells me, that the device is CID unlocked although it fails to recognize the model as a wizard.
Since i have already installed the ShellTool Version of NBD 9, i will not bother going further into detail unless someone gives me a good reason to flash another rom. Ist there?
Ghostzapper
ghostzapper said:
Hi,
where the heck can i download mtty.exe? Typed my fingers bleedy last night...
Ghostzapper
Click to expand...
Click to collapse
It's on the FTP and also:
http://files.pdamobiz.com/ROMs/XDA/mtty1.42.rar
Best regards,
EqX
Thx a lot
Keep up the good work.
Ghostzapper
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!
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
help me please bro,, i want hacked my htc hd 2 and first i flash with hspl in this
and susscessed,,
and next my step is flashing stock room and i download in this
Code:
4shared.com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html
i download stock rom LEO 2.10 next my htc hd2 updating sudenly htc hd2 restart before finished update the screen after restart is triangle look like this pic
and i tried another stock rom but the screen like this
and im waiting but the loading never finished
this my tricolor
SPL 2.08 before i flash stock rom my spl 1.42
anything idea how to fix my htc hd2 problem ???
thanks for your help
The problem is with the spl. In order to flash roms that are not for your device you need hspl. Your spl is only 2.08.0000, you need to change this to 2.08.hspl.
ClydeB1 said:
The problem is with the spl. In order to flash roms that are not for your device you need hspl. Your spl is only 2.08.0000, you need to change this to 2.08.hspl.
Click to expand...
Click to collapse
you mean i must download this file bro ?
Code:
forum.xda-developers.com/attachment.php?attachmentid=297541&d=1269287146
how i can change 2.08 hspl where my htc hd 2 can't connect with activesync ??
thanks for ur help bro
****thefuckerz said:
you mean i must download this file bro ?
Code:
forum.xda-developers.com/attachment.php?attachmentid=297541&d=1269287146
how i can change 2.08 hspl where my htc hd 2 can't connect with activesync ??
thanks for ur help bro
Click to expand...
Click to collapse
No need for ActiveSync. Put phone in bootloader (tri-colour), connect to pc and when device shows usb in the bootm section of the screen run the hspl app again. Choose 2.08.hspl and all will be fine.
****thefuckerz said:
you mean i must download this file bro ?
Code:
forum.xda-developers.com/attachment.php?attachmentid=297541&d=1269287146
how i can change 2.08 hspl where my htc hd 2 can't connect with activesync ??
thanks for ur help bro
Click to expand...
Click to collapse
thats correct
you must go into bootloader mode, start the the tool and then u can install it(push and hold volume down+turn on the phone)
ClydeB1 said:
No need for ActiveSync. Put phone in bootloader (tri-colour), connect to pc and when device shows usb in the bootm section of the screen run the hspl app again. Choose 2.08.hspl and all will be fine.
Click to expand...
Click to collapse
ok i'll try bro thanks again for ur help...u have yahoo id bro?
****thefuckerz said:
ok i'll try bro thanks again for ur help...u have yahoo id bro?
Click to expand...
Click to collapse
Pleasure m8. No I don't. You can PM me though if you have more questions.
ClydeB1 said:
No need for ActiveSync. Put phone in bootloader (tri-colour), connect to pc and when device shows usb in the bootm section of the screen run the hspl app again. Choose 2.08.hspl and all will be fine.
Click to expand...
Click to collapse
Thanks bro,,sucessfuly
what should i do now to hacked my htc hd 2 bro ?
****thefuckerz said:
Thanks bro,,sucessfuly
what should i do now to hacked my htc hd 2 bro ?
Click to expand...
Click to collapse
Load spl 2.08.hspl by running the hspl2 tool. Once that is successful (check in bootloader again to see that it has successfully installed) then you can flash to the rom of your choice.
hi pls help
hi i have same problem i did everything but for me it didnt work why i saw it worked for that guy pls help
loonyozzy said:
hi i have same problem i did everything but for me it didnt work why i saw it worked for that guy pls help
Click to expand...
Click to collapse
Enter bootloader and supply all of the info you see there.
Actually you can't do much wrong. just connect the to your pc and then use the brilliant hspl2 to hack your spl on the phone, and then you can reflash the rom....
I have had same symptoms, tried everything... then....
Finally I have noticed that I can't flash through USB because on my micro-sd card I have placed LEOIMG.nbh which caused HSPL error 0028002
Before you flash remove micro-sd.
I hope my experience will help.
SAME problem no resolution
HI I have same problem Screen with exclamation mark then boot screen with gour colours showing this
HX-BC
SPL-1.42.0000 XE.
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
So I've tried to install HSPL 1.42 With no card inside but during installation i get.
Download http://forum.xda-developers.com/attachment.php?attachmentid=297541&d=1269287146
1. Remove micro SD card.
2. Reboot phone while holding volume down.
3. Connect to the PC via USB.
4. Run HSPL2_RUN.exe and follow the steps on your screen
Same problem
Hi, I have also this problem. I tried to install the stock rom but during it an error occured and it stopped before finished. Then there is the triangle and "software update failed". My spl says that I have the version 3. and something and also when I try to run the hspl.exe an error occurs that says that a file RAPi.dll cannot be found and then it waits for usb connection and finaly an error occurs "cannot connect".
Please could someone help me ? WHat am I doing wrong ? Or what should I do ?
thanks