Related
Hi guys!
I have a couple of questions.
Last week I performed WM2003SE to WM2005 upgrade on my BA. It comes from German T-Mob. I bought it second hand, so I guess that the ROM I found on it was loaded some way along the road (it was WWE, and my device has a German QWERTZ keyboard layout, meaning it originally had to come with some non-WWE ROM..right?)
When I bought it, it had O2 ìsoftwareî (thatís called extended ROM, right?) v1.31, Radio v1.06 and Protocol 1337.45.
I had some problems installing newest WM2003SE as I was getting error about wrong CID when running .exe update file, so I went for Helmiís 2005 pack. Later I realized I should just rename .exe to .zip and extract needed files from WM2003 .exe updates. I used BaUpgradeUt (of course failed due to the wrong CID) and MaUpgradeUt_noID.
Firstly I upgraded to Helmiís WM2005 (v5.04.09 WWE), but after finished upgrade I started getting some errors for some missing or corrupt executable files after device starts up (see the screenshots), which disappeared when I reinstalled 2005 (reinstalling it for the second time I got those 3 check boxes on a boot loader screen, which I didnít see when doing the installation for the first time..that could be the source of my problems after the first installation). Someway along those actions I also cleared my storage (with a tool provided in Helmiís ROM, that has a red recycle icon). After deleting storage items, I found many apps found on original Helmiís ROM missing (good..I didnít need those
Then I decided to update my radio from 1.05 to 1.16 and it went ok, after I managed to connect the device in boot loader mode to USB cradle.
- Now, I find it rather strange to have that color-striped boot loader screen still appearing when I boot my device. Shouldnít it be replaced with some WM default or ROM assigned bitmap?
- I used GetDeviceData to determine the exact data of my BA and prior to upgrade it gave me something like this:
PH20B WWE some_letter T-MOB102 followed by ROM and Radio version.
After the ROM update (2003SE to 2005) I got this as a result:
PH20B WWE A T%CID? 5.04.09. 1.06.00 % 4
Then I upgraded Radio...
PH20B WWE A T%CID? 5.04.09. 1.15.00 % 4
As you can see, T-MOB102 part disappeared and itís replaced with an unknown CID part. I guess thatís why I still see the boot loader colorful stripes when booting/soft resetting my device. Is it a big problem, as the device works fine? Is it a normal occurrence after using MaUpgradeUt_noID?
- That ìProtocolî version/number (1337.45 in my case)..can that be updated and what is it?
- After the upgrade I noticed that my phone is not recognized as a PPC any more, but as a computer instead. The problem is that now it offers less services over bluetooth (only Active Sync on Mac and Network Access Point on Windows). On Windows computer, I cannot send any files through btooth OBEX and itís very annoying. Is that a problem with bluetooth and WM2005 on these devices one could read about on forums? Any way to fix it? I must say that I havenít installed the newest bluetooth stack (how can I check what stack version do I have now?).
I hope you're still awake after reading this
Answer is simple http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel
And you will receive the same answer whenever you ask beginner question
I appreciate your advice, however, you must know that although some of my questions were beginner questions not all of them were such and those still require direct answers rather than some generic answer you provided.
I read the 80% of the BA Wiki before posting here and I haven't found the answers I need.
For instance, I still don't know why those bootloader stripes are still present..or what happened to my CID part in device data. If it's messed up, how come it's working? If it's ok, why it's not mentioned on the Wiki?
You may correct me if I'm wrong, but after reading all of that, I still don't know wha't really included in the backup or why my SMS messages are still there after I performed a hard reset, but my e-mail settings are deleted...
Saying "Eat if you're hungry will not solve the problem of a hungry one".
In general, that approach of forwarding noobs or people with such questions to a first page of an ecyclopediae is not a solution.
You're right wiki isn't enough, there is a search! And let me told you a little secret - there is a google, (you know google dont you?)
After reading wiki you MUST realize that:
Bootloader - no way of removing stripes!
CID part - You didn't follow the step-by-step proccess in wiki. And because you are beginner you should follow the Helmi install procedure (or read through WM5-BA page) And what is more important you dont even know anything about CID (use google - it is in wiki but not in BA section)
+
Because its not important its not mentioned in BA wiki.
Read something about WM5 how it works and the differences between 2003SE. (Like a persistent storage) <- answer to your SMS and hardreset question. And use google to find more information rather than asking more question
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
do you have a G3 or G4?
What are your IPL/SPL?
Which other ROMs have you had installed on this wizard?
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
My answer to you is the same one I posted to you before --
READ THE STICKY ABOUT UNLOCKING AND FOLLOW IT STEP BY STEP!!
Then -- and ONLY then -- will you be able to flash to a custom ROM.
newbie2 said:
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
Click to expand...
Click to collapse
Yep, I've replied to ecomajor's various posts in various threads and have basically given up. Very little info each time and having a problem that nobody else that has followed the steps has had.
Sorry ecomajor, don't know what else to tell you that hasn't already been said numerous times.
One Last Try -- Then, I Give UP!!
Read the following post on how to flash ANY Wizard (yes, that includes the 8125) --
http://forum.xda-developers.com/showpost.php?p=1177659&postcount=1
Now, follow the directions in that post WORD FOR WORD and STEP BY STEP. The only reason it wouldn't work is that you're NOT READING and/or NOT FOLLOWING THE INSTRUCTIONS STEP BY STEP.
If you CAN'T read and follow directions, then don't be trying to flash different ROMs to your phone. If you're not willing to do what's necessary to help yourself, then noone else is willing to help you, either. . . especially when your problem has already been replied to with the same information over and over in 2 DIFFERENT THREADS now.
Let me detail you the exact steps I have taken. I have read through those posts, many times so I am certain I took those steps
1)device starts normally goto step 3.6 since unsure if unlocked.
2) read farias thread
3) download buttons rom
4)attempt to downgrade rom - failed
4a)tried 1.08 rom instead of button - failed
4b)tried wizard love- failed
5)download lokiwiz
6)followed all directions -failed - since was not able to downgrade rom.
Obviously these directions are not 100% foolproof - I know that the first time I tried installing WM6, I did not read through all the threads and after much effort I discovered that if I installed the official cingular 225 rom then I could get my ppc back working but since then I have had no luck getting flashing to work. Please tell me what I am doing wrong because noone has had my exact situation. there is no need to act all holier than thou and accuse me of not reading because since I screwed up the first time I have read through all these threads numerous times.
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
And I've attached the ROM Update Utility Readme.doc that describes the error messages and how to fix them.
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
mfrazzz said:
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
Click to expand...
Click to collapse
ecomajor said:
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
Click to expand...
Click to collapse
I've never tried it in safemode so I don't know if that will work or not, it was just an idea as we are grasping at straws here. But if you boot to safemode, and with the phone at the bootloader screen (hold down the camera button while you turn it on to get to the "rainbow" bootloader screen), if it shows USB above the left softkey then the computer and phone are communicating and Activesync does not matter. BTW:You can try the safemode way there at work as you will have no network connectivity in safemode so you don't have to worry about violating security policies.
You still have not answered my one question directly... Have you tried flashing the button rom to your phone on multiple computers? Or have you always done it from the same PC? And are the PC(s) that you are using running Windows XP?
What DOC chip does your device have? G3 or G4?
If you have a G4 then i guess you ruined your bootloader since G4 devices don't have and don't accept 1.xx IPL versions!!
I have tried button from multiple pcs. This time it gets up to 98% on button and then dies and it gives error 302 - update error for the button. This is a problem that I was having before.
Did you read the document I posted?? If you're getting Update Error 302, you're not going to be able to recover with anything other than the stock Cingular ROM.
Chances are that you did indeed ruin the bootloader when you tried using the ShellTool to flash a G3 phone. And I doubt seriously that you'll be able to do a warranty exchange if you can run the stock ROM successfully, so I'm afraid you're stuck now with the stock-shipped ROM.
So you are saying there is no way to fix the bootloader (like flashing it or soething) I was figuring I had screwed something up. I actually had read the document before but thanks for your help. Why is it that you can fix many other issues with the 8125 but not the bootloader?
I'm not saying it CAN'T be done. What I AM saying is that in the year I've been registered and active here, I've not seen any posts/threads about recovering from a bad bootloader. But that doesn't mean that there ISN'T a way to do it.
You might want to do a search of the Wizard section for bootloader error or recovering bootloader to see what might come up.
Good Luck!!
ok, I have read all there is to read on this site and on WIKI. What good is it if what I am reading makes no sense to me? I know what .cab files are and how to use them, but what is a .rar file and how do I unrar or unzip it? Do i really need to create files in DOS?
All I want to do is upgrade my BA (sx66/cingular using unlocked on tmobile) to windows mobile 5.0. I know there are way too many threads on here about people who are getting stuck or having certain errors or need help in some way. I can't even get started! The few "step by step" guides I found, start off easy enough an 3 steps into it they referring to things that I have no idea what they are or how to do (yes i have read all the "please read before asking questions" stuff) Again what good does it do if you dont know what you are reading. Maybe its not broken down into simple enough terms for the average joe.
In any event, is there anyone that can shed some light on this stuff for me or aid me in a walk through. Or am I just out of luck because of my lack of software engineering knowledge? Thanks for your time all and I appreciate any feedback. Surely there is someone out there as dumb as I in this area that made it through (or at least I can hope)
You need winrar (www.winrar.com) to "unrar" the files in order to use them.
Winrar works just like winzip but it handle .rar files. So basicly you will download winrar to your computer, install it, then download the rar file with the rom you want to upgrade your device.
Using winrar open the rom archive and extract to a folder on your computer.
Run build.exe, select the options you want for your rom and press the > button.
From there do as the guide says.
spunk32, calm down We are here to help, not kill newbies
Two things:
1. When you don't understand some terms like "unrar" that not PDA-related, just google it. Things like this are considered basic here
2. When you have specific problem about one of the points, post a question (let's keep it in this thread) and smb will try to explain. But try to understand some of us, that we are not going to explain how to copy or download a file
General comment:
ROM upgrading is not totally safe and error-prune. You have to understand fully what are you doing and what for/what is the result. Basic knowledge of the way the PDA works is also good, to make good decisions on the way. That's why I do not consider updating (especially BA from WM2003 to WM5) as a task for everybody (for ex. I think that updating WM5 to WM6 with full unlocking of Hermes is much easier, but still not safe).
I would propose you to use Baniaczek's ROM (instead of XPlode rom cooking set - I looked at the PDF guide - yes, this one is complex, but some of the pictures might be helpful) as there is one step less on the way.
Full guide for you is here (on bottom of the page)
http://wiki.xda-developers.com/index.php?pagename=Helmi
You should go through all the options here, when you update from WM2003. Remeber, that going back to 2003 needs to go through another procedure, that will recreate ExtROM (yes, this is one of the magic words you should understand to play with ROMs).
Thanks for the info guys. ill delve a little deeper and see what happens. im sure ill be back on here with a post when i come to another speed bump. thanks again.
ok, i have gotten this far: downloaded winrar software, downloaded the following ROM-Helmi_BA_WM2k5_AKU3.5_v1.4.CF2.R2. Then I clicked on MaUpgradeUt_noID.exe. When i click continue on the welcome screen, the next screen shows "software converting from....to..." all the data fields are blank. Is this normal and am I on the right path? I did NOT click on upgrade to continue the process b/c I wasnt sure if I had missed something. Thanks again all.
Read what I posted moment ago in "No data from device in MyUpgradeUt" thread. I just checked again screen while updating Xplode on my BA:
In From fields there is only Radio version
In To fields, I have only Ce Image Version: 5.35.05
All other fields are emplty (and not important after all, especially nonexisting ExtROM).
Press your power button, the record button (has a cassette on it) and your reset button at the same time. Wait for the Serial or USB to show on the screen (will be dark) then flash your ROM.
It is in the forums around here somewhere on how to do that but I am to busy to find it for you to post a link.
ok, i think i made a mistake. i got as far as the step where it says you MUST say YES to the first two things on the reboot screen or whatever. all of them said NO, i tried to change it to YES , but i did not know how to change it. i hit the mail button and the screen white and loaded as is. how do i get back to the screen where i need to make the "YES" changes and how do i change NO to YES??
ok, i re-read and saw where i missed how to toggle the YES/NO. so since i was dumb enough to miss that what have i done by not changing the "NO"s to "YES"s? The device seems to be working fine. Is there something that I am not aware of yet?
If you restarted the device and made the hard reset again, this time correctly (selecting proper settings) device should work fine.
You might not noticed, but if you take battery out for while and then start the device, radio won't start (there will be no version next to letter R - means GSM mopdule won't work). You need to make soft reset few secs after first starting of the device to make it run. This is on of not so many problematic things with BA under WM5.
i have not done anything to reset the "yes/no" settings and the device has been working fine all day. i dont ever take off my battery so hopefully i wont have the problem you were refering to.
also, is there any way to remove the camera software since i dont have a camera on my device.
how do i upgrade the radio? i tried WIKI, but i got error messages and when i tried to follow the troubleshooting the links didnt work. outdated i guess.
If you never done correctly hardreset of you BA, you should - you can have a lot of odd problems without hard reset after installing (or upgrading) WM5.
Radio: I followed Wiki and made update radio (1 year ago) from some old version up to 1.13 - without any problems. Follow step after step and port exact error message and on what was happening a this exact moment.
ok, i reset and corrected to NO, YES, YES. thanks. what about removing camera data? any ideas?
You cannot delete apps that are already included in the ROM - this is Read Only Memory, as you know.
When you feel comfortable with flashing and playing with all those files, you will be ready to try xplode kitchen in which you can just select stuff you need to be included in the rom. Manual is a bit longer but still nothing really hard. You can find PDF with full instruction on Wiki pages.
ok i understand what your saying about the camera app. i have tried many times and many versions of the radio upgrade and none work. i have gotten just about every error code there is. am i supposed to be in that "boot" mode when i run it or simple be synced? ill keep looking for a thread that has recent info, but what i see is out of date with links that are no good.
You should follow http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.15_Upgrade and Second Methord Type I EASY (this is the one I used). Because you have no camera, you device is PH20B1, but AFAIK radio is the same.
You need to put your device in "serial" booloader mode (non backlighted screen, "serial" or "USB" written in lower part of the screen depending on USB cable connected or not (Power+Softreset+Record).
blue tooth wont turn on
the wm5.0 has been working great. the only problem i am having is that the blue tooth wont turn on. i have tried every method of enabling it, but it always shuts itself off. any ideas?
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!
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.