I know there are others experiencing the 28% death wall while trying to flash WM6, but there doent seem to be any specific solutions to this.
I have a Dopod D810 and has already installed 1.30 olipro. Just trying to flash to the official WM6 ANZ Rom. No luck.
Any suggestions guys?
Should just be a very straight forward procedure. Flashing a Dopod with an official Rom.
should be, but it's not... mine is Dopod asia, and stuck at 28% when flashing. Not too sure, but really seemed to me that it was something related to hard-spl. After the 28% error, i reflashed an unofficial rom and tried the official again.
eventually it worked for me.
i guess you don't technically need to manually enter hard-spl first before flashing official ROM.. if anything went wrong i guess you could send it back to them..
safest is to use a modified RUU so it just flashes ROM without IPL + SPL.. i thiiiiiink problem is something to do with SPL
which unofficial rom did u reflash it to? I've been going back and forth with AX3L_OS v3.0.0.2 and the official ANZ dopod rom.
tried about 5 times now. still trying. each time it fails at 28% it's another 10 minutes to flash backto the unofficial rom.
maybe if i try to trce ur steps exactly it might work.
i was flashing to some pdaviet ROM, but i don't think that would make any difference from ax3l's...
have you tried flashing the official ROM with a modified RUU, or you really want the whole package...
If you're just trying to keep everything official i guess you could try to flash the official rom without manually entering bootloader and take your chances. Being that its an official ROM i guess it's safer, or at least covered in warranty..
One question, why don't you try to flash to official WM5 ROM, then to official WM6.. since technically it's supposed to work that way
seriously, i'm not sure why you'd want the official one though.. it's nothing special
Yeah I've tried flashing back to the official WM5 and then WM6, same story.
Tho I havent tried flashing the official WM6 through modified RUU, mainly coz i dont know how to.
Also, In the AX3L version of WM6, there doesnt seem to be a phonepad input method. only keyboard and block recongniser and one other one. Is that coz it's a modified rom, or does WM6 not have the phone pad input. if that's the case i can forget about flashing to WM6 all together.
can't remember if official wm6 has phonepad, but you can just install a cab for it, so it's not a big deal.
look on my site for a link to modified RUU official ROM... instructions are here
i had a lot of problems being stuck at 28%
what eventually i got it to flash to the aus rom was i used SPL 1.20 then it seemed to flash fine.
for some reason my phone doesnt like any other version of SPL besides the one on the latest aus rom either, i flashed to a cooked rom and couldnt flash back until i had put spl 1.20 back in then flashed back to the aus rom.
I have the same problem with 28% stucking
I try to reflash but I still have the same
do you have hard-spl? if so, which version? If you do, flash back a cooked ROM..
if not, you need to try to flash official ROM..
if neither is working, use splxploit. I think all links you need are in this thread already
I have a same problem.
I was upgraded from WM5 to Hong Kong Official WM6 chinese ROM, then I want to change to Official English ROM, I did the Hard-SPL 1.3 and get the SuperCID, but when upgrading the WM6 English officeial ROM, this was stuck at 28%.
Now I was able to flash back to WM5 rom, but I world like to Upgrade to WM6 official ROM, anyone help?
I had this problem when upgrading to the Australian WM6 official HTC Release. The way around it is to run the Trinity Service Provider & CID unlock program from the link below. Dont know why but to use either release, Dopod or HTC WM6 you must run this tool first.
ftp://xda:[email protected]/Trinity/Tools_and_Programs/HTC_Trinity_SIM_CID_Unlock_v1.zip
Hope this helps
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
HI, Thank for your reply, how can I do the modified RUU?
Hi all,
I have success to flash the WM6 official ROM.
this is my experience:
To flash the Radio ROM first, I has flash the 1.50.08.11 Radio ROM.
Then to download the Dutty NBH Tool to take off the Radio DOM of WM6 official ROM.
Then to flash the modify ROM.
Now, my phone is running WM6.
racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
Learn something new everyday. Never knew that simply modifying the RUU would itself allow the updates. Just tried it, and yes it works also.
racerx_ said:
you don't *have* to CID unlock your device to use these upgrades..
again, sometimes it gets stuck, sometimes it seems to work.. you can just keep trying.. mine magically worked after a while. the most sure method is to use a modified RUU, of which there's a few on the forums and a few threads regarding these issues..
Click to expand...
Click to collapse
how do mofify the RUU? and what do I modify it to?
thanx walterjm
Can you share HK-CHT rom for noSPL noIPL noRadio ? Thanks!
WildsideUK said:
I had this problem when upgrading to the Australian WM6 official HTC Release. The way around it is to run the Trinity Service Provider & CID unlock program from the link below. Dont know why but to use either release, Dopod or HTC WM6 you must run this tool first.
ftp://xda:[email protected]/Trinity/Tools_and_Programs/HTC_Trinity_SIM_CID_Unlock_v1.zip
Hope this helps
Click to expand...
Click to collapse
Can you share HK-CHT rom for noSPL noIPL noRadio ? Thanks!
I had the same problem and I resolve it by extract the rom and re-build it ... look at the thread http://forum.xda-developers.com/showthread.php?t=327667
Good luck
Related
Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey
Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..
Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!
That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.
pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.
I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.
Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...
At the point I am I need the help of experienced Users from the community.
I flashed a original HTC Wings (S730) with WM 6.1 ROM. It runs perfectly until I got a hardware problem (radio) . This is the reason I have to send it back to the official service.
Therefore I tried to go back to an official ROM from the http://wiki.xda-developers.com/index.php?pagename=WINGS_WM61_Alcaline
At first I flashed the earlier backuped Bootloder via sspl-0.91-wings.exe. This seems to be okay. But as I tried to flash an official ROM from the site mentioned above, during the flashing process I've got the note 'ERROR 294 Invalid vendor ID'. What was wrong? Did I forget any step?
Please, is there anyone who can describe the correct way back to 'warranty' for a newbie?
Thanx a lot.
have you tried all the ROM's? there is one prerelease and two release ROM's.. try both of the release roms, they might be for different production models/locations.
I tried both official released ROM's (signed as 'Ship'), not the prerelease version.
and if you first flash the shiped rom (with hardspl) and when done flash the back-up of the spl
With reference to an earlier statement of bigflavour in the thread http://forum.xda-developers.com/showthread.php?t=383617&page=17
I flashed back the original SPL at first.
Too bad It seems to be that I have a new problem now. Few minutes ago I have tried to reinstall hardSPL on the device via the well known sspl-0.91-wings.exe running on the Wings. But as I started the sspl, the device shows on the display that 'Access denied....is not digitally signed with a trusted certificate'.
Thereupon I thought I had to 'application_unlock' the device. After running the SDA_App...Unlock on my PC the display message shows succesful unlocking process. B U T, the sspl doesn't run as before.
Now, I'm totally confused. What has happened??
It's flavor, and unfortunately, I have no idea how to help you.
Probably tried the European english's spelling hehe.
Also This does seem like an odd problem, have you tried for kicks doing the factory reset to see if it will reset some of the registry and maybe fix your issues? I dont know anything about the spl's since I have no need to upgrade to 6.1, I wouldnt imagine it causing any more damage but again I dont know what all was done. I havnt followed those threads for a long time.
Thanx a lot. Apparently, the hint to make a hard reset hits the mark. Now I flashed back the HardSPL. So I'm back at the starting line . Does anyone knows if the official ROM from the http://wiki.xda-developers.com/index..._WM61_Alcaline is the latest one and can I use it for the warranty return?
Or should I look for an original German HTC ROM?
I was a little bit to fast. I will need a German ROM definitely, because the ROM from the Wiki doesn't include a the german language option.
Is there anyone who can help me with a original HTC S730 ROM for the german market?
Thank you in advance.
Hallo HSN,
if you give me a introduction how I backup my ROM, you can have my one. I own a German HTC S730. But I am confused when I read all threads about flashing etc....
One page introduction how to back up and you can have my one.
But I think that the Repair center here in Germany, doesn't care about the Rom you have installed.
OK i think i ****ed up bigtime.
I was on HSPL, and at first i flashed a stock rom.
After that i flashed DUtty's rom and it went ok.
It booted up with green screen problem and loads of locks and really really slow. After that i tried to use uspl but i was getting connection problems. After that i thought i should go to 1.15 stock spl and so i flashed that one, in order to use uspl. But the problems still persist, and now i cant revert back to a previous cooked rom.
Any suggestions ?
Use Manually Bootloader
Go back to stock spl, first flash stock rom, use sspl manual turn olinex and flash stock spl and then u can hspl again.
Hope it solves the prob. Just take a look at my Grafik Problem thread!
By
Well i fixed it and flashed everything ok.
A message to all flashers, DO NOT TRY TO FLASH ON WINDOWS 7. You may brick your device.
sedde said:
Well i fixed it and flashed everything ok.
A message to all flashers, DO NOT TRY TO FLASH ON WINDOWS 7. You may brick your device.
Click to expand...
Click to collapse
Hi,
Why, Windows 7 has the same drivers like Vista???
Can You express more crearly?
i flashed on Win 7 (build 7077)... i had to roll back the HTC USB Sync driver as explained in many threads about flashing the latest HD ROM v 1.56. i think some of our fellow members are not following all the steps to flash with the new ROM/SPL.
sedde said:
A message to all flashers, DO NOT TRY TO FLASH ON WINDOWS 7. You may brick your device.
Click to expand...
Click to collapse
A message to all flashers:
Read the instructions thorougly. If you cannot say that you understand 100 % of what the instructions tells you, read them again or do some research.
After following these steps you will almost certainly have a much better experience with custom ROMs.
-KJ
i tried reverting the drivers but it is simply not working. i am thorough and i do read the details.
I had no problems with the drivers. I just followed the correct procedures mentioned in the wiki and post#6 of Duttys v2.8 rom
Have you tried rebooting pc afterwards and pressing F8 as per the instructions to help load them?
i flash on windows 7 7068 almost 10+ times already with no issue , using custom ruu.
simranjits said:
i flash on windows 7 7068 almost 10+ times already with no issue , using custom ruu.
Click to expand...
Click to collapse
Same here. Use Windows 7 (7068) as my only OS and I've been flashing 20+ roms without any problems.
fjevel said:
A message to all flashers:
Read the instructions thorougly. If you cannot say that you understand 100 % of what the instructions tells you, read them again or do some research.
After following these steps you will almost certainly have a much better experience with custom ROMs.
-KJ
Click to expand...
Click to collapse
The instructions for all the different flashing methods are a big mess if you ask me.
There is no red thread, they all just blend together in a big mess and leave out answeres to simple questions that would clearify stuff for newbies.
The more i read the long pages of instructions the more confused i get.
nizzon said:
The instructions for all the different flashing methods are a big mess if you ask me.
There is no red thread, they all just blend together in a big mess and leave out answeres to simple questions that would clearify stuff for newbies.
The more i read the long pages of instructions the more confused i get.
Click to expand...
Click to collapse
I agree, they can be confusing, but once you have mastered it, you'll wonder what the problem was!
What exactly are you confused with? What steps have you taken? Where are you now in the process?
Don't worry about the phone it will be ok.
The steps are as follow:
1). Flash hardspl
2). Flash a stockrom
3). Flash USPL 2.5
4). With USPL on your phone flash to Dutty
To revert back to previous roms:
1). Flash hardspl
2). Flash your previous rom.
Grtz,
Leo
sedde said:
OK i think i ****ed up bigtime.
I was on HSPL, and at first i flashed a stock rom.
After that i flashed DUtty's rom and it went ok.
It booted up with green screen problem and loads of locks and really really slow. After that i tried to use uspl but i was getting connection problems. After that i thought i should go to 1.15 stock spl and so i flashed that one, in order to use uspl. But the problems still persist, and now i cant revert back to a previous cooked rom.
Any suggestions ?
Click to expand...
Click to collapse
Fallen Spartan said:
I agree, they can be confusing, but once you have mastered it, you'll wonder what the problem was!
What exactly are you confused with? What steps have you taken? Where are you now in the process?
Click to expand...
Click to collapse
Im fine, thanx, I have flashed my phone twice without big problems.
But the second time I got really confused when i tried to really understand it and followed the instructions step by step, it just sent me in a loop between all the different pages.
A simple question and a simple answere in the ROM-thread solved my confusion then, and now I just ignore the ramblings in the instruction pages.
Laurentius26 said:
The steps are as follow:
1). Flash hardspl
2). Flash a stockrom
...
Click to expand...
Click to collapse
I have a question about this. As my HD was replaced (warranty) I don't know which version I have (O2 or HTC). My first HD was a O2 branded with 1.14.207 ROM, the replaced one (from the same supplier) came with the 1.14.407 ROM which is the official German HTC ROM. I've just tried to download the newly released ROM by HTC, but the site states that the new ROM is not available for my device (but I could at least register the device). Could be that this is because it's an O2 device or probably because the new ROM wasn't yet released in German?
So is it really important to flash exactly the stock ROM (as the CID has to fit) or is it okay - like Laurentius said - to flash any stock ROM? Don't wanna brick my device when upgrading to 1.54/1.56...btw...why one has to go to a stock ROM when upgrading to 1.5x afterwards? Is there a difference when upgrading from 1.14 to 1.5x instead of 1.19 to 1.5x? I didn't get it yet...
Thanks in advance,
pal1m
pal1m said:
I have a question about this. As my HD was replaced (warranty) I don't know which version I have (O2 or HTC). My first HD was a O2 branded with 1.14.207 ROM, the replaced one (from the same supplier) came with the 1.14.407 ROM which is the official German HTC ROM. I've just tried to download the newly released ROM by HTC, but the site states that the new ROM is not available for my device (but I could at least register the device). Could be that this is because it's an O2 device or probably because the new ROM wasn't yet released in German?
So is it really important to flash exactly the stock ROM (as the CID has to fit) or is it okay - like Laurentius said - to flash any stock ROM? Don't wanna brick my device when upgrading to 1.54/1.56...btw...why one has to go to a stock ROM when upgrading to 1.5x afterwards? Is there a difference when upgrading from 1.14 to 1.5x instead of 1.19 to 1.5x? I didn't get it yet...
Thanks in advance,
pal1m
Click to expand...
Click to collapse
Any stock rom should do it as Laurentius said
A lot of confusion has come about from these newer cooked 1.56 roms so I wrote a guide. If you still have confusion please read the guide in my signature
Windows 7 is also most definitely not an issue. Several of us here are using it successfully.
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
USPL and HSPL do this for you so you are able to flash a rom or radio. Read this page from wiki. It'll help you understand
Follow cRaCKwHoRe's guide on how to flash (can be found in my signature). If you intend to do a lot of flashing I'd flash HSPL as its permanent whilst USPL is temporary and you'd need to re-use it before every flash to new rom or radio
Latest HSPL can also be found in my signature
Ah excellent thank you so much.
So can I flash straight to the newest 1.56 rom from my current version which is 1.19.61.1WWE on orange?
Or is there a stage in between I would have to do.
Thanks again.
futurama said:
Ah excellent thank you so much.
So can I flash straight to the newest 1.56 rom from my current version which is 1.19.61.1WWE on orange?
Or is there a stage in between I would have to do.
Thanks again.
Click to expand...
Click to collapse
Flashing from one HTC stock rom to another you don't need to use USPL or HSPL. But going to a cooked rom you do.
Answer to your query is it depends on route you take. If you go down the USPL route you'll need to follow cRaCKwHoRe's guide. Would take to long to explain and he as already done a very good tutorial on the subject. If you go down HSPL route, all you need to do is flash latest HSPL then 1.56 rom
That clears everything up. one last thing, which rom would you reccomend? I like the look of the enwer roms with WM6.
Thanks again much appreciated.
futurama said:
That clears everything up. one last thing, which rom would you reccomend? I like the look of the enwer roms with WM6.
Thanks again much appreciated.
Click to expand...
Click to collapse
I'm currently testing Dutty's V3.4. His V3.3 is already released but I'd wait for the new release hopefully in a few days. Both are based on WM6.1. Alternatively their is so many good roms out there. I'd also recommend Davideuck, EnergyROM & L26_THDV2.2 (Laurentius26). All very good roms by very good cooks. Best thing would be to try each of them and make your own opinion
thanks again mate, you are a legend, Ill post tonight to let you know how it went.
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
Does the phone really have to be unlocked before flashing a new ROM?
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
Does the phone really have to be unlocked before flashing a new ROM? I didn`t know that
yeeehooo got it all sorted and working!
Thanks everyone involved with XDA developers.
davemazo said:
Does the phone really have to be unlocked before flashing a new ROM? I didn`t know that
Click to expand...
Click to collapse
There are a few forms of unlocking but the bottom line is that you need to bypass the checking which is done in the flash process.
One way is permanat as done once no issues anymore - HSPL
Another is as and when you need - USPL.
Wiki has a walk through that needs to be upated but I thought still was useable.
Flash the new 1.56 shipped rom and then move on to cooked roms. (will help you by pass the greenscreen issue)
futurama said:
Please Help
I really am going crazy with this rom flashing stuff. I have read the wiki for 2 days.
I understand I need to CID unlock my phone before I can apply cooked roms. But after countless searches I cant find clear info on how to CID unlock my phone.
This really is a last resort, I have been rading for 2 days with no certainty of what to do next.
Thanks
Click to expand...
Click to collapse
Can you tell me were you got lost in wiki so that I can correct it in a more user frinedly version.
futurama said:
yeeehooo got it all sorted and working!
Thanks everyone involved with XDA developers.
Click to expand...
Click to collapse
Sorry to hijack your thread futurama but I am having the same problem. Could you let me know how you did it
Thanks HDuser. Not sure if you know where I`m up to but originally I flashed my Orange 1.19.61.1 ROM with USPL and then flashed Duttys 2.7 1.56 based ROM which has given me the green screen problem. An earlier poster suggested I flash Olinex HSPL 1.54 to cure the problem. The problem I am having now is the phone refuses to sync with the PC. I have tried Vista and XP, the PC does not hibernate or sleep or anything, the phone is set to not switch off. It will usually sync on first connection but after a few seconds it will disconnect and therefore HSPL is reporting as being disconnected.
I have tried the earlier HSPL and HSPL 1.56 (as the ROM in bootloader screen is reported as being 1.56 and SPL is 1.14). I feel I`m going round in circles and its only a matter of time before I brick the phone.
I have read and re-read the wikis but I am now just getting more and more confused.
davemazo
Look the best way to approach any problem is to go back to the roots.
Flash a stock rom, find your own stock rom and refalsh it, then take it from there.
Your post is missleading and I have no idea were to sart. One issue is your PC ist does not Hibanate, not or go into sleep mode, at the saem time you are saying that you can't sync. Sounds like you have other problems and those other problems are making you have problems with your device.
Thanks HDuser. Sorry for confusing you, but I am now totally confused myself, Basically though the phone does not sync with the PC, I have tried 2 PC`s, with Vista and XP.
But back to your point about flashing stock ROM, I have tried a link in the wiki to download the one I need which is Orange 1.19.61.1 but the link seems to be broken and I don`t know where else I can get it. It doesn`t seem to be on the Orange website or HTC.
HDuser said:
Can you tell me were you got lost in wiki so that I can correct it in a more user frinedly version.
Click to expand...
Click to collapse
There is a part on the black stone wiki that mentions I need to CID unlock my phone. It says you need to do this before you can flash roms, I felt it wasn't clear that, all I needed to do was flash HSPL in order to allow me to put new roms on.
This is what I did.
1:Flashed HSPL olinex 1.14.
2:Flashed HSPL Olinex1.56
3:Flashed MIRI WM6.5 10.0WWE
only part I had trouble with, my phone wouldnt let me flash the HSPL at first, I had to use a manual thing that you launch on the device the it lets you flash the HSPL.
futurama said:
There is a part on the black stone wiki that mentions I need to CID unlock my phone. It says you need to do this before you can flash roms, I felt it wasn't clear that, all I needed to do was flash HSPL in order to allow me to put new roms on.
This is what I did.
1:Flashed HSPL olinex 1.14.
2:Flashed HSPL Olinex1.56
3:Flashed MIRI WM6.5 10.0WWE
only part I had trouble with, my phone wouldnt let me flash the HSPL at first, I had to use a manual thing that you launch on the device the it lets you flash the HSPL.
Click to expand...
Click to collapse
It sounds as if you have it sorted now and everything working. As HDUser stated previously HSPL & USPL allows you to bypass the CID lock to enable you to flash new roms
Only thing I need clearing up, I can change my SPL back to the original version cant it?
Just incase anything goes tits up and I need to send it back
futurama said:
Only thing I need clearing up, I can change my SPL back to the original version cant it?
Just incase anything goes tits up and I need to send it back
Click to expand...
Click to collapse
Of course you can. All information you need including original stock radio's, roms etc are available in wiki to download.
Hi,
Just downloaded the new R3 UK firmware for my X1
I tried to Hard Spl my phone but it failed at 0%
But..
I thought id try flashing the firmware WITHOUT a hardspl using the microsd method.. and it worked :S is this normal?
everything seems to be working fine...
will anything happen to my phone in the future?
If it helps i was using 02 R2 firmware previously
Thanks
Adam
If I read your post correctly. You went and flashed an official SE Rom which you wouldn't need HardSPL for because they are released by SE and aren't custom roms.
You could of got the same by using the auto update service. You will only need HardSPL, is you try and flash any of the custom roms in this forum.
Well ive debranded by phone then...
and according to the turtorial flashing roms
http://forum.xda-developers.com/showthread.php?t=446070
you have to use HardSpl
I just wondered that if i didnt have a hardspl would this cause any problems with my phone.
That update would not have been available through SEUS because i have an o2 branded x1.
So am guessing there isnt going to be any problems with my phone? and if it ever breaks will it need to be flashed back to 02 R2?
Thanks
adamleerusse said:
Well ive debranded by phone then...
and according to the turtorial flashing roms
http://forum.xda-developers.com/showthread.php?t=446070
you have to use HardSpl
I just wondered that if i didnt have a hardspl would this cause any problems with my phone.
That update would not have been available through SEUS because i have an o2 branded x1.
So am guessing there isnt going to be any problems with my phone? and if it ever breaks will it need to be flashed back to 02 R2?
Thanks
Click to expand...
Click to collapse
Can somebody please send a message to the mods or topic creator or something to change the title to "how to flash CUSTOM ROMs?" This would make it much easier to understand, and less of a hassle for newcomers to flash OFFICIAL Roms.