Related
I tried to install Dcd Titan 2.1.0, It went through the ruu process succesfully, but when phone restarts it gets stuck in black HTC sceen past the Red model numbers. I tryied to use Exit boot loader, but restarted back to the same screen. I tried to connect active sync (all on Xp). tryied to install through RUU again, got an Error264 and recovery process went through there instructions, no luck. Been searching all over XDA sight,
I Have OLIPO 2.4 INSTALLED
Found that I should try Formating SD card to fat32, put 2.17 official in it, renamed to TITIMAG.nhb (OR SOMTHING CLOSE, done right on card).
I HARD RESET, AND IT WENT TO THE LOADING SCREEN AND HAS BEEN THERE FOR AT LEAST A HALF AN HOUR.
WHAT SHOULD I DO??????????
Keep waiting(WHICH I STILL AM)
Or does any one else have some suggestions
I hope this ain't bricked, Please tell its not
DCD's ROM do not include a radio. For the ROM to completely boot, you need to install the new radio ROM, which is mentioned in DCD's ROM threads. There is a thread on here with the 3.27 radio here.
looking at right
looking, but can i flash it to SD card
JonnyBoy313 said:
looking, but can i flash it to SD card
Click to expand...
Click to collapse
yea you can if ur card is FAT32
works for everyone else but me
Updated 6/16/08:
-Created bootsplash kitchen along with instructions.
-Included information about flashing via microsd card.
Little background on Titan boot sequence for those who don't know exactly what this kitchen/tutorial does:
Many confuse the term "ROM" with the OS ROM. The term "ROM" has been used so often in conjunction with the OS ROM, that it's become jargon. When one refers to the "ROM" he/she usually is referring to the OS ROM. The ROM is the read only memory that can only be altered with a firmware flash. In actuality, there are 5 parts that make up the total ROM.
1. SPL - Bootloader
2. Radio - GSM or CDMA radio
3. First Splash - Splash screen that shows Protocol, Rom, and Radio versions.
4. Second Splash - Splash screen after the Protocol, Rom, and Radio versions disappear.
5. OS - The OS, a.k.a. what you flash when you cook a rom with dcd's kitchen etc.
This is how we're able to flash the bootloader, radio, OS etc. separately. You notice this more when you flash with the microsd card. When the bootloader loads and checks the image, it tells you exactly what part of the ROM it is. If you're flashing the OS, it says OS. If you're flashing the radio, it says CDMA (type of radio the Titan uses).
The Titan has either 3 or 4 boot splashes depending on whether or not you use a startup animation. The first 2 are part of the ROM. The 3rd and 4th are the startup animation (if included as part of OS ROM) and the welcomehead splash (Windows Mobile splash, which can easily be changed without flashing anything by copying/pasting your image of choice named welcomehead.96.png to \Windows on your phone).
This kitchen cooks the First and Second Splashes of the ROM.
http://wiki.xda-developers.com/index.php?pagename=TitanBootsplashTutorial
Enjoy!
Awesome - Thanks GC!!
Nice. Will try later on.
"Below is a guide to cook a tiny ROM which will only flash your bootscreens. Flashing it will cause a hard reset, but will leave your current ROM intact."
So people would read!
Hey GC - This is the same error I got the last time I tried to use this tool.... Hae you seen this, and what does it mean??? I clicked on the nb_image_converter.exe and then these 2 boxes popup.....
Helpppppppp.....
Hey GC - This is the same error I got the last time I tried to use this tool.... Hae you seen this, and what does it mean??? I clicked on the nb_image_converter.exe and then these 2 boxes popup.....
Helpppppppp.....
Click to expand...
Click to collapse
Whoa wtf... this program has NOTHING to do with BuildOS. Do you have PPCGeeks BuildOS installed or something?
Yes, but why would it look for that?? This program is a simple executable??
No idea... try to completely uninstall PPCGeeks and see if it still pops up.
Thats the damdest thing..... Uninstalling the ppckitchen and the nb tool runs FINE.....
Thats the damdest thing..... Uninstalling the ppckitchen and the nb tool runs FINE.....
Click to expand...
Click to collapse
Haha, well no real reason to have it now anyway right?
You testing this out? If so let me know how the tutorial was and post up your bootsplash!
That goes for everyone, I'd like to get some feedback on how it goes. It seems like a lot of steps, but once you master it, it takes like a minute tops...screw using ppcgeeks kitchen for this.
Also, if you'd like to share your bootsplash, post it up!
gc14 said:
Haha, well no real reason to have it now anyway right?
You testing this out? If so let me know how the tutorial was and post up your bootsplash!
That goes for everyone, I'd like to get some feedback on how it goes. It seems like a lot of steps, but once you master it, it takes like a minute tops...screw using ppcgeeks kitchen for this.
Also, if you'd like to share your bootsplash, post it up!
Click to expand...
Click to collapse
Ok - Works great.... I did however make a batch file so that it's just easier to click on it instead of using a DOS box, lots of people may have an issue finding the folder they saved the images in, and it autostarts Duttys.... I can AIM it too you GC....
Here's my screen.....
GC14, was just wondering... You say that there is no way around the hard reset. Well if i remember correctly, quite a wails back, in the 3.27 Leaked ROM era, when i would flash my mogul with the leaked ROM, was the first time i got that annoying "Test purpose only" Boot screen flash.
Well my attempt to change it was to use the official Rom before this, by doing the SD card method, and only wait for it to say Finish flashing bootscreen, and i would reset the device immediately, to prevent any corruption.
This method indeed changed my boot screen splash, and nothing else, and it didn't hard reset anything.
So shouldn't anyone be able to just place the .nbh file into a SD card, and let it just flash the boot screen that way?
I'm only saying.. i actually haven't tried it, since i did it the long way anyway.
GC14, was just wondering... You say that there is no way around the hard reset. Well if i remember correctly, quite a wails back, in the 3.27 Leaked ROM era, when i would flash my mogul with the leaked ROM, was the first time i got that annoying "Test purpose only" Boot screen flash.
Well my attempt to change it was to use the official Rom before this, by doing the SD card method, and only wait for it to say Finish flashing bootscreen, and i would reset the device immediately, to prevent any corruption.
This method indeed changed my boot screen splash, and nothing else, and it didn't hard reset anything.
So shouldn't anyone be able to just place the .nbh file into a SD card, and let it just flash the boot screen that way?
I'm only saying.. i actually haven't tried it, since i did it the long way anyway.
Click to expand...
Click to collapse
I've never tried it. I simply said there's no way around the hard reset if you use the RUU. First and foremost, if people are going to try it, they have to rename RUU_signed.nbh to TITAIMG.nbh. If you want to try it and let me know, go for it.
Thanks gc14 (aka gcincotta ) for the tutorial. Worked great...now to play with some different splash screens!
Just to be clear this will hard reset the phone but will not erase the ROM. This means all contacts, programs, settings, etc... will be left intact?
great tutorial! worked like a champ! Thanks!
Updated 6/16
Great change brother..... I see you liked the batch file idea!!! Yours is pretty close to mine.... but better.... lol Nice job...
gc14 said:
Updated 6/16
Click to expand...
Click to collapse
Does the microsd flash have the same issue as others where it has to be a smaller card? Sorry for not being more specific. I haven't looked too much into that issue as I don't have a smaller card, I'm a 4gb microsd.
Does the microsd flash have the same issue as others where it has to be a smaller card? Sorry for not being more specific. I haven't looked too much into that issue as I don't have a smaller card, I'm a 4gb microsd.
Click to expand...
Click to collapse
Flashing via the microsd card is the same whether flashing rom, radio, or bootsplashes. Non microsdhc card, formatted to FAT32, with cluster size less than 4k.
Which splash screen is this? The Windows one or the (on DCD Verizon) the white verizon screen?
, I've been tryin to update my Mogul's ROM to the newest DCD ROM(3.2.6 i think) and I ran into some issues that I can't seem to find on the wiki. The first thing I did was upgrade the SPL using nueSPL-2.47 by putting onto a FAT32 Sd card(1gb). That worked out fine it looks like. When I go into the bootloader it says what it should.
So then I moved on to upgrading the radio ROM. For this I used Titan Radio ROM 3.42.50. Inside the RAR file it came in was TITAIMG.nbh. The wiki said thats what I need so I loaded that onto my Sd card and entered bootloader. It found it and asked me to press the power button and then did the update and said it was a sucess. From there... nothing happens. it stays at the gray screen. I figured I need to reset it myself so I pressed reset and now it hangs at the big yellow screen that says SPRINT and doesnt load into the OS.
The wiki says this is because I didn't load the right rom for my phone, but I'm almost positive this is the right radio for the mogul, no? I don't know what went wrong, so I'm at a complete loss.
Anyone have any ideas on how I'm messing this up?
you need to read this: http://forum.xda-developers.com/showthread.php?t=392133
your radio has to be matched with a compatible rom, since you're on radio 3.42.50, you need a gps/reva rom, any of the ones listed at the bottom.
you can flash a rom via microsd as well, but it wont load the stock os, which is what im assuming u are still on, with a newer radio.
good luck
donpedfodelruvo said:
The wiki says this is because I didn't load the right rom for my phone, but I'm almost positive this is the right radio for the mogul, no? I don't know what went wrong, so I'm at a complete loss.
Click to expand...
Click to collapse
You've mentioned installing an appropriate bootloader and radio for DCD's 3.2.6, but you have failed to state what OS ROM is loaded or if you did attempt to flash to 3.2.6.
Hmm.. Yeah I am still on the stock Os Rom. I didn't realize the newer radio would make it incompatible. I suppose the dumb mistakes are the easiest to make.
So now, I need to update the OS Rom and I should be fine. Only problem is... I can't figure out now how to update to dcd 3.2.6. I need to flash via the SD card but I can't find the .nbh file in the RUU directory. What else am I missing?
*edit* Figured all this out, see post below.
Okay... I spoke too soon, cause I'm not out of the woods yet. i upgraded the Rom and have it working on the phone. Cept', I guess my account is no longer tied to the phone anymore, cause I can't make calls or do anything related. Is the simple way to fix this just calling sprint up and just saying I want to switch my account over to this 'new' phone? I've done that plenty to switch back and forth between the two phones I own, but I'm wondering if there's something else wrong.
I did install the sprint carrier .cab, so I know that's not an issue.
donpedfodelruvo said:
Okay... I spoke too soon, cause I'm not out of the woods yet. i upgraded the Rom and have it working on the phone. Cept', I guess my account is no longer tied to the phone anymore, cause I can't make calls or do anything related. Is the simple way to fix this just calling sprint up and just saying I want to switch my account over to this 'new' phone? I've done that plenty to switch back and forth between the two phones I own, but I'm wondering if there's something else wrong.
I did install the sprint carrier .cab, so I know that's not an issue.
Click to expand...
Click to collapse
don't tell them you want to switch or anything... Just tell them you hard reset your phone and now your having this problem.
depending on the issue.. I know with verizon I either cant make calls (needs an Akey reset) or I cant get data (needs a DMU reset). I just call them and tell them I performed a hard reset because I had an issue and now I need (one of those things) reset. I'm sure it's the same for you.. this will happen when going from non GPS to GPS radio.
i usually flash the rom first then the radio both from sd. plus i dont think the card can be a sdhc
... I knew messing about with ROMS would do this one day..
I Started to flash the 3.14 (I think) update from the HTC site this morning, I realised after I started HSPL would get in the way of that...
SO now it loads to the coloured lines screen, I tried coping a image to the SD card to flash straight from that but I cant get it to search the SD card. All I get when I hold down the power and volume button is a "loading" message for a split second, then nothing else!
Help! Any ideas what I can do now?
Thankyou!
Ok, so I can now get it to read from the SD card that there is a image there - but it just sticks at "loading"
Ideas?
Dan84 said:
Ok, so I can now get it to read from the SD card that there is a image there - but it just sticks at "loading"
Ideas?
Click to expand...
Click to collapse
2 Options.
Previous flash has gone wrong, so reflash the rom you was flashing using sd-card (also check on what SPL you are).
Get a goldcard and reflash any other stock rom.
SPL-2.08.0000
Is whats on the screen, previously it said HSPL so I think one of the roms may have been successful enough to change to SPL... But im guessing this is bad now as it wont flash again from the SD card!
http://forum.xda-developers.com/showthread.php?t=725985&page=7
This updated it to 2.08.HSPL
Im fairly certain Ill be able to flash at least a stock ROM now.
Wanted to ask first, Ill be messing with Andriod and possibly windows 7. Is there anything I should preferably be flashing too? Are there any limits with 2.08HSPL I need to be aware of before I start?
Thanks,
Dan84 said:
http://forum.xda-developers.com/showthread.php?t=725985&page=7
This updated it to 2.08.HSPL
Im fairly certain Ill be able to flash at least a stock ROM now.
Wanted to ask first, Ill be messing with Andriod and possibly windows 7. Is there anything I should preferably be flashing too? Are there any limits with 2.08HSPL I need to be aware of before I start?
Thanks,
Click to expand...
Click to collapse
you'll need an updated radio for nand android or wp7 (each has its specifics - see threads).
but what wm rom won't matter, as well, it will be erased
no limits. if you have hspl you can flash any compatible rom, etc.
Have had my T-Bolt for about a month now and just rooted it yesterday! Loving it even more now! I decided to root because I was one of the lucky people that got the update a couple weeks ago and have been having random reboots ever since. I was hoping a different ROM might help with that.
I came from a D1 that I had rooted about a month after it first came out, so I know the basics of using Clockwork.
I put Das BAMF 1.6.3 on yesterday and it seems to be working good. Problem I am having is that I am still getting some random reboots. Not sure if it has to do with the radio installed on the phone or something with the kernal?
It isn't happening all the time. I noticed one last night and one this morning. Suggestions?
Which kernel & radio are you using?
I had the same problem had to switch to a different kernal. It was getting a little to warm causing the phone to reboot. Most noticeably when I used the navigation.
Sorry it took a while for me to respond. Been pretty busy.
After the reboot yesterday, I put a new kernel on there cause I say someone tried that when they got reboots and it fixed the problem.
Here is what I put on, the lean kernel, extremely undervolted - http://forum.xda-developers.com/showthread.php?t=1021404
It seems to be running good. No reboots since I put it on. But then this afternoon I got one. I wasn't doing anything crazy on my phone but it just rebooted out of nowhere. I was on 3G if that matters...???
BUMP
Had one random reboot today. Can't figure out what is doing it. This time I was in the middle of typing a text while on WiFi.
If you are using extremely undervolted try switching to normal. The extremely undervolted setting is also overclocked and may not get enough juice to run properly. see if running normal for a while also has you rebooting.
schmaltzy said:
BUMP
Had one random reboot today. Can't figure out what is doing it. This time I was in the middle of typing a text while on WiFi.
Click to expand...
Click to collapse
I like the BAMF Tom's, but the CM7 alpha for the Tbolt is stable and awesome... no wireless tether yet, but I'm sure it is on the way!
Sent from my ThunderBolt using XDA Premium App
I had random reboot problems after I flashed to the new radio. I switched back to the original radio and have not had a problem at all with bamf 1.6.3 or 1.7.
Sent from my ADR6400L using XDA App
I put the .7cdma and .6lte on and it solved my reboots. Before that I got random reboots and even a couple times where it just shut off. There is a radio thread in the dev section with all the combinations. Been on this radio for weeks and no reboots.
1.6.3 and 1.7bamf not o/c
OK.....need a little help with flashing a new radio....
See, I came form the origional Droid, which was super easy when switching ROMS. Download the ROM you want, throw the zip on the SD, boot into recovery, flash your ROM, good to go!
Seems a little more complicated with the Thunderbolt, so I'm still getting a little use to it.
I went to the post that has all the different radios, but I'm still not exactly sure on how to flash one. Can anyone explain???
schmaltzy said:
OK.....need a little help with flashing a new radio....
See, I came form the origional Droid, which was super easy when switching ROMS. Download the ROM you want, throw the zip on the SD, boot into recovery, flash your ROM, good to go!
Seems a little more complicated with the Thunderbolt, so I'm still getting a little use to it.
I went to the post that has all the different radios, but I'm still not exactly sure on how to flash one. Can anyone explain???
Click to expand...
Click to collapse
Pretty easy actually. Just download the image that you want to use. Make sure it is at the root of your sd card. Boot your phone into Hboot and it will try and load the file automatically at that point.
Tell the phone it's ok to install. Once you have it installed, don't forget to delete the image file from your root or at least rename it. Otherwise if you go back into hboot, it's going to try and install the image again.
Hope that helps.
Dnakaman said:
Pretty easy actually. Just download the image that you want to use. Make sure it is at the root of your sd card. Boot your phone into Hboot and it will try and load the file automatically at that point.
Tell the phone it's ok to install. Once you have it installed, don't forget to delete the image file from your root or at least rename it. Otherwise if you go back into hboot, it's going to try and install the image again.
Hope that helps.
Click to expand...
Click to collapse
How do you get into Hboot?
I'm running Das BAMF 1.7 Remix and I get a "bootloader" option under the restart. Is that the same thing??
Couple of ways.
If your rom supports it. You can hold the power button down and pick restart and then pick bootloader.
or if your phone is powered down, just hold the volume down key while holding down the power key and that should get you to the bootloader.
Edit: Make sure that your image is named PG05IMG at the root of your sd card.
It's the LTE radio causing reboots, so from http://forum.xda-developers.com/showthread.php?t=1045081 select either the second or fourth option. Any combo that has the 1.12.605.6 LTE radio. Also don't forget to rename it PG05img.zip and put it on the root of your sd card.
If your in hboot and it doesn't recognize the file, make sure it's not named PG05img.zip.zip, changing the name in windows will cause that to happen.
DixonToofar said:
It's the LTE radio causing reboots, so from http://forum.xda-developers.com/showthread.php?t=1045081 select either the second or fourth option. Any combo that has the 1.12.605.6 LTE radio. Also don't forget to rename it PG05img.zip and put it on the root of your sd card.
If your in hboot and it doesn't recognize the file, make sure it's not named PG05img.zip.zip, changing the name in windows will cause that to happen.
Click to expand...
Click to collapse
Thanks Dixon.
I was one of the lucky few that was getting quite a few reboots before I was rooted when Verizon sent out the update. Is it the LTE radio the cause for sure? I know there was a lot of speculation on what was the actual cause, but then I rooted so I stopped following the problem.
Does it matter that I have my LTE turned off all the time? I don't live in an LTE area so I never have it on, yet I still get 1 or 2 random reboots a day. Still better than the 6-8 I was getting when I wasn't rooted!
schmaltzy said:
Thanks Dixon.
I was one of the lucky few that was getting quite a few reboots before I was rooted when Verizon sent out the update. Is it the LTE radio the cause for sure? I know there was a lot of speculation on what was the actual cause, but then I rooted so I stopped following the problem.
Does it matter that I have my LTE turned off all the time? I don't live in an LTE area so I never have it on, yet I still get 1 or 2 random reboots a day. Still better than the 6-8 I was getting when I wasn't rooted!
Click to expand...
Click to collapse
I don't know if anyone can say for certain, but many people(Myself included) experienced reboots after switching to the updated .7 radios. After switching back to the .6 LTE radio, I haven't had a single reboot in weeks, and many others have had the same results. Whether it is the cause or not, switching seems to solve the problem. If it doesn't, then chances are something else is causing them on your phone, but you won't know until you try.
I usually have LTE turned off as well, and I know at least a couple of my reboots happened while it was turned off. Whatever the cause, it doesn't seem to be related to the use of the radio. Just having the .7 version loaded seems to be enough.
Should I make a Nandroid backup before I flash a new radio? Or would that not back anything up as far as the radio goes?
schmaltzy said:
Should I make a Nandroid backup before I flash a new radio? Or would that not back anything up as far as the radio goes?
Click to expand...
Click to collapse
I would always make sure you have a recent Nandroid backup before flashing anything. It won't back up the radio itself, but you never know what else could go wrong.
OK, last question....hopefully!!
There was just a new radio that was released. Looks like it is a new Gingerbread radio. Now I'm thinking about just throwing a gingerbread ROM and do everything once.
Question is....if I switch from a Froyo ROM to a GB ROM, in what order do I flash the ROM/Radio??
1) Backup, Wipe data/cache, flash ROM, boot into HBOOT, then flash the new radio?
or
2) Backup, boot into HBOOT, flash new radio, boot into recovery, wipe, flash ROM?
Doesn't matter. Some will tell you one way, others will tell you the other way.
From what I can tell, either way works. I've done both with the new radio and have had no issues either way.
Happy Flashing!