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.
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
focusedonsound said:
I had a bone stock Verizon Samsung Galaxy Nexus which suddenly began to boot loop last week after receiving a text message.
(1 year warranty is 1 month past)
Upon attempting to do do a factory reset via fastboot - clear everything. start from scratch. I am presented with what seems to be a working phone however if you move through the screens too quickly the phone will reboot.
I have since tried putting several different roms on the phone including flashing back to the stock original all present the same results.
When the phone finally comes up. I wait approximately 10 seconds in between each screen tap otherwise the phone will restart.
does anyone have any insight on this. I have been searching since Saturday night for similar issues/fixes but nobody seems to have mentioned this.
Is there a way to do a hardware test on the phone to see if it is in fact hardware related vs software related?
Thanks in advance for your time and help.
-Nick
Click to expand...
Click to collapse
Anyone have any ideas.
focusedonsound said:
Anyone have any ideas.
Click to expand...
Click to collapse
I think it's just an hardware problem.
Something happens when a part of code is executed and the hardware does not respond correctly.
Similar problems happen with desktop computers, a faulty memory module, for example may create a reboot due to the error, or making a driver to crash. These smartphones are little computers...
This is what i think IMHO. I'm a computer technician.
PS. Maybe when you scroll faster the cpu goes at an higher frequency an becomes instable, did you overclocked it in the past? Try to lock the frequency as lower as possible with a custom kernel and verify if the issue appears anyway.
Anyway I'll pay a lot of attention flashing a new kernel or recovery on an instable phone, if it reboots during flash you may brick your device!
I hope this helps.
Thanks for the reply,
This is kind of the theory that I had but I didn't want to make any assumptions. With my computer background I am very familiar and understand how to trouble shoot problems with a computer. However phones area whole new cup of tea.
The phone resided in an otterbox which could have led to overheating and ultimately the processor going bad. I am no so quick to flash a new kernal etc to restrict the frequency.
The thing that I find most odd though is that there have been no similar functionality reports.
-Nick
First of all, I deeply apologize if this kind of issue has been brought up before. But right now I'm in such a nervous wreck that I can barely search for similar topics for help.
Here is what happened. I tried to root my Android Samsung Galaxy Tab 3. 7 because I heard of all the good stories and satisfaction behind it. Shame on me, I really shouldn't have tried to do something like that when I have no experience with that type of stuff. So after following the instructions, I rooted my device. Then when I turned it back on, the first thing I noticed was:
- The startup had the Samsung logo on it, but there was no ''animation"
- The screen became VERY dim
- The colors were all strange
- There was slight flickering of the screen
I then went here because reportedly that will solve the screen issue, but after downloading the recovery file through zip, nothing's changed. I realized that you also need to download the RocketTab3.1.zip, but at this point, I'm so distraught over what's happened to my tablet that all I want is to unroot, and go back to the bright screen, and the way it was, even if it means that all my saved information will be erased.
I even tried to go to settings - reset to factory settings. All my saved info is gone (which at this point, I don't even care), and the tablet is just like how it was when I first received it - except it STILL has the screen problems.
Can someone please, please, help me? If I can get my tablet back to the condition is was before, I'm never going to try to root again. It's just not worth the anxiety I'm feeling right now..
ameva said:
First of all, I deeply apologize if this kind of issue has been brought up before. But right now I'm in such a nervous wreck that I can barely search for similar topics for help.
Here is what happened. I tried to root my Android Samsung Galaxy Tab 3. 7 because I heard of all the good stories and satisfaction behind it. Shame on me, I really shouldn't have tried to do something like that when I have no experience with that type of stuff. So after following the instructions, I rooted my device. Then when I turned it back on, the first thing I noticed was:
- The startup had the Samsung logo on it, but there was no ''animation"
- The screen became VERY dim
- The colors were all strange
- There was slight flickering of the screen
I then went here because reportedly that will solve the screen issue, but after downloading the recovery file through zip, nothing's changed. I realized that you also need to download the RocketTab3.1.zip, but at this point, I'm so distraught over what's happened to my tablet that all I want is to unroot, and go back to the bright screen, and the way it was, even if it means that all my saved information will be erased.
I even tried to go to settings - reset to factory settings. All my saved info is gone (which at this point, I don't even care), and the tablet is just like how it was when I first received it - except it STILL has the screen problems.
Can someone please, please, help me? If I can get my tablet back to the condition is was before, I'm never going to try to root again. It's just not worth the anxiety I'm feeling right now..
Click to expand...
Click to collapse
Nevermind! I fixed my tablet by using Odin and a firmwire! Phew, I barely slept last night, and now my peace of mind is back. Sure, I have to reinstall my favorite apps, but you know what? I couldn't care less as long as my beautiful tablet is working as it should again.
Mods: Please feel free to close/delete this thread!
It started about 8 months ago, in retrospect, after an OTA update. I'd be looking at some app when the screen would flicker and shortly after it would either go blank, reboot or simply turn off, it was maddening and I thought the end of my little tablet. I tried a couple of different things, thinking that somehow the bootloader got corrupted I reflashed that, didn't work. I then flashed the previous version of the bootloader, that really didn't work so flashed back. I'd always kept the tablet with the stock Samsung ROM so flashed the latest Lineage ROM (great piece of work) but that didn't help and actually made it worse, when I would reboot it seemed like it would immediately flicker when things were updating, it wouldn't stay on for more than a minute. I read about the potential for cracked battery leads so changed the battery and reflowed the solder around the terminals, that didn't solve the problem either. After that I started to suspect some kind of memory/software issue so in desperation I flashed it back to the beginning of time, the original Samsung ROM and that worked. I have the TAR if anyone needs it just let me know. After you do this your back to Android 5 and you'll notice that it will notify you of OTA updates, I updated BUT I found that past the 4th update the flicker came back, this might just be an issue with my tab but just be aware. I only use this now to read the news or my Kindle books, I did notice that some apps would trigger the flicker like My Radar or Zillow so I uninstalled them.
Hope this helps.
I've been running the latest update on the d2q Note 10 welcome it's a n975u1, and I've been running ice box as my device owner as well as revenant and also use a box to keep my apps under control, very conscientiously I must add.
Ever since the last update was ready to be installed I was trying to put it off because I was hoping to get off on one of those new routing techniques that keep telling me that I can't update my system Os or I won't be able to get it done, so I kept putting it off, but with each day my system kept getting more and more strained and suddenly just begin going into a straight boot loop going from the startup screen with the Android name printed across the screen and then saying it was booted and has been reset and then immediately going straight back to that Opening screen with the Android logo on it and repeatedly doing it until I catch it at the right time to Power It Off. My question is is there any way that I am going to be able to get around having to do a factory reset on this device or does anybody have any other suggestions that may circumvent this tedious measure at this point? I've been routinely wiping system cache, make sure I got all my backups ready to go during the periods of time that it doesn't go into bootloop,(which seems to be usually once a day for a few hours it will operate just perfectly until just suddenly shuts off with no warning signs). I was also able to get onto the Verizon update app via ADB download mode and they ran a scan on it and determined that they could fix my device if I were to leave it plugged in and allow them to do it. Theresa in the process of the repair that they said needs to be done. They didn't say what this repair would consist of, so I have no idea what is the real issue here. I've been trying to get as many system debugging reports as I can pick up along the way from various apps that record crashes and such but not sure really how to process that information to be able to determine what exactly the issue is. I'm at my wit's end and just about to point to just go for it the factory reset as much as I hate to do that! I think that I have Extreme Complex post-traumatic factory reset disorder and would do just about anything to avoid having to go through this again! If anybody has any advice I would very much appreciate it and I hope I'm posting in the right for him because all these Note 10 forms get kind of confusing when you got all the various processors and countries and all the other factors that you have to where to figure out where you're supposed to be asking a question here! LOL sorry, thanks!
Power management apps and launchers can boot loop you fast... so I learned
I get good run times with no power management on my stock N10+, but it's heavily optimized and I am using a package disabler.
To fix it you'll need to edit the offending apk(s) out of the boot sequence. I haven't a clue how to do that. The power management app is the most likely suspect though.