The problem I'm having is pretty severe!!!
My HTC 8525 was working fine until I tried unlocking it via Hermes unlocking tool,
It started off well, booted to the progress screen, but did not move...
When i tried resetting it, it went back to the 4 color screen, red blue green, white...
At this point I tried a hard reset, which did nothing but go back to the same screen.
I then went to htc'a website to see if I upgraded my rom to WM2006 to see if I can get back into my phone, but it goes to %12 in progress, then just freezes up...
When looking at image version its being upgraded too, it shows blank, as the upgraded image shows something, whatever it may be...
I have tried other upgraded roms, as well, but to no avail...
I know their is something that can get done, due to the fact that i can get to my boot screen!
Some help would be appreciated!
THANKS!!!!
What version of SPL are you using on your device?
Try SPL V7
http://forum.xda-developers.com/showthread.php?t=296722
When I tried doing that my phone doesnt even detect anything..
Is their a way that could go ahead and just install the orirginal rom that came with it and the radio...
Isnt just like installing a new OS like Win XP Or vista?
I had a similar issue. Just flash back to an original ROM and you should be fine. It worked for me.
I know their may be a thread about this already, but I honestly have no idea how to flash back my rom!
The problem is with most of these rom upgrades etc is that you need to use activesync, but that would not be possible to do in my situation....
Please some simple basic instructions would be great!!!
Thanks
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
ruff_ryder_v12 said:
I had a similar issue. Just flash back to an original ROM and you should be fine. It worked for me.
Click to expand...
Click to collapse
Um? How? I didn't think I could 'go back' ??
see this thread:
http://forum.xda-developers.com/showthread.php?t=356231
Related
I posted this in the Titan forum by mistake. Sorry for the duplication
I need some help...I'm freaking out...
I cooked a ROM with dcd's version 1.6.9 for BELL a few days ago and it was wonderful and worked great.
Today, I tried to upgrade to version 1.6.10 and I f___ed something up.
It starts the htc boot up screen as usual, then the Bell screen comes up as usual, then a Sprint screen comes up briefly and then the Windows Mobile screen comes on and HANGS........
I have tried cold reboots, and nothing. I cant connect to it with USB.
I can kick myself for making an error because I was rushing......
Can anyone please help............................
Edit/Delete Message
koilmaker said:
I posted this in the Titan forum by mistake. Sorry for the duplication
I need some help...I'm freaking out...
I cooked a ROM with dcd's version 1.6.9 for BELL a few days ago and it was wonderful and worked great.
Today, I tried to upgrade to version 1.6.10 and I f___ed something up.
It starts the htc boot up screen as usual, then the Bell screen comes up as usual, then a Sprint screen comes up briefly and then the Windows Mobile screen comes on and HANGS........
I have tried cold reboots, and nothing. I cant connect to it with USB.
I can kick myself for making an error because I was rushing......
Can anyone please help............................
Edit/Delete Message
Click to expand...
Click to collapse
Try the hard reset.
If that doesn't work then try the bootloader mode and reflash it.
Hard reset
Hard reset did not help, it hangs on windows mobile screen.
Can u give me a bit more detail on how to get into the bootloader mode?
I figured it out. You have to but it into bootloader mode by pressing the POWER and CAMERA buttons at the same time and then reboot.
Then load ROM as usual'
Thankyou
You are the fing master. OMG mine was in the EXACT situation and i was freaking out. its currently reloading the ROM back on. Thank you soooooo much.
it probably happenned because modules overlapped, run g'reloc before building to avoid this.
I have a 3125 that I acquired in a semi-bricked state. Bought it for spare parts, but think that maybe I can get it working. It will not boot to WM mode. Boots to bootloader with buttons held at power-on, which reports IPL 4.01.0001 and SPL 4.01.0000.
It recognizes the USB and the update tool recognizes it. But when the update starts, it never gets past 0% on the phone and the update tool eventually errors out and reports I need a newer update tool.
If I put in a µSD with the update file, it goes to the white screen briefly, saying it is checking the SD card, then goes back to tri-color.
I have tried both methods with the original Cingular ROM and the updated one. The µSD is properly recognized by a working phone with bootloader 2.04 (instructs me to press the key to perform the update, though I have not done so).
I have seen here that you must flash via µSD using only an official ROM, which I am doing, but I think that perhaps I don't have the correct official ROM to match this bootloader.
I do not know the history of the phone, so don't know how it came to have bootloader 4.01 or if the bricking happened at that time or later.
This is similar to, but not quite the same as, other threads I have seen where phones bricked after a bad load of WM6 and for which I have not seen a resolution. AFAIK, this was taken out of service before the WM6 ROM was cooked, but an attempt may have been made to load just about anything out there.
At this point, I don't really care what version of ROM gets in there, because I can use the informtation here to put what I want in once I can get to WM5. So, any light on what ROM I should try?
Anybody?
Well, my other 3125 is acting up (randomly resets itself) and now I'd REALLY like to get this one working. Anybody have a clue as to what I can try?
randomly reboots usually means that your battery door is loose. You ever get that "extra" one working?
rom
I have a 3125 with the same ipl/spl and have loaded several roms with no problem.
The link is for the official htc/cingular release. Try via ruu (with sd card removed) first, then if it does not work try the sd method. gl
http://download.america.htc.com/RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
lewnetoons said:
I have a 3125 with the same ipl/spl and have loaded several roms with no problem.
The link is for the official htc/cingular release. Try via ruu (with sd card removed) first, then if it does not work try the sd method. gl
Click to expand...
Click to collapse
I have tried both official ROMs with the same results both via PC and via µSD. What is the source of that IPL/SPL? (What ROM image loads it)? I suspect that if I can get THAT ROM image, then I can ressurect the phone. Maybe not and it really is bricked and the error message isn't really accurate.
Yours likely is SuperCID, so you can load anything, where this one appears to not be.
For the one who suggested the problem is the door: unfortunately not. A new door was one thing I did get from the bricked phone. Might be the actual door switch, though. I could try disabling it. Anybody know if its NO or NC?
rom
I will try to find out which rom loaded the ipl/spl, the only unlocking done on the phone is before I change a rom, I run the surrealnetworks cab. (app unlock)
will let you know what I find out reference the ipl/spl
the other thing you might want to try, is download all of the roms and run them, they are listed int he first sticky.
Tiger Shark said:
I have a 3125 that I acquired in a semi-bricked state. Bought it for spare parts, but think that maybe I can get it working. It will not boot to WM mode. Boots to bootloader with buttons held at power-on, which reports IPL 4.01.0001 and SPL 4.01.0000.
It recognizes the USB and the update tool recognizes it. But when the update starts, it never gets past 0% on the phone and the update tool eventually errors out and reports I need a newer update tool.
If I put in a µSD with the update file, it goes to the white screen briefly, saying it is checking the SD card, then goes back to tri-color.
I have tried both methods with the original Cingular ROM and the updated one. The µSD is properly recognized by a working phone with bootloader 2.04 (instructs me to press the key to perform the update, though I have not done so).
I have seen here that you must flash via µSD using only an official ROM, which I am doing, but I think that perhaps I don't have the correct official ROM to match this bootloader.
I do not know the history of the phone, so don't know how it came to have bootloader 4.01 or if the bricking happened at that time or later.
This is similar to, but not quite the same as, other threads I have seen where phones bricked after a bad load of WM6 and for which I have not seen a resolution. AFAIK, this was taken out of service before the WM6 ROM was cooked, but an attempt may have been made to load just about anything out there.
At this point, I don't really care what version of ROM gets in there, because I can use the informtation here to put what I want in once I can get to WM5. So, any light on what ROM I should try?
Click to expand...
Click to collapse
I have exactly the same problem. Did you ever find a solution?
Timmoi said:
I have exactly the same problem. Did you ever find a solution?
Click to expand...
Click to collapse
No, and I've seen even more folks with phones in this condition after a bad WM6 load and still no solution.
My best guess right now is that whatever crashes the system during a load somehow corrupts the boot loader and we are therefore SOL.
I've solved my random resetting problem by acquiring yet another phone with a bad keypad and swapping out my old keypad into it. So my need is no longer critical, but I'd still love to find a solution.
Tiger Shark said:
No, and I've seen even more folks with phones in this condition after a bad WM6 load and still no solution.
My best guess right now is that whatever crashes the system during a load somehow corrupts the boot loader and we are therefore SOL.
Click to expand...
Click to collapse
Just what I was affraid of. Thanks anyway for the answer.
Tiger Shark said:
I've solved my random resetting problem by acquiring yet another phone with a bad keypad and swapping out my old keypad into it. So my need is no longer critical, but I'd still love to find a solution.
Click to expand...
Click to collapse
That's just what I had in mind already. Hope to find some nice and cheap Startrek on Ebay or something.
Try this Full ROM:
RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
I have the same IPL/SPL version as yours. I always use this FULL ROM to flash my cell phone when I had problem with my customized ROM.
uniface said:
Try this Full ROM:
RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
I have the same IPL/SPL version as yours. I always use this FULL ROM to flash my cell phone when I had problem with my customized ROM.
Click to expand...
Click to collapse
Tried it, but without any luck
Thanks anyway!
So after having my Mogul for quite sometime, I figured it was time to upgrade the ROM which includes the GPS, etc etc. I followed all the instructions to the "t" and when I go to update it, the phone goes to the tri-color and says "USB" at the bottom...but on my computer, it stays stuck at 0%.
I've left it go for almost 30 minutes. I end up having to shut down the update and reboot my phone. Luckily my phone wasn't affected at all. (whew!) I've tried this three times and all end up being stuck.
I'm new to all this, so ANY help would be greatly appreciated. I've searched for this same occurrence but have not read about any resolutions to the problem.
Thanks for any help!
Anyone have any suggestions?
Right now I have ROM version: 2.09651.3
I have downloaded a ROM for the Quest 'version' of the Mogul which is 3.35.656.2....will this work?
I dont get why it wont update and install the ROM.
Any help is greatly appreciated!
what version of bootloader are you using?
if its not giving you an error try letting it go overnight. Maybe its just going REAL slow.
Other than that, try one of the intermediate ROMs first, or try re-downloading the ROM and going from that.
The process is pretty simple, sync, backup anything important, establish activesync/MWDC connection, run the RUU, press yes several times, restore backup/resync.
Did you ever unlock the phone? The sprint ROMs wont load with an unlocked phone, AFAIK.
not sure what you mean by version of bootloader....
As far as running reall slow, not sure, I might try that if nothing else works.
I'm going to try the 3.35 ROM and see if that works. So stupid that it is such an easy task, yet it doesnt work....and I never "unlocked" the phone...its basically factory straight from Sprint. Again, it was bought back in December 2007 so the ROM on it is pretty 'dated'
I'll let ya know what happens...
2.09... lol.
that rom was slooow. screen flickered.
lockups.
your problem is that you cannot use a rom from a different carrier unless you unlock first. Just get the latest sprint rom and flash it.
edit: perhaps i read your post wrong. do you have the sprint or qwest rom? the qwest rom will not work. the sprint rom should work fine providing the phone has not been unlocked with olipro 1.2. Check the bootloader version when in the tri color screen. if it says olipro 1.2 then you need to update to 2.4.
If it's stock then you should be good. you could try putting the phone into bootloader before running the ruu. sometimes this helps the connection since it doesn't mess with activsync. to get to bootloader hold power + camera and hit the reset button.
I need help!! This is the third time ive reflashed. The first time my screen was working, i got all my programs installed. Went to make a call and the speaker doesnt work. they say they can hear me but i cant hear them. I can hear them if i turn speakerphone on. Weird. And also when i slide open the keyboard, the screen would take unusually long to change to landscape and then not change all the way. That was fine i said i could deal with it. But just awhile ago my screen stops working, all it is, is an off black screen of the backlight. So i reflashed it. All through the installation i did not see the progress bar on my screen, but saw it on my PC. So i reflashed it for a third time, and the screen is still the off black. I just reflashed it to an old ROM of 3.35. and still the problem persists. My brother says i need to flash the IPL back to stock. I have no clue what that is though. Need help please. Need my phone back working.
kemlittleman said:
I need help!! This is the third time ive reflashed. The first time my screen was working, i got all my programs installed. Went to make a call and the speaker doesnt work. they say they can hear me but i cant hear them. I can hear them if i turn speakerphone on. Weird. And also when i slide open the keyboard, the screen would take unusually long to change to landscape and then not change all the way. That was fine i said i could deal with it. But just awhile ago my screen stops working, all it is, is an off black screen of the backlight. So i reflashed it. All through the installation i did not see the progress bar on my screen, but saw it on my PC. So i reflashed it for a third time, and the screen is still the off black. I just reflashed it to an old ROM of 3.35. and still the problem persists. My brother says i need to flash the IPL back to stock. I have no clue what that is though. Need help please. Need my phone back working.
Click to expand...
Click to collapse
You may be able to update your radio only and fix the problem from what I was reading. Please read through the wiki completely and then PM me if you need help after that. The link is here. The radio upgrade is here.http://rapidshare.com/files/125052225/Titan_Radio_ROM_3.42.30.rar.html and you will upgrade using the sd card method described in the wiki. Read well and you will understand it.
sounds more like you need to replace your phone. but first, try reflashing from the very beginning:
install olipro 2.4 (if you havent)
flash official sprint rom
flash dcd 3.2.5
flash radio 3.42.30
serfboreds said:
You may be able to update your radio only and fix the problem from what I was reading. Please read through the wiki completely and then PM me if you need help after that. The link is here. The radio upgrade is here.http://rapidshare.com/files/125052225/Titan_Radio_ROM_3.42.30.rar.html and you will upgrade using the sd card method described in the wiki. Read well and you will understand it.
Click to expand...
Click to collapse
Okay. Ive downloaded the Radio file. but searching through the wiki link, i go to the page where it has all the different radios. But says nothing about the SD card method. cant i just install it like i install the ROM?
Okay i finally got it working. And i can hear people on the phone. but why when i slide open the keyboard to go into landscape mode. The screen lags up really bad and doesnt load half of the screen?
and what the hell. now my screens went out again? anyone know of what hte problem could be?
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
She lives!!!
Okay, I'm not actually sure if the problem is solved but I'm back in WinMo 6.5 for the time being.
Since it had been off for a few hours I tried my luck again, plugged it into the wall and saw that it was stuck in the boot loop again. But I got distracted and left it, and when I came back it was on the orange WinMo setup screen.
Not sure what happened to make it go from not even getting power from the battery to working normally. But I see now my radio version is 2.05 which is massively old, I'm going to try and upgrade that first and see... hopefully it won't go back to being dead the moment I power down.
Shawn_230 said:
I think I may have bricked my OG HD2 (T8585) while trying to undo everything I had done to it, which was HSPL, MAGLDR and a NAND Android ROM.
It all started when I first tried to flash Kingdom's Sense 3.0 Gingerbread ROM. It told me to create a 340MB partition using HD2 Toolkit which I did. I then flashed the ROM as per the instructions, but it kept getting stuck on the boot logo so I decided to go back all the way to stock WinMo.
I downloaded a stock 1.66 ROM from HTC's website, tried to flash it via USB which failed because I obviously have no ActiveSync in Android. So I loaded the image onto my SD card and tried to flash by holding Vol Down and Power.
That was the first sign of trouble, about 1/10th during upgrade process it gave me some errors and rebooted to a black screen with a silver warning triangle.
Trying to go back into bootloader, I got the message about "upgrade ROM code error."
Since it had reverted back to SPL 1.42 I tried to reflash HSPL2 through USB, which worked fine, got the "We bricked it " message and everything. But then I tried to install MAGLDR and nothing, it fails even though it recognizes the USB connection.
So what can I do? On the one hand my device can accept and load HSPL2 and my computer is recogonizing the USB connection, but other than that nothing, it won't even turn on without being connected to external or USB power.
I also tried installing stock 1.43 ROM and that goes fine, it gives me an okay on everything but it gets stuck in the white HTC bootscreen in a loop.
I know I probably made a huge glaring mistaking to cause this, it's probably because I've bought a Transformer tablet and a Galaxy S2 in the last month so the steps regarding the HD2 were probably a bit of a blur. I guess the stock ROM probably included a radio that I wasn't supposed to flash, causing my device to be bricked.
But is there anyway I can get some type of OS working on this poor HD2 now?
Click to expand...
Click to collapse
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
germotlp said:
I had pretty much the same problem as you, but mine is the tmobile us version. I tried flashing back winmo from android via sdcard method but i got an upgrade error. I tried flashing with microSD card sizes 8gb, 16,gb, and then 2gb which was recommended, but still no luck. I managed to connect the hd2 through usb on the tricolor screen and flashed back to hspl2.08 and magldr and cwm were still on. But i would like to still get back to winmo stock as if it came from tmobile.
My question is if i download the latest update from tmobile which is T-Mobile HD2 MR Software (Version 3.14.531.1), what is the correct spl i should have installed on the hd2 so that htc and tmobile wont know that i messed with the spl? is it 3.03? I was going to connect via USB on the tri color screen again, run the EXE and manually install the SPL? I just need to know which SPL to install after i run the latest winmo update. Please advise on the SPL and the method i'm going to take on reverting back to winmo. Thanks.
Click to expand...
Click to collapse
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
This is driving me crazy now...
I managed to flash HSPL 2.08, and then MAGLDR 1.3, and then CWM recovery on top.
But this still seems bricked to me, still needs external power to turn on and I can't actually flash a working ROM... flashing a ROM via USB gives connection error and flashing via SD card goes fine but gets stuck in a boot loop.
What can I do at this point short of tossing the phone? I've tried stock 1.48, stock 1.66, a bunch of radios from 2.05 to 2.15... everything.
I am doing some research but the only results I find are T-Mo HD2s being bricked by the wrong radio. I have an original HD2 and I never flashed a radio intended for another HD2 model, so how is my phone so bricked all of a sudden?
All the threads I've found say if you can get into the bootloader then there's some hope but I doubt it because I can't successfully flash anything with it. I don't even know how I managed to get back into WinMo briefly last night... think my HD2 is probably just toast.
Okay, I finally solved my problems for sure - bent charging leads in the battery compartment!
Anyone having boot issues, take out your battery and look at the metal leads and you will probably find them bent out of shape. They are incredibly flexible, so just make them straight again and it will work. I assume it cuts external power briefly right before booting into WinMo, which is why it was rebooting constantly.
So I suppose for me this was a huge case of confusion, I got all confused with bootloaders and MAGLDRs when the problem wasn't even software related.
Shawn_230 said:
So it sounds like you lucked out, huh? So your HD2 works at least? I believe if you succesfully flash an official ROM like from T-Mobile, it will replace everything including the SPL back to stock - this is what I was trying to do by flashing official 1.43, to go back to factory mode.
I seem to be worse off than you though. I posted last night how my HD2 was back up running WinMo, but as suspected the moment I rebooted it was back stuck in the boot loop.
Any ideas? I wish I could get the HD2 working again so I could set it aside and get to playing with my new Galaxy S2.
Click to expand...
Click to collapse
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
germotlp said:
The problem with my hd2 is the CPU is overheating thus causing it to freeze or lock up, and gets it annoying. After hours of searching on XDA, that's what seems to be the problem. I can't even talk on the phone for more than ten minutes or else locks up. So my idea was to get it back to winmo stock and see if it still locks up. If it does then i will probably try to send it back to HTC and see if they send another one maybe or fix it.
Ive had no luck luck flashing back to winmo from sdcard so i think i should try flashing back to winmo via usb on the tri color screen. Ive read on XDA that if you flash winmo via usb that it doesn't replace your SPL, and you have to run HSPL4 and flash it manually. I'm just not sure which SPL i should flash. I'm assuming 3.03 maybe?
What you could try is using an sdcard that is 2gb or less. Ive read that anything higher than 2gb will cause issues. I'm still a noobie at this rooting biz. Hope that helps.
Click to expand...
Click to collapse
Which model HD2 do you have?
Find and download the stock ROM from this thread, get 1.66 since it will work with HSPL2 which is the latest HSPL that will work with MAGLDR (for Android and WinPhone7).
You can flash that through SD card and it will go back to total stock, including stock SPL. I assume you know how to pull the .nbh file from the ROM you download, so just rename to LEOIMG.nbh and put it on your SD card.
Go into the tri-color screen and it should flash fine and give you factory reset. This is where it wasn't working for me, but not because I had flashed the wrong ROM or something but because I had messed up the charging leads in the back while popping the battery in and out to reboot as I was flashing.
Man I downloaded 1.66 last nite and tried to flash back to winmo from android and its toast. Not sure what went wrong. Oh well.
Sent from my HTC Sensation 4G using XDA App