I posted this in his thread but moved it here I guess since its more of a question. Downloaded ZEDOMAX, rooted all was well and working good. Somewhere in this mess I got an error processcom.android.mms force closed. Did some googling around fingers pointed to factory reset. So I did but now the phone won't boot. The last thing I did was try to import some SMS messages using titanium backup from and htc aria to this phone and I guess it messed up the MMS database. I had installed root explorer, wifi tether, terminal emulator so I can see my linux server and setCPU and tried to import SMS messages. After a while I just rebooted the phone to refresh everything now all I get is a splash screen (android) and the boot sound but it shuts right off. I can access recovery/download modes but where do I go from here?
I did try to reflash it again but same thing, Turn it on you see the galaxy splash screen, then the android screen with the sound and it shuts right off.
just to update here. I put a stock kernel back on from here http://www.forums.acsyndicate.net/s...ed-from-a-non-rooted-phone.?p=12012#post12012 and I get my sprint splash screen and sound but it auto loops. I think I can get the phone replaced but the binary count is going to give it away and void it so I need to get a jig to fix that. guess i solved my own problem but what caused it i have no idea must be hardware
Worked out just fine. Some guides say you need 301k resistors but three 100k will do just fine. Solder the three together. If you want to trash your own micro usb cable cut away the rubber and the sheath to expose the pins. If you take your time and do clean cuts you can re-solder it all back (they are cheap if you order them online just the same). There are three on top, two on the bottom. So if you have the female part (opening) facing away from you the resistor needs to go on the the first pins on the top and bottom (left hand side). Stick it in the phone, download mode comes on and resets the counter as well.
Related
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.
So i recently got a free upgrade to a inc 2 by turning my og inc in under warranty for a blow speaker (for the third time) and i naturally rooted it and installed a nice miui rom. Now about a month later im out of town for work and the screen has died. The phone is still operational, but the screen is black.
I am wondering if this could possibly a firmware issue? i have tried pulling the battery and booting into recovery but the screen is 100% useless. the touchscreen still seems to work, i can unlock it and answer calls ect...
My hunch is that its a hardware problem, but i'd like to try and flash it back to stock if possible to eliminate the possibility of a rom issue.
Does anyone know a way to flash a rom onto it without the use of the screen?
Can i use the HTC sync tool to set it back to stock like i could with the OG incredible?
Any help is much appreciated, i'm pretty desperate here.
if it was me, I'd flash it back to stock using a ruu file, then do a warranty claim, cause then if it's a firmware/software issue the ruu will fix it. There's a thread somewhere around that has instructions to do that, give me a minute...
Edit -found it! Here ya go- http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/page__st__53
Sent from my Incredible 2 using xda premium
ok, so my new issue is that if i flash the ruu, and the screen still doesn't work, i'll be stuck at the setup wizard right? then i won't even be able to use google voice to make calls from my laptop. i guess ill have to wait till i get home, this would be so much easier if my pos nextel work phone had service out here in wyoming.
Yea, that's a tough one, I definitely wouldn't flash an RUU for the exact reason you bring up.
One option, although it isn't without it's own challenges, would be to try to install a VNC server on your phone, so you could then connect to and use it through a desktop computer. You could probably install it easy enough through the Android Market web site. Here's one: https://play.google.com/store/apps/details?id=org.onaips.vnc
If you download the Android SDK (http://developer.android.com/sdk/index.html), connect your phone to your computer, open a command prompt and run ddms, it'll bring up the Dalvic Debug Monitor. Here, you can go to Device>Screen Capture and it'll bring up a window showing the screen of your phone. There's a refresh button which will refresh the screenshot. It'll be a little hit or miss, but you should be able to reference the screenshot to tap on your blank screen to open the VNC app, hit the start server button, and then see what IP/port it's listening on.
Once you get the VNC server running and connect, you should be able to use the phone fairly easily, although if the screen is dead even during boot (no initial boot screen, no display in h-boot) it would seem like a hardware problem and there's probably not much you can do about it.
ChrisDDD said:
Yea, that's a tough one, I definitely wouldn't flash an RUU for the exact reason you bring up.
One option, although it isn't without it's own challenges, would be to try to install a VNC server on your phone, so you could then connect to and use it through a desktop computer. You could probably install it easy enough through the Android Market web site. Here's one: https://play.google.com/store/apps/details?id=org.onaips.vnc
If you download the Android SDK (http://developer.android.com/sdk/index.html), connect your phone to your computer, open a command prompt and run ddms, it'll bring up the Dalvic Debug Monitor. Here, you can go to Device>Screen Capture and it'll bring up a window showing the screen of your phone. There's a refresh button which will refresh the screenshot. It'll be a little hit or miss, but you should be able to reference the screenshot to tap on your blank screen to open the VNC app, hit the start server button, and then see what IP/port it's listening on.
Once you get the VNC server running and connect, you should be able to use the phone fairly easily, although if the screen is dead even during boot (no initial boot screen, no display in h-boot) it would seem like a hardware problem and there's probably not much you can do about it.
Click to expand...
Click to collapse
Yeah i think i'm hosed, i have no screen at all, i can't get the ruu to run, it comes back saying i have the wrong device. i guess im just gonna send it back and hope they don't notice.
captainlovesac said:
Yeah i think i'm hosed, i have no screen at all, i can't get the ruu to run, it comes back saying i have the wrong device. i guess im just gonna send it back and hope they don't notice.
Click to expand...
Click to collapse
Where is it indicating that it's the wrong device if you have no screen?
Please Delete Post
I ran into a similar problem with black screen over the weekend.
However my phone was not rooted.
This is how it happened.
I was using my phone then I saw the screen flicker once or twice, then it went black.
I pulled out the battery and powered up again.
The phone vibrated, and after a while the four bottom buttons light up.
The volume keys work and I could receive incoming calls, but the screen just stays black.
One thing to note is that my pocket was a little wet before I pulled out the phone to use.
Also that I did use my phone for a good 5-10 mins before it went black.
What I am trying to determine is if it is a software issue or hardware.
Are the bottom button lights separate from LCD screen, so that even if they light up it could still mean LCD is bad?
Any help would be appreciated, thanks!
I've been running CM9 for almost 2 months now and its been great. 6 days ago my phone started entering docked mode by itself. I'll be doing nothing at all and it just pops up with the dock screen. Most of the time its the desktop dock screen, but once or twice it has been the car dock screen. I found that there was a newer version of CM9 released so last weekend I flashed that following all the camera gps fix instructions as well. I also made sure to remove and re-install "custom car home" and "galaxy dock sound redirector" just in case. The phone has been fine since saturday, but all of a sudden an hour ago it started doing it again.
Can anyone point me in the right direction?
Thanks.
bikewiz said:
I've been running CM9 for almost 2 months now and its been great. 6 days ago my phone started entering docked mode by itself. I'll be doing nothing at all and it just pops up with the dock screen. Most of the time its the desktop dock screen, but once or twice it has been the car dock screen. I found that there was a newer version of CM9 released so last weekend I flashed that following all the camera gps fix instructions as well. I also made sure to remove and re-install "custom car home" and "galaxy dock sound redirector" just in case. The phone has been fine since saturday, but all of a sudden an hour ago it started doing it again.
Can anyone point me in the right direction?
Thanks.
Click to expand...
Click to collapse
Back up to google and try a clean install? make sure .android secure is deleted. wipe data, dalvik, cache, system 3x (Don't forget to backup your angry birds progress.lol)
Okay, I just spent a couple hours dusting off my android skills and I deleted all my downloads for rooting and roms. I started fresh and got the latest odin, cwm, cm9 beta3, and gapps. I used odin to go to a fresh stock EL30 rom. The reason I did this was because I wanted to start from scratch, and also because my PC would not recognize my phone when plugged into the USB cable using a known good cable and uninstalling/reinstalling the Samsung USB drivers. After the fresh install was done, my USB connectivity was working again and I loaded all my new downloads on the SD card to reflash CM9.
I got all done loading everything and in the setup of my phone it asked if I wanted Google to restore my backed up wi-fi passwords, bookmarks, etc. So I allowed it to do so. It then started re-downloading all my apps from the Play store. Those must have been backed up too I thought. Walked away from the phone for a half hour and came back to it. Hit the power button to wake up the phone and its on the dock lock screen with the big clock time and the "set-alarm" option. I also tried plugging into my USB on my computer, nothing. Back to square one after over 2 hours of messing around with this.
Gonna try wipe date, cache, dalvik cache 3x and reflash cm9 and gapps. This time I wont let google load the backup and see what happens.
okay so I reflashed cm9 beta3 like i said i was going to and after about 5 mins of toying around with customization like turning off the widget auto add in play store and adjusting my volumes and ring tones, my phone popped up with the dock screen again.
WTF?
Have you tried cleaning off the USB port? According to my research (took all of a minute on google) car dock mode is triggered when the phone senses a resistance between pins 4 and 5 of the micro-usb of about 619 k. A resistance of about 365k will triggered Desk Dock mode.
So. if you have a bunch of crud jammed into the USB that could be enough to cause the problem you have.
UGH! You are probably correct!
I got fed up so I odin'd to stock and took it into the sprint store to get it swapped out. I gave them the usual "my phone doesn't charge intermittently" which has worked for all my service plan replacements in the past. They did clean crud out of the charge port, but i insisted that it still needed to be replaced. So, he took the phone completely apart (for what readson i dont know) puts it back together and tells me he has to order me one because they are out of stock on replacements. I go to walk out of the store and I have no radio bars. I go back and say hey, i think u forgot to reconnect the antenna. He agreed so he took it apart again. After that the phone would no longer power up so after another hour of trying to fix it, they had to give me a loaner phone (aka 2006 flip phone).
Thanks for the info. Hopefully this thread will be useful to someone else in the future.
A couple of months ago I broke my power button ,and managed to turn on the phone by abusing and slamming the power button to something hard,
Now ,I flashed the stock rom via odin ,rooted again ,and installed cwm .
Now ,phone accidentally turned off ,and went in a bootloop ,a quick one :show only samsung then turns off .
I can't manage to power it on in anyway .
I just want to backup the phone ,and then full wipe it.
I can't access download mode since phone is quickly rebooting!!
I need help ASAP ,Please..
TiTAN-O-One said:
**Just to be clear, I am not responsible for anything that goes wrong with your device but actually, your phone is pretty much useless with this issue if it isn't fixed so lets just give it a shot like I did**
So I bet a couple of you guys may heard of this issue, I'll be giving the link on what this issue is about (if i can find the link).
Do note that this fix will result in damaging the exterior of your phone if you don't do this carefully. Lastly before we begin, you'll lose a power button completely and switching it on requires your phone Charger and a few button combinations
Now in order to fix this, you'll need
• A plus-tipped screwdriver
• A flat head screwdriver (bigger ones are prefered)
• Your "unusable" Galaxy W
• A whole lot of patience
1st step is easy, just disassemble your phone till you have removed the Main Board. There is a guide you can follow to do this on YouTube by the Channel L355ON5 if im not mistaken
2ndly, when you get to the main board, flip over your board such that the main camera module is faced down.
3rdly, you're gonna find your power switch. When you found it, you can see that it is made of 2 colours orange and white.
4th, heres the tricky part, use your flathead screwdriver and apply pressure and scrape off the white part of the switch COMPLETELY. Its okay if you damaged your power switch because you won't need it anyways.
To check if your phone is fixed, you can clip the Display's flex cable into the main board, and then use your battery and connect it to the 3 pin contacts. If your phone did not boot, thats good news because from Keith's post (if you can find it) we know that if you try to insert the battery in the phone, it will automatically switch on by itself and that means that you haven't fix the issue nor solve anything really.
So lets say everything went correctly as mentioned above, you can now screw the parts back together.
So to turn your phone ON, connect your Phone to youe wall plug and then quickly press the button combination keys for going to Recovery Mode upon switching on you your wall plug switch. You shld then be able to go to Recovery Mode and reboot your device
Now all of this may sound scary to you but I've done all of these steps and I got my Wonder back exactly a year after I broke it. :sly:
Galaxy W 8150 Disassembly & Assembly: http://youtu.be/ZjcucJDzfmk
How to Easily Fix Defective Power Switch/Button for the Galaxy S3: http://youtu.be/3Glllc7bEJs
These 2 videos are where you should be watching before trying in case gd luck
Click to expand...
Click to collapse
This is my tutorial. I had this problem once and did this. I tried to understand what I was doing and finally got GWonder working and this is the only to do it if you lost your warranty.
Via the Internet
Unfortunately I left the phone on in its waterproof/dustproof cover, inside my fully-packed bag with no breathing space and in the car with windows rolled up under the hot sun for several hours.
Once I retrieved my phone it was already boot-looping.
It was very hot. I opened it up to see if there was anything burnt inside (motherboard, camera, SIM, etc.) but didn't see anything out of the ordinary (I'm no expert either).
It gets very warm quickly when I charge it.
I tried to get into the boot recovery mode to see if I could fix the loop by deleting cache or formatting or whatever tips I came across. It would boot, show the Note 4 Samsung Logo with the blue-lettered "recovery boot" in the top left-hand corner, vibrate, then restart and rinse and repeat.
The only hope I have is that it can get into download mode and I have not rooted the phone yet (and I have tried unsuccessfully so far). Is there anything that can be done to fix this? Thanks in advance to anyone who can help.
*shrugs*
Oh well, I'm a bit disappointed there hasn't been any reply to this
I've given up and replaced the motherboard and it's working again.
If any mod would be kind enough to delete this thread which didn't amount to anything, I'd be grateful.