Please help..
I have the HTC P4000
I have downloaded these before I started from here:
http://www.lifesnotsogood.com/dcd1182
Bootloader: titan_SPL_2.40-olipro.exe
Carrier file: dcd Telus Carrier 20080706.cab
Radio: Titan Radio ROM 3.42.30.rar
Rom: dcd_titan_3.2.0.exe
Kitchen: dcd_titan_kitchen_3.2.0.rar
Then started to follow this:
http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
I. Prepare with EPST:
- Done
II. Install the correct bootloader
- I did this and it told me I had 1.04, so according to the instructions, I ran the titan_SPL_2.40-olipro.exe file and followed its instructions..
Got to the screen where it said to uplug and plug back in, except when I plugged it back in, it never resynched.. Active synch stayed grey.. But I followed the instructions anyways, and it said that it flashed successfully.. (Even showed the bar on my phone go across, but very quickly..)
Except when it restarted, it kept going to the coloured bootloader screen, which says:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
And then sits there and does nothing..
So I went to:
III. Radio Upgrade
-> B. Change the radio with a full carrier Radio & OS ROM flash
--> B. Flash via the USB
It again ran me through that same grey screen, but still no active synch connection. Now when I restart my phone, it shows the HTC screen, with this info:
M 09
P DCAAXAM-4350
R 3.42.30
D 2.13
And some other set of numbers that I can't read..
And then it goes to the TELUS screen and it sits there. I can still go to the bootloader fine if I use the POWER-CAMERA-RESET option, but my phone doesn't start. It stays on the TELUS screen.
What do I do now. Have I bricked my phone?
Boot to the bootloader, and you should see the bottom of the screen go from Serial to USB mode when you plug in the mini USB cable.
You should be able to flash at this point using the RUU.
If you are still having problems then, you need to go into ActiveSync, and uncheck 'Allow usb connections'...
You updated the bootloader and radio, but you didn't update the ROM. Just go into the bootloader and flash the ROM now and it should be fine.
He doesn't need to uncheck the allow usb connections..
Ok, now it says:
Verify that you want to update ROM version from:
Image version: (blank)
to
Image version: 3.42.30
I clicked next, it showed the progress screen.. Went to 8% then my P4000 restarted and this error came on my RUU:
ERROR [328] INVALID COMMAND
P4000 is still stuck on the TELUS screen..
That's not the ROM, that's the Radio. You need to flash the ROM. Run dcd_titan_3.2.0.exe with your phone in bootloader mode and connected via USB.
Cool, now I'm in WM 6.1, waiting for customization.. I want to do this right.. Thats the next step?
Thanks alot man..
Make sure you install the Telus Carrier cab now.
This is gonna sound dumb..
But how do I do that? The FAQ doesnt mention anything about this..
I've extracted "dcd Telus Carrier 20080706.zip" and see a few files..
Do you know how to install a cab file (application) on your phone?
Yes I do, but I'm in the custmozation screen.. From what I know, I shouldn't be continuing past this..
No, it's only when flashing the stock Sprint roms that you have to worry about customizations. It's fine when flashing a custom rom.
Set it up, when it boots to the today screen, copy dcd Telus Carrier 20080706.cab to your phone, then run it to install. Then soft reset.
Ok I continued by it anyways.. and now im in, I installed the carrier cab file using my microsd, restarted..
Doesn't seem to be activated or anything.. I dialed a # it says to press *611 to activate,.. that doesn't work, was there a diff thing i'm supposed to dial?
Ah, I got it.. its *22803 Restarting..
Cool, now I'm up and running.. But I need the kitchen now right?
I followed the FAQ, and it says to do this:
V. Kitchen
Run BuildNB.bat to execute BuildOS
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
When I run BuildNB.bat it comes up with an error saying:
"Windows cannot find RomUpdateUtlility"..
240sxer said:
Cool, now I'm up and running.. But I need the kitchen now right?
I followed the FAQ, and it says to do this:
V. Kitchen
Run BuildNB.bat to execute BuildOS
Hit the play button when you have selected your choices.
Exit BuildOS once it has completed.
Let the batch file complete its jobs.
When I run BuildNB.bat it comes up with an error saying:
"Windows cannot find RomUpdateUtlility"..
Click to expand...
Click to collapse
Uhh... are you just flashing to DCD 3.2.0 ROM, or are you trying to flash your own version (kitchen) of that ROM? If you just want to flash to his ROM, then you're done.
Cool, now I'm up and running.. But I need the kitchen now right?
Click to expand...
Click to collapse
No, you're all done. You either install the premade rom (which you did) or a rom you cook from the kitchen. One or the other.
ya, do what he ^^^^^ said...
Thanks guys, I really appreciate it. All is well now. It's just that the FAQ wasn't that clear.
Related
Apparently, I'm pretty stupid.
I just got the Cingular 8525; I have spent two hours on this site.
Things I've noticed:
One page says go into bootloader; one page says not to allow usb connections.
I do not know if I am supposed to have my non-Cingular SIM card already in the phone when attempting to do anything.
I have seen connect via USB and use mtty (with what settings do I use when I click on USB from the dropdown menu (if any) and do I connect with mtty via USB in bootloader or when the phone has booted into Windows 5.0 and again what about the non-Cingular SIM card?).
I have flashed my computers BIOS several times but I do not understand how to flash this phone based on the myriad of instructions all over this site (and RFTW did not help which is why I am here with 40000000 questions).
The steps to go from SPL 1.06 to an unlocked SIM/CID phone are?
Things I do understand:
I have SPL 1.06 (I know this from bootloader).
I must downgrade to 1.04 from 1.06 then run the upgrade to 1.06 from the Hermes Upgrade wiki page (I already downloaded all of the Cingular files).
Thanks in advance for any clarification.
I unlocked my 8525 last week, I had bootloader 1.06 so I downgraded to a ROM with boetloader 1.04(you can find it here http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades ).. then just follow the instructions in the zip file you downloaded(i used HERM_Unlock_v2a), which are:
1. Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 this unlocker will not work, please wait for the next version]
2. Connect your phone to your computer using the USB lead.
3. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
4. Wait patiently.
5. Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
7. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
8. Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
9. You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
10. Process is (hopefully) complete!
11. If the phone requests unlock code when you put a locked SIM, the code is: 22051978
I assume I want go to 1.04 for Cingular which is 1.30.502.1.
What about my SIM card? Is it supposed to be in phone when I run this file? (it's a t-mobile sim).
I assume the activesync connection via usb is okay? I cannot get it to connect (even though the phone is on and booted into Windows 5.0); is this because I have not inserted the SIM card into the phone? Note: after I unplugged the device, setting allow USB connections on the device in the ActiveSync settings, then plugging it back in, it connected via USB in ActiveSync (4.2). However, I just got a box saying the version of ActiveSync is not compatible with this mobile device. This occured after I started the installer and it showing Verifying the information on your PDA phone.
I received an update error 260 since it thinks the phone is not connected via USB (and I noticed the ActiveSync icon in the system tray is gone).
I went to check the M$ page to see if there is a later download; there is not. Then, the AS icon return (trying to update outlook, install nero mobile) so I decided to run the installer again and now sees my current version 1.34.502.1 and I have the option to upgrade ROM
MilanoRex said:
I unlocked my 8525 last week, I had bootloader 1.06 so I downgraded to a ROM with boetloader 1.04(you can find it here http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades ).. then just follow the instructions in the zip file you downloaded(i used HERM_Unlock_v2a), which are:
1. Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 this unlocker will not work, please wait for the next version]
2. Connect your phone to your computer using the USB lead.
3. Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
4. Wait patiently.
5. Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
7. Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
8. Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
9. You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
10. Process is (hopefully) complete!
11. If the phone requests unlock code when you put a locked SIM, the code is: 22051978
Click to expand...
Click to collapse
crazyut said:
I assume I want go to 1.04 for Cingular which is 1.30.502.1.
Click to expand...
Click to collapse
right
crazyut said:
What about my SIM card? Is it supposed to be in phone when I run this file? (it's a t-mobile sim).
Click to expand...
Click to collapse
doesn't matter
crazyut said:
I assume the activesync connection via usb is okay?
Click to expand...
Click to collapse
It is ok, but generally it causes more problems than it helps. Best is to disable the checkbox that says "enable usb connections" on activesync settings and you'll see the icon on the system tray turn gray with a red "X". Then you need to start the RUU when the device is in bootloader mode (tri-color screen). After you have upgrded the rom (or radio rom) you can reenable activesync again if you want.
crazyut said:
I cannot get it to connect (even though the phone is on and booted into Windows 5.0); is this because I have not inserted the SIM card into the phone?
Click to expand...
Click to collapse
SIM card and activesync have nothing to do.
crazyut said:
I received an update error 260 since it thinks the phone is not connected via USB (and I noticed the ActiveSync icon in the system tray is gone).
Click to expand...
Click to collapse
Icon was gone because RUU checks your current rom version using activesync and then kills it an put device in bootloaer mode. If RUU cannot kill activesync correctly errors happen:
You will avoid the 260 error if you disable usb connections on desktop activesync as I told you, and start the upgrade in bootloader mode... only difference you'll notice is that RUU will not report your current rom version.
Hey. I left the RUU software running (the 25+ minute variety) while I went to buy a case and care charger. I came back and evidently, the phone had rebooted because, it is at the Windows Mobile screen to setup the Windows Mobile device. I assume it is safe to do the 2a software. After that, am I able to update the RUU back to 1.06?
Thanks for your help, Milan and pof!
I rebooted into bootloader to confirm successful downgrade to 1.04 from 1.06 and it was. The RUU software from the upgrade page for Cingular appears to have been successful.
I am now going to attempt the 2a software.
Yes, now follow all the instructions on sim&cid unlocker v2a, and when finished, flash the cingular 1.34 rom again.
pof said:
Yes, now follow all the instructions on sim&cid unlocker v2a, and when finished, flash the cingular 1.34 rom again.
Click to expand...
Click to collapse
It's now on the upgrade screen to Radio 1.16.00.69 but it does not show the previous version. Is this normal? I have not pressed upgrade yet. I have the splitter with the AC and USB cables into the phone (currently in bootloader mode at SPL-1.04).
yes, it is normal... i told you before:
pof said:
RUU checks your current rom version using activesync
[...]
start the upgrade in bootloader mode... only difference you'll notice is that RUU will not report your current rom version.
Click to expand...
Click to collapse
pof said:
yes, it is normal... i told you before:
Click to expand...
Click to collapse
I got the 114 error as promised in the readme. I exited the program using the EXIT button.
The next step:
6. Soft reset with stylus (Device will not be hard reset and no data will be lost)
On the phone display, it still shows Upgrade Radio Stack Please Wait..
The soft reset is the simultaneous OK and Power?
I just took the battery out and reset; it appeared to go okay. I copied the exe file to the phone and was able to run the file as in the readme. I then reset the phone, put in the t-mobile sim and it works.
Thanks much to POF and Milan for their straightforward approach. You can use this thread as a tutorial!
Is there any reason I should add the 1.06 file back to the unlocked 8525?
SPL 1.06 to SPL 1.04 back to SPL 1.06?
Hi:
I followed pof's (with pof's help) tutorial on how to unlock the Cingular 8525. I am currently at SPL 1.04 (downgraded form SPL 1.06) and had run the v2a software to unlock. It works great with T-mobile (I was a Cingular customer but made the switch).
My questions are:
Is there any reason to go back SPL 1.06?
If I do go back to SPL 1.06, it does not affect the unlock status of the SIM or CID?
I still am confused about the Radio and what that does in relation to the CID, SIM, or phone. I assume the Radio is affected the SPL version that you have?
I have tried to peruse through various pages regarding downgrading (the 13 page thread for example) to see if that question is answered.
The radio ROM controls the GSM/GPRS/UMTS hardware in your hermes. You cannot independently upgrade it unless you are running SPL 1.04. There is no reason IMO to go to any other bootloader version.
Sleuth255 said:
The radio ROM controls the GSM/GPRS/UMTS hardware in your hermes. You cannot independently upgrade it unless you are running SPL 1.04. There is no reason IMO to go to any other bootloader version.
Click to expand...
Click to collapse
Oh okay, that clears up yet something else I did not understand
Thanks for the tip on the bootloader version; I will leave it at SPL 1.04.
That being said, I am currently in the middle of the Radio 1.20 thread; I have not finished reading it yet (I can only do so much at work before people wonder what I am doing). Have you upgraded to Radio 1.20? If not, what radio are you running and what do you think of its stability and/or functionality?
Thanks!
I'm running the 1.20 radio. It and the 1.35 TyTN ROM are the best combination I've used so far.
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?
With PPCGeeks undergoing their upgrade, where can I download 2.40-olipro from in the mean time? I'm wanting to do some rom upgrades but it seems I need this to unload things for it. I'm trying to install the radio 3.27 and one of the titan 2.x roms with the GPS update.
here u go...
Mod Edit:
Unfortunately the attached file was for an earlier version - see posts below for 2.4
origins81 said:
try hitting search first
Click to expand...
Click to collapse
I did and 2.40 olipro only gave me messages saying that I needed it, not that it was called TitanUnlock. Thanks for the link.
Did I miss somthing?
I downloaded the file and it still said version 1.20Olipro did I miss something?
I saw that it was 1.2 but it didn't register that it was the wrong version and that probably explains the problems I was having trying to load the new rom.
olipro 2.40 here you go
this is the link when ppcgeeks.com comes back up you can get it.
however attached is the file you want and need. BUTTTTTTTTTT
you will now need to find the "re-locker" so you can relock the old olipro and use the new.
Thanks for the file, but I guess if I need to find another program, will wait for either ppcgeeks to come back up or sprint to release the offical rom.
Does anyone have the program for "re-locker"?
Here's the file with the proper name. It's not the easiest to find especially with the other side being down. So without being rude I shall set you in the right direction. Plus if you search for "titan unlocker" as per the other file name you are liable to be loading the OLD unlocker not new since it is generically named such.
edit....
Sorry I guess my interrution while posting this caused me to duplicate someones post....
Thank you for the links. You are far from being rude, but show you understand that all the searching in the world won't help when you don't have the right information and that one of the main supports is missing.
Thank you all for your help! I ended up googling and searching and came upon this post from another board.
"I had the exact same problem.
Connect your phone (while in Windows, not from the bootloader) to your computer and make sure it creates an ActiveSync connection.
Download the file from here: ftp://ppcgeeks:[email protected] . Extract it and it should launch the Titanunlocker.bat. If it doesn't, just launch the batch file from the place you extracted the files. Follow the prompts, and when it's done, you should have 2.40 installed. I too couldn't get 1.20 off, but after I did this, I now have 2.40 bootloader."
----------------
Also if you are stuck with the bootloader screen (rainbow) you can just run titan_exitbl.exe in the file I've included it will allow you to boot. Also you must disable activesync from looking for usb connections if you have to go the titan_exitbl.exe route.
The file listed able will actually attempt to update to 2.40 once you run it, really automated.
Thanks to PDAPhoneHome's jrider for the post.
I was on 1.20, but I didn't have to relock or anything to upgrade to 2.40. I just went onto the bootloader screen, then ran the RUU exe for 2.40 in the TitanUnlocker zip.
Oh boy, uncrackable Apache 6700!
I cannot get the hard SPL to crack!!!! Help!!!
I currently have Bell Mobility 2.13 on my phone. I have installed .NET framework 3.5 on my PC. I have done a hard reset on my 6700. Connected to activesync. I have tried to run kaiser-HardSPLv1, titanunlocker and Hard-SPL-MFG. I my phone locks up before I get to a tri-coloured screen. I disconnect from my PC and reconnect, then the Flash upgrader program starts and my phone turns off by itself and then my PC gives me an connection error. Any ideas?
I cannot get the hard SPL to crack!!!! Help!!!
I currently have Bell Mobility 2.13 on my phone. I have installed .NET framework 3.5 on my PC. I have done a hard reset on my 6700. Connected to activesync. I have tried to run kaiser-HardSPLv1, titanunlocker and Hard-SPL-MFG. I my phone locks up before I get to a tri-coloured screen. I disconnect from my PC and reconnect, then the Flash upgrader program starts and my phone turns off by itself and then my PC gives me an connection error. Any ideas?
Click to expand...
Click to collapse
Dude...this is the Titan forum, not Apache. Why you would try altering your bootloader with unlockers specifically meant for other devices (kaiser & titan) is beyond me.
superlover911 said:
I cannot get the hard SPL to crack!!!! Help!!!
I currently have Bell Mobility 2.13 on my phone. I have installed .NET framework 3.5 on my PC. I have done a hard reset on my 6700. Connected to activesync. I have tried to run kaiser-HardSPLv1, titanunlocker and Hard-SPL-MFG. I my phone locks up before I get to a tri-coloured screen. I disconnect from my PC and reconnect, then the Flash upgrader program starts and my phone turns off by itself and then my PC gives me an connection error. Any ideas?
Click to expand...
Click to collapse
This post shows that people are not worried about what they do to their phone. 911, you need to read the wiki for your phone (APACHE 6700) and do not use any software or roms for other devices (i.e. 6800, Kaiser, Titan, etc) unless you are 100% certain what you are doing. You are really close to hosing your phone.
Read this twice. http://wiki.xda-developers.com/index.php?pagename=HTC_Apache
x64 compatibility?
Am running XP x64 edition and the 2.4 Olipro wasn't working, saying it cannot run in a 64-bit OS.
Any suggestions/solutions? I don't have access to any 32-bit computers.
EDIT: Already resolved elsewhere:
MrTek said:
it is because the sleep4 command is 16bit which is not allowed to to run on 64 bit os
just edit the cmd file in a text editor and replace sleep4 with pause
now it will pause when it runs which means you have to hit enter to continue which should be enough a delay
i just did this exact same thing tonight without issue
Click to expand...
Click to collapse
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
I want to install dcd's newest Titan ROM to my phone. I'm just getting everything organized, and my bootloader isn't listed under the "Install the correct bootloader" heading on this page: http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
I'm just wondering if anyone knows what I should do with my 1.07 bootloader?
ThomasHW said:
I want to install dcd's newest Titan ROM to my phone. I'm just getting everything organized, and my bootloader isn't listed under the "Install the correct bootloader" heading on this page: http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
I'm just wondering if anyone knows what I should do with my 1.07 bootloader?
Click to expand...
Click to collapse
Just boot up into your Current functioning OS and connect to Active sync until icon turns green, then. Now run the Olipro 2.40 unlocked Bootloader and follow its instructions until it comes up saying you must unplug and plug the phone back in. PLEASE dont miss that, DO NOT hit a key to continue UNTIL you have UNPLUGGED the phone waited a moment, then plugged it back in. Then you can hit a key and continue but PAUSE again and minimize that window. Now right click the Active sync icon on your PC's taskbar. Pick connection settings and then look for the Box with Allow USB connections. Clear the box (disable) the usb connections. Then click OK. Now open the window back up and click to continue. That will exit the Bootloader and reset the phone. Now right away UNPLUG the phone and Manually place it in Bootloader Manually. Now PLUG the phone back into the PC. Now flash your Custom ROM and GPS radio 3.35 and up. Hope this helps
Perfect instructions. Thank you very much!
Now...
1. Install the ROM using an ActiveSync connection and running the .exe file from my computer
2. Flash the radio .nbh file using a MicroSD card
3. Run the carrier customization once it's booted
Is this right?
ThomasHW said:
Perfect instructions. Thank you very much!
Now...
1. Install the ROM using an ActiveSync connection and running the .exe file from my computer
2. Flash the radio .nbh file using a MicroSD card
3. Run the carrier customization once it's booted
Is this right?
Click to expand...
Click to collapse
Well everything is right except the Auto Cust. That depends on if you are using a different carrier than the Branding on the phone and its EXT ROM contents. But you got the idea.
Got it done. Thanks a lot for your help!