OK, let me start by saying I am NOT getting the bootloader, I am NOT getting stuck on a startup screen, and I am NOT new to loading HTC ROMS (but I am new to the titan - former owner of Hermes). With that out of the way....
I bricked my Titan - It won't startup at all. Plugging it into the USB port generates a red LED and nothing on the screen. The only USB activitey seen on the computer is the HTC USB modem (no other communciation appears to be possible - no activesycn, no response to ROM updates etc.
This is the order of the bricking
1. Started with Default Verizon install (less than 4 days old)
2 unlocked with olipro 1.20
3 attempted install of Sprint 3.35 update to get radio (failed and rebooted device at 11%)
4. attempted intall of radio 3.27 (sucessful)
5. installed NexVision 3.35 cooked rom
6. ran into some stability with the rom (phone remained "Unactivated") and reverted back to ruu_signed_verizon stock ROM
7. Booted OK (phoen remained "unactivated"
8. reattempted install of sprint 3.35 (thinking rom instability was due to radio version) device rebooted itself at 11% and failed.
9. installed olipro 2.4 thinking it might circumvent the 11% reboot issue on Sprint ROM.(appeared sucessfull) phone never came back after that.
Now I'm dead in the water... Pulled the battery, Tried a hard reset (2 softkeys under screen/press soft reset) - no change in the device.
are there any secrets to unbricking a Titan?
Starting with the default Verizon ROM, updating to olipro 1.20
Hold off for a little bit, at the moment there is no unbrick, but ImCoKeMaN and jocky are working on this. Your phone now is booting into Qualcomm download mode and it is recoverable. It's just a matter of a patched loader to get a new spl on it...
thank (fingers crossed)... even tried the relocker by ImCoKeMan and it's not detecing the device either...
Time to be patient and wait for CoKeMan to come to the rescue.
just to make sure...
when you tried a hard reset... sometimes people dont know to hold the soft keys for a couple seconds (this is my experience anyway)
jsut for kicks try this again... press and hold the 2 soft keys, press reset button, keep soft keys held down, release reset button, wait a couple seconds then release the soft keys.
Hmmm I remember someone else with a similar problem not too long ago. He thought he had bricked the phone too and was getting the same red led when he plugged it in, but nothing else. His problem was that he had a defective battery. If you could get your hands on a spare battery I'd say try that...I'm not 100% sure it's the battery, and if it's not then I hope cokeman comes through for you...but if you can check that out, I definitely would.
gcincotta said:
Hmmm I remember someone else with a similar problem not too long ago. He thought he had bricked the phone too and was getting the same red led when he plugged it in, but nothing else. His problem was that he had a defective battery. If you could get your hands on a spare battery I'd say try that...I'm not 100% sure it's the battery, and if it's not then I hope cokeman comes through for you...but if you can check that out, I definitely would.
Click to expand...
Click to collapse
Was just about to post the same thing, red LED is definately an indicator of a battery issue, could be defective or just totally dead. If you unplug the battery and reinsert it and then plug in the usb charger without turning it on do you get a green LED? If so I would say battery is 100% discharged and wait for it to charge (I have had this happen). Otherwise if it is still red after that I would say replace the battery (I had this happen on my first titan, it was doa due to defective battery).
jjlwork said:
Was just about to post the same thing, red LED is definately an indicator of a battery issue, could be defective or just totally dead. If you unplug the battery and reinsert it and then plug in the usb charger without turning it on do you get a green LED? If so I would say battery is 100% discharged and wait for it to charge (I have had this happen). Otherwise if it is still red after that I would say replace the battery (I had this happen on my first titan, it was doa due to defective battery).
Click to expand...
Click to collapse
Exactly, all the roms downloaded from HTC recommend having at least a 50% charged battery.
Yup, battery was at 99% before the upgrades. with or without the battery in it reacts the same, with or without the USB in it reacts the same.
I left it plugged in all night, no change.
Solved (but not really)
Since the phone was brand new, Verizon techs took it back as a "faulty phone"... thankfully the Red LED to them means "bad battery" too and when they replaced the battery and it didn't fix itself they exchanged the phone.
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
wow, i didn't (i did-but not reallly) know that it was really really possible to brick your phone, i thought there would more or less always b e a way out. pretty scary!
Shadowmite said:
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
Click to expand...
Click to collapse
It's good that your phone was replaced, but to all the naysayers in this thread, you don't know what you're talking about. If the bootloader won't come up when you reset while holding power and camera, then the SPL is gone and the phone is booting into download mode. If you want to check this, connect to windows, it should find a new device, a qualcom debug port in download mode (you might need a driver for this).
The issue is being worked on and a solution will be found.
Click to expand...
Click to collapse
Ok well then I guess you could call me a naysayer then. And I assure you I am no dummy myself, in fact, I'm a Computer Engineer and work with embedded systems alllll day long. I don't doubt your knowledge about the bootloader and the SPL, but before you doubt MY knowledge explain this one to me. Stock battery, no bootloader, no nothing...just red LED. Replaced battery and all of a sudden phone boots...both normally and when forced into the bootloader.
I have the exact same problem. I don't remember exactly how it happened, but was similar scenario to previous posts. I believe I was trying to get the 3.35 radio installed for use with dcd's 3.0.1 kitchen, although I can't be positive.
QPST shows that it is seeing a Qualcomm device in download mode. Here is the exact model# it displays:
Q/QCP-XXX (Download)
Hope this info is useful to those that don't have a titan stuck in this mode.
Yep, that is a brick currently, but a method to fix it is being attempted.
Basically the phone has a dual core cpu with 1 core running the spl, and wince; and the other runs the oemsbl, qcsbl, and amss (the radio). Your spl is missing so the operating system core is doing nothing. However the phone side is still up and running. (this is mostly theory)
So we need to have a patched bootstrap to send in download mode (notice qpst software download actually sends over a bootstrap 7500.hex file found in your qpst bin directory) which will load the spl back into the correct areas of memory. I don't believe we can jump to it because we are on the wrong core.
Do you know which address range the SPL sits in memory?
JTAG ?????
Shadowmite said:
Yep, that is a brick currently, but a method to fix it is being attempted.
Basically the phone has a dual core cpu with 1 core running the spl, and wince; and the other runs the oemsbl, qcsbl, and amss (the radio). Your spl is missing so the operating system core is doing nothing. However the phone side is still up and running. (this is mostly theory)
So we need to have a patched bootstrap to send in download mode (notice qpst software download actually sends over a bootstrap 7500.hex file found in your qpst bin directory) which will load the spl back into the correct areas of memory. I don't believe we can jump to it because we are on the wrong core.
Click to expand...
Click to collapse
Hey Shadow, I think you are correct, and also possibly do you think that JTAGing it would work ? Grad the image from a good one and load it into a dead one. I do not yet have one to take apart yet to try, but if i get a bad one to take apart I might just get it.
It would be great to see this issue resolved as this same problem happened to me last nite and the "friendly" folks at Bell Mobility took one look at the phone and told me it was water damage. I've had the 6800 for about 20 days and it has not been close to water. Anyways, that's besides the point. I look forward to seeing some kind of resolution to the matter....thanks!
Do you see same in QPST ?
Escobar600 said:
It would be great to see this issue resolved as this same problem happened to me last nite and the "friendly" folks at Bell Mobility took one look at the phone and told me it was water damage. I've had the 6800 for about 20 days and it has not been close to water. Anyways, that's besides the point. I look forward to seeing some kind of resolution to the matter....thanks!
Click to expand...
Click to collapse
Do you see this same thing they report with the QPST also ??? Man I would not break mine to fix the problem, but would love to have one to poke at too.
Yes I am having the same problem phone basically dead....
Shadow may fix it, but,,,,
Escobar600 said:
Yes I am having the same problem phone basically dead....
Click to expand...
Click to collapse
I am not going to take mine apart to look for it, but i am sure there is a JTAG port inside these as there is every other I have seen.
Related
I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.
Thanks in advance if anyone can come up with something that helps... I can't imagine what that might be though!
This morning I had a stock Mogul... original ROM, no hacks, even had the Sprint S/W on it. It worked fine.
I downloaded the new Sprint ROM 3.35.651.2 and ran it. While running the Mogul rebooted, went to bootloader, then failed. It was then stuck in bootloader mode. I read up and found that a successful flash should bring it out gracefully so didn't troubleshoot much. I tried a couple of times more to no effect. It was still in bootloader mode.
I then downloaded the old 2.17.651.0 ROM from HTC and that wouldn't work either. Still in boot loader mode.
I read somewhere that a guy got the 3.16.651.0 leaked ROM to update even when the others would not. So, I downloaded and tried it. Everything looked good! It was loading the ROM, the bar went across the screen to 100% and then...
nothing. A black screen. Vista loaded some new drivers and seemed to know there was a USB device attached but I couldn't connect to it in any useful way through Explorer and it didn't show up in the Mobile Device Center.
I thought I'd try flashing it again but since the screen was black I was just guessing. I did a hard reset (both soft keys plus soft reset button) and I got nothing... not even the same connection I'd had after the 3.16 update.
Now, I plug in the device and get no USB connect sound or notification in Windows. I get a orange light on the right LED for maybe 15 seconds then it goes out. Other than that one brief LED the thing is a brick as far as I can tell.
Any ideas? I plan on taking it in to Sprint tomorrow and telling them they bricked my phone with their update if I can't figure anything out tonight.
Thanks!
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Geckotek said:
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Click to expand...
Click to collapse
Yes.
FYI... I just left the battery out for about 5 minutes (what the heck, worth a try right?) and put it back in. I get no lights, buttons do nothing, soft & hard reset do nothing, forced bootloader does nothing. The only way I can get the phone to do anything is to plug it in to a USB cable. The orange light comes on for about 15 seconds then goes out. The computer never recognized there is a new USB device attached.
I loaded many custom ROMs on my old 6700 and never had a problem. I leave my new 6800 alone and wait for the upgraded stock ROM and look what happens! Guess I shoulda used a custom ROM instead, eh?
lol sounds like a legitimate "brick" to me. Very strange, and congrats on your new mogul paperweight (i also have one that was a victim of water) haha, good for holding things down on the windy days.
Yup, bricked.
Sprint couldn't figure out how to unbrick it and just gave me a new phone. The new one upgraded nicely and now I have GPS!
Everyone enjoy the upgrade!
same problem
no need to retype what you said. i had the EXACT same problem. phone was completely bricked and continued to crash at 11%. I went to my local store (i work for sprint, and i know a smart tech there) and was told it was kaput. Hard reset, tried to reload other roms, the whole 9 yards. It's a goner, and now i have a new mogul in my hand. I'm afraid to try it again. I'm running vista, and im wondering if that's the problem.
Anyone with vista have the same bricking problem? Is it an issue to directly upgrade from factory rom to the 3.35? My old brick had the current 2.17 or whatever... HALP
Vista
The first time I tried the update I connected the Mogul to my Vista Business 64bit Thinkpad T61p.
The second time I tried it (on the new Mogul) was from my Vista Business 32bit desktop (white box).
I don't know if that helps or not. The second time went smoothly.
On another note... an entertaining one... while I was in the Sprint store today waiting for their tech to confirm that the phone was bricked another guy came in with a Mogul and complained of the same thing. I took the last Mogul they had in stock. Poor guy. I hope they get more soon... there are a lot of people who want GPS and are upgrading their phones. That means there are gonna be some more bricks I'd think.
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
Have HardSPL installed on phone. Got phone on eBay - has very few hours. Came with a Rom that displayed TEST ONLY which was WM5. GSM radio worked, Bluetooth worked and Wifi worked. Tried installing shipped HTC WM6 Rom - did it through ActiveSync - should have used MSD card. - Rom installed though everything was ok but didn't install a SIM card to test phone - used it as PDA and WIFI for a week no freezes. Now this morning wanted to switch phones over and inserted SIM - saw NO GSM on boot - never really noticed it before.
Checked in ABOUT section to see if a radio was loaded - comes up blank. Read some things about NO GSM errors - got a little nervous - so I thought I'd reflash entire ROM tonight with SD.
Followed directions and get into update process and it seems to freeze at GSM with progress bar at about 15% - for about 30 minutes.
Removed battery and it boots to TRICOLOR. (I freeked out at this point)
Put a HardSPLv7 on SD card and did the above - update was successful
Phone boots up to OS still with no GSM
Tried the update process again with the same ROM - still has problems and never gets past the same point as before. Will try another ROM but I'm a little doubtful. If I can recover it back again will try just upgrading radio to see if it makes a difference.
ANY SUGGESTIONS or is the hardware fried?
Thanks.
OK, think it may be back and I was able to reflash using a wm6 stock HTC ROM. Think either my original flash of the same ROM was bad - downloaded a new file and flashed with the SD - originally did it via ActiveSync.
To get it to work I did a couple of hardspl reflashes and got into the OS. DID a couple of hard resets and magically GSM appeared. Turned phone off and then NO GSM appeared again. Did the hard reset again - came back. Not taking anything for granted put in a SD card and reflashed. Held my breath and for some reason it did a complete flash and never really hung up for more than a minute or two. Soft reset - GSM was there. Turned phone off and on a few times and its still there. Phone now finds the GSM radio much faster than before. Can make and receive calls (does wake out of sleep) - signal strength is same on my other Cingular 2125. Will try out tomorrow and see how it goes. Either the reflash does it or something is loose in the hardware but if it works a few hours tonight it should be good.
Will be a little hesitant to reflash after this but will see after a stress test.
Hold both softkeys and hold the power button
You can also hold both softkeys and put the stylus into the reset hole. Tell me if that works.
Initially no. When I attempted to flash the HTC Factory Rom it froze. Prior to that I did a couple of hard resets using the two softkeys and reset pin. With the resets couldn't get the GSM radio to turn on. Tried the ROM flash but it froze (about 1/10 of the way) - so I basically OS bricked it by removing the battery when it was at this stage. Got to the bootloader screen. Tried to flash OS again with SD card - still froze. SO I thought reflash HardSPL and the OS magically appeared and did the steps above.
After a couple of hours - call made, turned off and restarted device no problems still have GSM radio. Can receive a call when in standby. May try to do another hard reset and see if it still works after a day or so of testing phone but I want to try it for a few days by turning it on and off and making and receiving calls. If I can do another hard reset and everything works I think it was just a bad initial flash through ActiveSync. May get bold and flash another ROM as a test.
Since the phone worked with the TEST OS when I got it I think the only factor is the WM6 flash that I did. More than likely the hardware is OK but only time will tell.
I don't believe you will recover your radio rom now as you interrupted the flash. It generally takes 30 MINUTES to flash a complete rom. You stopped it during the radio rom flash, BIG MISTAKE....
If you can find the SHIPPED STOCK ROM or the original radio rom then you might have a small chance at recovery, we're talking about you winning the lottery 10 times in a row chance...
If you try to flash anything but the original radio rom then you can kiss the phone functionality goodbye....
Good luck finding the right roms...
Cheers...
Its not bricked. In my post said I did a full recovery and its working with the stock HTC WM6 ROM with the HTC radio. I can receive and make calls. Able to ActiveSync with the PC and have hard reset a few times just to make sure all is well. I believe there is still a hardware problem - either a loose connection inside or something else is going on but I think its definately hardware. When the stylus is out of the holder EVERYTHING works fine - have a signal - can sync - can charge it - no issues. If I put the stylus in part way no problem - push it in all the way during a call it will still say connected yet will hear nothing and can't disconnect. Pressing end has no effect yet the phone will still function - just the in call symbol stays and the green led still flashes.
Turn it fully off and back on with stylus out - shows GSM radio code and phone will now work.
Have to check the service manual to see if the stylus holder when the stylus is inserted pushes on anything vital. Can't imagine thats it. But so far with the stylus out everything is ok. Will attempt to use it tomorrow see if thats it.
Know it sounds stupid but thats what I'm observing so far. Its late here see what happens tomorrow
Thing is running and can use the phone (no static, three bars) but last night had a few no GSM messages during a cold boot. Ran it all night and it seems to be working - booted a couple of times, charged it, sync'd it and actually put the stylus in (don't know if thats the problem) and still working. May be a loose connection that is currently ok but who knows when it will stop working. Other possibility is heat or a failing radio. Could also be battery but thats doubtful. Could have messed up the stack during the initial flash so I'll see over the next few days. This one is starting to drive me a little crazy because it works then for no reason it will stop then resume after a hard reset or reset. Could also just be the version of the ROM I'm using but it came from the repository on XDA-Developers. Just rebooted it when I was typing this and it still finds GSM radio.
Tried it for a day and I think the radio is fried. Started out finding GSM then when driving around with my Bluetooth heard a bleep which indicates loss of signal - saw it hunting then it finds the signal. During a call for about 3 minutes just drops call and on the screen the dialer won't let you disconnect the call.
Rebooted got the NO GSM message - eventually found it - briefly then NO GSM again.
Tonight opened it up and reseated and cleaned motherboard contacts including radio. After hard reset got GSM again - briefly. Then no GSM
Tried upgrading and downgrading radio via SD card - no go would only hang up Tried complete with OS - same thing. Tried through ActiveSync method SSPL and got same.
So I think the phone is pretty much not really a phone - can still boot into OS. May try some more but I think its definately a motherboard issue. Shouldn't be that hard to flash and the GSM should at least be stable.
When I bought it on eBay and first turned it on saw a TEST ONLY message on boot with a WM5 Rom. The seller was a little vague just said it freezes sometimes. Got it cheaply thankfully so I'll keep hunting around for another unless someone has a suggestion?
The Radio seems to be the touchiest part of the Hermes. When it fails theres nothing that seems to be able to fix it. Look for another cheap Hermes. At the very least you will have spare parts.
how weird is this I have just gone through just the same problem and took a day to sort it out . ok here is what I did in the end . now what you need is any official rom pref wm5 . I can send you a link if needed to the one I used ... now try flash it from the pc it will stop at 12 percent ....... now take battery out and boot in bootloader mode .... now flash any rom that's wm6 etc .... devise will restart .... now take battery out and re boot it may take two or three boots to get it working prop without the no gsm error but trust me it will boot . when its booted up flash the original wm5 shipped rom run through the rom sequence and when its waiting to flash saying zero percent manualy put your phone in bootloader and wait 30 odd min tadaaaaa phone is now perfect ... now flash any rom you like as the radio is fixed . its something to do with the 12 percent bit it hangs on .??!!! sorry its long and complicated but I have my hermes back to life through doing it ................... let me know how you get on bud. if needed 07832999919 uk . so its 0447832999919 oh I have hard spl 1.40 spl 1.1 or something lol can't remember . anyway good luck
Ok, think I initially really messed up my flash and the WM6 which was the official HTC version may have been corrupted but showed full flash. When I tried again I would also get the 12% even with a SD flash. So I tried flashing just a RADIO ROM which did complete. The NO GSM message still would pop up maybe 50% and not necessarily everytime.
When to MTTY.EXE and did a bad block check - no problems
In MTTY did a FORMAT/CLEAR.
Left everything alone and again reflashed just the RADIO - things seemed to be better - less NO GSM.
Tonight - just before you posted I successfully did a complete reflash with the HTC WM6 rom with Radio 1.48. Very surprised it worked this time - no hangups except during the GSM part which only stopped a minute or two.
Complete reflash in about 10-12 minutes with the SD card method.
SO far things are working - tried a reboot a few times and now radio is found every try. Will try for a few hours and try again tomorrow.
What I did have is a white screen/with image once - it was cleared by just pressing briefly the power button. So it may be heat related - don't know.
Keep me posted in this thread whats going on and I'll do the same.
What ROM WM5 did you flash to get yours to work?
Spoke too soon! Put in a sim card - powered up and it worked. Tried making test call and it worked. Tried again and it showed dialer and dialing and never connected. Could not use the dialer to hang up. Also showed drop in network. Tried turning phone radio off in dialer and back on - showed !X. With the phone off hook image at the top bar. Tried again - same thing. Expected to see no GSM when power cycled and it did show NO GSM.
Right now its working even after a few power cycles but honestly I think the successful flashes may be due to the GSM radio being found. If it doesn't find the radio and you attempt to flash thats why it hangs. If you phone works for a few days or day I'd be very surprised. The real test is to try it when moving from tower location to tower location. Thats where I noticed the radio was acting up. With a bluetooth headset it will beep indicating a drop in carrier. When its doing this the radio isn't working properly and can't lock on to a signal
If your phone does work PLEASE post what you did and what files were flashed.
For my phone I think its heat related. Possibly the heat from the circuitry is opening up or stressing out a component causing it to fail. I really think my motherboard is faulty and reading on the HERMES this isn't that uncommon. Being that the phone has so little hours I think it must have been a return or factory reject.
More than likely I'll have to purchase another phone needing a screen or one thats in poor shape to salvage the motherboard and attempt to put it in my case since the housing and screen are pristine with little to no use. I've been told that any 8525 motherboard will work but I doubt it since the Dpad is different and I have a front video camera.
No, ANY Hermes mainboard will work... Hermes are identical internally, even the 8525 is able to use the front camera, it just isn't included in that model.
Cheers...
Thanks, makes my life easier!
ok mate i used htc orig rom by orange uk google the words,,,, orange spv m3100 update ummm ok hang on il grab the link for you ...
http://www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_1007.exe then flash hard spl then update your rom to whatever you like ,,, hope this helps buddy
Might try it tonight but I really think I need a new mainboard. I am able to flash only when it finds the GSM and I think any hangups are due to the GSM radio circuity failing or some strange power flux on the motherboard. I am having strange multiple freezes/slowdowns as well as NO GSM errors. Tried a WM5 and WM6 specific for my HERM200 and no change. When it works it will work and make and receive calls but after a while without a load but under load - multiple calls, running excel or other things the radio will drop or it will attempt a call, not connect and will not let me hang up. No software update will fix this issue - it has to be hardware.
If I have successfully done base HTC ROM flashes - complete with radio phone should theoretically work. I have to face reality with this one which although looks pristine is a lemon and have to buy a working beat up 8525 and try the motherboard as long as the seller assures that the phone can make and receive calls without problems.
Also have other issues with screen fadeout which I know is tied to the dPad controller - but I can live with that for a while and I have a source for a part replacement and can try a quick fix to verify its just the dPad.
You got lucky so far - but if you try to use the phone all day running multiple programs or CPU intensive tasks your radio still may fail. You could also try upgrading the ROM again to something that is MFG and see if it takes.
It is possible to flash the OS without flashing the radio, It will be a cooked rom but they're better in most respects than a stock rom. Faster, leaner with all the bloatware removed.
No software change is going to fix this. Its not a software bug its a flaw in the hardware. Can't flash a radio Rom - thats a chip problem. Its basically a low level format and write to eprom. Thats pretty basic. Also making and receiving calls is also pretty basic. The dialer has been around for a while and is pretty stable.
Hi everyone!
I would just like to receive some user experience since I haven't found anything on the net or forums.
The thing is, my HD2 (HSPL 3, Radio 2.12.50, ROM Energy 6.5), after months of tests and fun, freezed as usual (like a normal WinMo) but this time did not start up after a battery removal ( or a soft reset button).
The first two startups were followed by an 8 vibrates code than nothing. I've removed a battery and tried to boot again but this time nothing happened.
The only action I can hear is the starting of the vibration motor while trying a Hard reset. No charging, no leds are working nothing.
Seems that BIOS encounters an error and stops, but where can I find to what error the 8 vibs code is related?
Any help, resolved identical story or information would be highly appreciated.
bootloader is work ?
Hi, thanks for your reply,
Can't exactly tell you if the boot is summarized before or after a bootloader starts.
From my point of view, it seems that he freezes on some BIOS check.
I tried to boot in both normal mode and hard reset but he freezes even before the screen is loaded. He only starts to vibrate (makes a little noise) than nothing.
I hope it's a hardware problem not some junky app that damaged the BIOS (if any)/xSPL so that I can even try to use my guarantee hoping that they will not know what kind of OS I have on it.
Regards
I've had the same issue but I think mine vibrated 7 times. After pulling the battery and letting it cool a few min it fired up fine.
TKhawk01 said:
I've had the same issue but I think mine vibrated 7 times. After pulling the battery and letting it cool a few min it fired up fine.
Click to expand...
Click to collapse
Yeah, seems it is some kind of an overheating issue. I've tried to cooled it down but seems that the heat already damaged something.
I've put it on reparation under warranty. Just crossing fingers they will not find out about the cooked ROM or the HSPL that was on it..
Anyway, thanks for helps guys. Will keep you updated about the resolution if any.
Regards
I too have this issue.
1 vibration when phone powers on, followed by 7 vibrations in a row (8 in total)
It seems to happen whenever I use Android for extended periods of time (15min+ Android freezes and then when resetting it occurs) and is becoming more frequent.
Worked out that it was heat related, but not sure if its worth restoring windows and returning for warranty repair. Are there any easy ways to replicate in Windows? How did you go cthulhu0dyssey with the warranty repair did it solve your issues?
Also can anyone point me into the right direction on the easiest way to restore windows on the device, if that is what I end up having to do?
SPL: 2.08.HSPL (HSPL3)
ROM: Energy Leo COM2
Radio: 2.15.50.14
Android: MCCM SE V3.4 (SD) (http://forum.xda-developers.com/showthread.php?t=841644)
mullaly said:
I too have this issue.
1 vibration when phone powers on, followed by 7 vibrations in a row (8 in total)
It seems to happen whenever I use Android for extended periods of time (15min+ Android freezes and then when resetting it occurs) and is becoming more frequent.
Worked out that it was heat related, but not sure if its worth restoring windows and returning for warranty repair. Are there any easy ways to replicate in Windows? How did you go cthulhu0dyssey with the warranty repair did it solve your issues?
Also can anyone point me into the right direction on the easiest way to restore windows on the device, if that is what I end up having to do?
Click to expand...
Click to collapse
Would be really convenient to try helping you with this problem if you specify your ROM, Radio, SPL, Android version/type (SD/NAND).
[The Punisher] said:
Would be really convenient to try helping you with this problem if you specify your ROM, Radio, SPL, Android version/type (SD/NAND).
Click to expand...
Click to collapse
Sorry, knew I forgot something, edited original post. Another thing to add is that when it happens if I pull the battery out and wait a couple of mins it powers on fine and boots into Windows/Android with no problems.
Just thought I'd send a follow up post.
I removed Android and loaded back windows mobile. After a while it just keeps rebooting until the phone will no longer turn on until it cools down.
Heat seems to be the cause. Guess its back to the shop!
Just thought I'd add an additional comment to say I got the phone back from repair, reinstalled android and now the problem has gone away.
Update here!
Hi guys,
Same here, Leo came back form the repair (completely new hardware + SPL 3.03) saying that there was an known issue with one conductor. Whatever...
Was glad to find out Cotulla rolled-out HSPL 4 so I can finally enjoy Android from internal memory, though I hope overheating issues were solved 'cos I don't think they'll give me a warranty repair for the 4th time ...
Hello there. I´m worried because my Evo 3D CDMA won´t boot or charge at all. The red light is not turning on. All happened apparently with no reason, I left the phone there a few minutes, then it was dead. Maybe if I tell what I did before can help...
I had installed a few minutes ago the Virus ROM 3.0, I flash roms almost every 3 days, so I´m used to it. So, it worked fine after installation. I began to play a few games, when the battery died. I conected it to the charger, waited a few minutes and turned it on again (still plugged to the charger), it started normally. Then I had to answer a phone call, when I got back, the phone was dead!! "Maybe the charger got disconected" I thought. But the charger was fine, I tried many different chargers and nothing.
The red light is not turning on.
I´ve tried many different buttons combinations (camera+power), etc. I can´t get into fastboot (power+volume down). I´m S-ON HBOOt 1.5. So there is no CWM. I have to use windows CMD every time I need to flash Something.
Can this be a battery issue (considering that when the phone died it had about 3% of battery), or is it a fried motherboard, perhaps? It had happened before, but I removed the batttery for a few minutes and It worked.
But I´m scared because the phone is brand new, and it has less of two months of average using. And don´t tell me to go to Sprint service since I´m in El Salvador and I got the phone at eBay.
Any help would be appreciated. Thanks.
My fiest EVO 3d did this, the guy told me that it was a lemon. I got a instant replacement, not sure if its in the discovered mode by a dev,
Pull the battery, unplug charger, then battery back in and try turn on.
Sent from my PG86100 using XDA App
mariosaigon said:
Hello there. I´m worried because my Evo 3D CDMA won´t boot or charge at all. The red light is not turning on. All happened apparently with no reason, I left the phone there a few minutes, then it was dead. Maybe if I tell what I did before can help...
I had installed a few minutes ago the Virus ROM 3.0, I flash roms almost every 3 days, so I´m used to it. So, it worked fine after installation. I began to play a few games, when the battery died. I conected it to the charger, waited a few minutes and turned it on again (still plugged to the charger), it started normally. Then I had to answer a phone call, when I got back, the phone was dead!! "Maybe the charger got disconected" I thought. But the charger was fine, I tried many different chargers and nothing.
The red light is not turning on.
I´ve tried many different buttons combinations (camera+power), etc. I can´t get into fastboot (power+volume down). I´m S-ON HBOOt 1.5. So there is no CWM. I have to use windows CMD every time I need to flash Something.
Can this be a battery issue (considering that when the phone died it had about 3% of battery), or is it a fried motherboard, perhaps? It had happened before, but I removed the batttery for a few minutes and It worked.
But I´m scared because the phone is brand new, and it has less of two months of average using. And don´t tell me to go to Sprint service since I´m in El Salvador and I got the phone at eBay.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
I saw some tread about rom manager app causing sudden death.did you have it?what kernel were you on?
Sent from my HTC EVO 3D X515m using xda premium
josephnero said:
I saw some tread about rom manager app causing sudden death.did you have it?what kernel were you on?
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
No, I didn´t have that app, and I had Chad Goodman´s Anthrax Kernel V2...
mariosaigon said:
No, I didn´t have that app, and I had Chad Goodman´s Anthrax Kernel V2...
Click to expand...
Click to collapse
Might be the battery man... I would swap to another battery.
reaper24 said:
Might be the battery man... I would swap to another battery.
Click to expand...
Click to collapse
I hope it is only the battery, because it´s not expensive... But do you think I should try charging the battery manually? You know, some people say it´s a good way to restore a battery,,,,
maybe the battery or bricked phone
reaper24 said:
Might be the battery man... I would swap to another battery.
Click to expand...
Click to collapse
How did you activate it? Did you download a GSM version of the rom or a CDMA one.....
reaper24 said:
How did you activate it? Did you download a GSM version of the rom or a CDMA one.....
Click to expand...
Click to collapse
Actually we have CDMA in El Salvador too... The rom installed fine, and was running fine, the phone died while.. let me remember... Ah, I was installing a Chainfire 3D plugin, but I had never problems with Chainfire in any rom before, so the big deal is,
1) Is it a faulty battery? I remember once, the battery died the red light started blinking. Maybe the battery is bad.
2) Is it hard bricked? or soft bricked?
3) If it is bricked, is there a way to restore it?
mariosaigon said:
Actually we have CDMA in El Salvador too... The rom installed fine, and was running fine, the phone died while.. let me remember... Ah, I was installing a Chainfire 3D plugin, but I had never problems with Chainfire in any rom before, so the big deal is,
1) Is it a faulty battery? I remember once, the battery died the red light started blinking. Maybe the battery is bad.
2) Is it hard bricked? or soft bricked?
3) If it is bricked, is there a way to restore it?
Click to expand...
Click to collapse
I doubt it was bricked due to the phone wouldn't boot at all when you got it.. Did you update the radios or software when you got it? I know the latest software for CDMA is 2.17 virus R75 to R80 3.0 eternity is based and built off it...
My guess is the battery is shot I would try that you can find them cheap..... So the red light doesn't come on at all when you plug it in with the battery in the phone..?
You would really have to spank a phone to brick it... If the hardware isn't broken you should be able to restore a bricked phone... That takes skill and alot of reading....
What other chargers did you try? Could be the usb cord is bad or the charger... Battery could be no good. Last thing it could be is a bad charger port... Maybe..
reaper24 said:
I doubt it was bricked due to the phone wouldn't boot at all when you got it.. Did you update the radios or software when you got it? I know the latest software for CDMA is 2.17 virus R75 to R80 3.0 eternity is based and built off it...
My guess is the battery is shot I would try that you can find them cheap..... So the red light doesn't come on at all when you plug it in with the battery in the phone..?
You would really have to spank a phone to brick it... If the hardware isn't broken you should be able to restore a bricked phone... That takes skill and alot of reading....
Click to expand...
Click to collapse
I got the phone brand new. I have
1) Unlocked bootloaders via HTC metod
2) Installed tons of roms (I`m a flashaholic)
3) Never installed an incorrect ROM or kernel.
And yes, no light at all when I plug the phone to the charger. it`s totally dead.
UPDATE
I have discovered something about a RUU. check it out:
"This is a link to the Evo stock RUU and a description of what it does. It isn’t anything that wasn’t available already online, I just like providing a central location to get everything.
What is this?
RUU is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
What can I do with it?
You can use this to “unroot” your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can’t fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it’s not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn’t.
How do I use it?
Download the file below and run the exe.
What else do I need to know?
This will set your phone back to 100% bone stock.
You don’t need to run this unless you are trying to return your phone to stock. You won’t get anything special from running it."
IF I RUN THIS PROGRAM, IS IT POSSIBLE I CAN GET MY PHONE BACK TO LIFE?
mariosaigon said:
I got the phone brand new. I have
1) Unlocked bootloaders via HTC metod
2) Installed tons of roms (I`m a flashaholic)
3) Never installed an incorrect ROM or kernel.
And yes, no light at all when I plug the phone to the charger. it`s totally dead.
UPDATE
I have discovered something about a RUU. check it out:
"This is a link to the Evo stock RUU and a description of what it does. It isn’t anything that wasn’t available already online, I just like providing a central location to get everything.
What is this?
RUU is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
What can I do with it?
You can use this to “unroot” your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can’t fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it’s not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn’t.
How do I use it?
Download the file below and run the exe.
What else do I need to know?
This will set your phone back to 100% bone stock.
You don’t need to run this unless you are trying to return your phone to stock. You won’t get anything special from running it."
IF I RUN THIS PROGRAM, IS IT POSSIBLE I CAN GET MY PHONE BACK TO LIFE?
Click to expand...
Click to collapse
Your phone would have to be on like in Hboot or in a rom....And need to fastboot flash stock recovery... or make it a zip file to do....
Also you would have to relock your phone.. Once it was relocked you could run this...
I am only going off what I have seen haven't had to relock my phone to throw stock on it... I have seen some guides in the dev section to do it.. But the phone has to be on to get the sucker to work,,,,
My guess is the battery is no good... If it's brand new I don't know why the charger port would be bad in it... I would try another battery first man...
reaper24 said:
Your phone would have to be on like in Hboot or in a rom....And need to fastboot flash stock recovery... or make it a zip file to do....
Also you would have to relock your phone.. Once it was relocked you could run this...
I am only going off what I have seen haven't had to relock my phone to throw stock on it... I have seen some guides in the dev section to do it.. But the phone has to be on to get the sucker to work,,,,
My guess is the battery is no good... If it's brand new I don't know why the charger port would be bad in it... I would try another battery first man...
Click to expand...
Click to collapse
OK, before I commit suicide I will try to get a new battery (I`ll have to buy it at eBay, since no once else has this phone here) That should be the only solution. Thanks for you time. I´ll let you know what happened as soon the battery comes (a month, maybe)
mariosaigon said:
OK, before I commit suicide I will try to get a new battery (I`ll have to buy it at eBay, since no once else has this phone here) That should be the only solution. Thanks for you time. I´ll let you know what happened as soon the battery comes (a month, maybe)
Click to expand...
Click to collapse
Reallly that sucks I would look around do you guys have a sprint store....?
What do the battery contacts look like on the battery ? Still a goldish color or do they have some black burns lines to them? Try to take a eraser on a pencil and wipe the contacts down and plug the battery back in talking about the battery don't use it on the prongs where the battery plugs in at .....
Worth a shot man lol I have done this in the past......
reaper24 said:
Reallly that sucks I would look around do you guys have a sprint store....?
What do the battery contacts look like on the battery ? Still a goldish color or do they have some black burns lines to them? Try to take a eraser on a pencil and wipe the contacts down and plug the battery back in talking about the battery don't use it on the prongs where the battery plugs in at .....
Worth a shot man lol I have done this in the past......
Click to expand...
Click to collapse
haha, it`s just that it`s so stressing having a $340 brick. I tried the eraser wiping trick but It didn`t work. Maybe I`ll have a friend manually charging the battery.
I´m going to sleep for now.
Thanks again
mariosaigon said:
haha, it`s just that it`s so stressing having a $340 brick. I tried the eraser wiping trick but It didn`t work. Maybe I`ll have a friend manually charging the battery.
I´m going to sleep for now.
Thanks again
Click to expand...
Click to collapse
I know the feeling lol That sucks,,,, Hope it works out for ya man..
Happened to me before. Try leaving it on charge for 8 hrs or so and remove the battery and replace every so often. BTW I got it on virus eternity as well. Also, I would get an extended battery to kill two birds with one stone if the previous method doesn't work.
Sent from my Quad core thingamabober with dat XDA Premium
Hello guys, I'm experimenting the same issue! It was working like a charm, then I left without simcard in airplane mode, but with wifi on.
When out from wifi coverage, it turned off (maybe because of the battery drain) and can't bring it back to life!
This is just incredible, I can't believe there is no way to wake up it.
I'm trying to charge with its charger, with PC connection and nothing happens: red light for a little while and everything off again after a couple of seconds ... I'm getting nervous :-(
I don't think the phone is bricked or a bad battery. When you plug the charger in, turn the light off in the room and see if the phone charging led is very dim. Sometimes when my battery is very low and I put it in the charger it does this. The other scenario is that the phone may be in download mode which I doubt. If it is then you can follow the last steps from the hboot 1.50 downgrade guide.
Sent from my PG86100 using xda premium
I just skimmed the posts so sorry if I missed it, but...
Have you tried "adb reboot recovery" just to see what happens?