Develop Bugs

Strange Brick

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!

Boot loop problem

Ok, so this is not my phone that I'm trying to fix. Its a buddy of mine that has never rooted or messed with his phone. Apparently this just suddenly happened out of no where. He can get into a 3 button bootloader but it says "reboot" "reboot bootloader" and "power down". Again this isn't my phone and I'm not familiar with HTC at all. Please help lol
Sent from my SCH-I500 using xda premium

That's the fastboot screen, what happens when you press the reboot bootloader?
Sent from my PC36100 using Tapatalk

similiar problem
I'm having a similiar problem and have read many threads and apparently the problem i'm dealing with is a hardware issue...apparently... I just don' understand how a phone will only boot up to the home screen for a moment and then go through boot loops. When i go into hboot it will stay there and never crash and never bootloop, it will literally stay there until batt dies. It seems a software issue or something to me??? I've rooted it, tried divers roms, radios, etc. all to no avail, so, I then unrooted. I have charged it all the while off and while on. I have pulled the charger and plugged it back up without turning it on just to make it as fully charged as I can. I have let it bootloop until it shuts itself off. I have left it in hboot until the battery completely died and then turned it back on and repeated this until it would not start again. Nothing has worked, I've called HTC and Sprint but it's not under warranty and I am broke.
I am desperate for help....desperate. I have no money to replace it. I will take any suggestions and at this point try anything since it is not under warranty. If anyone is up for a challenge and project, PLEASE pm me. I've exhausted my knowledge, i've even prayed. Can anyone here offer any advice? I'm willing to pull this thing apart and examine the internals but I don't know what to look for, perhaps someone else does though.

From my experience you can do one of two things.
1. Hold volume down and power until the bootloader screen shows up. When in there use the volume buttons to go down 2 to where it was wipe data/factory reset. Hit the power button to select it and then volume up to confirm. Everything on the phone is lost, nothing on the memory card is touched. Then give it a couple minutes when it restarts and it should boot fine.
2. Take the phone apart, I have seen some that bootloop and its because the camera is loose. I know it sounds weird, but over time with phones being dropped or just the movement of being in a pocket can cause the camera to become knocked even a little loose. Simply push on the camera and you will feel it lock into place. Then put the back plate back on and turn it on and you're done.

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

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.

[Q] Glitched Out?

Phone: SGH-T989
ROM: Jedi Mind Trick X4
I'm going to try to explain this the best I can so... my apologies for any loops or confusing parts in my story.
~Basically once my phone was removed from being charged, it jumped itself into some kind of boot loop. I did not do anything just unplug it and check the time
~~The process it went though before it started to work again
~It ended up just shutting down and booting up. When it booted in only got as far as the "Deviant Development" screen and the load bar only loaded up to about 20-30% before it just rebooted itself. From there my phone was stuck on vibration. It would only vibrate for a split second, stop and vibrate again. Even if I tried to get it to make it load the TWRP recovery screen it would just boot itself again once the "Team Win" logo appeared. (Update) Device options randomly appeared by itself when I went to put it on sleep. I just tapped the button and from there it just rebooted itself.
**Question**
I'm just curious to know if anyone may know why my phone suddenly acted like that, my phone has no damage at all, never been dropped. First I ever experienced this. Any advice or suggestions?

LuciferzRage said:
**Question**
I'm just curious to know if anyone may know why my phone suddenly acted like that, my phone has no damage at all, never been dropped. First I ever experienced this. Any advice or suggestions?
Click to expand...
Click to collapse
Sounds like you have a sticky power button. I think there are a few threads about it on here if you search.

[Q] Endless reboot loop even when trying to enter recovery

One beautiful day the phone just restarted from itself. (wasnt really shocked though) After that it entered again into a boot loop, Im saying again because it happened once before and i noticed it was the SD Card and I just had to format it. So far so good, but now it doesnt matter if I pull out the SD Card or SIM, even battery... once ive put the battery the phone starts booting from it self and restarts everytime on a different place, like samsung logo, CM logo, CWM recovery, download mode.. it just cant stay on one place so i can choose an option. Only once ive managed to do a cache and dalvik wipe, also didnt help. Keeps rebooting and rebooting. Ive tried different ways of booting, with USB cable, with the recharger adaptor and without them. Left it for a whole night without battery, didnt help. I cant even manage to flash the stock ROM again, still reboots. I thought the power button was stuck or something, tried moving it arround but also didnt help. If you ask how many time Ive flashed the device... well perhaps countless, about 40 times counting the stock firmware. (maybe this number for some other maniacs is little, but now i see it like too much, because im kinda attached to this phone, the previous HD2 suffered a lot more xD) So guys my question is, do you have any suggestions? Ive searched the internet to check if the symptoms are close to hard brick but... didnt really saw any identity.

So.....
Normal boot.....it reboots, shuts off reboots.......?
Recovery mode.....reboots, shuts off, reboots.......?
Download mode.....reboots, shuts off, reboots......?
Battery insertion.....reboots, shuts off, reboots.......?
Same sequence every time?
Irrespective of which of the above scenarios is taking place?
If you just sat and watched it without pressing any buttons, will it endlessly reboot, shut off, reboot?.....
During this cycle, does it get to the same point in the boot process before restarting?.....
Sent from my GT-I9100 using xda app-developers app

keithross39 said:
So.....
Normal boot.....it reboots, shuts off reboots.......?
Recovery mode.....reboots, shuts off, reboots.......?
Download mode.....reboots, shuts off, reboots......?
Battery insertion.....reboots, shuts off, reboots.......?
Same sequence every time?
Irrespective of which of the above scenarios is taking place?
If you just sat and watched it without pressing any buttons, will it endlessly reboot, shut off, reboot?.....
During this cycle, does it get to the same point in the boot process before restarting?.....
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thank you! I thought nobody will answer. It reboots right after passing 3 to 5 seconds, sometimes on the CM Samsung splash, sometimes on the spinning CM circle(boot loading image), when i succeed entering CWM or download mode reboots again. I cant boot it normally and reach the home screen. I read something that it could be from the kernel boot code, im using CM 10 (if im not guessing wrong).

I've answered a number of threads in the XDA W forum where members were experiencing similar issues to yourself. I doubt it's software related as during access to download mode and recovery mode , the phone isn't even using the "main" system software and kernel....these modes use their own independent kernel and system (it would be HIGHLY unlikely that two separate systems and two separate kernels are suffering from the same fault).
If all of the symptoms I wrote about in my original reply apply to your phone, then it all points towards a faulty power button.
As I understand it, Samsung uses a type of button commonly referred to as "temporary push to make" which means that when you push the button, two contacts are bridged to make an electrical connection but when you release the button the contact is broken. Under normal circumstances, this "make, break" sequence will start a normal boot sequence. Under normal conditions, long pressing this button again will begin the shutdown process. Now assume for a moment that the button has become damaged....where this contact that is meant to be momentary, has in fact become permanent......the result would be a phone that will attempt to start up and shut down in an endless cycle....basically, YOUR phone........
Sent from my GT-I9100 using Tapatalk

Yeah, I also thought that as a reason but discarded it quickly because the button doesnt have any problems when pushing it. I mean it freely comes back when pushed and i can also freely push it without problems. Also discarded that problem because i thought the button cant stop the booting cycle while booting, but it seems like it can. Thanks for all the answering I will try fixing it and will report as soon as possible.

The plastic button is separate to the electrical part I described....so it is entirely possible for the part you normally touch to *seem* to be working as it should.....only for it to work against the faulty electrical part........
And yes, that type of fault IS caused by the permanent contact of a faulty electrical button. Anybody who has a normally booting W (as I do) can re create this fault simply by pressing and holding the power button......the phone WILL enter a boot/shut down/reboot cycle for as long as the button is held........
The same condition can be re created on my S2 in exactly the same way as well.....
Sent from my Infected KitKat bar.....

Well.. bad news.. i've managed to disassemble it, tried to see whats wrong with the button (not the plastic one), tried moving it arround, nothing seems to be damaged, still stable at one place, also tried booting the phone 3 times without any covers and the result was the same...
Perhaps i should drive it to service.

Check your date of purchase.....Samsung phones have a two year warranty.......
Sent from my Infected KitKat bar.....

Well bad luck here also, i got it almost brand new from England and I'm not from England. I bought it over online shop sold as a second hand long time ago, it was just a matter of time to damage him. Thanks anyway for all the help, I'll see what i can do with the service.

Bad luck mate.....word of caution though.....as you've found out, the button is soldered directly to the motherboard, Samsung's "modus operandi" seems to be rather than attempt to repair the button, simply replace the entire MB........for a phone that is outside warranty, this will have (erm) "cost implications" lol......basically they like to charge as much as they can in situations like these.....eg/ board replacement when button repair would be enough.....
Sent from my Infected KitKat bar.....

keithross39 said:
Bad luck mate.....word of caution though.....as you've found out, the button is soldered directly to the motherboard, Samsung's "modus operandi" seems to be rather than attempt to repair the button, simply replace the entire MB........for a phone that is outside warranty, this will have (erm) "cost implications" lol......basically they like to charge as much as they can in situations like these.....eg/ board replacement when button repair would be enough.....
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
True, my phone suffered the Power Off Loop as you may know from my previous thread. I decided to send my phone to a couple of repair shops and they said that the phone "cnt be repaired". i thought they knew about the change of MB but no. So rite now, my Galaxy W is in the grave ...
Sent from my GT-S6500 using xda app-developers app

i had encountered this issue with my galaxy wonder today and would like to seek for solutions over the internet. regardless that i also checked the button by disassembling the covers and separated the plastic button with the one on the board and tried to boot it but it still the same.
as most of you guys experienced this issue, what would you guys suggest me to do with my phone? i wish to save this phone for sentimental reason. would change the button DIY-ly is worth it? is it available for me to get the parts?
or did you guys manage to get a better solution?
thanks!