Am having a problem with unlocking a Hermes using the SIM_CID Unlock version 3A
I appear to be stuck in a loop with the unlock process. I appear to have got as far as having installed OliPro (while still being at bootloader 1.01) but keep getting error 262 UPDATE FAILED
I can then recover to the tri-colour screen and process as far as RECOVERY SUCCESSFUL
But I cant get as far as updating the radio or whatever else it unlocks towards the end of the process and no new ROM loads (if that is what the unlocker does?) The percentage screen appears but doesnt progress at all. Then I get ERROR 262 again.
Is starting to the bootloader screen a sign of a bricked Hermes? I can get SERIAL to show and can get it to change to USB on that screen when I plug it into a computer but cant get any proper communication with the unit from the computer with that screen in place: ActiveSync obvoiusly wont start. As I left the 3A unlocker, it said RECOVERY SUCCESSFUL but does that necessarily mean that I have a brick now? I thought that the installation of olipro by SIM_CID unlock version 3A means that the unit is now hard-unlocked?
(Yes, I did try Hard-SPL-V7.zip but cant set up any communication between the exe file and the tricolour screen)
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
I thought that tricolour screen meant that it is ONLY starting in bootloader mode?
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I am a bit lost: How do I get into bootloader mode? I thought that it starting in the tricolour screen meant that it had started up in boot loader mode? Is there some combination of pressing buttons and 'on' switches like on my Blue Angel?
As it appears to have got stuck in a mode while in an upgrade process which didnt work when this error occurred, when I get it started, what should I flash to get the bootloader updated, the SIM and CID unlocked so that I can choose which ROM to flash? Should I continue with the SuperCIM_CID unlock or Hard SPL?
I have fully unlocked another Hermes before and have been playing around with ROMs but this one seems to have worked out differently: I was under the impression that loading OliPro meant that it was unlocked?
(Sorry about that answer: I will try RUU_Unwrapper.exe again)
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I did what you said and immediately I unchecked the tick in USB, I heard that the computer was establishing communication with the Hermes
But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??
V7 still wont run but v3A still will!
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: This device both will and wont coopeate at the same time. But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE on error 260\.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: (Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
(Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
The computer IS communicating with the device (as I said it does give the 'ding' showing that the computer knows it is there) but it wont hard reset! It just goes straight to the tricolour screen immediately on startup. Even using a three hand method of pressing both buttons, pushing the reset in and putting the battery in at the same time gave the tricolour screen. And Windows Explorer cant get into the device. It seems to see it but there is no tree at all. So I cant use the Post 1160 method to flash from an SD card.
Even more baffling, i have now flashed a stock ROM successfully and v7 STILL wont communicate with the Hermes!! In desperation I even moved the directory to the root of C: Are some of these devices encrypted differently from others? So suddenly it boots properly and I immediately did a hard reset and erased everything and now Guess what? It hangs at the Windows Mobile screen! Needing a hard reset all over again
Should I just keep on trying Super SIM and CID unlock again and again until it works? (I assume that I have no longer got OliPro on it, though it does show a SPL of 1.40) There must be a way of unlocking this unit but this total non-cooperation doesn't seem to be covered in the Wiki. Is there a version of the Hermes like the Wizard which is more difficult to unlock than the others?
Sorry to reply again when no one gave any ideas on my last posting but I am wondering, horror of horrors, whether this might be a hardware problem?
I am now stuck at the tricolour screen ( 1.01, SPL 1.40.Olipro)) which turns on whenever I put the battery in. Connecting to the computer doesnt make any difference and obviously I keep getting ERROR 260 which seems to be a connection error meaning that the computer either isnt connected to the device (or that some software is conflicting somewhere, which is unlikely as flashing to the stock ROM did work before I tried to run V7 again)
Is there any possibility that running SuperCID&SIM unlock (which has never completed) caused all of this and is there any rescue procedure or should I just assume that this is a hardware problem now (or should I do a fresh posting)?
Is it inherently suspicious that tricolour turns in when I just put the battery in AND that even though SERIAL changes to USB on the Hermes, running the v7 hard update utility causes ERROR 260? [Or cant you run V7 when you already have OliPro installed somehow?]
There IS communication: Though I reported in my last posting that I could flash the Cingular ROM, flashing to the Cingular ROM now gets consistently stuck at 14%, sometimes with an ERROR 264!
Related
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
PuckX said:
Ok I have searched the forums pretty hard the last couple of days, and I have not found anyone that has the same issue as mine. It's not too big of a deal as everything operates but it is an issue all the same. This is all of course after I have succesfully ran HARD SPL v7 and upgraded to Black 3.0.1. Basically I decided to use POF's SuperCid Unlocker 3a (yes I know if I had HARD SPL 7 then why go through the trouble of Unlocking my CID, let's call it a need to mess with things) and everything went succesful. Then after the fact I read that it is still good even if you have SuperCID to upgrade the SPL to 2.10 and have read some peoples signatures and it appears that they have succesfully done this. Here is my issue;
When I run the CustomRUU it autodetects my SPL no problems, HARD-SPL? is checked, everything seems to go fine until it gets to the boot loader, once it is there, the progress bar pops up, zings to 100% and then reboots, cool? no because it didn't actually upgrade anything everything is still the same. Ok, so I tried the format SD card and rename *.nbh file to HERMIMG.nbh and put only it on the card, when I go to bootloader it does a quick flash to the screen like it recognizes the image but then goes to boot loader and nothing changes (the flash is so quick I can't even read whatever message it may be showing). I have tried pretty much every flashing method I can come across. MTTY wont recognize that I even have a USB port so I have been unable to try that method. So two questions:
I have SuperCID, so should I continue to even bother to get to 2.10?
If so, is there anything else I can try? Or do I need to get MTTY to work and try that as that is really the only thing left?
Thanks for any and all help anyone can provide.
Click to expand...
Click to collapse
Did you look on the bootloader screen to see if your SPL changed? To my knowledge the only place you can see it is in the bootloader screen (tri-color screen) And flashing Olipro's Hard SPL only takes a couple seconds so it sounds to me like it is working as designed.
Or are you trying to flash a different rom? If so then try deleting everything you have in the directory you are using and re-downloading. You might have over-written the file you want to flash with the HardSPL one. You shouldn't be using the hard spl wrapper to flash a rom in any case, i believe that is mentioned in bold at the top of the Hard SPL thread.
Ok nevermind I was able to get it to work and MTTY was the answer. This is the 2 steps I had to follow:
From the thread: http://forum.xda-developers.com/showthread.php?t=291723
sp3dev said:
Hi. I`ve finally found the way to connect mtty and run rom update utility in Vista. tested on rtm 6000.
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
Click to expand...
Click to collapse
Then Do This:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG
Flashing SPL-1.01 MFG instructions
Put hermes in bootloader mode (side ok + power button + softreset)
Connect Hermes to computer using USB cable.
Open mtty.exe, select "USB" from the dialog box, then hit Ok.
Hit enter twice and you'll see the "USB>" prompt.
Then type these commands: (note the use of 'lnb*s*')
USB>task 32
Level = 0
USB> lnbs SPL-1.01.nbs 50020000
USB> task 8
Device will reboot after this, with bootloader 1.01-MFG on it.
Once I was able to do all this I was succesfully at 1.01 at which point I ran the Custom RUU and upgrade to 2.10 without issue. Once again all right there in the forums, just had to be pieced together to find a solution.
Thank you all for all your dedication to these projects, you make owning a PDA more fun than I am sure was originally intended. I love messing with things.
I have also attached the necessary files from the original posts to perform this for anyone else facing this issue.
PuckX said:
Ok nevermind I was able to get it to work and MTTY was the answer.
Click to expand...
Click to collapse
Cool, glad you got it working
I'm following Mr Vanx's guide for upgrading my Jasjam from WM5 to WM6, but am having trouble with flashing the new bootloader onto the device. It's a second-hand telstra imate. I just bought it off ebay a couple of weeks ago and need to upgrade it to get it to read sdhc memory cards. I can't get it to connect to optus' (my mobile contract provider) mobile internet either, which I did via GPRS on my old phone. I'm hoping by upgrading the OS I can remove all of Telstra's code so It's not trying to connect to telstra's 3g network when I start the web browser.
When I get to the last step of the Hard-SPL installation, where the "updater will flash the new SPL and then restart your device (this will take generally less than a minute)" , the phone restarts almost immediately after clicking yes when prompted on the phone. The screen quickly goes to the bootloader screen, which says
"herm 100
IPL-SSPL by Des
Herm 100
SPL-1.09.ds"
The PC says that it can't connect to the phone and I should check the cable, which is still connected
The phone stays on the bootloader screen until I hit the soft reset, and WM5 boots like normal.
Has anyone else had this happen?
Yup,
Same problem over here. I had the problem before. But i fixed it! The only question is how did i do that? short term memory.
I'm trying to solve the problem. If its solved i will let you know.
Till then hang on
I've been trying again today. Still getting the same result, though I figured out if I just leave it when it gets to the bootloader screen, the pc I'm installing from eventually comes up with Error 260.
I'm thinking now that the XP firewall may be the issue, but I'm having trouble disabling it because it's managed by "group policies" (it's a work computer). I'm going to try either finding out which port to unblock, or starting the pc in safe mode so I can disable the firewall altogether.
I fixed the problem with the following softwaretool Hypercore. Just intergrate the Hard spl from olipro. After this the error dissapears.
I constantly get a communications error, and it never leaves 0% on the status.... No clue on what could be wrong... Anyone have a suggestion? I've looked on all the faqs and didnt see anything else I could try.
ghostyroasty said:
I constantly get a communications error, and it never leaves 0% on the status.... No clue on what could be wrong... Anyone have a suggestion? I've looked on all the faqs and didnt see anything else I could try.
Click to expand...
Click to collapse
That means you didn't successfully unlock.
If you put your phone into bootloader, it needs to say 1.20 Olipro, not 1.10, which it probably does.
Retrace your steps on the unlocking process.
- DogGuy
When I put the phone into the bootloader, it says 110... and I unhook and rehook up the usb cable, and the activesync doesnt detect the titan anymore.
I then use the exitbl program to reboot the device, and then continue once my titan reboots.
Then I get the 262 connection error after the status shows 0% on both the titan and my computer for a while.
Leave your phon ein bootloader mode and run the unlocker. As long as the screen says USB it should work.
ghostyroasty said:
When I put the phone into the bootloader, it says 110... and I unhook and rehook up the usb cable, and the activesync doesnt detect the titan anymore.
I then use the exitbl program to reboot the device, and then continue once my titan reboots.
Then I get the 262 connection error after the status shows 0% on both the titan and my computer for a while.
Click to expand...
Click to collapse
Thats where you went wrong. You aren't done with the unlocker, and *do not* run exitbl until after the RUU has already run. The RUU is actually installing the unlocker, you are just sitting at a temporary bootloader to allow the 1.20's RUU to actually run.
edit:
So, run unlocker, do the disconnect-reconnect when told, when the RUU comes up, you need to follow it all the way through to completion, flash and all, and you'll end at 1.20 Olipro. Then you can finally use the exitbl. If the RUU does not come up, check the directory \TempTytn\ and run the romupdateutility.exe thats in there.
Good luck,
- DogGuy
Thanks DogGuy.. So I run it even if Activesync doesn't show a connection once I unplug and replug the titan???
As long as when you reconnect the usb cable the bootloader itself says USB at the bottom, you're just fine.
- DogGuy
Thanks, I got 1.20 now... So I'm off to try a rom.. Any suggestions? I'm thinking about dcd's version
can someone post instructions to get into bootloader mode? thanks
whoa, DogGuy posting at xda!!!!!
It's DogGuy to the rescue
WOOOOHOOO!!!!
I'm glad I read this first.
I will probably try this over the weekend.
BTW will this work on Vista?
same Problem
I ran into the same problem...
I used a different USB port and either turned activesync on or off... can't remember and did the unlock again. It detected the phone differently on the other port for some odd reason.
wow another one from dcd
Hi Folks,
I'm stuck in the tri-color screen for bootloader 1.06.
I have DCD 3.2.0 w/3.42.02 radio on the XV6800 and was trying to upgrade to radio 3.42.30. My system is Vista 32-bit.
I ran the Titan Relocker and it put SPL-1.06.0000 back onto the device and was planning on then putting 1.2 onto it.
Running titan_exitbl.exe says "Cannot open USB port. Please make sure, that USB connection in ActiveSync is disabled."
Unfortunately it is now stuck and even after ending the Sync Center service I can't get titan_exitbl.exe to pull it out of the Boot Loader.
Ideas? Thank you!
I could fire up an old XP laptop and try it from there.
Loaded ActiveSync 4.5 on an XP laptop, disabled USB connections, ran titan-exebl.exe and the device is booting now.
I'll continue on and see what else I can screw up.
Loaded SPL 1.20
Loaded 3.42.30
Loaded SPL 2.40
Device is back to working! Off to see if GPS is back after being lost with 3.42.02.
titan-exebl.exe
Where can I find titan-exebl.exe? Google doesn't turn up any results other than here?
titan_exitbl.exe
Never mind... just located it on my own hard drive!
Cheers!
Stuck on Bootloader
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Try changing your spl back to 2.40.
Throwing it back into the tri color screen again and flash the sprint stock 3.35
But put it on the root of a fat32 formatted micro sd card in the flavor of under 2gb.
Just run the exe from your computer it will extract the files from the exe to some location on your computer, normally the ruu update folder.
There will be a ruu_sighned.nbh file locate it and copy it to the fat32 formatted card rename it TITAIMG.nbh
Let the phone boot into the bootloader and it should detect the file on the sd and update the rom for you, by stating loading ......
Then will prompt you to update press power key.
Sense you are not on sprint don't let the first time custimizations run ... pull battery once you get to your mobile today screen on first boot...
Use active sync or the sd method to update your rom to whatever you wanted originally.
Most full updates from carriers the ones that flash both the radio and rom will run regardless of the boot loader thats on the device.
Happy flashing
Just thought I'd toss in here that GPS does work, but I have to use GPS Viewer to get a lock on the satellites first.
softwind said:
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Click to expand...
Click to collapse
please i have this problem how to fix this?
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
drewcam888 said:
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
Click to expand...
Click to collapse
Thanks!!! Ok, i cant remember eactly what is the v radio but i think 3.35 or 3.42 i cant remember exactly it's one of these. the SPL 1.06 Locked i cant unlocked i cant use titan_exitbl.... the SD update doesnt work stuck on loading.., i cant update from pc stuck 0% then Recovery Error help me. I My phone is bricked? Sorry for my english....
Did you try to install 2.4 unlocker?
drewcam888 said:
Did you try to install 2.4 unlocker?
Click to expand...
Click to collapse
Yes, i try from SD and nothing stuck on loading... from windows with RUU nothing 0% stuck and then UPDATE ERROR[262] now i don't know to do
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
drewcam888 said:
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
Click to expand...
Click to collapse
Ok, but how run from windows? If i cant connect via activesyncs the phone is on SPL mode i cant out of that and the msdos windows say "No device conected" when press enter from windows i cant unlock. Any idea? I'll try 2.47 but how run from windows with the phone en SPL Mode?
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
drewcam888 said:
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
Click to expand...
Click to collapse
Look i cant run Hard-SPL-MFG (Olipro 2.40 Unlocker) because when i run the Bat Or MSDOS Windows say "No device connect" question me if i want retray copy the file.
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
drewcam888 said:
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
Click to expand...
Click to collapse
No luck, method A SD Card Loading.. then cheking... then show a number corner 00028002 and say down Not allowed.
Method B, via PC and RUU then ERROR INVALID VENDOR ID.
Any idea? Thanks bro.
I think my phone is bricked... noway load the rom... i've tried load bootloader unlocked via SD last option and nothing!! damn this is so