request for help with Kaiser (after using search and trying fixes) - Tilt, TyTN II, MDA Vario III General

Device: HTC TyTN II
Bootloader: KAIS130
SPL-3.28.0000
CPLD-8
ROM: RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship
Problem: I tried to sync the device with my desktop (running XP Media Center edition sp3) using ActiveSync 4.5 like I normally do. However, this time the device wouldn't sync and it would just hang. I unplugged the device from USB so that I could try again. The phone immediately went into bootloader. It is currently stuck in this mode.
Steps taken:
First I called HTC tech support hotline. The rep walked me through several steps, but nothing fixed the problem. We tried soft resetting, holding down the power + camera buttons and then soft resetting, hard resetting: nothing worked. He then stated that the device's ROM probably got erased when I unplugged it from USB. He instructed me to download the official 6.1 ROM from HTCs website and then try to re-flash the phone.
I tried doing this, but I still cannot get the ROM onto the device. In bootloader, I plug the device into USB and I get an error message that the device is not recognized. I soft reset the phone and then run the RUU and it begins to flash the device. After 10 minutes, I get a message saying that the flash was successful but the phone just resets back to bootloader.
After searching through the forum and wiki, I am still at a loss as to how to proceed without instruction from an expert. I think I read something about using mtty, but I am afraid to do so on the Kaiser because I read that typing the wrong instructions could be disastrous.
I humbly request any kind Kaiser experts to help me with my problem! Thanks

sir topas said:
Device: HTC TyTN II
Bootloader: KAIS130
SPL-3.28.0000
CPLD-8
ROM: RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship
Problem: I tried to sync the device with my desktop (running XP Media Center edition sp3) using ActiveSync 4.5 like I normally do. However, this time the device wouldn't sync and it would just hang. I unplugged the device from USB so that I could try again. The phone immediately went into bootloader. It is currently stuck in this mode.
Steps taken:
First I called HTC tech support hotline. The rep walked me through several steps, but nothing fixed the problem. We tried soft resetting, holding down the power + camera buttons and then soft resetting, hard resetting: nothing worked. He then stated that the device's ROM probably got erased when I unplugged it from USB. He instructed me to download the official 6.1 ROM from HTCs website and then try to re-flash the phone.
I tried doing this, but I still cannot get the ROM onto the device. In bootloader, I plug the device into USB and I get an error message that the device is not recognized. I soft reset the phone and then run the RUU and it begins to flash the device. After 10 minutes, I get a message saying that the flash was successful but the phone just resets back to bootloader.
After searching through the forum and wiki, I am still at a loss as to how to proceed without instruction from an expert. I think I read something about using mtty, but I am afraid to do so on the Kaiser because I read that typing the wrong instructions could be disastrous.
I humbly request any kind Kaiser experts to help me with my problem! Thanks
Click to expand...
Click to collapse
I suggest getting in touch with the moderator named GSLEON3. He is probably going to be your best bet of getting back up and running. Good Luck

Ok, I can't get in touch with GSLEON3 (I'm sure he's extremely busy) and I don't want to pester him so if anyone else out there can help, I certainly appreciate it. Here is my theory for the solution based on further reading of these forums (but since I have no technical training I don't know if I am even on the right track). I'd appreciate if anyone with the proper knowledge can confirm or reject this course of action:
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
(taken from http://forum.xda-developers.com/showthread.php?t=394543&highlight=stuck+bootloader)
redbandana cautions that one must use HardSPL or risk bricking the device. However, in the post about SPL Questions it states:
"Well, at the moment this is where we are at. We are still investigating the full effects of what an SPL can do to vary the performance of an OS. For now there is a large consensus that the newer HTC 6.1 ROM SPL seems to work well for most of the newer 6.1 ROMS (stock and cooked)."
So my question is, will the stock SPL that came with the official HTC 6.1 ROM be ok to use mtty, or do I need to flash the old HardSPL?
I appreciate any advice on how to proceed, especially if I am totally wrong about how to fix this. Thanks!

sir topas said:
Ok, I can't get in touch with GSLEON3 (I'm sure he's extremely busy) and I don't want to pester him so if anyone else out there can help, I certainly appreciate it. Here is my theory for the solution based on further reading of these forums (but since I have no technical training I don't know if I am even on the right track). I'd appreciate if anyone with the proper knowledge can confirm or reject this course of action:
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
(taken from http://forum.xda-developers.com/showthread.php?t=394543&highlight=stuck+bootloader)
redbandana cautions that one must use HardSPL or risk bricking the device. However, in the post about SPL Questions it states:
"Well, at the moment this is where we are at. We are still investigating the full effects of what an SPL can do to vary the performance of an OS. For now there is a large consensus that the newer HTC 6.1 ROM SPL seems to work well for most of the newer 6.1 ROMS (stock and cooked)."
So my question is, will the stock SPL that came with the official HTC 6.1 ROM be ok to use mtty, or do I need to flash the old HardSPL?
I appreciate any advice on how to proceed, especially if I am totally wrong about how to fix this. Thanks!
Click to expand...
Click to collapse
mtty is not a toy and there are some risks of bricking involved. Anyhow, it is a tool that is used for situations similar to yours. Follow the steps that are provided. Step 3 may be different for different pc's, so just look for port 1. After you run mtty, install a version of hard spl. If you plan on installing a 6.1 rom, install a spl that is compatible with it such as, 3.28hard, 3.29, or the new 3.56. I'll be around for an hour feel free to pm me.

Sorry mate, usually takes me a day to catch up with my PM's, etc...
I can't say for sure on the 3.28 SPL as I have not disassembled it. Well, technically I did, just to prove a point that it was the same as 3.29, but I didn't document any of the commands.
The 3.28 HardSPL is NOT an MFG spl, so it definitely WON'T support some functions. I don't know what all the fuss is about SPL's. I use my own customized version, based of course on Jocky's work, but it's still a 1.1 SPL version & I never have any trouble.
For the 3.28 & .29 SPL's, I do know that if you are stuck because of an RUUNBH error, the correct sequence is:
cmd>set 16 0
cmd>task 8
Task 8 is not "format", I don't know where you got that & task 0 will freeze out MTTY.
Have you done an info 8 command?
cmd>info 8
That will tell you more about the issue.
BUT MOST IMPORTANTLY, only connect mtty to USB, not to port. You can mess other things up like external drives, etc. Ports are only when connecting to OEMSBL/Radio Boot Loader.

BTW, a screwed up USB port pin or block can cause this issue as well. Take a look at the pin block, is it perfectly straight?

Ok, here's the weird thing. I was going to try the mtty to do info 8 command, and I powered on the device (it had the SIM card and microSD card removed.) The device started up and performed a hard reset, and then loaded up! It had a ROM on it! Not the original factory ROM that was loaded (which had TomTom preloaded) but the factory ROM I downloaded from the HTC e-club that I tried to flash. I thought my issue was solved, so I put in the SIM card. However, when I turned on the device (with SIM card in) I get the bootloader screen. What the heck is going on?

GSLEON3 said:
BTW, a screwed up USB port pin or block can cause this issue as well. Take a look at the pin block, is it perfectly straight?
Click to expand...
Click to collapse
Yes, it is straight.

Hi everyone,
Thanks for trying to help me. It's all a bit too confusing for me so I just decided to bite the bullet and send it into HTC. Thanks again!

Related

My turn to brick it...

Hi All
Owning a Vario III and using Hardspl I upgraded to the latest incarnation of HTC's ROM (WM6.1). Having been caughtout with the freezing issue and after reading some posts about removing Hardspl I began to do so.
After reading the Idiots guide which stated :
'2. Flash the OEM ROM to your device (this will restore your OS but not the bootloader, we'll get to that below)'
I couldnt locate a proper T-mobile Wm6.0 ROM so thought as I'm just getting rid of the Hardspl I'd use the standard HTC ROM WM6.0 which went on fine.
This allowed to rid my phone of the HARDSPL.
I was then getting the Vender ID error when trying to load the new WM6.1 HTC ROM (which of course I would get as HARDSPL had been removed).
I then thought sod it and Ran SSPL-KAIS.exe and then began to run the latest HTC ROM. It started fine but bombed out at 15% and then I was left with a Tri-color screen and the message below :
In the Upper right hand corner it says RUUNBH
On the left side a little lower it says
KAIS1*0
SPL-1.56.0000
CPLD-8
At the bottom of the screen if I have USB plugged in it says USB, if nothing is plugged in it says Serial.
I cant seem to run MTTY 1.16 or 1.42 as I'm using Vista and the processes are slightly different (though I stopped what I thought were the relating ones to no affect)
Anyone on this awesome forum got any bright ideas as to how I can resurrect this one ?
btw : if I/we do manage to fix this one, do you think it will be possible to a) have a copy of the OEM T-mobile ROM ?? b) still upgrade to latest Wm6.1 ROM without the need for Hardspl ??
Cheers all
Steve
RUUNBH errors are from incomplete flag clearing after a flash. All that is needed is MTTY, 1.42 is best, & a few commands.
The first command is:
cmd>set 16 0
The second based on what SPL you now have (1.56) is:
cmd>boot
For use with Vista, you'll need to follow the dirsections used to flash via vista, & roll back the USB drivers. Do a search for Flashing with mtty and vista in google.
FANTASTIC !!!
Many many thanks for your prompt help !. Magic.
Im back up and running thanks to you brilliant help .
Do you think its worth trying again to Flash the phone using SSPL-KAIS and the latest HTC ROM ? or do u think I should quit whilst I'm back up and running ?
Alternatively, is there a way for me to sidestep the T-mobile lock without using HardSPL ?
Apologies for the questions, but after reading the many many posts on this, my brain is deffo boggled !!
Big thanks
Steve

I can't tell if I have successfully Hard SPL'ed

Hi
I am having some problems when trying to upgrade my Orange SPV M700 to Hard SPL. I have followed the instructions given in "TrinityGuides.info" but I am not convinced the Hard SPL has actually worked okay. This is what happens:
1) I follow the initial instructions (run ROMUpdateUtility.exe) and click on the various screens ("I understand" "I completed") etc
2) I get to the point where the screen says "You are now ready to update your ROM image. This operation takes approximately 10 minutes"
3) I then click on "Next", the progress bar screen appears and I get the message on my SPV about running programs - I select 'yes' on the SPV.
4) Immediately I hear the Windows XP 'dum-dum' noise letting me know that a USB device has been disconnected. Also my ActiveSync is gone. I have not done anything to cause this though - the connection just goes down.
5) I then get a message telling me that the device is not connected and I have to exit the Hard SPL routine.
6) After reading the FAQs on TrinityGuides.info I re-run the "ROMUpdateUtility.exe" and get to the progress bar screen again. This time I see the grey screen on the SPV, with progress bar rapidly completing on both the SPV and my Desktop screen progress bar.
7) After literally a few seconds I get a screen telling me "Congratulations! Your ROM update is now complete etc"
Even though I see the congratulations message I am not convinced it has successfully installed Hard SPL.
Firstly, whereas the messages suggest it can take up to ten minutes to do the Hard SPL mine only takes a few seconds. Secondly, when I follow the TrinityGuides.info instructions on how to check the Hard SPL (by pressing power, camera and soft reset) I see this:
On my tri-colour screen this is displayed:
IPL-0.50
SPL 1.07.0000
The "TrinityGuides.info" instructions say that I should see this:
TRIN100
IPL-0.50 (your device may show IPL-1.00)
TRIN100 MFG
SPL-1.20.Olipro
I have tried both the "Hard SPL 1.20.Olipro" and "Des' Crash-Proof SPL" but nothing makes any difference to the display I see.
Can anyone help me? I am concerned that if I don't have the Hard SPL correctly installed I am going to risk bricking my SPV if I try upgrading the ROM, unlocking the SIM etc (which is what I want to do). Is there any other way I can tell whether Hard SPL is installed correctly?
Thanks in anticipation!
Spivvy
If i remember correctly hard SPL is a quick process, it's the ROM flashing that takes ten minutes or so. As to why it's not working i can't offer any help, sorry.
Hi DeeDee
Thanks for taking the time to reply. If, as you say, the Hard SPL does happen very quickly (in my case it seems a second or so) then that's good to hear as I was sure something had gone wrong.
Does anyone know if what I see on my tri-colour screen is correct? (i.e. IPL-0.50, SPL 1.07.0000) as before I proceed with any more drastic updates I'd like to make sure my SPV is protected against bricking.
Thanks again
Spivvy
UPDATE.....
I spotted this person's solution to what seemed to be a similar problem to mine:
http://forum.xda-developers.com/showthread.php?t=382246&highlight=ActiveSync+disconnects
I decided to try his fix. I used Olipro 1.20 Hard SPL.
The Hard SPL procedure did continue in a more convincing manner than my previous attempts, and the progress bar took a bit longer to complete, and I also received a message telling me that the operation was successful. I then did a soft reset and felt that maybe this time it had worked.
In a rare moment of feverish optimism I pressed the buttons to check the SPL version now on my Orange SPV (power, camera and soft reset). However, it is still telling me this:
IPL-0.50
SPL 1.07.0000
i.e. nothing seems to have changed. No sign of Olipro's SPL again.
In a word, I am flummoxed.
In two words, I am very flummoxed.
So, I am still putting out an appeal to you clever bods as to how I establish if I have a safe Hard SPL on my Orange SPV, or is it still looking a bit iffy (a technical term for "not very good")
Thanks
Spivvy
i am seeing the latter version with OliPro SPL, OK it's v1.2 but it's still different from yours.
Are you trying this on Vista or XP, personally i have always used XP for flashing. Whether that's going to make any difference i don't know.
I have a question along similar lines, although not identical. I'm completely unable to get from the triband screen to the bootloader screen. I'm trying to flash from my mini-SD card, but one it gets into that SSPL triband screen, it doesn't do a thing. I'm running vista on my PC, and can't seem to get any useful action trying to flash from there. Getting a little frustrated, cause I haven't even been able to SIM unlock my phone so far... Considering going the IMEI route, although that won't do anything for bootloader and upgrapding ROM later on... Any advice, or should I just use IMEI and go the easy way?
Dan
Hi DeeDee
I am using Windows XP, which I think is the preferred OS for this type of operation. Very puzzling.
Thanks
Spivvy
Hmmmm.....
It's looking like I am not going to resolve this problem as no one has posted an actual solution. I am not sure what to do now - my gut feeling is that my SPV M700 has not been Hard SPLed (based on what it displays as described earlier).
All I know is that I have followed the TrinityGuides instructions (and other postings with information about this type of thing) accurately. I have done it several times (using both Olipro 1.2 and Des Crash Proof) - but, for some inexplicable reason, my SPV M700 would appear to refuse to accept the Hard SPL.
As no one has said otherwise I have to assume that the tri-colour screen information I see in bootloader mode does mean that I have not successfully SPLed?
I can't understand why some (in fact most) people seem to get the Hard SPL flashing performed okay and yet mine refuses. I know from searching the postings that there are a few unlucky souls like me who have not been able to do it successfully.
If anyone does have any suggestions I really would be grateful to hear them, but for now it looks like I have drawn a blank. Pity.
I have run out of ideas - could it be some other program I have installed is interferring with the process? Is it my version of ActiveSync (4.5.0)? Is it some setting I have got on the SPV M700 that is preventing the Hard SPL? There surely has to be a reason why the Hard SPL is not working?
Still hanging on, hoping that some shaft of light might shine on my SPV M700 one day...
Ho hum...
Spivvy
Hey u are not alone, my Trinity ( Dopod D810 variant ) just simply refuses to flash to any hard spl as well, same problem as yours, i am using windows xp to flash so i doubt its the driver problem.
I found a solution to this problem though, i use SSPL to flash cooked rom to my device.
http://forum.xda-developers.com/showthread.php?t=293632
Just paste the .exe onto your trinity and open it using file explorer, it should enter bootloader with a "by des" behind the bootloader number, it should be safe to flash then.
I tested flashing WM 6.5 by savesaint, Finix's 6.1 with no problem
ADDons: Anyway the reason i suspect is because my one has been flashed with HTC P3600 rom, yes, by HTC without dopod branding, hence the problem
Hi there - thanks for that tip. I will try that link you suggested, and have a go with the file. I'll get back to let you know how it all went.
Many thanks for taking the time to post your suggestion.
Cheers
Spivvy
Hi
I thought I would report back as to the progress (or lack of it) regarding the failure to Hard SPL my Orange SPV-M700. There's not much to report I'm afraid, which may be largely to do with my lack of confidence etc.
I checked out the link suggested above by "/b/-TarD" (using SSPL to flash cooked rom to device - as described at:
http://forum.xda-developers.com/showthread.php?t=293632
However, when I read the various posts and experiences I still felt that this might not be the solution I was looking for. I am not very technical with all this ROM flashing but the original Hard SPL method seemed to me to give me some insurance against bricking my SPV-M700. This SSPL does not seem to leave you with a Hard SPLed device (I am not exactly sure what it does to be honest), and in fact some people seem to have had quite difficult problems after using it.
Call me a cowardly old geezer but I have backed away from trying the suggested solution at the moment (but still very grateful to user "/b/-TarD" for his suggestion).
My aim was to:
1) Get the basic HARD SPL on my SPV-M700 - Olipro or Des, but having followed all the Trinity guides faithfully, it would appear that my device doesn't wanna play ball with me — very frustrating.
2) Re-instate/upgrade the GPS radio thingy (which I believe you lose after you Hard SPL)
3) Unlock my Orange SPV-M700 so that I can use any SIM card in it
4) Then, finally, consider upgrading the ROM to one of the newer WM6 versions, or a better WM5 version.
But, at the moment, it would seem that it's not to be.
Ho hum....

Major Help PLease!!

Hi, Am New Here
I just wanna ask something about my O2 xda IIs, i had found out recently that my phone became soo slow.. even my SMS cant even appear.. soo i tried to let my brother fix it..
He tried to fix it with looking for softwares.. he was able to do soo what he call reformting my phone.. but in the end the Phone just stuck up in the Windows Logo.. please help me abou this problem..
My phone Specs
HTC O2 xda IIs
R 1.02.00
G 1337.32
D (i dont know what the version)
Phone Specs After my bro cooked it..
R 1.02.00
G 1337.32
D 5M6.5.1
Can you give me details about installing, upgrading
i think my bro can fix this.. can please give me the details? and softwares needed for my phone to able to operate again
THNX
welcome to the forum!
what your brother did was, flashing another rom. d-two's wm6.5.1 actually.
the fact that the device is stuck in the boot logo now can mean 2 different things, one is good and one is rather bad:
the good one is: he forgot to hard reset the device.
to perform a hard reset please go to -=this site=- and have a look how it's done. after flashing a device, a hard reset is necessary to clean up all the old crap, that is left from the rom before, like the registry and the contents of the storage drive.
the bad on would be: he screwed something up during the flashing
if the first method didn't get you anywhere and you are still stuck in that splash screen, you should look for "stuck in splash screen" or "stuck in bootloader" or "format blueangel mtty"
what that means is: the rom did not flash correctly and with a device with a broken rom, you don't want to start flashing again. so you need mtty to format the device before it should be flashed again.
my personal guess would be no. 1
with best regards
Chef_Tony
Dear Chef_Tony
Thanks for the quick reply.. your correct that the 1st one is only the problem that am not stuck at the bootloader but still... Even though am still stuck at the screen logo after try other roms... can you give me good ROMs that i could use?
I get the ROMs on this thread
http://forum.xda-developers.com/showthread.php?t=428030
i tried those ROMs but still no good i followed the instruction very well.. But still no progress can you still help me ??
By the way whats "mtty" can i use the second method that you give me can you tell me the instruction that i should follow
thnkx and more Power!!
i would, of course, recommed d-two's wm6.5.1 build 23071, which will be released tonight.
if the problem persists with other roms, you are stuck in splash screen and you need to take the mtty method. that is a little complicated, and i have never done it before, therefore, i cannot take responsibility, i just looked for what worked for other people (which is what i meant by search for those terms, it would have lead you to the solution, but here you have your own copy of the solution)
1. Download mtty v1.42 from http://files.pdamobiz.com/ROMs/XDA/mtty1.42.rar
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.
good luck.

ba update

Hy!
I have a ba with broken power button. The button has rend a pace of motherbord. How can i update my rom without this? Can i turn on the bootloader mod by shoftware? How can i repair it?
(i can't speak eglish, but i try it! )
thx!
hi and welcome to the forum!
there are several things that come to mind:
1. in my signature there is a link to the htc blueangel service manual that can help you fix your power button, because sooner or later, you might need it.
2. assuming that you already use a wm5 or higher rom, before attempting to upgrade you can try a dry run and try to put the device into bootloader mode by running enterbl.exe on the device (it comes with every RUU), then without upgrading you perform a soft reset to restart it and then try a hard reset with only reset+camera+record and see if the menu shows up. then you are good to go.
3. if you are running wm2003, you should check, whether your rom is already WWE, you might be able to upgrade without putting the device into bootloader mode before beginning.
please post back if any of that worked. if not, i still have an idea involving mtty, but i would have to look it up first and maybe it is not necessary.

[Q] This is depressing, stuck on SPL [email protected]! Trying to flash to a HSPL ROM

Hey guys,
New to this whole world of flashing devices and have been browsing for days trying to learn and understand all the different terms associated, so please forgive me if i say something that doesn't make any sense
Trying to upgrade my HTC Touch HD (Blackstone), Rom version: 1.14 WWE (put my phone into bootloader and the SPL is 1.14), was trying to update my phone which is when i came across cooking roms and updating them via flashing, have read Digital Outcast's Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL], decided i wanted to follow the HSPL which is when i came across
http://forum.xda-developers.com/showthread.php?t=671277
and wanted to install the 'blackSTONEhenge HyPer MaxSense' Rom, said i needed RADIO ROM version 1.14 or above, my stock standard HTC has RADIO Version 1.09, which meant i had to try and flash my devices radio rom.
What im not sure is this HSPL, i dont fully understand if im supposed to try and get/put HSPL on my phone before i do any flashing/ im not sure if HSPL is the 'thing' that allows flashing to become capable...
If someone could help me out as i have been browsing the forums for a few days and its driving me nuts as usually i would have worked it out by now!
Cheers,
Scott
Go to this link
http://forum.xda-developers.com/showthread.php?t=505377
dont get confused
1.just download "HSPLWrapper_Blackstone_156OliNex.zip" from "Attached files".
and unzip in a empty folder.
2.connect your phoneto pc via active sync.
3.run HSPLWrapper_Blackstone_156OliNex.exe, click yes/next/ok(sorry dont remember what was it, you phone will restart in bootloader (three color screen and hspl will be done automatically.
thats it.
now flash any radio or rom of ur choice.
nice explanation, just let me add some newbie information:
basically, what you are facing, is flashing three things:
1. you flash hspl, which means that your device will be unlocked for roms of all carriers and all countries, and you will be permanently ready to switch roms any time you want, as it remains in your phone, whatever you do (hard reset, flashing a stock rom, whatever).
2. the radio rom, the radio is the bridge between the windows mobile operating system and the hardware. this is responsible for the fact, that for example switching on wi-fi is done with the same button on any device, independent from which wi-fi card is actually installed. it controls wi-fi, gsm, 3.5G communications, bluetooth, camera and sound input and output. the latest radio for the blackstone is 1.17 (.25.09 i believe). it offers the best quality in all beforementioned services, but drains slightly more power than previous versions, due to higher performance.
as there is actually yet another stepping stone between the OS and the radio, rilphone.dll, it is advised to use a new radio with the cooked roms offered here. most chefs integrate a new rilphone.dll in their roms and they work best with the corresponding radio rom.
3. in the end, you will flash the actual OS rom that changes your operating system, possibly the language, the manila version and everything else. just like formatting your windows xp pc and installing windows 7, your apps, settings and personal information (in this case contacts, appointments, sms...) will be gone.
for it to work, you must flash hspl first, or your device will be unable to accept actual roms, and then proceed with the radio, and before flashing the actual OS rom (in your case blackstonehenge), you should perform a task 29, either you can flash it (see task 29 thread), or use mtty or use advanced ruu, which has an extra option to do it.
this was just a basic introduction to make it easier for you, to understand, what you are actually doing, when attempting to flash, the rest and all the steps to take are in the tutorials, i just find it easier to do, when you actually know, why you do certain steps, helps you remember for the next time.
regards
Chef_Tony
Ok thanks guys for the responses, and especially chef_tony's, cheers.
P.s. Sorry for the complicated response below, its hell to read
I have tried to follow:
Dummies guide: flashing 1.56+ roms [v 2.0] - [HSPL][USPL]
http://forum.xda-developers.com/showthread.php?t=505377
And it hasn't worked, when I follow the HSPL steps I get to step (HSPL2c) and it just sits on 0% and give an Error [262] code (this is the section where we try to flash Blackstone_156OliNex to the device.
The tutorial says: run HSPLWrapper_Blackstone_156OliNex.exe, which then tells us to establish an activesync connection, which i think means we have to get the bootloader mode to USB, in order to get the bootloader to USB Mode I have to connect my phone to the pc before running the HSPLWrapper_Blackstone_156OliNex.exe and leaving it connected to the pc to A) establish the activesync connection(Windows device centre doesn't register the phone as connected whilst in bootloader) then B) get the bootloader mode the USB.
So what i have done:
So the phone is connected to the pc, activesync registers the phone(leaving the phone connected i then),
place it into bootloader (shows USB Mode)
Then run HSPLWrapper_Blackstone_156OliNex.exe (i run it as an administrator)
the program tells me to establish an activesync connection (Windows device centre doesn't register the phone while its in bootloader, which dummies guide tells us to do), i dont know how to establish an activesync connection whilst the phone is in bootloader, so anyway i hit next, next and just click update the rom, and it just sits at 0% and give an Error [262]
Im not sure if the reason for this error is because i haven't put HSPL on the device, im still not 100% sure about the whole HSPL, i think all i have to do for this is run the HSPLWrapper_Blackstone_156OliNex.exe ?? then is the HSPL issue sorted?
Thanks again guys,
Scott
Dis-regard this post
easy thing. i had the same issue when attempting to install hspl for the first time. as described in the tutorial post you mentioned, i went to the part troubleshooting:
Troubleshooting - manual SSPL
- Boot up your phone.
- Copy SSPL-Manual-TouchHD.exe to your phone. In a file browser on your phone browse to where you copied SSPL-Manual-TouchHD.exe and run it.
- Your phone will reboot into its bootloader and should show SPL v 1.07.OliNex.
- When it shows USB at the bottom then run HSPLWrapper_blackstone_156OilNex.exe from your computer again.
- Go to step HSPL3 if successful.
with this extra step it worked for me, because installing sspl directly on your phone, it prevents 262 connection errors and unlocks the device temporarily which makes it easier to install hspl.
Thanks again chef,
ok i connected my phone, then copied the SSPL-Manual-TouchHD.exe to my device, run it and it loads into bootloader, shows spl 1.07OilNex, doesn't show USB no matter how long i wait, i unplug it and don't get serial mode either
Tried re connecting it and still no USB or serial mode comes up :\
I had tried following the troubleshooting tutorial before i posted on here for help
Should i try running the HSPLWrapper_blackstone_156OilNex.exe without USB mode showing?
and really appreciate all the help,
Scott
Following with interest
Tony and Scot enjoying the posts and hoping to pick up a few pearls of wisdom before upgrading. I have played around with my Touch HD and had it dual booting with android from SD card. For some reason I can no longer use my camera in wm 6.1.
I can not find camera.exe cab and was considering upgrading to wm 6.5 to see if that solves the problem.
Billy, im just stabbing at the dark here, but im guessing if you do flash your device to wm 6.5, during the installation of the upgrade, you're .exe for the camera will be re installed and should work again. Gdluck
Upgrading to wm 6.5
Probably right Scotty, I just want to make sure I don't brick the phone for the sake of getting my camera to work again. Have you managed to complete the upgrade?
Haven't yet, just waiting for some words of wisdom from tony
I also had Error [262] when tried to apply HSPL last week.
But, I applied USPL path to install HSPL!
So I entered USPL and started HSPL install.
Then process finished without any problems.
And it's working excellent... now on the 3rd ROM since appliing HSPL...
good idea, the most important thing is to get a stable connection for the bootloader, and if uspl makes it easier to install hspl, i would definitely give it a try. as posted before, depending on your soft branding, first installing hspl can be a hassle, however, once it's done, you never have to deal with it again (which is also, why many long term blackstone users including myself hardly remember, how to go about changing the spl).
also, since you mentioned that in sspl, you didn't see serial or usb in bootloader mode, make sure that your connection is actually stable. in bootloader mode, windows needs another driver for the device from what is used to sync the device (when it is switched on). especially, when using windows vista or windows 7, you should have a look at the thread "[tut] dummies guide: updating htc sync drivers".
especially on windows 7 x64 it can be quite a lot of work to get it running, because these drivers are not digitally signed, so you'd have to sign them yourself, which requires permanent test mode and comes with a watermark on your desktop, which, in turns, can be removed again. in that case, i would advise you to try a windows xp pc first to get your device up and running and you can deal with this later.
so, in short form:
1. in case you use windows vista or 7 and haven't dealt with the driver yet, have a look at the link to the tutorial or use a windows xp pc with activesync installed.
2. if you are positive that drivers cannot be the issue, or you successfully updated them, step forward and try the "uspl to install hspl" method, bodisson suggested.
CRACKED IT! dont have time to type how but ill post what happened once i wake up, thanks for all the help guys, you guys are legends!
Many thanks to Chef_Tony for his help in this matter. You've a lot of mod like qualities mate
Scottygrot, I'm glad you got it sorted in the end.
I'm closing this thread now. In future please post all flashing issues in Dummies Guide thread
Ta
Rick

Categories

Resources