I've had a read through the forum, but cant seem to see anything that matches my problem. Apologies in advance if there was something which i missed. So here goes:
A friend of mine upgraded my Mda vrio II yesterday with the TNT Wm6 rom, its the one he uses, so I went with that. The upgrade went fine, and I actually quite liked the TNt rom as it was quite nippy. However, the next day I noticed a bug in it. It would reboot when I slided out the keyboard. I thought a hard reset would solve the problem, but it didn't. After the hard reset I slid out the keyboard to check if the problem was still there, and what do you know it went blank like usal...BUT instead of restarting, it just stayed blank and from then on it fails to start!! There seems to be no power at all. I tried to hard reset it again without any success. I connected the charger to see if the amber/green light comes on, but nothing happens.
Is there anything I can do to revive it? ANy help would be much appreciated.
ANy one have nay suggestions?
Dead battery?
Nope..its not a dead battery. I tried my mates working battery..and its still dead!!
Any more suggestions?
Reflash with a different ROM or a ROM you know works. If you still have issues then its probably a hardware problem of some sort with the keyboard.
WB
I would reflash if i could...but the phone doesn't even start up. I connected it to to my computer usb to see if i can connect via active sysnc, but nothing. Seems like its totally dead.
Sorry, missed the point about you not being able to switch it on.
Have you tried taking the battery out and leaving the phone without a battery overnight to see what happens? Might just work.
There was a debate on here a while back about being able to power a phone from the charger without the battery in it. Clutching at straws really but search around to see if you can find that thread. I guess if you can get power to the phone then you can look at other options like a reflash, if you suspect the rom.
Don't know what else to advise, I'm afraid. Hopefully someone will come along soon with a gem of an answer.
Good luck.
WB
Wacky - I've left the battery out of the phone for couple of hours but not overnight..something to try I guess. As for the charger being able to power the phone on...ill try that as well.
I just can't understand how the TNT rom can mess up a phone to the point where it doesn't start up when it installed successfully, or supposedly installed successfully in this case. I wonder if anyone else who installed TNT had a similar problem..hmm. I cant even seem to find the tnt thread to check..lol.
Bummer! I have had the TNT V2.0 for about 8 weeks with no major lockups or hard resets. I did not notice any problem posts on 'its rights' TNT thread like yours 'pulling out the keyboard'. This is one of the best Roms that I have flashed (I have the Hermes 8525 not the MDA).
Related
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
I recently tried to flash my stock verizon xv6800 with the instructions that were given on the ppc.stoleyour.net site. I followed those instructions exactly to a T. Worked fine the first hour before I went to bed. I put it on charge overnight as I do every night and when I woke up, I could never get it out of safe mode. When I got to work that morning, I did a hard reset. Everything was working absolutely great including the gps which is what I really need. (I'm a flight paramedic). Then all of a sudden after about 4 hours into the shift, the phone went completely dead. Should've had plenty of charge to make it for about 24 hrs. When I tried to plug in the charger, nothing - not even a charging led. I tried taking out the battery for a few minutes then for a few hours... and still nothing. No charge and wouldn't turn on. I have searched every titan forum possible and never saw a post that resembled the problem that happenned to my phone. I got a replacement phone and tried the good battery and new charger on the old phone and old battery and still nothing. I used this bootloader - OliPro MFG 2.40Hard SPL. This rom - DCD Titan ROM 3.2.5 and this radio - Titan Radio version 3.42.50 I allowed the customizations to run. I live in South Carolina. Any ideas what might have happenned? Input would be greatly appreciated. I do realize that I install all of the custom things at my own risk. They work for most everyone on this forum. I would like a verizon titan gps phone as well.
My opinion, that website you used was my FIRST introduction, if you will, to the whole flashing thing. It worked GREAT for me. If you followed the steps given there along with using all the files from the links, then you could have done no harm. I would venture to say that what happened to your phone was completely unrelated to flashing it. If it doesn't even turn on, then Verizon will not have a way of seeing that you did anything to your phone, so just take it back and get a replacement. Of course, you probably don't wanna mention the flashing part when they asked you what happened
Also, don't be afraid to reflash with your replacement phone. I highly doubt that your flashing caused the problems, therefore flashing a new phone should go much better for you.
I just wanted to find out if anyone else out there might have had the same problem. I didn't figure that it was due to the flashing just a mean cooincidence. I might give it another try.
Hi all,
As the title says, I can't get Sense to load. Any help/advice, preferably me not having to HR, would be much appreciated.
Here's a bit of background info: Yesterday afternoon I noticed my phone was running very low on battery power, I think it was down to 3%, fortunately I was at home so it wasn't a problem.
I plugged the phone into the wall charger and left it. About 4 hours later I went to unplug the phone expecting to find a fully charged up battery. However, the phone was turned off, I very rarely turn my phone off. Puzzlement followed for a second or two until I realised I hadn't switched the plug switch on. What a dummy!!!
Therefore, the phone had powered down through having no battery power. Sense has not loaded since. Would this cause Sense not to load??
I've had a prior problem with Sense not loading and I did a Hard Reset, I couldn't see what else I could do.
But I'm hoping someone quite a lot more knowledgeable than myself maybe knows a way round this without resorting to a HR.
Thanks for any help.
Anyone please?
If you still have the origional ROM running i would say bring it back to the shop from which you got it from and let them repair it
Otherwise i would say try to install HSPL and push another ROM to your phone so that will repair the fault. Installing ROMS wont take to long
wilwilwel said:
If you still have the origional ROM running i would say bring it back to the shop from which you got it from and let them repair it
Otherwise i would say try to install HSPL and push another ROM to your phone so that will repair the fault. Installing ROMS wont take to long
Click to expand...
Click to collapse
Thx for the reply.
Yes I'm still running original ROM although I updated the original 1.43 ROM to 1.72 via the HTC website. I don't yet feel brave enough to flash a custom ROM. Although this might be the right time to do it now. However, if there is anyone who may know a workaround for this without having to flash a custom ROM or hard reset, I would be very grateful.
Thx.
This is not a useful post but i had the same on mine, and had the same update line as you. Out of interest were you running GTX when the freeze happened?
Both times i had to done to me was on the GTX theme, atm not running it due to the effort of reinstalling everything after a HR, i feel your pain!
chris10230 said:
This is not a useful post but i had the same on mine, and had the same update line as you. Out of interest were you running GTX when the freeze happened?
Both times i had to done to me was on the GTX theme, atm not running it due to the effort of reinstalling everything after a HR, i feel your pain!
Click to expand...
Click to collapse
No GTX theme on my phone and the phone didn't actually freeze. As mentioned in my original post, the problem has come about. I think, due to the phone powering off through lack of battery power. This was due to me not switching the plug switch on after having put the phone on charge.
Thx for the suggestion anyway.
try this thread
forum.xda-developers.com/showthread.php?t=594275&highlight=unable+launch+htc+sense
conantroutman said:
try this thread
forum.xda-developers.com/showthread.php?t=594275&highlight=unable+launch+htc+sense
Click to expand...
Click to collapse
Thx for the link, I'll take a look and report back.
Cheers.
That happened to me couple days ago. Tried everything but nothing helped. Had to hard reset in the end.
Right, a couple of problems have recently appeared on my hero one of them being major and the other minor but annoying!
Firstly I'll explain what I had done before it happened, I'd just flashed FroydVillain 1.2.1 and the nindroid-v1.2-352-691-test-signed kernel.
After this at somepoint that day (don't exactly know when) the trackball notification light turned on, and stayed on ever since. This happens the second the phone is booted after being off, even in recovery mode!
A few days after i decided i was fed up with this problem and decided to sort it, to the best of my limited knowledge, and flashed a variety of ROMs and kernals,. Still no luck! THE DAMN THINGS STILL ON!
Then to top it all off the phone is no longer recognised by any computer when attached via USB. I've done some hunting and tired clearing drivers etc like suggested in this forum still nothing,
Any ideas?
Are these hardware faults?
Hello!
Well... I have this phone since yesterday... I plugged to the computer with Kies, and well, a update was available... now the phone have Froyo and the aesthetics changed completely, it looks awesome.
But, the phone have this ANNOYING problem that, after using it... like 5~10 minutes of no activity, when I try to use the phone again it doesnt work... doesn't respond to any button, I have to take off the battery in order to restart it and that over and over again...
I've realized also that this happens when I'm using wifi, if I left the phone with wifi on this happens, without wifi seems to work fine.
Somebody have any clue what could be? there's little information about this issue in the internet...
I think I'm going to return it but I want to try everything I can do (without voiding the warranty) since the phone was perfect for what I wanted.
Thanks in advance!
Hey. I got the same problem here. It only happened a few times when I just had froyo that came stock on my galaxy 5 but I recently installed cyanogenmod 7 and now its happening everytime I put my phone down.
So I'm guessing it may be directly related to what rom is installed? I've heard about it happening a bit to people who have 2.1 installed to.
I dont know too much but it seems the only fix is to take out battery and turn on.
Sorry I can't help more. I hope somebody knows a bit more than me on this.
Think this is called something like the 'wifi sleep of death', something to do with the rom. i'd try change the rom and see if it still occurs
Thanks for the hints tho!, but I returned the phone... it seems that is a bug related to the update of the phone, since I know that with the out of the box 2.1 version it doesn't have that issue...
You know, the mobile carriers also do weird stuff to the roms... -__-