Related
Hey Guys..
I have a Desire here in my Hands with a strange type of Brick.. (at least one I've never seen before) ..
It just does not react to anything at all. The battery is charged and I tested with another cell to be sure that is not the trivial cause.
No Bootloader, No HTC Logo, No reactions at all..
Did happen while flashing a Froyo 2.2 Rom + Radio + App2SD (from the xda forums) via ClockworkMod Recovery but I wasn't there to witness the actual Flash.
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Then battery removed -> Brick.
Anyone got any Idea?
messywrk said:
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Click to expand...
Click to collapse
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Regards,
Dave
If you can access fastboot as opposed to bootloader you might be talking failing that back to HTC it goes
if your phone can not turn off whilst holding either volume down or the back button then yeah it's a brick, send it off to htc, just say it overheated and wont turn on again
foxmeister said:
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Click to expand...
Click to collapse
The battery was removed after flashing and rebooting.
Installed in the following order:
32.41.00.32U_5.08.00.04.zip
LeeDrOiD_V1.2b.zip
942_desire_froyo_a2sd-signed.zip
every process seemed to work normal, no error happened.
Then rebooted the Desire and the "Box with Android-Bot" Screen appeared.. this hung for 30 min or more when I could not think of any other solution than removing the battery to reset..
After this -> nothing.
I suppose as you say it has to do something with the Radio ROM..
Been coming from OpenDesire 1.6b - every flash ran perfectly up to this point.
Damn, I think this one has to go back to HTC.
Is there any possibility to unbrick a phone thats not responding at all?
Could HTC be aware of the modifications or will they really just go with the "overheated and won't turn on again" explanation?
Thanks for your help so far guys!
Yea, the little Droid with the box thing is during a radio flash and you should never pull the battery during that as it does result in a brick.
Can you reach fastboot as mentioned up above?
..tried pressing the "back" button with the power button and the vol-down button together with the power button..
even did the "insert the battery while holding the button" method..
I don't think I can get the thing to Fastboot..
But I will look further into this and try..
..
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
messywrk said:
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
Click to expand...
Click to collapse
I know someone who sent their phone back with a pretty much identical issue and the phone was fixed under warranty no problem.
Regards,
Dave
yay!
you know, even one post of you telling me it went allright for another guy is a big relief..
EDIT: just wanted to let you know I tried invoking fastboot via usb and the android PC tools..
just keeps waiting for the device.. and waiting ..
..will analyse USB traffic in general to conclude if there is a little itsy bit of life left in the phone, but I think this is a dead end too.
thank u all for ur help i have managed to unlock the phone as described
thanks alot every1
saifiraq: You seem to have stumbled in the wrong thread or could we help by coincidence?
..UPDATE:
Did usb-sniffer analysis while pulling battery, trying to turn on, plugging usb in etc.
NOTHING at all..
My baby is on it's way to HTC now.. wish me luck guys!
Ok my Evo stopped vibrating at all on everything. Even when I first boot it, the vibrate doesn't work.
I dont have the insurance, but can I still go to like a Sprint Repair Center and swap it or can they fix it?
Or do I have to send it to HTC?
First determine if it is hardware or software. What happens when you hold down the volume down button... Do you ever feel it vibrate then?
Nope its defiantly hardware
Seems like that would be a manufacturing defect covered under warranty.
nick8197 said:
Ok my Evo stopped vibrating at all on everything. Even when I first boot it, the vibrate doesn't work.
I dont have the insurance, but can I still go to like a Sprint Repair Center and swap it or can they fix it?
Or do I have to send it to HTC?
Click to expand...
Click to collapse
Download an app called sound manager. After it's installed hit menu and vibrate settings and make sure they're turned on. (just to make sure, it doesnt hurt) Good luck.
Try dildroid.
Sent from my PC36100 using XDA App
lol tried all those trust me im not a noob i would know if its software def hardware HTC said it would take 2 weeks wtf!!
I had the same problem with my evo....it stopped vibrating at all and i actually found out it was a result of dropping the phone. i have to be extra carefull now with mine because if it falls it will stop vibrating again and i will be forced to drop it again purposely untill it vibrates again...lol
give it a good shake, mines done that once before and that was all it needed to start working again
edit: just noticed this thread is three months old...
Hey xHausx
xHausx... thanks!!! it worked like a charm, vibration is now working again on my 2 months old EVO.
Thanks again!
Having the same issue here. Could someone link me to the RUU that would correct this?
Original post:
Hi All,
I've recently realized that none of my notifications will cause my EVO to vibrate.
I rooted my phone using unrevoked about 4 months ago, and up until about a month ago everything was working fine, when the vibration notifications suddenly stopped.
I have tried checking all settings (which are set correctly), downloading the Sound Manager application, and most recently (today), flashing to the Fresh 4.1 ROM, all to no avail.
I have also attempted (unsuccessfully) flashing back to the original EVO ROM (3.2 i think), after setting S-chip back to "On", but was receiving an error message stating that the main version I was trying to flash is older than the current one.
Attempts to revert back to factory defaults also did not correct this problem.
I have been searching different sites for about 3 days now hoping to find some information on how to correct this or perhaps someone who has has a similair issue.
Any assistance would be appreciated.
Thanks in advance.
I am running miui 12.11.1, stock kernel. My droid incredible as the AMOLED screen. My home button and the lower left part of the screen no longer respond to touch input. I have to rotate the screen to use parts of my screen now or I can't type in the "a" on the keyboards, or pull down the menu in landscape mode. I've wiped cache, and full wipe, but it has made no difference. I also cannot mount the internal sd card but that is a known issue with this rom I believe.
I've also tried going to a completely different rom CM 6.1 stable. but I have the same issue.
Ideas or assistance would be appreciated.
this sounds like a hardware issue and is most likely unrelated to ROM/kernel/recovery
Sounds like the digitizer screen. Same thing happened to me. Look on Ebay for a new one.
this happens with certian Dinc's. i bought a new screen to fix my home button issue because they are linked, i ended finding out it was a loose cable but according to HTC its a rare problem and was isolated to a few phones
eh. . that is ok. If it is a hardware issue than I'm just unluckly. I guess I just need to remember to rotate the screen left instead of right. Is there an easy way to map the home button to the search hard button?
I guess if it is really annoying I'll sell it to one of the devs here who could put it to good use.
Doubt its a hardware issue so test it before listening to anyone on here. I have miui as well and I have the same problem then I did a nand and flashed a new rom and it worked but I restored and the nand and the problem was back. I thought it was kernel but I flashed different ones but that isn't it...i flashed the zip for data throttling instead of editing it myself but I doubt that is the prob...so I have no cle right now I was just going to give up because now I don't even get any calls so make sure you test to rule out a hardware issue because I doubt it is bc I have the same issue and they keep getting worse until I flash a new rom. I'll try to figure it out. Ley me know on recent changes you made so that I can have some help trying to figure it out.
Well, Like I said, I wiped, factory, reset and flashed a completely different rom (went from MIUI to CM Stable) and one side of the screen was unresponsive. I turned off the phone to put in a battery and now I have all my buttons and everything seems to be working again.
vincent_price said:
Well, Like I said, I wiped, factory, reset and flashed a completely different rom (went from MIUI to CM Stable) and one side of the screen was unresponsive. I turned off the phone to put in a battery and now I have all my buttons and everything seems to be working again.
Click to expand...
Click to collapse
I've heard of issues with extended batteries where the pressure distorts the screen so it doesn't work...
Could that've been the case?
I doubt it was the battery, I had the original battery in there when it was not working and I'm using the extended battery now and it is working, both batteries have identical physical dimensions. It may very well be a hardware issue, I noticed that when I was having problems, I could not mount my sdcard on my pc. The cable was plugged in, the phone asked if I wanted to sync with the PC but it never showed up in windows. I did it just now (running CM6) and it works. The usb cable/port is underneath the home button so maybe that port is just fragile and causing issues? I never liked the location of that port, it should be on top of the phone or underneath, away from screen as much as possible.
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
Hi everybody!
I have an almost 2 years old DHD which I think is completely bricked. It was working for approximately one years perfectly and then suddenly it stopped working. Whenever I tried to turn it on, it only vibrated once and did nothing more. Sometimes it turned on and these working periods were enough to restore to stock condition (It was rooted and had Eng S-OFF before.). I had brought it to service and they said they was not going to repair it as the device got water damaged. I'm pretty sure it was not! After a few weeks, it started working again. I was using it for 3 months then it bricked again and it's the situation today as well.
Previous week I looked into the development thread and saw all of these new amazing roms. So I took my DHD to see if it's working or not. The situation is the same. Everytime I power it on, the phone only vibrates once and nothing happens. I'm not able to get into hboot mode. At some very rare occassions the phone turns on and works flawlessly till reboot. When I connect it with USB, the computer doesn't recognize it. Battery is charged, I even tried another battery.
Does anybody know what happens with the phone? I'm open to any possible solutions to try. Please don't suggest to bring it to service or repair it, because I have another phone, just want to try to recover it and ask your ideas about the problem.
Thanks in advance!
Greetings,
Adam
So you say you cant enter in fastboot or recovery?
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
paescheh said:
So you say you cant enter in fastboot or recovery?
Click to expand...
Click to collapse
I cannot enter into hboot mode. Didn't try recovery, but assume it's the same.
waterbox said:
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
Click to expand...
Click to collapse
I also think it's a hardware problem. Will take a more careful look at the battery.
Sent from my CM10-powered GT-I9103
need help
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
goofed again said:
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
Click to expand...
Click to collapse
Wrong sub forum buddy, post in the One V Forum.
Its possible that there isn't "water damage", but there could be moisture getting into the phone causing it to act erratic. To cancel out that possibility, submerge it in a closed container full of rice for a few days
Sent from a satellite