Related
Hey All,
I just started working on my phone last night. I installed some 3.xxx radio, and a new ROM that I cooked up. The problem is I did not unlock the phone before I did it, so now I start the phone and it is stuck in a pre-splash screen. Does anyone know where I can get the stock Windows Mobile 6 ROM for it so I can re flash it and then re-cook it? Cause it has OBVIOUS signs that I tweaked it, so it would be hard to explain that it was something "A guy at circuit city" told me to do to get WM6.1. Please help!
Okay I need more specifics. What carrier are you working from?
Stuff
Verizion X6800 went from 2.04 radio to a 3.xxx and wm6 to wm6.1
Just flash your phone with Olipro from microSD card, then u can flash any ROM (exp DCD 3.2.6) also from SD card.
shag1233 said:
Hey All,
I just started working on my phone last night. I installed some 3.xxx radio, and a new ROM that I cooked up. The problem is I did not unlock the phone before I did it, so now I start the phone and it is stuck in a pre-splash screen. Does anyone know where I can get the stock Windows Mobile 6 ROM for it so I can re flash it and then re-cook it? Cause it has OBVIOUS signs that I tweaked it, so it would be hard to explain that it was something "A guy at circuit city" told me to do to get WM6.1. Please help!
Click to expand...
Click to collapse
Make it easy on yourself. Flash a Telus or Sprint ROM over to your phone. THis will fix any booboo's. YOU MUST STOP CARRIER CUSTOMIZATIONS from runing. After this is done, reflash with nueSPL 2.47 like you did and then put on a custom ROM.
This is your easiest option.
If you want the hard route put your phone in bootloader mode and tell me line by line what you see. That will tell us at what state you are in if you really want to try to figure out what you did wrong.
Either way, let us know how it turns out.
Read here for steps:
More info
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
Its still messed up trying the other suggestions. Does anyone know where I can get the original. WM6 rom so I can try again. Or can I unlock it without it so I can load a ROM....also I don't have an SD card.
Thanks for all the help so far
I had Magloader and WP7 in it. As time went by I upgraded to HD7 and never looked back. It's been a while since I have touched XDA and WM6.5.
My assumption is that even with Magloader, you only have to flash your stock ROM and it'll revert back to WM.
Mine won't go on and I suspect that I flashed a Non-Tmobile compatible ROM. Can someone confirm that this is the case? Here's the ROM string: RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.0 7U_2.04.50_22_2_Ship.exe
I understand completely that if I messed it up then it's messed up. I just wanna make sure there might be other solutions or something I am missing out.
-Thanks in advance!
----------------------------------
Is this a final answer? I need to know if it's bricked and nothing else can be done.
Anyone thinks a shop may be able to recover it back? It won't go on at all..
tictac0566 said:
Sometimes, it´s easier than you think.
You´ve got 2 options to get rid of HSPL. One of those options would be simply described in the original thread of HSPL.exe software. If you would have checked this program a little bit, you would have noticed the very fact that you can select what SPL or HSPL you want to install.
Second, you can flash your stock ROM via SD card method, this will replace HSLP and everything else - this does not work using RUU.exe via USB.
Click to expand...
Click to collapse
By the looks of the radio installed (2.04.50_22_2), I would say that you did brick your T-mobile phone. Take a look at the following thread for a possible solution to unbrick your phone:
http://forum.xda-developers.com/showthread.php?t=668347
Hi thanks for the response Lavell. Would MTTY be able to do anything?
The phone doesn't turn on at all, or it seems.
I've never bricked one before so Idk if this is the way it happens.
its gone. dead. it will need JTAGging or a new mainboard.
that thread wont help, the phone wont power on, and that thread requires you can get into bootloader.
that's a really early rom you used, the tmous didnt even exist when that rom shipped.
If you want to get rid of it let me know please!!!
Hey guys, don't mean to hijack the thread but I got the same problem here.
Had WP7 but could not use 2g so I went back to MAGLDR113 and installed the file below:
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship
It went all the way to 100% but now the phone is dead. Computer makes a sound when I plug in usb but I have tried changing batteries and all but it doesn't work.
Does anyone know in Dallas or areas around how to do that JTAG thing?
There is no proper documentation on how to go back to stock 6.5 Windows or at least I could not find one
S2K_MoZo said:
There is no proper documentation on how to go back to stock 6.5 Windows or at least I could not find one
Click to expand...
Click to collapse
At its most basic, its the same for ALL hd2's, ,
1 get the correct stock rom for your region&vendor
2 flash it
thats it.
Sadly lots of times this is shortened to
1 get stock rom
2 flash it
and people just assume they can use any stock rom, and since they usually already have HSPL installed, it allows the flash to start, and tmous phones die.
Yeh think the HSPL installer should of had a TMOUS version either blocking known bricking radio & ROMs or just an on screen message warrning & advising on checking before comencing with flash.
At end of the day it is the users fault for not researching or using a TMOUS rom to be 100% safer !
http://dl.htc.com/ruudownload/t-mobileUS/Filedownload.aspx?pid=leo
Fellow XDAers,
I'm in dire straits for some assistance.
I've been a member for some time now, lurking here and there, contributing when I have something of value. I've been through several phones, with an EVO 4G being my latest acquisition. Once I left Sprint as my carrier (Monthly rates were just too high for my blood), I was left with a phone that I couldn't flash to another carrier worth my valuable dollars (yes I know I could flash to Cricket or Metro PCS but I've never been a fan of their service). So, I started reading this forum and may others in regards to rooting and flashing.
After accomplishing this and having a case of ORD, I finally settled on FreshROM.
It worked well and outside of the occasional lag, I was pretty happy with my setup. Then a friend of mine finally converted from the TP2 to the EVO 3D. After answering several of his questions about rooting and flashing, he made the leap and flashed InfectedROM w/ beats audio baked in.
Being an audiophile and music blogger, I was of course interested to see if there was a ROM available w/ beats in it for my device. I found this one HERE called BlazingROM and installed the file from the first D/L link using the normal SD card method and Clockwork.
I of course cleared the Dalvik and the other cache. I didn't make a backup of my FreshROM as I already had one on my SD Card and in Dropbox for safekeeping as well as a Stock Odexed backup just in case.
The ROM installed just fine and I was enjoying the different elements of it while re-installing my apps with Titanium Backup when, the ROM started giving me messages that I was running low on internal storage space. I stopped TB and started using Apps2SD to move what I'd installed so far to the card. I then went back to TB to finish but with every installation, I'd get the "Internal Memory Low" message again.
By this time, I was scratching my head. I mean, yes I do have 20 must have apps but with FreshROM and Apps2SD, I was able to have almost all of those apps on the SD card without any issue. Now with this BlazingROM, why would I be encountering this issue? I then noticed that this new ROM had some sort of baked in Task Manager, which was the process giving me the error messages. So I attempted to use it instead of A2SD to move anything I could to the card. After doing so, I once again went back to TB to finish but upon the first install, I got the error message again. By now, I'm getting a little pissed and I still haven't even tried out the beats audio part of the ROM yet.
So, I decided to go back to basics. I opened Clockwork and did a Dalvik wipe and a re-flash of the ROM. Once that finished, I re-booted the phone. It was to no avail, as the Task Manager happily told me my Internal Memory was still too low.
I kind of panicked, not really…but a little…but I kept my wits about me and quickly went back to the post I got the ROM from in search of answers. I scoured any and all related replies which the consensus of brought me to the conclusion that my SD card should be formatted and then partitioned to accommodate the BlazingROM’s internal memory quirk.
Having no need to ever do so before, I then asked Mr. Google how it is properly done. Of course searching there brought back many links and after reading the majority of them, I settled on the method that involved ditching Clockwork Mod for Amon Ra’s recovery as it had more necessary options to partition than CW. That accomplished, I then found a guide for the different sizes of partitions as well as a discussion on the difference between EXT2 and EXT3 as well as the pros and cons of upgrading from one to the other.
I opted to leave the swap size at 0 (zero) and go for a 512MB partition. Once that was done, I then once again went through the steps to get BlazingROM flashed and running and once again, the evil “Internal Memory Low” message laughed at my efforts.
Fine I thought, I'll just go back to my good old trusty FreshROM until I come across another one w/ beats audio and none of these memory issues. I turned off the device, went to the Bootloader, chose Recovery and from CW Recovery, wiped the Dalvik again and chose to install FreshROM from zip on SD card.
Everything was going fine. It installed and I chose to re-boot the phone. That's when tragedy struck.
When my phone attempted to start up, the normal Boot Screen I'd come to love, where if you have the volume up, you see a hybrid of Tux and Andy while being greeted with a stylized "FRESHHHHHHHH!!" became stuck in the dreaded Boot Loop.
Back I went to Mr. Google to get some answers. This time he directed me to posts from here at PPCG to XDA to Android Central and various others. Almost every post I read instructed me that a Boot Loop could easily be fixed by placing the PC36IMG on the roots of my card and allowing the Recovery to find it in the Bootloader. I did so but it didn’t seem to make any difference. The phone continued to loop.
I did a battery pull but this time when I went to the Bootloader, ensured that it was indeed finding the PC36IMG and re-booted, I ended up with the Black HTC screen with four exclamation marks in the corners.
I’d never seen this screen before…so now I’m really panicking.
Off I went again in search for a solution. This time, I came across posts at all of the sites mentioned before but with a different solution involving the use of an RUU to take the phone back to it’s out of the box stock ROM state. Fine I thought. The phone will still be S-Off and I’ve got everything backed up on TB and Dropbox, it won’t be hard to get it back to where it was.
After checking the posting dates to ensure I was getting fresh info and links, I ended up at Shipped-ROMS. I D/Led what appeared to be the latest one and most recommended (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe) to remedy my issue along with some instructions in a Word Doc regarding it as well that I found on another site. I even followed another post that added that I should install HTC Sync in order to have the right drivers on my PC for the RUU to work properly.
Long story short, after trying 10 different RUU’s as well as installing HTC Sync, uninstalling Sync and installing different HBoot drivers (2.10, 2.02, etc.) in all possible combinations, the only thing I’ve managed to do is end up with my phone still showing a Black HTC four exclamation mark screen. The only time the screen is different is when the RUU fails (either due to Error 152, Error 238 or Error 330) and I unplug the USB cable. The screen then shows an RUU Bootloader with these results:
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0808
Mar 30 2010, 11:24:04
RUU
Parsing ….[downloading ZIP]
[1] RADIO_V2 -OK
[2] SPLASH -Fail-PU
[3] RECOVERY -Fail-PU
[4] WIMAX -Fail-PU
[5] USERDATA -Fail-PU
[6] BOOTLOADER -Fail-PU
[7] SYSTEM -Fail-PU
[8] BOOT -Fail-PU
Partition update fail!
Update Fail!
For some reason, each and every RUU gets up to around 32% to 40% and begins to show signs of failing while Updating User Data.
I’m reluctantly conceding defeat on this, as I have no clue as to what to do now. I’ve even gone as far as downloading Android SDK to try and figure out how to push the RUU or some kind of fix through ABD Shell.
If anyone has anything constructive that could help, I’d appreciate it greatly.
Wow. sorry my friend. I feel your pain as something similar happened to me with a HD2 once..my nand had gone bad. it seems you have pretty much tried everything. only recommendation I have is if you are still able to flash stuff try older version radios (downgrade radios first) before you try to RUU and don't neccesarily go for latest RUU you find. also leave out your SD card while trying the RUU. - fully format your SD card is also another thing I did not see in your long list of things you already tried? if you can't flash thru recovery (or maybe even your recovery somehow is messed up!?) try this new tool called Android Flasher I just saw someone has released on XDA. looks very good but I have personally not tested it yet. http://forum.xda-developers.com/showthread.php?p=18279765#post18279765
good luck maybe one of these combinations might work.
Gonna try and see what this can do to help later this evening. I appreciate the help and will report back what happens.
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
When flash was full, HTC titan began freezing at random places, I deleted some pictures/videos/apps, looks okay until during charging it suddenly reboots and now it is stuck at bootloader HTC screen, I did hard reset, same thing, factory reset, one of 3 tries of factory reset, I can get to windows however only basic phone call works, everything else crashes. The other 2 out of 3 hard reset attempts, either stuck at installing apps (during the initial setup phase), or stuck at HTC logo.
Finally out of options, I tried to use RUU (ROMUpdateUtility.exe) with the downloaded original US Cingular ROM (Original named IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.02.26_A_16.27.00.23_Signed_ETERNITY_RELEASE.nbh renamed to ETERIMG.nbh in order to flash), and got same crash/freeze as above. By the way I did verify the SPL bootloader matched the ROM.
Contacted HTC support, they say I have to send it for repair if I want to go that route, anyone know how much they charge? Mine is out of warranty. Only 1.5 years!
Right now it is stuck at installing apps again, and it seems getting harder and harder to get past that stage in order to have basic phone call functionality.
Try to boot phone without any sim card and give feedback
Sent from my GT-I9205 using xda app-developers app
jopa7 said:
Try to boot phone without any sim card and give feedback
Sent from my GT-I9205 using xda app-developers app
Click to expand...
Click to collapse
Hi, thanks for reply. Results are the same as before except it gives warning SIM ERROR when there's no sim card.
sf3000 said:
When flash was full, HTC titan began freezing at random places, I deleted some pictures/videos/apps, looks okay until during charging it suddenly reboots and now it is stuck at bootloader HTC screen, I did hard reset, same thing, factory reset, one of 3 tries of factory reset, I can get to windows however only basic phone call works, everything else crashes. The other 2 out of 3 hard reset attempts, either stuck at installing apps (during the initial setup phase), or stuck at HTC logo.
Finally out of options, I tried to use RUU (ROMUpdateUtility.exe) with the downloaded original US Cingular ROM (Original named IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.02.26_A_16.27.00.23_Signed_ETERNITY_RELEASE.nbh renamed to ETERIMG.nbh in order to flash), and got same crash/freeze as above. By the way I did verify the SPL bootloader matched the ROM.
Contacted HTC support, they say I have to send it for repair if I want to go that route, anyone know how much they charge? Mine is out of warranty. Only 1.5 years!
Right now it is stuck at installing apps again, and it seems getting harder and harder to get past that stage in order to have basic phone call functionality.
Click to expand...
Click to collapse
Stop please! You need to tell us what exactly do you mean when your flash is full...your internal memory? It appears by your 2nd paragraph you're attempting to HSPL your device. If you're stuck at the HTC Logo it normally means you're using the wrong radio firmware for the rom; my device for example is HSPL...I will never forget the effort I put into that feat, but the radio had to be changed to version 17 not 16 though you will find roms that will operate on 16, so let's start with what exactly are you trying to do...thanks!
berrywr said:
Stop please! You need to tell us what exactly do you mean when your flash is full...your internal memory? It appears by your 2nd paragraph you're attempting to HSPL your device. If you're stuck at the HTC Logo it normally means you're using the wrong radio firmware for the rom; my device for example is HSPL...I will never forget the effort I put into that feat, but the radio had to be changed to version 17 not 16 though you will find roms that will operate on 16, so let's start with what exactly are you trying to do...thanks!
Click to expand...
Click to collapse
The Titan was untouched, unmodded, fully functional. Then over time ts internal flash drive (16GB) became totally full.
Deleted some pictures/videos from within Zune software, uninstalled some apps and I get back 1GB or 2GB.
Recharged again then during this recharging period, it rebooted, ever since then, it became the state as I described in original post.
Sometimes stuck at HTC logo, sometimes after another factory reset (accessed from vol up + vol down + power HSPL menu),
The radio was 16, and the RUU program indicated it installed the 389(?)MB rom successfully, I made sure I downloaded the original cingular rom that had same radio 16 number.
Just trying to get Titan alive again, not even attempting custom firmware. From what I read on the forum, I will need USB-Y cable + goldcard
to install custom stuff. However I believe the RUU program I used allows flashing of stock ROM.
sf3000 said:
The Titan was untouched, unmodded, fully functional. Then over time ts internal flash drive (16GB) became totally full.
Deleted some pictures/videos from within Zune software, uninstalled some apps and I get back 1GB or 2GB.
Recharged again then during this recharging period, it rebooted, ever since then, it became the state as I described in original post.
Sometimes stuck at HTC logo, sometimes after another factory reset (accessed from vol up + vol down + power HSPL menu),
The radio was 16, and the RUU program indicated it installed the 389(?)MB rom successfully, I made sure I downloaded the original cingular rom that had same radio 16 number.
Just trying to get Titan alive again, not even attempting custom firmware. From what I read on the forum, I will need USB-Y cable + goldcard
to install custom stuff. However I believe the RUU program I used allows flashing of stock ROM.
Click to expand...
Click to collapse
I was going to recommend Goldcard and it works perfect! You're stock so you need a stock ROM. Double check your model #, mine for example are PI39100s. I HSPL'd my Titans via Goldcard. You might want to attempt the HSPL process if you're nuts enough to try it. But be aware you will need the correct debranding ROM to do so. But for your purposes, you need "stock". I was really surprised how easy the Goldcard method is...it picks it up right out the blocks and you follow the prompts.
berrywr said:
I was going to recommend Goldcard and it works perfect! You're stock so you need a stock ROM. Double check your model #, mine for example are PI39100s. I HSPL'd my Titans via Goldcard. You might want to attempt the HSPL process if you're nuts enough to try it. But be aware you will need the correct debranding ROM to do so. But for your purposes, you need "stock". I was really surprised how easy the Goldcard method is...it picks it up right out the blocks and you follow the prompts.
Click to expand...
Click to collapse
The RUU.exe works with stock firmware reflashing already, so when I tried it it was stuck at 4% complete for a minute, then 67% for 30 sec, then 87% for 30 sec, then finally complete 100% successfully, then after reboot, it enters the setup stage and stuck at installing apps again even after 10 minutes. There's something wrong with the phone, so weird, maybe a hammer will do the trick.
this is where i got stock rom (googled htc rom)
http://www.persianhtc.net/index.php?dir=Titan(Eternity)(Bunyip)(Ultimate)/rom/original/nbh/
Maybe I will try another stock rom, IMG_Eternity_Cingular_2.01.502.04_Radio_16.23.03.17_16.27.00.23U_OS_7.10.7740.166.nbh and see what happens.
sf3000 said:
this is where i got stock rom (googled htc rom)
http://www.persianhtc.net/index.php?dir=Titan(Eternity)(Bunyip)(Ultimate)/rom/original/nbh/
Maybe I will try another stock rom, IMG_Eternity_Cingular_2.01.502.04_Radio_16.23.03.17_16.27.00.23U_OS_7.10.7740.166.nbh and see what happens.
Click to expand...
Click to collapse
Bear with me for a moment...I own a HD2 which is a joy to flash Android and Windows Phone or the both of them, WP on NAND and Android on SD. I've had devices dating back to Windows Mobile 6.1 and flashing my Titans is identical to flashing all the rest of them once you're developer/interop unlocked to do so. As the HD2s age, their internal ROM become corrupted so the gurus here came up with NativeSD, now I realize were talking about two different animals here but when you flash a Windows Mobile/Phone operating system you reformat and erase whatever it is to be installed on; it doesn't matter if its micro sd memory cards or internal rom. I don't know if there is an equivalent Task 29 (wipes the memory) for the Titan's internal rom or is it even necessary; it's standard procedure on the HD2 via the HD2 Toolkit. I want you to do me a favor and send me what is on your bootloader screen, specifically the SPL, I'm thinking it's 2.05 but there are some others running around too. It is clear you can flash, but when I'm hung on the HTC logo it's the radio that is wrong, so please double check that the radio is correct. I'm not aware there are any radio 17s out there on stock but I am by no means an expert at all of this. Know this, there is the real possibility that you have a corrupted internal memory and where it is corrupted or fragmented is a big deal. I'm asking myself can the memory be erased before flashing and I don't have that answer. The roms you're using suggest you're not using a Windows Phone 7.8 stock Rom, but neither do I know if there is a stock flashable 7.8 Rom; I have the debrand 7.0s but none of the Mango 7.5s; I only have the flashable custom 7.8s but will look later this evening for one. I realize I may have asked you this before but please let me know what your model number, SPL, radio, and verify one more time if upon completion of the rom install does the phone reboot automatically after initial setup...the language, time, date, you hit next and start installing apps...is it the first install apps or afterwards where you hit next before you get to the start menu for the very first time. If at all possible do you remember inside your settings, under "about" how much memory you had, and how much was available. Thanks!
sf3000 said:
this is where i got stock rom (googled htc rom)
http://www.persianhtc.net/index.php?dir=Titan(Eternity)(Bunyip)(Ultimate)/rom/original/nbh/
Maybe I will try another stock rom, IMG_Eternity_Cingular_2.01.502.04_Radio_16.23.03.17_16.27.00.23U_OS_7.10.7740.166.nbh and see what happens.
Click to expand...
Click to collapse
_________________________________
|
| PI3910
| SPL-2.1.160015.3(133679)
| eMMC SMS 15028MB, FA32
| TOUCH A1(F:81,ID:1,V11,B:F8)
|
| Radio-16.23.03.17
|
| Serial
| APPSBL
|
| IMG CRC
| FACTORY RESET
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is what it looks now after succesfully flashing the IMG_Eternity_Cingular_2.01.502.04_Radio_16.23.03.1 7_16.27.00.23U_OS_7.10.7740.166.nbh
That means it upgraded successfully to a more updated Cingular stock rom, if I can use RUU to flash stock rom again
and again, it means writing internal flash is okay(?), but reading internal flash becomes problematic. I noticed
recently I can't even get to setup screen.
berrywr said:
Bear with me for a moment...I own a HD2 which is a joy to flash Android and Windows Phone or the both of them, WP on NAND and Android on SD. I've had devices dating back to Windows Mobile 6.1 and flashing my Titans is identical to flashing all the rest of them once you're developer/interop unlocked to do so. As the HD2s age, their internal ROM become corrupted so the gurus here came up with NativeSD, now I realize were talking about two different animals here but when you flash a Windows Mobile/Phone operating system you reformat and erase whatever it is to be installed on; it doesn't matter if its micro sd memory cards or internal rom. I don't know if there is an equivalent Task 29 (wipes the memory) for the Titan's internal rom or is it even necessary; it's standard procedure on the HD2 via the HD2 Toolkit. I want you to do me a favor and send me what is on your bootloader screen, specifically the SPL, I'm thinking it's 2.05 but there are some others running around too. It is clear you can flash, but when I'm hung on the HTC logo it's the radio that is wrong, so please double check that the radio is correct. I'm not aware there are any radio 17s out there on stock but I am by no means an expert at all of this. Know this, there is the real possibility that you have a corrupted internal memory and where it is corrupted or fragmented is a big deal. I'm asking myself can the memory be erased before flashing and I don't have that answer. The roms you're using suggest you're not using a Windows Phone 7.8 stock Rom, but neither do I know if there is a stock flashable 7.8 Rom; I have the debrand 7.0s but none of the Mango 7.5s; I only have the flashable custom 7.8s but will look later this evening for one. I realize I may have asked you this before but please let me know what your model number, SPL, radio, and verify one more time if upon completion of the rom install does the phone reboot automatically after initial setup...the language, time, date, you hit next and start installing apps...is it the first install apps or afterwards where you hit next before you get to the start menu for the very first time. If at all possible do you remember inside your settings, under "about" how much memory you had, and how much was available. Thanks!
Click to expand...
Click to collapse
I did double/triple check radio is 16 for my very original stock rom and the roms I downloaded all have radio 16 as part of filename.
Model: PI39100
SPL: Original: 1.10, now is 2.1
Right now can't even get to setup screen now, it used to be 1 out 3 hard resets I can reach that stage, now it always reboots
after it failed to get past Windows logo stage (which happens about 8~20sec after HTC logo and AT&T logo stage)
sf3000 said:
_________________________________
|
| PI3910
| SPL-2.1.160015.3(133679)
| eMMC SMS 15028MB, FA32
| TOUCH A1(F:81,ID:1,V11,B:F8)
|
| Radio-16.23.03.17
|
| Serial
| APPSBL
|
| IMG CRC
| FACTORY RESET
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is what it looks now after succesfully flashing the IMG_Eternity_Cingular_2.01.502.04_Radio_16.23.03.1 7_16.27.00.23U_OS_7.10.7740.166.nbh
That means it upgraded successfully to a more updated Cingular stock rom, if I can use RUU to flash stock rom again
and again, it means writing internal flash is okay(?), but reading internal flash becomes problematic. I noticed
recently I can't even get to setup screen.
I did double/triple check radio is 16 for my very original stock rom and the roms I downloaded all have radio 16 as part of filename.
Model: PI39100
SPL: Original: 1.10, now is 2.1
Right now can't even get to setup screen now, it used to be 1 out 3 hard resets I can reach that stage, now it always reboots
after it failed to get past Windows logo stage (which happens about 8~20sec after HTC logo and AT&T logo stage)
Click to expand...
Click to collapse
My apologies that I haven't replied sooner; I'm a full time college student thus I'm a bit busy. If your SPL is 2.1 then you have not successfully installed the Cingular 1.10 ROM otherwise your SPL would read 1.10 which this ROM and the European 1.09 ROM are used to downgrade the SPL on the Titan for HSPL and custom ROM flashing...which you've made me aware that is not what you're attempting to do but it is one of the steps towards doing just that. I'm going to attach my notes on my HSPL of my device which is extensive. There might be something in it that might help you. But for example my bootloader reads: PI39100...HSPL2.5.160015.3(137079)...eMMC SND 15188MB...CotullaH(F:81, ID:1,V11, B:f8)...double space...Radio-17.5006.08.27. I realize you're not trying to HSPL but if you are able to get your SPL to read 1.10, I think you should try it, the worse that can happen to you is the SPL will read SPL2.5.160015.3 not HSPL2.5.160015.3. I still recommend the Goldcard Method. My notes will be attached as a Word file.
berrywr said:
My apologies that I haven't replied sooner; I'm a full time college student thus I'm a bit busy. If your SPL is 2.1 then you have not successfully installed the Cingular 1.10 ROM otherwise your SPL would read 1.10 which this ROM and the European 1.09 ROM are used to downgrade the SPL on the Titan for HSPL and custom ROM flashing...which you've made me aware that is not what you're attempting to do but it is one of the steps towards doing just that. I'm going to attach my notes on my HSPL of my device which is extensive. There might be something in it that might help you. But for example my bootloader reads: PI39100...HSPL2.5.160015.3(137079)...eMMC SND 15188MB...CotullaH(F:81, ID:1,V11, B:f8)...double space...Radio-17.5006.08.27. I realize you're not trying to HSPL but if you are able to get your SPL to read 1.10, I think you should try it, the worse that can happen to you is the SPL will read SPL2.5.160015.3 not HSPL2.5.160015.3. I still recommend the Goldcard Method. My notes will be attached as a Word file.
Click to expand...
Click to collapse
Mine was SPL 1.1 before any flashing, now it is 2.1 because I flashed a SPL 2.1 Stock ROM.
Let me try to flash it back to SPL 1.1 again. I am not planning to use custom ROM so I don't think I need a gold card for now.
Used same RUU to flash back to HSPL 1.0 from 2.1, anyway it still looks dead to me. It's a loss.
Anyway thanks everyone for the help.
The weird thing is I can flash back and forth between 1.0 and 2.1, meaning internal flash drive has no issue during writing.