Related
I don't know why I use HTC_Uni_SIM_Unlock_v1 with my phone !!!!
Now I can,t use IT. During the boot stops same seconds after the windowsmobile screen. It's impossible to contact it.
Read "Problem 5: Device shows NO GSM when booting" on the Common Upgrading Problems in HTC Hermes" wiki page. Solution is there for you
Maybe we should post a warning along with the Universal SIM Unlock tool instructions... such as
DON'T EVEN THINK ABOUT USING THIS WITH A HERMES!!!!!!!
There seems to be at least a couple of new victims every week!
I follow solution n°5 but I have a broblem with the bootloader. The Buttons are correct ?
Thanks
domomedia5 said:
I follow solution n°5 but I have a broblem with the bootloader. The Buttons are correct ?
Click to expand...
Click to collapse
Yes: SIDE OK + POWER + STYLUS RESET
I not be able to connect via USB the phone ! The radio rom 1.20.31.10 don't recognize my phone
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
is this the correct rom
thanks
Yes, this is the correct rom:
If you get a "ERROR 120: COUNTRY ID ERROR", do not disconnect the device, run MaUpgradeUt_noID again.
when I arrive to the window from ver. to ver. there are no description of the version !
what can I do
No problem, this is normal it is because the device is in bootloader mode.
how many minutes I had to wait
no more than 30min
It's stop from 30 minutes on cheching information on your device !?!?!
If the Hermes screen shows "Upgrade Radio Stack Please wait........." just wait until it finishes, if not, reset your device and put it back in bootloader mode, and run MaUpgradeUt_NoID again.
Make sure you've previously run the 'erase' commands in mtty sucessfully:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you can not success with radio upgrade, do a full rom upgrade using a rom matching your CID, start the upgrade from bootloader and make sure usb connections in activesync is disabled.
Ok...I have been through all the posts about upgrading etc. I still have a problem and I'm sure that I'm overlooking something....but I can't figure it out on my own. Here is what is happening (it does the same thing with every RUU that I've used...the DST fix...upgrading to WM6....etc)
1. I run the RUU and let it go through its routine (extract files, verify info on pc, etc.)
2. I check the box that says I have read the readme and click next
3. The next screen appears and it has the following steps:
Connect to the USB cable (check)
Establish an ActiveSync Connection (check)
Disable standby and hibernation on PC (check)
Make sure batter is > 50% (check)
Then I check the box and click next
4. I pick the update and click on the update button
5. I verify that I want to upgrade my phone from ROM verion x.xx.xxx to x.xx.xxx and click next
6. The program tells me that I am finally ready to update...and if I am sure I want to proceed to click next...so I click next
7. As soon as I click next...the progress bar comes up on my pc and my phone goes into standby mode (no bootloader...just standby). The progress bar never moves.
8. After a minute or two the RUU give me the ERROR [260]: Connection
9. I reboot my device and repeat steps 1-8
10. I reboot my device and my computer and repeat steps 1 - 8.
Now if I leave my device connected to the usb and close out the RUU after it gives me the ERROR [260], and then run the RUU again...when it is first verifying the information on my pc (before it asks any questions and before it tells me to connect my device) it will throw the device into bootloader mode. If I try to keep running the RUU while the device is in bootloader mode it give me the error that my device is not connected. I have tried and tried...maybe one of ya'll can help me. Thanks in advance
Chris
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
gerald_s said:
Some questions:
.) Is your desktop PC running XP or Vista?
If you have a firewall running, close it.
.) If you running Vista check this guide:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=23&Itemid=27
.) What updates did you try to flash?
.) Did you install Olipros bootloader first?
Click to expand...
Click to collapse
XP
No firewall
I tried to flash the WM6 from AT&T I assume its beta
and no did not install the Olipros bootloader
Ok...I think I found out how to do this...Ya'll can tell me if I'm screwing something up.
I go through all the steps listed above until it gets to the progress screen. When it gets there I manually put the the device in bootloader mode (Power, side ok, and reset). Once I do this...the progress bar starts moving. I will let you know if this works...
Hmmmm
Its not the way it should work but if it works its ok
You should have installed Olipros HardSPL first and then try to flash an official rom. If its working then something with your download is wrong.
What ROM is on there now?
Has the phone been CID unlocked?
Oli's CustomRUU is better, you may want to unpack the ROM and put the NBH in a folder with Oli's RUU and then do the upgrade.
BTW, gerald_s is right, you should not have to do that... what you may want to do is put the phone in Bootloader mode manually (while not connected to the PC), then plug in the USB, then start the RUU. That helps some people with 260 error.
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
You may be trying to flash a rom that includes the radio rom. What is your device? Is it possible that your device is a new x01ht with radio 1.14 and radio bootloader 0182? If yes, then you will get this error when you try to flash a rom with this method because during the flash it will be disconnected by the radio bootloader because it is not overwriteable. If you flash using the NBH file on the microSD, it will skip past radio and radio boot and just flash the other parts of the file.
mikebraeuer said:
I've got the same damn issue... it's driving me crazy. I had this occur when I flashed my Hermes100 from the stock version to Custel's. After about 15 starts and reboots it took. I'm now trying to get to Vp3G's 3.60 and it continues to give me the 260 error.
I am trying to figure out how to fomat my micro, but really hoping to find a solution over cable.
Hermes 100
IPL 1.04
SPL - 2.10 Olipro
Any suggestions?
Click to expand...
Click to collapse
If you are running windows XP, just connect the card to the computer, open MY COMPUTER, right-click the removable disk that is your microSD and then click format. Default in windows xp is to format using FAT32 filesystem which is perfect.
The thing is... if you dont know how to format a drive in Windows, should you be flashing your device yourself?
Which Solution???
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Wantoknow said:
I've got a Softbank X01HT with:
S/N: HT639
SuperCID <--- result of checking by mtty
IPL: 1.04
SPL: 2.10Olipro
GSM: 1.47.00.10
OS: 3.54.07 WWE
I tried to flash with new Schap 3.54c but the process would not be done coz ERROR 262 or ERROR 302. Fortunately, after failure of flashing, my device is still normal running. Then I tried to flash radio 1.51.00.10 but I got the same above. Once again, I have just tried to flash splash screen and I got the same result too. It mean my device can not upgrade anything !
Anybody here show me a solution that help my device to become a normal device, I mean it will be able to flash anything ROM as it would be! Don't tell me READ and READ, I had read so much . And don't tell me use MTTY again SPL1.01MFG, I think that is a final solution
Click to expand...
Click to collapse
Have you tried flashing with your microSD?
Kevbodian said:
Have you tried flashing with your microSD?
Click to expand...
Click to collapse
I forgot to tell that, I had flashed through extra memory card yet, and could be done!
But I wanna flash ROM against CustomRUU through MS Active Sync as I had used before. Can you help me
i have a problem very similar to Chris. when i check the box "yes activesync is syncronised", and then the progressbar shows up and the phone goes into standby.
i've turned standby of in powermanagement options.
my os is XP
i use active sync v4.5
and this is first time i try this.
i've read something about this bootloader, i can get there but then i cannot sync with active sync. so i kinda stuck.
have been searching the forums and this was the same problem as mine but i don't understand your solutions.
//KufrA
--Problem solved--
i did all things without activesync,
1. start phone in bootloader
2. do the install
3. wait 0% to 100%, and done.
is there a problem with active sync or why do i have to do anything with it at all?
Hi guys,
I need your help. You'd make me amazingly happy if you could solve my problem.
I have an Orange SPV C100 (french one) and I keep trying to flash wm6.1 (the one Blackdragon_860 has released).
My problem is : I can't flash that rom. The updating process crash at 4% and I get an error saying that the ROM is corrupted.
Do you have any ideas to help me ?
Here are some additional information taken from the Hard-SPL And Soft-Spl walktrough :
1. Copy spl.nb, spl.lnk and jumpspl.exe to the root of device
Click to expand...
Click to collapse
I've done that alright
, hold camera and launch spl.lnk -
Click to expand...
Click to collapse
I've done that too.
you`ll see the white screen
Click to expand...
Click to collapse
I have no white screen. Instead a file named JumpSPL.txt is generated... Here is what is inside :
-----------------------
Comandline is: 0x10000000 \SPL.nb
SPL File: \SPL.nb
Jump Address: 0x10000000
kmode is 0
SPL file size: 524288 bytes
3. From the flasher folder run ROMUpdateUtility.exe and follow instructions to flash the Hard-SPL if needed. or you can flash *ANY* oxygen rom
Click to expand...
Click to collapse
I've done that too. I put RUU_Signed.nbh from wm61OxygenUpdate1.rar in the same directory than ROMUpdateUtility.exe
Before the flashing process itself, ROMUpdateUtility.exe tell me I going to flash the image version from 1.7.74.1 to : 1.01
Then I have a rainbow screen which says :
ONBL : 1.07.0000
SPL : 1.07.0000
Oxygen : IU
The flashing process start, then crash and 4%... Saying that image file corrupted.
One last information :
I got the same error with other ROMS. Here the list of what I already tried :
Blackdragon_860's rom, released the 11-05-2008
Standard rom, the one that comes with Soft and Hard SPL (weight about 641Ko)
A Russian rom, taken today from zfree (here)
I didn't tried the chinese one. But as edgeofthestring has eventually the same problem than mine, I not will go for this rom.
I tried to be as complete as possible... I truely need some help.
Plz plz plz hrlp.
Thx
Guigoui
Try first flashing this rom:
http://www.megaupload.com/nl/?d=6B0FDY24
After this hard-spl and than flash any rom you like
Always use rom loader from hard-spl and before flashing rename rom to RUU_Signed.nbh
i also tried to flash the file posted by you but after 4 % the phone reboots and the setup gives me the: " invaliv vendor id " message
Default
ok. may it works when you do it like this:
1. restart your phone
2. Copy spl.nb, spl.lnk and jumpspl.exe to the root of device
3. restart phone, don't connect to your PC!
4. open total commander, hold camera button and launch spl.lnk
5. Do you see a white screen? if yes proceed if not it has no
point proceeding, flashing will fail anyway!
6. Now connect your phone to your pc using the usb cable
7. From the flasher folder run ROMUpdateUtility.exe and follow
instructions to flash the Hard-SPL
8. After flashing Hard-Spl, to avoid reflashing, use always use
flasher from hard spl and rename the desired rom to flash to
RUU_signed.nbh
Hope this will finaly work for you!
i have tried it, i have the wm6.1 chinese version rom and the hard spl is not working at all in this rom, i have tried it with total commander and after the white screen appears and i connect the phone to the pc it is nor recognized by the pc...
thx nemphis for helping me... but it just don't work.
Believe me I'm not numb. I can read and use my little brain... I think I tried everything (including throwing my device to the other side of my room). There is something that keep my device from displaying this f*****g white screen.
Just for the record, I repeat, I have a french blocked orange C100...
If someone has got in the same problem and finally sorted it out, plz share how.
Nemphis, thx again but I doubt I will ever have wm6.1... Anyway I give up, so I guess I will never have wm6.1...
By the way, I also tried the rom you advised but as you so rightly said "if not it has no point proceeding, flashing will fail anyway!".
Thx you all...
c u...
by by
Is your phone sim unlocked also?
When reading through these forums there also are people saying you still need this: http://www.imei-check.co.uk/
Or ask your operator for the sim unlock code, they should give it when your phone is more than 1 year old.....
Phone simunlocked today... gonna try again tonight... Hope it will eventually work this time... Last hope anyway...
guigoui said:
Phone simunlocked today... gonna try again tonight... Hope it will eventually work this time... Last hope anyway...
Click to expand...
Click to collapse
Was your phone "app unlocked" before begining ? I would assume it is necessary, but won't pretend I'm a guru...
Christophe - Lyon - France
@guigoui :
I had this same, white screen didnt appeared .. but after unlocking using this way: http://rapidshare.com/files/105133496/Unlock_HTC.rar.html you'll see it (after runing SPL.lnk with camera button pressed) all is working !!!
I've WM6.1 !!!
Thanks!
This sounds pretty good vovakk... I'll test your file tonight (because I had no white screen after having my device simunlocked)
I can't to stand waiting until tonight...
It WORKED !!!! Now I have WM6.1 !!!
Ok so here are some additional information that could be useful.
Be sure you have .net framework 2.0 or newer before starting the unlocking process (the file shared shared by vovakk) otherwise you would be stuck at the second step.
When at step 5, I'm not sure which profile is required but, for me, it worked with "No security".
Once you've done step 5, you'll get THE white screen when laucnhing SPL.Ink (I confirm). You can start flashing.
I've flashed several rom as nemphis told me to, and it worked. Here is the list in the right order, with some notes :
1. http://www.megaupload.com/nl/?d=6B0FDY24 (given by nemhpis) : takes about 2-3 minutes, when done, I believed that my device was dead because it took a while before the PIN screen showed. Don't panic, just wait.
2. http://rapidshare.com/files/65732449/hspl.7z.html (the original Hard-Soft SPL - created by sp3dev) : extract, don't change anything, just launch RomUpdateUtility.exe. Flashing process takes less than 1 second
3. http://rapidshare.com/files/114457795/wm61OxygenUpdate1.rar (THE Windows Mobile 6.1) : In the RomUpdateUtility.exe folder, just replace the original NUU_signed.nbh by the one inside wm61OxygenUpdate1.rar. Launch RomUpdateUtility.exe. Eveything else is like 1. except that my device rebooted fast without being stuck a while on the windows mobile logo screen. The device reboot, you enter your PIN and then welcome to WM6.1 !
Hope someone would find interesting to read my so long posts...
I thank you all for your patience and help... I wouldn't be able to do it by myself.
C you
hey GuiGoui can you upload this file here or Rapidshare please. Megaupload is way tooooo slow. RUU_OxygenWM5_1.5.401.2_R3_4.1.13.28_02.67.90_HTC_EUR_Test.exe
thanks
I can't.... 8Mo limited...
guigoui said:
It WORKED !!!! Now I have WM6.1 !!!
Ok so here are some additional information that could be useful.
Be sure you have .net framework 2.0 or newer before starting the unlocking process (the file shared shared by vovakk) otherwise you would be stuck at the second step.
When at step 5, I'm not sure which profile is required but, for me, it worked with "No security".
Once you've done step 5, you'll get THE white screen when laucnhing SPL.Ink (I confirm). You can start flashing.
I've flashed several rom as nemphis told me to, and it worked. Here is the list in the right order, with some notes :
1. http://www.megaupload.com/nl/?d=6B0FDY24 (given by nemhpis) : takes about 2-3 minutes, when done, I believed that my device was dead because it took a while before the PIN screen showed. Don't panic, just wait.
2. http://rapidshare.com/files/65732449/hspl.7z.html (the original Hard-Soft SPL - created by sp3dev) : extract, don't change anything, just launch RomUpdateUtility.exe. Flashing process takes less than 1 second
3. http://rapidshare.com/files/114457795/wm61OxygenUpdate1.rar (THE Windows Mobile 6.1) : In the RomUpdateUtility.exe folder, just replace the original NUU_signed.nbh by the one inside wm61OxygenUpdate1.rar. Launch RomUpdateUtility.exe. Eveything else is like 1. except that my device rebooted fast without being stuck a while on the windows mobile logo screen. The device reboot, you enter your PIN and then welcome to WM6.1 !
Hope someone would find interesting to read my so long posts...
I thank you all for your patience and help... I wouldn't be able to do it by myself.
C you
Click to expand...
Click to collapse
How did it work............ i ended up lockin my phone it was unlocked before... now no application works... anymore it say this application is not have signed certificates..... PLZ ANY1 HELP I DONT EVEN KNOW HOW TO HARD BOOT THIS HANDSET..... I NEED URGENT HELP PLZZZZZZZZZZZZZ...
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Update - I just tried this:
http://forum.xda-developers.com/showthread.php?t=326953
but without success. I get an Error [260] and the entire process stops.
Anubis1965 said:
Hi All,
I had on my Athena the previous Michy Rom (2.04 with SPL 1.20) and when I saw the new version (4.00 with SPL 3.5):
http://forum.xda-developers.com/showthread.php?t=411371
I decided to install it. Like an idiot, I did not pay attention to the fact the SPL was different... I started the flash process and when I realized my error, it was too late.
The upgrade did not completed (as expected :-()) and now I am stuck with a corrupted bootloader screen, so I can't proceed (the device does not boot so I can't access ActiveSync).
Any way forward? Thanks for any hints!
Anubis
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showthread.php?t=405814
lakeman said:
look here
http://forum.xda-developers.com/showthread.php?t=405814
Click to expand...
Click to collapse
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Anubis1965 said:
I have seen that thread. But the problem is different. I have also tried to reload a vanilla WM6 ROM but I cannot go past the corrupted bootloader part...
Anubis
Click to expand...
Click to collapse
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
If you see in bootloader mode ID showing somenting different than ATHE100 the solution is HERE http://forum.xda-developers.com/showthread.php?t=405814
I had the same problem! whell restart your pc and then connect the device to it. now start flashin an spl 1.20 rom. i did it and it worked! I hope i works for you too.
Cheers, Hirad
lakeman said:
When you are in bootloader(three coloured screen) what do you see?
remove sim and sd card , hold camera button all the way in and press the reset button(on the back close to the battery cover)
Click to expand...
Click to collapse
Thanks - already tried!
When I reset/hard-reset the phone (tried many ways) I see a garbled boot image (with random pixels here and there)... It is definitively not the usual bootloader with the information about the various ROM components and the "USB" text at the bottom.
Anubis
Solution!
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
You are right and this is what sergiopi and I were referring to , specifically this post
http://forum.xda-developers.com/showpost.php?p=2154726&postcount=33
We were refering to the whole thread so you could learn the background.
However you are incorrect in your advice about how to enter bootloader
All you need to do is hold in the camera button and reset
spoonter said:
I managed to do the same thing - had an old AP ROM with SPL 1.2 already installed then earlier today I tried to upgrade to the new Mitchy R4 SPL 3.5. I thought my Ameo was bricked, but after some pain it is now working again.
Here is what I did:
1) Enter bootloader mode using the very tricky Camera+Volume+Reset method.
2)
Follow exactly the steps in post 33 here:
http://forum.xda-developers.com/showthread.php?t=387454&highlight=mtty&page=4
Note, I'm running Vista so to get the USB option to show in MTTY, I had to first open "Windows Mobile Device Center" in Control Panel then disable the USB.
Also, note you should find your MAC under the battery flap.
3) Now all you need to do is reset, enter the bootloader mode again, and re-try the ROM (PS, make sure you use the correct SPL version!
Hope this helps.
Click to expand...
Click to collapse
Thanks - you are giving me some hope! I am on a business trip now and my Athena is at home, but I will try that as soon as I am back
Anubis
I've been reading around and trying to get my head around how to get this going but felt I should just ask. I want to put Dynamics 7 on my phone but I don't know where to start? Could somebody help me out? Thanks for at least reading.
I take it you have a Titan? You really will need to study up on flashing before attempting to do anything to your phone, HSPL will be the first thing to consider and then you will probably need to use the Gold-Card method to successfully flash your chosen ROM,
HSPL Thread here: http://forum.xda-developers.com/showthread.php?t=1684912
Best of luck
I'm trying hspl and its not working on ruu. It cant get a connections why is that?
Also: I found these intstructions somewhere else. Is it safe to follow?
1) Turn off your HTC Titan.
2) Turn on your HTC Titan, enter SPL mode by doing so.
3) Unrar the compressed file DFT__HSPL_WP7SG1.rar
4) Go into DFT_HSPL_WP7SG1\1_SPL205\TITAN\ inside the directory where you extracted the file DFT__HSPL_WP7SG1.rar
5) Run ROMUpdateUtility.exe
6) Wait till the precedure finish to install SPL (0% -> 100%)
7) At the end of the procedure the device will reboot.
8 ) Enter SPL mode, or turn the device off and enter SPL mode again if you didn't make it in time.
9) Go into DFT_HSPL_WP7SG1\2_HSPL\
10) Run SFT_HSPL_WP7SG1_INSTALL.exe
11) Install HSPL following the istructions on screen.
12) At the end of the procedure the device will reboot.
13) Enter SPL mode, or turn the device off and enter SPL mode again if you didn't make it in time.
14) This time you should be able to read HSPL2.5.160015.3 and CotullaH at the top of the SPL screen
15) Unrar the compressed file DFT Eternity 24 langs Freedom V1 Pearl Edition.7z
16) Run ROMUpdateUtility.exe
17) Wait till the precedure finish to install the custom rom (0% -> 100% , it will be slower this time)
18) At the end of the procedure the device will reboot.
Personally I would stick with the information you find on this site, Many happy custom ROM users out there will agree, Read first, Understand, Then attempt if you are 100% sure, Otherwise you will be asking how to un-brick your phone.
I understand, then quick question on RUU am i doing task 28 or 00? It's not giving me a country error it just says my phone is not connected.
Sounds like you are using the Advanced ROM Update Utility? Are you sure this is the method recommended for flashing your chosen ROM or HSPL even? Read the HSPL thread and it says if you cannot establish a connection then use the Gold Card method, Think you need to do a bit more reading.
I asked because it says " If flash fails with error "Country ID error" you should use gold card to flash. Im not getting that error. just no connection.
Edit: when i put in spl mode it connects then goes to 4% then give me error 294. is that the Country Id?
Cloudsdabomb said:
I asked because it says " If flash fails with error "Country ID error" you should use gold card to flash. Im not getting that error. just no connection.
Edit: when i put in spl mode it connects then goes to 4% then give me error 294. is that the Country Id?
Click to expand...
Click to collapse
Before you do anything else, do you have a USA AT&T Titan or EUR Titan? This is very important
It's a USA I just read about having to gold card US ones. Already ordered everything just wish I didnt have to go through all this trouble.
What have you done so far? I guess since you "have ordered your stuff", nothing yet. If that's the case, make your gold card with the EUR 2.5 ROM (get it from here) and before you do anything else, flash using the gold card method with this ROM.
That will de-brand your Titan (meaning take it away from AT&T's clutches!). Supposedly, if you have a USA AT&T Titan you must do this first or be stuck like the rest of us with 2.5 SPL and no HSPL and no way of getting a custom ROM on our device until this $#!7 is fixed.
thanks so much! Yeah ill try it haha.