I have a Cingular 2125 (a.k.a. HTC Faraday\Tornado\SPV) Anyhoo!! I attempted a flash of rom; something happened; the update froze and I was forced to reboot the device. Upon, restart I attempted to regain access to the bootloader. The device powers on to a white screen, only. No bootloader, I cannot connect to it via the PC (Windows doesnt even acknowledge a USB device is connected) So, rom updates and activesync is feutile. I can turn the device off from the white screen by holding power. And when I do a glimps of garbled code is at the top of the screen. Not really code, Its more like if a digital dinosaur doody'ed all over. i.e. colors, random segments of geometry, stuff like that. I dont know what this is presenting upon power off. Well whatever. I need to get to bootloader and fix ths phone. telnet. mtty. serial. 2.5mm COM serial . I have the supplies, the tools, the money, Help ME make this phone stronger, faster, and smarter than ever before.
Any Support, Help, Comments, Condolenses Feel Free to Buzz IN.
Related
Hi Guys,
Managed to blag a "broken" XDA Orbit from work.
Reportedly, this unit was dropped in the bath some time ago, but has been sitting on a desk for a few weeks - should be nice n' dry now!
When I connect to a usb charger (for my HTC Tytn), the top right LED on the phone flashes etc, but doesnt turn on. After a while, the light disappears.
Found something strange - the bootloader (which I tried to access via Voice Dial + Power + reset pin hole), actually works, tho without pushing the reset pin hole! I.e holding down just Voice Dial and Power puts it into Bootloader mode.
This makes me think two things:
1. The reset "btn" is damaged - jammed on or something
2. The connection inside is damaged
The Bootloader reports as follows:
IPL 1.25.0001
SPL 1.25.0000
USB
When entering BootLoader mode, the PC plays the "Hard Ware Connected" tones...
Is there any chance flashing using bootloader mode would get this puppy up and running again?
The phone was originally on a company account with O2 - would flashing to WM6 etc unlock the phone?
Be very interested to hear any suggestions!
Do a search on the Artimis forums for the O2 UK ROM and try flashing that to the device, you have nothing to lose!
read this http://forum.xda-developers.com/showthread.php?t=332269
cy80rg said:
Hi Guys,
Managed to blag a "broken" XDA Orbit from work.
Reportedly, this unit was dropped in the bath some time ago, but has been sitting on a desk for a few weeks - should be nice n' dry now!
When I connect to a usb charger (for my HTC Tytn), the top right LED on the phone flashes etc, but doesnt turn on. After a while, the light disappears.
Found something strange - the bootloader (which I tried to access via Voice Dial + Power + reset pin hole), actually works, tho without pushing the reset pin hole! I.e holding down just Voice Dial and Power puts it into Bootloader mode.
This makes me think two things:
1. The reset "btn" is damaged - jammed on or something
2. The connection inside is damaged
The Bootloader reports as follows:
IPL 1.25.0001
SPL 1.25.0000
USB
When entering BootLoader mode, the PC plays the "Hard Ware Connected" tones...
Is there any chance flashing using bootloader mode would get this puppy up and running again?
The phone was originally on a company account with O2 - would flashing to WM6 etc unlock the phone?
Be very interested to hear any suggestions!
Click to expand...
Click to collapse
I would strip the phone down and blast it out with and airline/air duster, then leave it apart for a day or so to dry-out some more.
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.
Hello everyone,
having major USB issues on my GNex. It's not charging anymore, but when the phone is off, it displays a charging animation. I could get it to charge once since this occurred, I left it plugged in overnight on my Mac (phone turned off). Did the same thing last night, no charge at all.
Mac OSX does not recognize the device, my Windows machine keeps telling me something like "the connected device is not working properly and can't be used... ". This message pops up every few seconds, so I guess it's constantly connecting and disconnecting. I can't access the internal storage on both systems.
My first guess was a hardware defect. But when I try to boot into recovery mode, a screen instantly pops up that shows Andy and displays a message: "Downloading. Do not turn off target.". In the upper left corner it displays " ODIN MODE" in small red letters.
When I press the power button in this screen (there is a big arrow pointing to the button with "start" written in it) the phone just normally reboots.
I can't get into fastboot mode because of this. I can get into CWM Recovery when i use the reboot into recovery option built in the ROM.
I dunno much about Odin (next to nothing). Has it something to do with Samsungs Kies? Could it be that something has put my phone in this "ODIN MODE" and it constantly tries to download something, making the USB port unusable? The port is not completely broken, as the phone displays a charging animation when it's turned off... so there is some connectivity left!
Thoughts coming up that this could be some kind of software issue. If there is a possibility to get out of the Odin Mode, it may solve the problem.
The phone is unlocked and rooted, running AOKP Milestone 5 and franco kernel.
I tried to restore an older nandroid, but it did not change anything.
Would send it in for exchange, but not able to relock the bootloader due to no fastboot access. If it can be confirmed that this is a hardware problem, I have to pay for the repair, I'm fine with that.
Has anybody any ideas that could be helpful? Any help is much appreciated, thank you in advance!
Do a search and you will find at least 30 helpful threads. Basically you only need to replace your USB charging board and it works again. Should be a warranty issue, but Samsung has really been an ass on handling this issue lately and claiming water damage.
I have mentioned it many times here: this problem can be probably solved by thoroughly cleaning your USB with soft toothbrush.
True, I also cleaned my port but it only fixed it temporarily.
Thanks guys. Tried to clean the port, nothing changed.
Ordered an OEM charging board off ebay, hope changing it will fix the issue.
Only thing I'm wondering about is, that the phone is stuck in Odin Mode when I boot it up with Vol. - and the Power Switch. So I downloaded Odin but it does not recognize the phone...
I am also facing the same problem. I am currently using the phone by charging the battery externally. Can someone confirm that changing the USB flex cable is the solution ?
Just posted in another thread but it is definitely the USB port for me. Using an HTC Vision (Google g2)
Hi everyone,
first off, I've spend days now trying to find a fix. If I've missed anything, I'm sorry, it wasn't for lack of trying.
Here's the situation: I have acquired an HTC One X earlier this year which has worked quite flawlessly. I went ahead and unlocked the bootloader and installed a custom recovery. However, since I handed the phone off to my not-so-techy sister I did not use a custom ROM, and after the HTC update failed with the custom recovery I reversed that as well. The device should now be stock everything with unlocked bootloader.
After a few months my sister encountered heavy problems, though. She described them as battery related (wouldn't turn on correctly) and eventually she moved to a new phone. Now I have gotten the device back and I am trying to fix it. After charging it I managed to have it boot once. However, I but it to the side and wanted it to load some more. Ever since then the screen doesn't come on. The charging LED seems to work fine (eventually switched from red to green, too, indicating that the device is fully charged) and the button backlight still works, too. Most significantly though, the device is recognized as MTP device in Windows: I can access all the data in the storage without problems.
I have read that there is an issue with the HTC One X and the display connector so eventually I went ahead and took the device apart. It's lying in front of me now in pieces, but I still couldn't get the screen to come alive. The obvious conclusion would be to buy a new screen but the device doesn't feel like it's worth the investment. Besides, I would like to know for sure that it's the screen before I do anything.
So I turn to you guys and ask if you have any idea how I could access the phone via my computer. I tried to boot it up in bootloader mode but due to the strange standby methods HTC is using and not seeing anything on the screen I haven't been able to do that yet: Whenever I connect my USB cable it's recognized as MTP device, not ADB. Debugging seems to be deactivated so that doesn't seem to be an option. Does anyone have any idea how I could get the phone to talk to my computer (i.e. get into the bootloader or ADB screencast for sure)? With my Galaxy S I could simply plug in this dummy micro USB and would be sure to end up in download mode.
Any help is appreciated!
tl;dr: HTC One X screen is dead but LEDs work, is recognized as MTP device. How to make it talk to the computer?
Thanks,
rien
Alright, sometimes just posting stuff like this helps already. I was now finally able to get the phone into fastboot (apparently) and it's reacting to the fastboot commands. I suppose the next step is to load CWM and connect via adb. This way I can at least do a factory reset.
Does anyone have any ideas regarding the original issue with the screen? Especially since it does seem to work occasionally. And doesn't show any fragments...
Can I enable USB debug mode from within the recovery to work in the system?
So I've searched here AND the entire net for a fix for this but I cannot find it anywhere. I'm decently experienced in the area of androids, flashing, and rooting and currently own a rooted Moto G Play running a debloated stock rom with Xposed installed as my main device (besides the point but just so you know my level of experience.)
I was recently given a HTC Desire 526 and was told by the giver that she couldn't turn it on. So obviously my first thought was to try to enter bootloader mode. I charged the device and held the volume up and power keys to enter bootloader, and it was successful, but still no image on the screen, mind you there is zero visible damage on the phone screen or water damage on the inside so I'm guessing it can't be that the screen is broken physically. I confirmed that it was in bootloader by running fastboot and it is listed under devices when I run "fastboot devices." Vibration works and it occasionally outputs sound so I know the phone turns on (at least). I'm completely new to HTC devices and when i try to do almost anything involving flashing with fastboot I get the s-on error. Adb isn't available as I know that developer options, and furthermore, usb debugging has not been enabled on this device at all in the past.
Can I hard reset with just hardware keys (vol up, vol down, and power)? Everything online says yes and then the instructions go on to explain how to reset via the on screen bootloader menu navigation, that of which I can't see nor navigate with a black screen (I know these "solutions" to this problem make no sense considering I asked about a device with a screen that won't turn on, very frustrating haha.) If not, does anyone have any suggestions on what I could do to get the screen to work? Not sure if this matters but it is a verizon phone. Any info is appreciated as I'm coming to my last leg trying to get this going. So annoying feeling it vibrate and hearing sounds because I feel like it is definitely fixable without replacing the screen but I'm not 100% sure. Thanks.
Edit: My only solution is to see if someone who owns this device (currently I know no one with this device) can direct me on what to push, when, to reset without my screen, so I can navigate through that phone or through pictures of it.
This post can be deleted. Still don't know the cause but it turned on and all is well now. Now I'm just searching for a proper root method!