right ok so i woke up to find that the battery had died in the night but the the phone wont switch back on. only using stock rom 1.66. it just gets stuck on the bootscreen.
i soft reset the thing and it started up and went to the sim card set up. after that just on a background ive never seen before and the taskbar was like a metallic grey sort of theme (was just stock before). it said tap here to launch sense but it kept failing. the bottom bar looked really strange as well (sort of silvery too, looked quite cool actually). i tried to restart it again but now stuck back at the boot screen and soft resetting isnt helping this time.
I dont get it.???
p.s havent been installing/ flashing anything lately and it was working fine before.
First thing, check for bent battery pins.
Give it a good charge turned off, take out your sd card try booting it up.
Did you try a hard reset? If not give that a go.
Hope one of those helps in some way....
well all the battery pins are sticking up like they should.
it was charged turned off as it wouldnt boot up and i tried taking out the sd and sim card.
my next plan would be to try a hard reset but i wanted to avoid that if possible.
just doesnt make any sense why it happened and why it did boot up once but into some other kinda alternate theme - and then wouldnt anymore.
Could be that something was being written to your SD card when the battery failed causing some kind of corruption. The other theme you describe sounds like default winmo because of sense not loading properly.
I think its a job for hard reset.
Sent from my HTC HD2 using XDA Premium App
cant flash the rom it just stays on 0%
OK few questions.........
Can you get to bootloader? (3 colour screen. turn on holding vol down)
If so, what does it say?......
What are you trying to flash?
Are there any error messages?
yeah can get to the bootloader fine. it just looks normal. i had hslp and managed to flash back to spl 2.08 fine.
just tried to flash the stock 1.66 rom. just stayed on 0% then said error connection on the pc. tried again same thing.
no error messages or anything on the phone.
hmmm....
is "serial" changing to "usb" on bootloader when you connect to pc??
The only things I can think to suggest are the old favourites like;
Try another USB port.
Uninstall / Reinstall Activesync or WMDC
Try another PC.
strange. i flashed hspl again which it let me do and now the rom has flashed. so all appears to be ok for now.
thanks for your help.
still dont get what happened with it tho
No problem.......
At least your back up and running again....
Something strange indeed.
chrisman99 said:
after that just on a background ive never seen before and the taskbar was like a metallic grey sort of theme (was just stock before). it said tap here to launch sense but it kept failing. the bottom bar looked really strange as well (sort of silvery too, looked quite cool actually).
Click to expand...
Click to collapse
naked windows mobile
chrisman99 said:
cant flash the rom it just stays on 0%
Click to expand...
Click to collapse
chrisman99 said:
yeah can get to the bootloader fine. it just looks normal. i had hslp and managed to flash back to spl 2.08 fine.
just tried to flash the stock 1.66 rom. just stayed on 0% then said error connection on the pc. tried again same thing.
Click to expand...
Click to collapse
accidentally chose 2.08.0000 instead of 2.08.hspl? and/or followed by the wrong stock 1.66 rom
chrisman99 said:
still dont get what happened with it tho
Click to expand...
Click to collapse
sense got corrupted and wouldnt start, (it happens, no clue why) so you were seeing naked winmo. A hard reset would (usually) have fixed it without all the flashing.
Just one of those glitches that happen now n again.
doesnt look too bad naked
Related
After i upgraded to this radio i have had interesting problems with my phone. ithought it was bricked and it very well could be. But sometimes it decides it wants to work but after a minute or two it cuts off. when a softreset or hard reset are perfromed i get nothing but a white screen. I can tell it goes thru the whole process bekuzz usually after putting it to sleep a few times i get my regular screen but the radio doesnt seem to be connected. any help would be appreciated. also the buttons on the face of the phone dont seem to work.Thanx
What is "Regular Screen"?
Regular screen means the screen u would normally get after your boot and splash screen. Or better said my today screen. Sometimes i cant get my today screen up. i had BL 1.04 before the upgrade if that matters any
Today screen is very good! your device isn't fully bricked. It may be a bad radio flash or it may be a hardware issue that merely coincided with your radio upgrade. Next time you get a today screen, try to flash one of the other sspl based radio only updates (find in wiki under radio only upgrades). Remember to practice safe flashing techniques!
usb on rear usb port. No usb hubs!
all winapps closed
running winXP Pro
activesync connected
screensaver/sleep mode off (flashing takes 20+ minutes)
i have flashed the 1.27 radio again without having my today screen and that did nothing. It went thru the whole process of flashing and everything but same results, just a white screen when booting up and afterwards. im downloading the 1.34 radio now.
You need to flash the sspl version which requires first being on the Today Screen (not white screen). Tri-color boot screen will show v1.09-Des if you do this.
i guess i will have to wait to see if i get another today screen and hope that it doesnt reset itself
does it matter that i can put my phone to sleep and wake it up over and over, i just keep getting the white screen. bekuzz now i cant seem to get my today screen back anymore
ok i have done what u said and flashed the 1.34 radio and still have the same problem. after the flash i had my today screen for a minute then it reset itself and now is gone and back to the white screen. also when i was on the today screen i didnt have control of the buttons only touch screen.
i think i may have a different problem. it doesnt seem to be resetting itself everytime it goes blank but that the screen is dying on me. hmmmmmm....... this is quite strange. i can also recieve calls. i cant answer them but the handset rings.
This may be silly but if I were in your place I'd just reflash everything with an official rom that replaces everything (i.e. SA 1.35) and see if that fixes the problem (though i might wait until somebody who knows more then me verifies this is a good thing to try). I'm wondering if the bad flash somehow effected something in your OS or something.
When I mess something up like this, I like to get back to a place which has been known to work - then I have a better idea of where I am (ie brick or bad flash)
Hope this helps
yea i actually went back to the original cingular ROM that came with the phone. so we shall see what happens from here. i also will have Cingular send me a new phone, i was tired of the scratches anyway. So far they havent noticed that my phones are supercid yet. Keeping my fingers crossed
Hardware problem IMHO...
Sleuth u are right. No matter what i do to the phone it yields the same result. My screen still turns off and the buttons dont work. iwonder what couldve caused this. i didnt drop it. well not recently anyway. BTW.... is there anyway to get the original 1.16 radio back on there. i tried doing it but it just hangs at 0%.
Thanks Sleuth for all your help, you are definetly one of the reasons this forum is helpful. That and that good ole WIKI.
Im upping it right now to my folder on the ppcgeeks ftp. r4 of my rom, and sorry that it took so long guys. Its still a work in progress, and i am nowhere near completion of it.
FYI: I just tried loading your ROM but my 6800 keeps freezing at the Windows Mobile Version 6.1, the screen that says "Tap the screen to setup your ...."
I loaded a previous ROM and it works fine.
pete9976 said:
FYI: I just tried loading your ROM but my 6800 keeps freezing at the Windows Mobile Version 6.1, the screen that says "Tap the screen to setup your ...."
I loaded a previous ROM and it works fine.
Click to expand...
Click to collapse
Ditto.
Tried soft and hard resets as well as running unlock util.
mugsy77 said:
Ditto.
Tried soft and hard resets as well as running unlock util.
Click to expand...
Click to collapse
weird. like i said on ppcgeeks, i didnt have a problem, try flashing it again, and then hard reset.
I just pulled the battery because i was having the same problem and it now works no problem.
Pulling the battery worked, thanks!
No problem...happy that for once I helped out instead of always being helped.
Per Angel, he's going to look at a memory leak issue that was just discovered. You may choose to wait until he gets that squared away until updating. Angel, is it just a matter of soft resetting daily to prevent a memory leak?
mugsy77 said:
Per Angel, he's going to look at a memory leak issue that was just discovered. You may choose to wait until he gets that squared away until updating. Angel, is it just a matter of soft resetting daily to prevent a memory leak?
Click to expand...
Click to collapse
yeah, thats what i have had to do, wake up and soft reset. from what i have heard it is a problem with 6.1 right now, and i guess thats what we get with beta software. I recommend that you use dcd's right now until i get this all figured out. i will prolly post a cab pack for all my software that i use on the roms.
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
Hello Everyone,
I bought a verizon Titan with a kitchen ROM with WM 6.1. Yesterday I decided to try to cook one myself with WM 6.5. Everything was fine except ehe "start" button stopped working after some minutes. I cooked another opne with less programs. Then I thought it would be a good idea to use the Spbbackup I had to try to get some programs back. It told me that there has been a ROM update I clicked ok and it did its thing.
I had problems with that ROM so tried one that was in one called WM6.5Beta with WM 6.5 after that it boots, then I get a WM6.5 green screen and then the screen goes white. I though it was the Radio so I updated to the 3.42.5. No change, I tried the exitbootloader program no change. I tried to get another kitchen ROM into the Titan but the pc does not detect the Tytan. Ive tried everything I even used the las Sprint Stock Rom via Sdcard and it got to the Htc screen "no Radio". I installed the 3.42.5 Radio and I got to the WM6.5 green screen again and then it turns white.
The weird thing is that if I press the Powerbuton i get the "Power will be turned off and you may lose.." you know the usual. but I can not selkect either yes or no, the screen freezes and turns black. Another wird thing is that all the screens I see when I boot are the one I installed in my last kitchen ROM. I have tried millions hard resets, softresets, removing battery... I am really lost and I need my phone back!! Did I brick my phone? I can put new Roms and Radio through sd card method but this new ROMs dont seem to take effect since I always get the same screens...
Any help will be appreciated.
oh also If I slide the keyboard there is this "chimes" sound. So I guess a ROM is actually active but the screen is white and nothing else works...
The Flex Cable is going bad. Its the wiring so the screen can slide in and out. It can take abuse and go bad over time. Easy replace.
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
I've had that problem after a bad flash, but it still let me get into hboot and recovery without problems, so I doubt it was that. Don't have a clue what it could be though... at least you got him taken care of with a refurb. Maybe the inability to boot to recovery could be not having amon ra or cwm installed (never tried without one) and if he wiped /data or /system I don't know if factory reset would know what to reset to (again, never tried).
Edit: Also, with me, the phone never died. White HTC screen would stay up until I pulled the battery and it would still recognize the charger.
exactly! it's a problem after a bad flash. i wonder if this dude was lying and tried to flash something, his battery died, and it bricked it
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
edit - there is one difference: my battery never died. I took my phone out of my pocket at 5:40 to look at it, and it was fine. I looked at it again at around 5:50 and I had the white htc screen. At this point I pulled the battery and started googling.
second edit - could the forced update have something to do with it??
nope, he brought his in before the update.
have you gotten anything to work? when we called customer service, they just replaced his phone for him..i hope it works out for you, man. maybe try to get into fastboot and wipe the phone, or something? i know i was able to get into the bootloader..maybe you can push a factory reset from the comp
avertist said:
I am currently experiencing the exact same problem; I was able to replicate everything you describe, including what happened when you tried to go into recovery or factory reset mode. I have NOT tried to root or do anything else untoward with the phone ... if anyone has any idea what I can do other than get a new phone and lose all my data, I would really appreciate it!
Click to expand...
Click to collapse
If you want to at least get the data off of it you can try using testdisk.
http://www.cgsecurity.org/wiki/TestDisk
I used it for my external sd card that wouldn't read in the phone or computer anymore and had all my nands and other backups on it. It seems like it won't work on Android but it will, but since I formatted it in the phone it didn't seem to have a volume name.
After you select the drive and it comes up with the partition table list, select [None].
Then select [Analyse]
I think that's when it will list all your directories.
You might be able to hook up your phone and get stuff off the internal card if you leave it at the white htc screen, not sure. But I have used testdisk successfully on a drive and the sd card that all systems said was unreadable and needed to be formatted. Anyway, it's worth a shot to see if you can get your stuff off it even if you have to return it.
jayochs said:
so this guy came into my store who had a rezound, never once had a problem with it ever...then the battery died fully overnight because he forgot to charge it..
so when he woke up, it was dead obviously. he then plugged it in, and the orange light came on for 5 seconds...then shuts off. and nothing happens. this even happened when he brought it in for me to try. so i'm like, wtf, probably a bad battery maybe?
so i put in a good one we've got...same thing. so i ask if he's rooted or anything, he says no...but i did a search, and found some posts that when people had bad flashes of roms, it would stick at the white screen, and they had to restore a backup in CWM for it to work.
so i tried to see if maybe he was rooted...went into bootloader, hit recovery, and the phone just died. just shut off. so i was like, thats weird...so then i tried to do a factory reset....same thing, i hit factory reset, the white HTC screen came rgiht up, then the phone just died...and this was with a fully charged battery, too.
eventually we had to just call up and get him sent a refurb, but still, has anyone seen this problem? nothing i could do could get it to boot, and that's such a ****ty feeling especially if this guy said that he NEVER had a problem with any HTC phone, especially this rezound, until that battery died and it would'nt turn on again.
Click to expand...
Click to collapse
Yeah I had a lot of white screen time when I had the Evo! A co-worker of mine had this happen on his Evo. It was from overheating. Now I realize this is the Rezound we're talking about but brilliant phones do think alike.
Sent from my ADR6425LVW using Tapatalk
happened to me when the kernel didn't flash but the rom did. Had to boot into fastboot and flash a kernel through a command prompt on my PC.
Just finished dealing with this after a bad flash. I couldn't boot, couldn't flash a new rom because of the Mainver error and couldn't get into recovery. Finally fixed it by deleting the PH98IMG.zip file. That let me get into recovery. Then had to flash back from ICS to Gingerbread. The I could follow the instructions to fix the Maiver error.
I had heard reports that people had data loss issues from the battery dying all the way in the rezound? Something tells me running the RUU on the phone would have fixed it.
Sent from my ADR6425LVW using XDA App