Related
Got the radio upgrade 3.3x and all works well with 2.x dcd rom, but upgrading to 3.0.1 has problems with phone calls. Both receiving or outgoing, the device resets 10 sec into the call. Also Voice Command 1.6 not working. sucks.
verizon xv6800
I'd be willing to bet millions you didn't follow directions when flashing.
Nope. Cooked a kitchen, tried the Verizon Rom....neither work with 3.0.1. works great with 2.x though.
Voice Command 1.6 now working OK as well under 2.3.2. I is happy. Still looking for good GPS software. I really liked Earthcomber, but doesn't work with this rom.
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
OK so I cry for help. Why the heck would I apply a Sprint update to a Verizon handset, granted both CDMA. I upgraded the radio at the same time as 2.2. The 2.2 DCD rom I'm using that WORKS WELL should be no different than the upgrade to 3.0.1. Unless I'm forgetting to stop customization with a soft reset.
You're not getting the point!!!
The only reason to flash sprint's official rom is so you can update the radio to its latest version. After this is done, it DOESN'T MATTER whatever rom you flash next, such as a Verizon rom. Use DCD's 3.0.1 rom it should be working. You would have known this if you read instructions. If you flashed the radio alone first, then your settings (ESN, MSID, etc) will be wiped. You will have to re-enter these either manually or call up Verizon to do it for you. This is probably why you can't make calls.
Exactly my point. I flashed the radio with the Oli 2.4 and updated the radio from stock verizon. Then flashed 2.3.2 and all is good with the new radio. So why doesn't it work with 3.0.1? I just found my way to the In and Out Burger via Odyssey Mobile locator.
Everyone keeps telling me that i didn't follow the destructions but they don't point to where they are.
Maybe wrong radio ver?
Crap. Mine says 3.24.00. I guess that's my problem. I'm an idiot.
Please point me to the proper radio D/L.
Thanks,
Sorry for asking what is probably a simple question, but I am having the same problems. I have SPL-2.40.Olipro atm, installed the verizon ROM upgrading to 3.0.1 from NexVision's Hybrid rom. My radio is upgraded to 3.25 or whatever it was supposed to do fine. On vibrate mode, when a phone call is incoming, I get stuck in an ever ending vibrating. I can text, and attempt to cal lsomeone but nothing can be heard and no one can hear me. I know i screwed up somehow- but what exact steps do I do to remedy this?
Thank you in advance
We have to do the Sprint radio update to 3.35 first, which is an upgrade from 3.27. Then go to ROM 3.0.1.
It's always interesting to me how people jump up to say "you're doing it wrong" but don't tell you how to do it right.
Here's how to do it right.
http://forum.ppcgeeks.com/showthread.php?t=17667
Gecko122, There is more to the Sprint file than just the radio... It includes the ROM as well.... My understanding is this:
1st - Run Olipro unlocker 2.4
2nd - Run Sprint Official upgrade , NO CUSTOMIZATIONS.
3rd - Load Custom ROM.....
That has worked for me.....
PS - the DCD 2.x.x series do NOT play well with the new radio, hence the 3.0.1 kitchen.... Driver differences....
do i have to flash back to a former version of dcd or anything? or can i start from a messed up 3.0.1?
hi Penn,
Well, exactly what have you done to your phone?
Bootloader version?
ROM version?
Radio Ver?
Then we can start from there and develope a plan to help ya.
Ignore that above - I re-read you original post....
Here's what you can do and correct me if I'm wrong Penn...
You have Oli-pro 2.4 bootloader loaded
You have DCD 3.0.1 ROM loaded
You have the 3.27 Radio loaded?
If the above is true, then we have options..... Let me know
gcincotta said:
If you tried to flash the radio standalone, then the verizon cooked rom...you didn't follow directions.
The ONLY way to successfully upgrade to 3.0.x is by flashing the sprint update to upgrade the radio.
Click to expand...
Click to collapse
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
No, I flashed new radio stand alone package by dcd first day from an olipro 1.20 then 3.0.0 rom then 2.40 bootloader, and then one day later 3.0.1 rom... I never use sprint upgrade at all, and I have no problem about my phone at all. There is not just one way
Click to expand...
Click to collapse
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Gecko, the reason why I did not "tell" you how to do it the right way is because dcd's thread has 94 pages of information on how to do it the right way. I've even posted several times on different pages in that thread with explicit instructions on how to. While I am always very eager to welcome newcomers to this community, I also strongly encourage them to read, research and educate themselves before touching their device. It doesn't mean I'm not a nice guy and don't like to help, because if you search my posts you will see that I help a lot around here. If you had simply taken 20 minutes and even skimmed dcd's thread, you would have found the answer yourself in no time.
gcincotta said:
Correct me if I'm wrong, but weren't you the one with the extremely long, complicated post about how you were able to get everything working that way?
http://forum.xda-developers.com/showpost.php?p=2014972&postcount=326
Secondly, you may have been able to get everything working, but you're lucky. The chance of problems occurring by flashing this way is way too high in my opinion to even bother, not to mention others have had problems that absolutely cannot be fixed without reflashing back to stock and updating with the sprint update. That is why dcd removed the standalone radio from the Radio Rom thread.
Click to expand...
Click to collapse
Wow... I'm sorry, I had not been keeping up with the issues of others, so until you said that just now, I had no idea. You are right, I am really lucky, so thanks for bringing it to my attention.
No problem
Hi all,
So I installed the Official Sprint ROM issued this month and I have the following problems:
- Battery won't last more than one day
- Phone won't wake up from standby at certain times
- Phone slow after running some applications, including built-in apps like Word, Excel, or IE. Sometimes this result in the phone just simply hanging
In either situation above, except battery issues, a soft-reset is required.
I have tried the following:
- Do a hard reset, try without ANY applications
- Remove HTC_CM_Guardian.exe and SDDAEMON.exe
Anyone have the above three problems? with the new Sprint Official ROM?
I feel like going back to the old Sprint ROM. I have a separate BT GPS, so I don't care about A-GPS functionality as long as my phone is stable.
Why don't you cook a clean rom with the 3.0.1 kitchen and get rid of the sprint rom?
One question - did you let the customizations run after you installed the ROM?
If not, you need to hard reset let the customizations run, hard reset again and then you can bypass the sprint customization.
Otherwise......
......now that you have the new radio installed, I'd recommend trying one of the clean ROM's from either No2Chem (over at PPCGeeks) or DCD's 3.0.1 ROM.
DCD's has a "Touch" look to the skins and has over 24MB of RAM free on first boot.
All you'd need to do is run the 2.40 Olipro SPL unlocker and then flash DCD's 3.0.1 ROM.
Much more stable than the OEM.
nosmohtac said:
One question - did you let the customizations run after you installed the ROM?
If not, you need to hard reset let the customizations run, hard reset again and then you can bypass the sprint customization.
Click to expand...
Click to collapse
I did on the 1st try, but something gone wrong, most troublesome is that the "Text Message" account now shown in Pocket Outlook. So I hard reset again and let the customizations run.
nosmohtac said:
Otherwise......
......now that you have the new radio installed, I'd recommend trying one of the clean ROM's from either No2Chem (over at PPCGeeks) or DCD's 3.0.1 ROM.
DCD's has a "Touch" look to the skins and has over 24MB of RAM free on first boot.
All you'd need to do is run the 2.40 Olipro SPL unlocker and then flash DCD's 3.0.1 ROM.
Much more stable than the OEM.
Click to expand...
Click to collapse
So you're saying that it's better to use Sprint's official Radio but use DCD's ROM?
What I gather from this forum and PPCGeeks is that people either use Sprint's Official Radio and ROM or just forego that and use kitchen's ROM completely, but not a combination of both as mentioned above.
[EDITED]
OK, so I got Olipro and DCD 3.01 Kitchen. Just so I am doing the right thing since I have ALREADY installed Sprint Official Rom with Radio v. 3.35.05, please let me know if this step is correct:
1) Connect to ActiveSync. Sync as usual
2) Run Olipro v. 2.40. This will open a Command Prompt. Let it do it's thing.
3) Once done, load DC 3.01 Kitchen ROM. No other Radio ROM needed.
4). Done.
Am I correct?
There is no radio with the kitchen. The sprint official radio release (3.35.04) is the official radio whether you use the sprint official update rom or a custom rom of your choosing. No other radio works with the newer roms except this radio. That is why if you choose to use a custom rom, you STILL have to flash the sprint update to get the radio, then you flash your custom rom on top of it (with no radio) to get your own rom on there.
lanwarrior said:
Hi all,
So I installed the Official Sprint ROM issued this month and I have the following problems:
- Battery won't last more than one day
- Phone won't wake up from standby at certain times
- Phone slow after running some applications, including built-in apps like Word, Excel, or IE. Sometimes this result in the phone just simply hanging
Click to expand...
Click to collapse
I've cleaned that ROM (gutted to the base OS and functions) and have experienced none of those issues and none of those complaints are voiced in the thread using that kitchen.
I do not think that your problems are due to that specific base of Sprint ROM. Possibly some of the apps or simply a bad flash? Did you attempt to remove HTC Guardian or other components from within the active OS or did you extract and build your own ROM from the Sprint?
For severe battery problems there a couple of threads where a few people have experience excessive drains, but that's with the more recent DCD builds.
gcincotta said:
There is no radio with the kitchen. The sprint official radio release (3.35.04) is the official radio whether you use the sprint official update rom or a custom rom of your choosing. No other radio works with the newer roms except this radio. That is why if you choose to use a custom rom, you STILL have to flash the sprint update to get the radio, then you flash your custom rom on top of it (with no radio) to get your own rom on there.
Click to expand...
Click to collapse
I already have Radio 3.35.04 when I installed Sprint Official ROM upgrade. That's why I want to confirm that I need to run Opilo 2.40 unlocker and then upgrade to DCD ROM on top of the current Sprint Official ROM.
Keystone said:
I've cleaned that ROM (gutted to the base OS and functions) and have experienced none of those issues and none of those complaints are voiced in the thread using that kitchen.
I do not think that your problems are due to that specific base of Sprint ROM. Possibly some of the apps or simply a bad flash? Did you attempt to remove HTC Guardian or other components from within the active OS or did you extract and build your own ROM from the Sprint?
For severe battery problems there a couple of threads where a few people have experience excessive drains, but that's with the more recent DCD builds.
Click to expand...
Click to collapse
Yes, I tried it after Hard Reset. I did remove HTC Guardian from the active OS.
lanwarrior said:
I already have Radio 3.35.04 when I installed Sprint Official ROM upgrade. That's why I want to confirm that I need to run Opilo 2.40 unlocker and then upgrade to DCD ROM on top of the current Sprint Official ROM.
Click to expand...
Click to collapse
You are correct, you can flash any custom ROM on top of Sprint's. DCD's is a good choice.
lanwarrior said:
I already have Radio 3.35.04 when I installed Sprint Official ROM upgrade. That's why I want to confirm that I need to run Opilo 2.40 unlocker and then upgrade to DCD ROM on top of the current Sprint Official ROM.
Click to expand...
Click to collapse
That is correct.
DCD's ROM doesn't include the Radio, and the new radio version is what unlocks the GPS and EVDO REV A features. The SPL unlocker is what allows you to load ROM's that aren't OEM on your device, and If you aren't familiar with how to build your own ROM using DCD's kitchen (it's pretty easy once you get started), then he has carrier specific ROM's already linked on his most recent release page. The links are just above the images.
http://forum.xda-developers.com/showthread.php?t=376150
Yeah just unlock with olipro 2.4, then you have a choice between dcd (which I personally use) or another clean rom like no2chem's.
same issue as stated in first post
Hey just want to say great site guys! There is no other website that can comes close to the knowledge available here. But in response to the who started this thread the official sprint rom is crap! Once phone goes into standby or "LOCK" 99% of the time "Soft Reset" is required. Ive "Soft Reset" my mogul no B.S. 100 times since I've flashed there ROM. Radio is a great improvement but honestly, they need to hire or pay NOCHEM or DCD for their talents because w/out their ROMS the MOGUL would've ended up on the side of the highway. I agree with the last post. Use the official radio, but don't run yourself through the wringer with the SPRINT ROM. You will rip your hair out!
meek420, again, I've had zero issues of lock-ups using a cleaned out version of the Sprint ROM.
I do not think such problems are endemic to that ROM.
Had dcd 3.1.1 installed running fine. This morning decided to upgrade to 3.1.2. Another post advised it was easy to upgrade using sprite backup (new version allows restores across dif device platforms and OS) so I wouldn't spend several hours...again...tweaking my device. Made a backup and flashed dcd 3.1.2. Installed fine and then I used Sprite to reinstall my software. Device appeared to be restored back to dcd 3.1.1 and Activesync would not connect. Sooo I figured I would start from scratch again and did hard reset. Rom is dcd3.1.2...phone works...boots....everything appears normal but still no activesync. Tried disabling 'advanced network funtionality' on device...several reboots...uninstall activesync...reinstall...etc etc...still no connection. I've searched and tried the suggestions mentioned but I'm at a loss. Does anyone have any ideas how to get activesysnc to connect. BTW...when I connect via USB I hear 'chime' and the activesync icon spins but then times out with no connection. Sorry for lengthy popst but I wanted to try and provide all info....help please!?!?
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Well..I fixed it...sorta....reflashed 3.1.1 with SD card and all is well again...I think I borked up something when I used Sprite....not gonna do that again. Will try 3.1.2 again and tweak for a few hours.
edsai said:
I'm having this same exact problem. On top of that since I can't get activesync to work, I can't copy the verizon carrier cab to the device and run it. I can't even run it from an SD card so I've got a brick of a phone.
I'm trying to reflash to dcd 3.0.4 verizon-specific to see if I can get a working phone. Yesterday when I tried it, I was able to go back to stock by running the relocker and all that but I can't anymore for some reason. The relocker won't work.
Click to expand...
Click to collapse
if you have data you can always download it from the thread but I suppose that wouldn't work without verizon customization...hm...I was going to flash to this (sorry nochem dcd comes out with a really stable and fast rom, now about that kitchen...)
at any rate...I hope the problem gets settled
Well 3.1.1 works great...flashed 3.1.2 via SD card and back to same problem...no activesync and no data. Strange...I have the updated Alltel radio on my device. Anyone else experiencing this. I'm on Alltel
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
gcincotta said:
Are you installing the alltel carrier cab everytime you flash? It is REQUIRED with these roms.
Click to expand...
Click to collapse
Yes...installed the proper alltel carrier cab...still didn't work. Am considering downloading 3.39 radio and see if dcd 3.1.2 will work with that radio...currently I have the new alltel radio.
Hello everyone, hopefully you can help me figure out what's wrong with my HD2.
.:BACKGROUND INFO:.
I bought a used TMoUS HD2 a couple months ago and it was working fine up until last month. At first, it would freeze and I would have to do a battery pull, but as time went on, it froze more and more often. One day, I think it froze around 20 times in a row. Eventually, I let the phone sit without the battery for a few minutes before I tried booting it again. When it did boot, I figured maybe there's something wrong with the software, so I did a hard reset. After the hard reset, the phone will boot into the desktop and then freeze (If I'm lucky) or sometimes it will just freeze on the T-Mobile "Stick Together" screen. I tried flashing a the stock ROM and it would always stop at 8%.
I've always used the stock ROM since I got the phone, not sure if the previous owner flashed it before, but it does have HSPL 2.08. The only thing I've done to the phone are the registry tweaks I got from these forums. Here's a list of applications I installed to my HD2:
Chainfire 3D Driver Update
Co0kie's Home Tab
appelflap HTCRamDisk
ATT WAP MEdiaNet and MMS Settings
Band Switch V2.8 Auto Disconnect Data
Battery Increment Display 1.66 ROMs
CleanRAM
ClearTemp v1.3.1
GoogleMaps
JayVee Disable Clock Flip
Long Press Send Key Alt Tab
RAMDisk Opera Cache
TCPMP v2 Video Audio Player
TX Opera Mobile 10 Flash Support
WM Long Life 0.66. 0302
Not sure if this is relevant or not, but the last thing I remember installing was Co0kie's Home Tab before the freezing started.
.:HD2 SPECS:.
OS Version: 5.2.21892 [21892.5.0.89]
Manila Version: 2.5.20121412.2
Rom Version: 2.13.531.1 [90963] WWE
Rom Date: 04.28.10
Radio Version: 2.10.50.26
Protocol Version: 15.39.50.07W
.:THINGS I'VE TRIED:.
Flashing a Custom ROM via USB will stop randomly at different percentages depending on which ROM I flash. I've tried a few different ones.
Flashing the stock ROM
(RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship) via USB always stop at 8%.
Flashing the stock ROM
(RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship) via SD card will give me an error (RADIO_V2 - RSA Fail). I've attached a picture of this error.
Since flashing the stock ROM via SD Card gives me an error (RADIO_V2 - RSA Fail), I decided to flash a new Radio (Radio_Leo_2.15.50.14), but it gives me the same error. (I've also attached a picture of this error) I haven't tried other ones because I'm not exactly sure which ones to try and I don't want to brick my phone...if it isn't already bricked yet.
Can anyone suggest some Radio that's safe for me to try flashing for my TMoUS HD2? I'm really out of ideas on what to do besides that, any suggestions would be greatly appreciated!
***EDIT 1*** (01.21.11) - Tried Task29, went all the way to 100% but the phone fails to reboot. Flashing a ROM after Task29 doesn't work Also added a picture of the bootloader screen.
***EDIT 2*** (01.21.11) - Added a list of radio and ROMs I've tried flashing in post #9.
You can flash any radio with .50. in the name.......
NEVER flash a .51. these will brick your phone.
However this doesnt sound like a radio problem. The only thing I can think to suggest is to read up on "Task 29" this will completely format your device memory and should allow you to reflash a new ROM.
Best of luck........
Thanks for your reply, Conantroutman! I just tried Task29 and it was stuck at 58% the first time, and the second time it completed all the way to 100% (With a success message from my PC) but my HD2's screen just goes black instead of rebooting. After a battery pull, I tried installing the stock ROM and the same thing still happens. It stops in the middle of updating and says there's a communication error.
Any thoughts?
Sorry, the only thing left to suggest is to try the whole process again on another PC. Also try uninstalling active sync / wmdc from your PC and trying again.
Chipped From The Bunker Via A Sandwedge
No need to be sorry I really do appreciate the help! Would upgrading/downgrading the HSPL do anything?
If it stops working using the pc then try using the sd card method.
Do a search for hd2 sd card flashing and you should find out how...
Might be more lucky without the pc in the mix, especially if there are communication errors involved...
Cheers...
ultramag69 said:
If it stops working using the pc then try using the sd card method.
Click to expand...
Click to collapse
I've actually done that as well. The flash also fails but at least it gives me an error (which I've posted a screenshot of in my first post). Not that I know what it means though Hopefully someone with more knowledge can help me decipher it.
Just a question, did you changed previously your radio? If yes to witch one?
kurt-willems said:
Just a question, did you changed previously your radio? If yes to witch one?
Click to expand...
Click to collapse
I've been reading up on how to flash stuff since I got the phone last year, but I never tried to flash anything until the beginning of this week. I'm not sure if the previous owner did though.
These are the radio I've tried this morning:
-2.10.50.26
-2.11.50.20
-2.11.50.26
-2.12.50.02.2
-2.14.50.04
-2.15.50.14
I used the SD card method to flash all the radios above. Some of the radios failed before the progress bar finished, but some actually went all the way. The phone doesn't reboot itself after it finishes though, so I have to do a battery pull. It doesn't seem to make a difference since I still can't flash any ROMs after I flash the radio.
And these are the ROMs I've tried to flash:
-CR192 Desire HD v6.5.3.0.9 Beta
-RUU Leo 1 5 TMOUS 2.10.531.1 Radio Signed 15.34.50.07U 2.08.50.08 2 Ship
-RUU Leo 1.5 TMOUS 2.13.531.1 Radio 15.39.50.07U 2.10.50.26 Signed LEO Ship
-RUU Leo 1.5 TMOUS 3.14.531.1 Radio Signed 15.42.50.11U 2.15.50.14 2 Ship
After leaving the battery out of the phone for a day, I tried Task29 again and managed to complete it (all the way to 100% and a proper restart) without freezing. So then I tried flashing a stock rom, but that stopped at around 8%. When I go into bootloader now, it seems that my HSPL has been removed and I'm reverted back to regular SPL.
If I decide to use Task29 again or flash a stock rom, do I need to install HSPL? Should I install HSPL first or just leave it alone and flash normally?
kin869 said:
After leaving the battery out of the phone for a day, I tried Task29 again and managed to complete it (all the way to 100% and a proper restart) without freezing. So then I tried flashing a stock rom, but that stopped at around 8%. When I go into bootloader now, it seems that my HSPL has been removed and I'm reverted back to regular SPL.
If I decide to use Task29 again or flash a stock rom, do I need to install HSPL? Should I install HSPL first or just leave it alone and flash normally?
Click to expand...
Click to collapse
Yes, install the right HSPL first. Then, do task 29, then you install the correct radio, lastly you can install custom rom.
Good luck
silverwind said:
Yes, install the right HSPL first. Then, do task 29, then you install the correct radio, lastly you can install custom rom.
Good luck
Click to expand...
Click to collapse
Thanks Silverwind, I'm using HSPL3 to install HSPL 2.08, but it always fails. I can install regular SPL 2.08 perfectly fine though. I'll leave the battery out for a day and try again to see if it makes any difference.
Hello,
I have a huge Problem:
Last weekend i installed HSPL on my European HTC Titan and flashed Dynamics V2.0.
This Rom was extremely buggy and wasn't booting again after I turned it of once.
Then I tried the second Rom, Eburon V2.1, which had the same Problems.
After that I installed the European Stock 7.8, which worked better but also stopped working after I installed the official Facebook App.
The next one I used was EB Edition V2.6, worked for a whole day but stopped working after I installed an App from the market. Now the phone isn't booting any more.
I have always installed the right radio, which was in the download file.
My question is:
Are those custom roms so buggy or am I the only person who cannot install any Rom?
How can I fix these problems?
When there is no solution to that I have to sell my HTC Titan and buy an Android Phone again, where custom roms are really working...
P-Froggy said:
Hello,
I have a huge Problem:
Last weekend i installed HSPL on my European HTC Titan and flashed Dynamics V2.0.
This Rom was extremely buggy and wasn't booting again after I turned it of once.
Then I tried the second Rom, Eburon V2.1, which had the same Problems.
After that I installed the European Stock 7.8, which worked better but also stopped working after I installed the official Facebook App.
The next one I used was EB Edition V2.6, worked for a whole day but stopped working after I installed an App from the market. Now the phone isn't booting any more.
I have always installed the right radio, which was in the download file.
My question is:
Are those custom roms so buggy or am I the only person who cannot install any Rom?
How can I fix these problems?
When there is no solution to that I have to sell my HTC Titan and buy an Android Phone again, where custom roms are really working...
Click to expand...
Click to collapse
The answer to your question is; no! I'm currently running Eburon 2.1 and it's running as good as Eburon 2.0 which I've posted runs as smooth as a baby's butt! I'm not familiar with the European Stock 7.8 and I'm curious as to whether it's a custom ROM and designed to run with HSPL. Microsoft's Facebook app has always been buggy; however, within the People Hub it runs there too and all you have to go is go up under your settings and accounts and put your username and password there and you're good to go. As for your phone not booting, I have no idea.
What you need to do is literally start over; if...if...you do not have HSPL; double check this up under your bootloader. Attempting to install all these different ROMs begs the question if you re-locked your phone. Start from knowing for a fact your device is HSPL and has the words "CottulaH" on the bootloader screen. If it does, proceed to flashing your ROM but make sure you have at least a 50% battery charge and the installation process isn't disrupted for any reason. It's a toss up here as to which ROM is the best but you can't go wrong with either the Dynamic 2.0 or Eburon 2.x series.
P-Froggy said:
Hello,
I have a huge Problem:
Last weekend i installed HSPL on my European HTC Titan and flashed Dynamics V2.0.
This Rom was extremely buggy and wasn't booting again after I turned it of once.
Then I tried the second Rom, Eburon V2.1, which had the same Problems.
After that I installed the European Stock 7.8, which worked better but also stopped working after I installed the official Facebook App.
The next one I used was EB Edition V2.6, worked for a whole day but stopped working after I installed an App from the market. Now the phone isn't booting any more.
I have always installed the right radio, which was in the download file.
My question is:
Are those custom roms so buggy or am I the only person who cannot install any Rom?
How can I fix these problems?
When there is no solution to that I have to sell my HTC Titan and buy an Android Phone again, where custom roms are really working...
Click to expand...
Click to collapse
Sounds to me like you are getting bad flashes? Most WP7 custom roms are very stable and perform well 99% of the time. Been using the Dynamics rom on one of my Titans for 2 months or so with no problems whatsoever. The official FB app is buggy...I don't even both installing it.
Now, I'm not here to bash Android, but I dabbled into cooking some Android roms a few years ago. IMHO custom roms on WP are about 10x's more stable than any Android rom I've come across.
Ok, thanks for your replies, but just don't use the official Facebook app isn't a solution.
Could it be a solution to wait ca. one hour after installing a rom and let the phone configure everthing (maybe the phone needs that time)?
Because I set up all my accounts and install the apps I need directly after the rom has booted. Maybe it works if I wait before doing that.
P-Froggy said:
I set up all my accounts and install the apps I need directly after the rom has booted. Maybe it works if I wait before doing that.
Click to expand...
Click to collapse
Definitely - not. This is not a reason of your issue. I would offer to repeat the procedure of HSPL-ing. All customs work at least not worse than the stock roms.
I guess you may have the hardware issue. To be 100% sure - try to flash older stock - like 2.05 (with 16 radio). If it also does not work for you - than - pass your phone to the workshop - it's hardware.
AndrewSh said:
Definitely - not. This is not a reason of your issue. I would offer to repeat the procedure of HSPL-ing. All customs work at least not worse than the stock roms.
I guess you may have the hardware issue. To be 100% sure - try to flash older stock - like 2.05 (with 16 radio). If it also does not work for you - than - pass your phone to the workshop - it's hardware.
Click to expand...
Click to collapse
I had that idea after flashing Deepshining V3: The readme says that you have to activate "Trust all applications" in Root Manager, I wanted to do that, but I got an error message "No root access. Be sure you have fully unlocked your rom".
This was very weird, because that's the app needed to permit other Apps root access.
Also, none of the 3 soft buttons worked.
I waited a couple of minutes and restarted the phone several times, and suddenly the soft buttons worked and Root manager had root access.
P-Froggy said:
I had that idea after flashing Deepshining V3: The readme says that you have to activate "Trust all applications" in Root Manager, I wanted to do that, but I got an error message "No root access. Be sure you have fully unlocked your rom".
This was very weird, because that's the app needed to permit other Apps root access.
Also, none of the 3 soft buttons worked.
I waited a couple of minutes and restarted the phone several times, and suddenly the soft buttons worked and Root manager had root access.
Click to expand...
Click to collapse
Looks like the phone is swapping or caching something for ages. Maybe it's a Storage card malfunctioning. So hopefully the fixing will be just card replacement.
Mhh, ok, so what should I tell HTC? I can't say that I wanted to install custom roms, but none of them is working, so the phone needs a card replacement xD.
I tried installing Dynamics V2.0 again, and it works until I try to install WhatsApp, then it ends up in bootloops.
But the original stock 7.5 Mango worked without any problems. If the storage card is damaged, the original rom would also not work.
P-Froggy said:
But the original stock 7.5 Mango worked without any problems.
Click to expand...
Click to collapse
Did you install stock Mango AFTER you had tried all possible customs and it worked w/o issues?
AndrewSh said:
Did you install stock Mango AFTER you had tried all possible customs and it worked w/o issues?
Click to expand...
Click to collapse
No, before flashing a custom Rom everything worked, and since I tried to install custom roms I have nothing but Problems...
P-Froggy said:
No, before flashing a custom Rom everything worked, and since I tried to install custom roms I have nothing but Problems...
Click to expand...
Click to collapse
So - once again - try to flash stock. If it works - the problem is installing HSPL. If it does not work properly - just send the phone to workshop. Maybe it's just bad coincidence - the card died when you had installed HSPL....
AndrewSh said:
So - once again - try to flash stock. If it works - the problem is installing HSPL. If it does not work properly - just send the phone to workshop. Maybe it's just bad coincidence - the card died when you had installed HSPL....
Click to expand...
Click to collapse
Maybe it works now.
I did the whole HSPL Flash Thing again and now I was able to install WhatsApp on Dynamics V2.0.
It's only a small Progress, but it is one.
I will try the Rom tommorrow and if it crashes again, I go back to Stock 7.5.
similar problem
my Problem is, that after installing the Dynamics Rom, the device is just showing the white bootscreen with the htc-logo on it.
I am still able to enter bootloader mode, but I don't see any advantage in it.
The device was Vodafone-branded.
I hope someone can help me.
Did you follow the instructions at this link http://forum.xda-developers.com/showthread.php?t=1684912 before flashing the Dynamics Rom?? If you didn't debrand and unlock with HSPL you get stuck or have the wrong radio rom installed.
malvo26 said:
Did you follow the instructions at this link http://forum.xda-developers.com/showthread.php?t=1684912 before flashing the Dynamics Rom?? If you didn't debrand and unlock with HSPL you get stuck or have the wrong radio rom installed.
Click to expand...
Click to collapse
I did. But I think I know what I was doing wrong. The step between finishing HSPL installation and Dynamics setup...should have I installed the phone first and done a Zune synchro? Cause I didn't -.-
Just install the radio rom that comes with the Dynamics rom. That should do it. You don't need a Zune synchro afterwards unless you want to copy pictures, music, videos back to your HTC.