Hey guys,
Recently i have had some problems with my touch dual so I decided to downgrade to a previous official firmware. I had the newest official WWE firmware on it previously.
The ROM installation was successful, everything went good...but now everytime I turn on my phone it never gets past the "please align ur screen" section. My phone is responding to all the screen taps perfectly, but everytime i finish the final tap (on the top right hand side of screen) it always goes back to the middle cross. I can never get past the "screen align" section!!!
Please help !!
thanks
JAMinGUY said:
Recently i have had some problems with my touch dual so I decided to downgrade
Click to expand...
Click to collapse
What sort of problems? Hardware issues before flashing? Which version did you flash from and to.
it always goes back to the middle cross. I can never get past the "screen align" section!!!
Click to expand...
Click to collapse
Try reflashing the ROM or even WM6.1 Official:
http://www.4shared.com/file/8884562...2094051_Radio_NikeMR_1652825_signed_Ship.html
This is from US, and will update the SPL, radio, and ROM. Make sure the phone is provider unlocked (is not locked to one particular phone company) before doing so.
EDIT: My bad. I need to learn to read.
my previous ROM was: RUU_Nike_HTC_ASIA_WWE_2.12.707.2_Radio_NikeMR_1.65.29.22_signed_Ship
I flashed it to: RUU_Nike_HTCASIA_AUS_1.31.710.12_Radio_Nike_1.58.21.23_signed_Ship
after the flash, it now will not get past the "align screen" page everytime I turn on the phone, although it DOES respond to the screen taps.
I can connect it to the computer to problems, it still connects to activesync so i can still flash it to various OFFICAL ROMS.
rling said:
What sort of problems? Hardware issues before flashing? Which version did you flash from and to.
Try reflashing the ROM or even WM6.1 Official:
http://www.4shared.com/file/8884562...2094051_Radio_NikeMR_1652825_signed_Ship.html
This is from US, and will update the SPL, radio, and ROM. Make sure the phone is provider unlocked (is not locked to one particular phone company) before doing so.
Click to expand...
Click to collapse
Rling, I see you are from AUst too? me too....
The hardware issue I had while using the 6.1 ROM was that my screen taps on different icons would not work, instead everytime i tapped the screen, it would goto my contacts.
I am now trying to download the link U posted and see how that works .
thanks
Hey I tryed flashing it to WM6.1 Official ROM:
http://www.4shared.com/file/88845629...gned_Ship.html
but it said invalid vendor ID and wouldn't flash...........my niki100 is still stuck in the "screen align" screen.....responds to screen taps....but doesn't go past the screen align section!!!!!!!!
any ideas anyone??????? help!!!!!!!!!!
anyone have this problem with their touch dual's before?????????????
JAMinGUY said:
Hey I tryed flashing it to WM6.1 Official ROM:
http://www.4shared.com/file/88845629...gned_Ship.html
but it said invalid vendor ID and wouldn't flash...........my niki100 is still stuck in the "screen align" screen.....responds to screen taps....but doesn't go past the screen align section!!!!!!!!
any ideas anyone??????? help!!!!!!!!!!
Click to expand...
Click to collapse
Invalid vendor ID would pop up if you have a phone other than Nike. Sure it is not a neon? The info would be printed in the battery compartment.
yeah in the battery compartment it says NIKI100
i am 100 % sure its not a NEON
If it's a NIKI100, then the only other time it would give the error if the phone is locked to a phone company. You'll need to CID unlock the phone first.
Nah its not locked to any phone company, I can use telstra, optus and 3 sims in it no problems...
I have success in updating or downgrading it to various ROMS...but it always loops the "screen align" section on the various ROMS.............
JAMinGUY said:
Nah its not locked to any phone company, I can use telstra, optus and 3 sims in it no problems...
I have success in updating or downgrading it to various ROMS...but it always loops the "screen align" section on the various ROMS.............
Click to expand...
Click to collapse
Phone not locked - Checked.
Radio - Higher than 1.65 - Check on boot screen (the red letters on right)
ROMS - Official and custom.
If the screen alignment loops despite all the above, then it could be a hardware problem.
I remember my brother's mda vario. There was a error with the touchdisplay, so it stuck at the screen align screen.
Maybe this is your error.
Put the orginal rom and orginal spl on it and send the device to your vendor.
Today a employee of UPC picked up my phone for a reparation at HTC.
I've enclosed a letter with my complains so I hope that they will repair it without any costs. Let's hope for a solution. As soon as I know something I'll let you guys know.
me too having the same problem tried even changeing touch pad
any solutions pls
regards
riaz
Related
Hi, looking for advice on how to fix if possible a M3100 with failed phone functions. Started when 3G went down in area, swithced to GSM worked for a while then lost signal completely, tried hard reset to fix but during setup i tried to set a pin for the phone element of the device as prompted to do so, on re boot the pin screen showed but neither touch screen or keyboard would allow me to enter it so i re- booted and same thing happened a number of times. Tried hard re set and device works except phone, no signal and doesnt recognise sim as present, cannot enter phone menu through any route. My sim works perfectly in my old phone. Is this hardware or software, phone functions failed before hard re set? would un locking fix this or does it need to go back to HTC?
Any advice appreciated
What do you see in the boot screen when soft-reseting?
You should see in red letters your radio version next to an "R" in the bottom-right part of the screen.
On boot up i see the following in red at the bottom of the screen:
M05
S04
B05
D 1.23
NO GSM
"NO GSM" shows that radio rom is probably screwed.
Go into bootloader and run the commands "rtask 1" and "rtask 0" in mtty. This will try to turn on the radio and reset it.
Also see the output of commands "checkimage" (should give you a radio image CRC checksum) and "info 8" to see that your flash is intact.
If the process above does not fix the problem you should better go for a replacement with Orange... or if it is not possible wait until they release a ROM upgrade and see if it fixes the problem.
Do not flash any other rom if you pretend to return the unit.
Info 8 shows all blocks reversed
rtask 1 has no effect
Check image shows results for all except radio image crc showing wait interpreter time out
The unit is an e-bay special so cannot return it, wil flashing rom with non ornage version fix this problem? or must it be orange to work properly with network services?
Thanks
I don't know if flashing would fix it, but if you have no warranty then go for it. It doesn't need to be an Orange rom, you'll get the Vender ID error if the flashed rom doesn't match your CID, but just follow the instructions on the wiki...
LC said:
The unit is an e-bay special so cannot return it, wil flashing rom with non ornage version fix this problem? or must it be orange to work properly with network services?
Thanks
Click to expand...
Click to collapse
Au contraire, book it in at
http://service.htceurope.com/
it is based on seriel number you don't need no stinkin' paperwork....
I have bought from eBay and sent back under warranty many times ;-)
Just don't flash a dopod rom on there just yet as then they'll know...
Richard
Thanks for the help and advice, will send it to HTC
LC said:
Thanks for the help and advice, will send it to HTC
Click to expand...
Click to collapse
If you do end up being charged for a 'bad flash' etc the most it will cost you is about £30. Better than a non-working device.
Richard
Please help me. I recently upgraded to the Black satin rom and everything was fine. However the touchscreen on my M3100 has started to go haywire.
After being on for about 5 minutes the touchscreen doesn't work. It seems like the top right hand corner is faulty as the close button keeps being pressed again and again. I think it is probably the phone that is faulty rather than the ROM.
Anyway I need to revert back to the original Orange ROM (WM5) so I can send it back to orange. I've only had the phone about 3 weeks so its still under warranty.
I tried to load the ROM off the orange business website but it errors when trying to load the rom on. I assume I need to downgrade the bootloader thingy.
Any help much appreciated!
www.mrvanx.org
Look for "downgrade guides"
I'm in a similar boat mdavix!
I've just tried flashing an original T-Mobile WM5 ROM using MrVanx's guide but it doesn't progress beyond the bootloader page. Instead the update times-out and gives Error 260 - "Cannot connect to PDA"
Getting late (that's when Bad Mistakes Happen lol!) so will come back to it at the w/e I hope. Let us know if you have any luck!
sim
--
T-Mobile MDA Vario II / schaps 3.57a / Radio 1.41 / HardSPL
interestingly, I put black satin on my new M3100, and the screen started going. So I put it back to the latest Orange release (from the website) 2.11.61.1, but it was still screwy. Sent it back to Orange, and got a different recodnitioned phone back. They said the ROM was the issue, and the one they gave me had 2.11.61.3 on it. This version is not available for download... has anyone else seen it?
Do orange know what is happening to the screens? Is something getting burnt out? does 2.11.61.3 have a fix?
Well... I'm too scared to put WM6 back on, now, although I really want to. I at least want to wait till I can get hold of the update for 2.11.61.3, and even then, I'm not sure.
I have looked at the downgrade guide but don't really fancy the re-compiling the nbh business.
The strange thing is that if I take the battery out for a couple of minutes, then replace and boot up, the screen works for a while!
Is it worth trying a different rom?
mdavix said:
Is it worth trying a different rom?
Click to expand...
Click to collapse
No, it's a hardware problem, I assure you.
Ok, thanks vp3G.
So I still need to get back to WM5.
I'll have to give mrvanx's downgrade guide a go!
Is this still current? Is this the correct one to try?
I carried out the steps in the downgrade guide and attempted to flash the resultant rom onto my M3100. It started to update got to 1% and failed with a transfer error!
Now when I turn the phone on it just comes up with the three colour screen!
Have a broke it forever? The screen reads:
HERM100
IPL-1.01
HERM100
SPL-2.10.Olipro
Please help!
Phew! Panic over, I've managed to get the Black Satin rom back onto my phone.
I'm stuck at the screen alignment screen again but at least its got an OS on now!
I still need to load WM5 on tho. I think I'll try re-doing the downgrade guide and see if that helps.
I'm looking at duttys nbh tool and notice that the device id is HERM200. My phone is an M3100 so a HERM100. I'm going to change the value to be HERM 100 and re-compile. Hopefully that was the problem last time!
Hi all,
First of all I want to let you know that I did search the forum for a solution. In fact, I found a lot of workarounds but none of them actually worked.
Let me give some details about my problem: My Hermes was working fine. I was running the official WM6 ROM supplied by HTC, so no customized ROM here.
It was going fine until the WM frozed. Then I soft reset the device and after that I never got cellular signal again.
While booting the device I got the message: "no GSM".
First thing I tried was to flash a new radio ROM. In all the attempts the progress bar never moved from 0% and after a while I got the communication problem error.
Then I tried flashing a whole ROM. This time the progress bar stopped at 81%. Apparently in the first 81% it flashes the OS and in the last 19% it writes the radio. Anyway, I tried this a few times and never finished.
In fact, after every communication error message I got stuck in the bootloader screen.
The only thing that works is to flash a ROM WITHOUT the radio!!
Is there anything I can do to save my phone or am I condemned to use my Hermes as a phone-less pda?
I tried everything I found in the wiki/forums, but I couldn't find a working solution.
I suspect that the blocks of memory where the radio data reside got corrupted, could that be possible?
PLEASE HELP!
thanks in advance!
Chris
A similar thing happen to me several months ago. While on a call my phone froze and when I soft-reset it the dreaded 'No GSM' issue appeared. I tried flashing radios/full roms/etc, but nothing worked. I ended up sending my phone to the htc repair facility and they fixed it at no cost. (Other than not having a phone for ~10 days)
Thanks dang, but I don't have a HTC service center where I live (Argentina, LATAM)
I'm faithful that the people of this wonderful community will be able to help me.
Just for curiosity, where did you send your device? Is it in the US?
cheers
sounds like a hardware problem to me...
Hi, there! I found that a lot of us who have bricked our Hermes, don't have a responsive radio bootloader, so when they try to flash a full rom, the progress bar hangs to 13%, or 81%. This is because at that time the flasher is trying to enter the radio bootloader, but because it's corrupted, it hangs. Till today there is no known solution to this one. I'm far away from England where I bought my Hermes, so I'm not thinking to send it back for repair. I'm a programmer, so my knowledge may be usefull here. The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
How can I try that?
windshearx said:
The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
Click to expand...
Click to collapse
You can use 'lnb' in HardSPL without having a real SuperCID; however you will not be able to flash a radio with 'lnb' command. The radio chipset has its own bootloader, the and the SPL just acts as a pass-through sending the data directly to radio chipset through the s2410 UART.
I had one device with non-responsive htc_boot and tried all kinds of SPL patches to flash htc_boot again on radio, without success. The only known method to fix this is to take the BGA chip out with hot air and reflash it with special hardware, as it is not common to have this equipment at home, your only option is to send it somewhere to do it for you.
However, I don't want to discourage you to research on it, maybe you find something i didn't
I have a similar problem
I also have a NO GSM and corrupted CID but I can access KITL and use it with PB 5.0. and I followed this steps here but the phone doesnt boot completely. It stops just after the two boot screens on Black WM6 ending on a white screen and the debug window on PB after loading all sort of things begin showing these lines over and over:
@@@@@@ HUB state changes now @@@@@@
[HDC]HubStatusChangeThreadPN TRUE
[HDC]HubStatusChangeThreadPN FALSE
Is there any hope for me? I have the cingular 8525
thanks
Gents, do you think the solution presented in http://forum.xda-developers.com/showthread.php?t=280425 could help me?
Please advise.
thanks again
chriscec said:
Just for curiosity, where did you send your device? Is it in the US?
Click to expand...
Click to collapse
I sent it to the HTC service center in Texas, US.
I just got my replacement from ATT.. Had the same problem. Its a hardware problem.. I wouldnt waste anymore of your time.
first, i'm sorry for my english
I've the same problem with a V1605 (french SFR), i've tried every solution but flash radio doesn't work.
I can flash cooked os without any problem, but it's impossible to put official
It's only a pda now, it's better than a brick
My hernes use to be the same as you 'NoGSM'.I tried to install the official rom,but it 's not work at all.I called to service center ask this problem,so they said that it must be only changed the mainboard. That 's terrible!!!
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
otoro_315 said:
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
Click to expand...
Click to collapse
That only works with phones with KITL...which I don't seem to have.
Sorry, how to config the phone with KITL and solve the no gsm problem.
No GSM but when sim inserted
Hi all, First sorry for my bad english.
I also have 2 bricked Tytn Hermes 200. Its not my personal ones Its my company's property, which pple were using this phones. So i'm facin with problem which many pple here having but with exception. both phones having no gsm error when sim inserted but without sim its fine. In other words , device info showing every info including IMEI when sim unavailable. And some times works with sim but after making few call and receiving phone hangs(not system) and goes off from network but anthena signal still showing few bars. I'm thinking maybe the radio hangs totally and goes off, and after soft restart NO GSM. I also tried many flashing upgrading those things nothing can really help me.
When im flashing original rom from HTC (the latest one HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108) its hanging on 12% and doing 3 or 4 times recovery , but its finishes succesfully. So what exactly happening in 12th%?. Maybe its started flashing radio and stopped on bad block ? But then why its finishes succesfully after few retry?. Ok so if any one wants to experiments on the phones except radio welcome. I'll help. And some can give me quick example of how to check bad blocks?.
Tnx.
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
otoro_315 said:
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
Click to expand...
Click to collapse
My device is still SuperCID and I know I don't have KITL...I have SPL 1.04 as well and HTC Bootloader is 0108. I can't install any ROMs with radios as they will hang at 11/12%. I will attempt this "overload" method where it seems some people have had luck with it...after a few recoveries it just finally installs...but I don't think that will be the case.
If I can't fix this in a few days, I will most likely use my warranty or just wait for the Kaiser.
My variation of No GSM
I feel like I have problem 1A...where I am able to boot into OS but no GSM.
I am still SuperCID, SPL 1.04, HTC Bootloader 0108. Last known radio before corruption was 1.48.00.00. ROM where this problem occured: VP3G 3.60.1.
I was not even in the middle of an upgrade...just a soft reset after my phone ALREADY lost GSM capabilities during a tether session. It was stuck with no signal in Phone Mode...I put it in Flight Mode...then tried to move it back to Phone Mode and it wouldn't do so. I soft reset...and the no GSM stuck.
I tried to reinstall radio...many errors...stuck on bootloader. At first, OS's only were not installing as well but I got past that. Now I am able to boot into OS's with limited capabilities...and they will NOT ACTIVESYNC at all. Regardless of how old or new the ROM is. I tried older OS's that I knew worked in the past for me...but they refused to activesync.
Due to that, I am not able to install latest HardSPL 2.10Oli via SSPL. That seems to be the only way to do it according to my knowledge and what I've read. Maybe mtty was capable but I'm not sure. HardSPL 1.40Oli wasn't giving me any problems though, but I just wanted to have the latest one so I can avoid IPL damage.
I can only install anything if I start the device in bootloader...and I'm only limited to the OS since my Radio Bootloader seems corrupted.
I'm not sure what caused the corruption in the first place...but I feel annoying now posting on different parts of the forum with a problem that seems to be growing in the community.
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Your phone's cdma. This is a gsm forum. I'm assuming that you're trying to brick your phone with the gsm hard spl and not trying to flash the proper hard spl. Stop doing that, your phone is getting pissed at you. Go to ppcgeeks or the cdma (Herman, not Raphael) forum here.
haha leave it to me to find the wrong way to do something. I appreciate your heads up Ted!
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Try here: CDMA Herman
same issue on GSM phone
Hi I have the same problem on a GSM phone.
I get the updating bar on my phone- it stays stuck at 0%.
then a communications error
Thanks in Advance
What is the problem with the RUU update?
I have searched for a solution to the RUU update/upgrade problem; none so far. Apparently, it is a major issue. I am interested in upgrading my Windows CE on my Xperia 6.1 to 6.5. I must have tried over a dozen times. The update process stops at 0% and Error [262] is reported. What can we do to resolve this? Is it compatibility or scalability issue? is it a problem with the software? The fact that it is working for some . . . and not for others is a source of concern about the stability of the software and this has potential implications; or it may well have to do with the hardware limitations of the PDA. Any ideas of a workaround?
You might try the Experia forum. You also might want to try Experia Roms.
I used to experience this issue as well. I simply go into communications and hit the USB to PC connection. Then remove the advanced functionality check. This has resolved many of the communication errors when playing with ROMS. This has been true with both GSM and CDMA devices.
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Dunno if i can link to another forum. If not, appolgize and Admins remove the link than please.
For the 262 error, look here:
http://www.4winmobile.com/forums/windows-mobile-faq/13329-ruu-errors.html
player911 said:
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Click to expand...
Click to collapse
Yes they are coming with a new bootloader. I just got my phone replaced from ATT and the new one came with 1.95 version while originals were 1.90. There is no HARD-SPL out for 1.95.
The way to do it now is to flash an old original AT&T rom with the 1.90 bootloader (since it's original, it won't require HardSPL). Then go ahead and everything should work as described in this forum/wiki.
Interseting. Sounds like a winner. Next time he comes around I'll try this.
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
smicale said:
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
Click to expand...
Click to collapse
You should probably go to your ATT store and tell them you'd like to get the official Hard SPL update.
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
smicale said:
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
Click to expand...
Click to collapse
If u want to use not the official rom made for ur provider and phone, hardspl is the only way. Any custom rom needs hardspl. Otherwise ur phone will not accept the rom.
But look here http://forum.xda-developers.com/showthread.php?t=410150
and flash the stock 1.90 SPL first, then u are ready for hardspl.
Description how to do stock spl is in this thread. Its normally meant for going back to stock for repair, but it should also solve ur issue.
NOT SHURE BECAUSE IN THE CDMA SECTION, IS UR PHONE CDMA OR GSM. MY SOLUTIUON IS FOR GSM !!!!!!
U SHOULD CHANGE THE POSTING SECTION IF ITS GSM !!!!!
Try doing the HardSPL in a Windows XP machine (needs .NET Framework 2.0 and ActiveSync). Goodluck.
i had the same problem as you and i maybe have a solution for you
go to your usb settings and look if you have a check box saying something about advanced networking. if it is indeed checked uncheck it and your problem will be gone hopefully
i did it on my telus touch pro and i am now able to upgrade my phone to winmo 6.5
It all started when I upgraded to the new official TMOUS ROM. I then wanted to install OzROM_5.20_24635 instead since it's TMOUS friendly. But to do so, I needed to install a 2.07-2.12 radio and was not able to do so - the process was stuck at 0%. Now as a result, my phone has been intermittently inoperable. I installed a SimTravel sim card into it (it's unlocked) - it recognized it once, then stopped picking it up completely and would reboot within minutes of powering on. Then I purchased a Lycamobile card and all seemed to be going well, but I just had it crash during a phone call with customer service (for some reason my sent SMSes never make it through, but I can receive them fine) and now it won't start. The symptoms are always the same - seven "buzzes" or vibrations, however you want to call them, and the phone is stuck at the first T-Mobile screen. I've tried hard resets and they have worked to a point - now they don't. How can I restore this thing?
Oh, just got it to reboot by waiting about a minute after taking the battery out... It went through the orange Windows 6.5 screen, then rebooted itself and buzzed seven times again...wtf???
You need to flash a previous offical TMOUS ROM (to get away from the 3.14ROM). This will get your SPL back to 2.10 or 2.08 - instead of the present 3.03.
Then you can use HSPL3 to change the SPL to a 2.XX.HSPL. Follow the rest of the instructions from the OzROM thread.
fred_up said:
You need to flash a previous offical TMOUS ROM (to get away from the 3.14ROM). This will get your SPL back to 2.10 or 2.08 - instead of the present 3.03.
Then you can use HSPL3 to change the SPL to a 2.XX.HSPL. Follow the rest of the instructions from the OzROM thread.
Click to expand...
Click to collapse
Where can I get that ROM? Which version do I need?
Also, my problem now is that while I can get the phone to boot, it restarts during the setup process - I can't get to the home screen...how can I flash it in this situation?
Lovely new development. When it doesn't buzz, it shows the numbers (in pink, like the radio version (2.15.something, btw)) and hangs there. Ugh.
Try * HERE *
The phone now freezes midway through the update...the same seven buzzes and nothing...
highlanderfil said:
The phone now freezes midway through the update...the same seven buzzes and nothing...
Click to expand...
Click to collapse
I read some users reported the same issue, and bad news is that most of them have to bring it to htc repair center (is it a bad news? )