Related
Hi guys,
I bought a brand new TP2. I did upgrade it (flash ROM) with the one published by HTC (wm6.5 for europe, not linked to any operator).
Everything is fine except that, every day, it stops without obvious reason but always when I do not manipulate it.
It stays with a black screen.
This night it happened when charging. I removed the plug but the led (green one when charging is ok) staid green. Means to me that it's not a screen issue.
Power button does not help. Nothing happens.
I need to soft reset or to remove/replace the battery to have it restart.
I have read that it could be due to a certain threshold of app. memory (83%).
Thus I installed cleanRAM that, every 3 hours, clean the RAM. Thus I'm quite certain that is it not a problem of memory.
Any idea ? Suggestion ?
Thanks a lot for your help !
I've had the same problem, but only WITH cleanram. The way I solved it is to use the excluded list in cleanram so it doesn't tamper with tf3d. Now it works fine, no more soft-resets in the morning
You should try nopushinternet and SSK TP2 Dynamic Resource Proxy cabs. they will lower your usage up to 20%.
you could also try scheduled restart, maybe that will help if it is already resetting every day.
hreiner said:
Hi guys,
I bought a brand new TP2. I did upgrade it (flash ROM) with the one published by HTC (wm6.5 for europe, not linked to any operator).
Everything is fine except that, every day, it stops without obvious reason but always when I do not manipulate it.
It stays with a black screen.
This night it happened when charging. I removed the plug but the led (green one when charging is ok) staid green. Means to me that it's not a screen issue.
Power button does not help. Nothing happens.
I need to soft reset or to remove/replace the battery to have it restart.
I have read that it could be due to a certain threshold of app. memory (83%).
Thus I installed cleanRAM that, every 3 hours, clean the RAM. Thus I'm quite certain that is it not a problem of memory.
Any idea ? Suggestion ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the club. Same problems here but yet without result or ideas
I honestly have gone without resetting my phone in 4 days and it is running like I just reset it. Go through the forums and find the popular cabs to get an idea what everyone is using to help make their TP2 stable.
I think you talking about this problem: http://forum.xda-developers.com/showthread.php?t=619113
I think it's good thing to join our force in one thread.
This is the third time I have had this problem. Randomly my phone slows down to a halt, the data connection does not work, most setting icons take 10 minutes to load if they do at all yet my texts still work.
There are NO apps running in the task manager.
I have removed most of my programs.
My mods are just removing the TF3D crap, nothing serious.
My stock task manager icon is missing from the top right.
and when I rebooted the phone I would get two errors, one with opera and the other with ~pcom-something.exe"
The other times I reset to unit to "factory out of the box" but I am sick of resetting up the phone with my apps, mods and such.
Has anyone seen this before?
What rom do you have on your phone ? What do you mean by removing all the tf3d crap? And have you flashed different roms without using task29 in between? It sounds like its time to task29 and reflash.
Sorry, I removed the TF3D stuff with mostly registry edits. I am still on a stock 6.1 rom.
Well, it could be pretty work-intensive to try and track down exactly whats causing your slowdowns and freezes, and since you have had to keep on hard resetting it, I would think that you dont really have much to lose by flashing a new rom. If you like the stock 6.1, you could just download it from the Windows Mobile Rom Developement subforum. Alls you would have to do is hard spl your phone and then flash it, it should take less than an hour start to finish, including downloading the rom.
Also:
My stock task manager icon is also missing from the top right.
and when I rebooted the phone I would get two errors, one with opera and the other with ~pcom-something.exe"
I can set this back to a stock ROM with the phone itself and I have all my apps on my card. Doing all the registry things is a pain only because I did not memorize them... YET, haha.
Is there a better task manager to see whats eating up resources?
If you're running the ROM that actually came stock on the Tilt II, then the hot fixes for the issues you are describing can be found here on HTC's website.
http://www.htc.com/us/support/tilt-2-att/downloads/
I'm on verizon, will it matter?
Mother F-er.
Just rebooted to try and get the errors again and instead got this:
"The device is unable to boot because either you have turned off the device incorrectly or tired to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
The operation will delete all of your personal data and restore the device to it's factory default settings."
I guess my decision is made, but wow I am not happy. This phone may go into a lake.
... edit:
Volume up does not do anything. AWEsome.
Yeah it matters, here are some Hot fixes for you're touch pro II. Don't know if they will help ya though: http://www.htc.com/www/supportdownloadlist.aspx?p_id=250&act=sd&cat=all
I took the battery out again and put it back in. Same message and the volume up did not work again.
So I pressed volume up about 100 times then held down the power button. Nothing changed.
Then.... I slide open the keyboard and closed it. Put the unit down and about 45 seconds later I heard all 100 volume up presses in a row. The stock WM volume menu was over the windows boot screen, and then the task bar showed up. Then the unit shut off and rebooted but took forever. It looked normal , but SLOW.
Now:
"A problem has occurred with Opera9.exe"
then:
"A problem has occurred with cprog.exe"
WTF is going on. I have not installed/uninstalled ANYthing for weeks.
set the phone to factory defaults last night and changed everything back. Meh.
Thanks for the ideas guys and I will be doing those "hotfixes" very soon!
Cheers,
Dan
Well, this phone is doing it yet again.
It barely works.
everytime I press something it takes between 5 seconds and 1 minute to do it.
i have no signal
most programs do not even try to start
resets change nothing (done this about 100 times today)
What the hell is going on with this phone? This was just as random. Was working as normal until around noon and then it just slowed way down and I could not make calls or answer them.
Grr.
so:
when I reboot the phone, I have the green start up screen for ~5 minutes.
the phone does not work after it fully starts up.
I can not open "remove programs"
I do not have the task manager in the top task bar, but when I go into settings and open task manager, there is nothing running.
I run "cleanRAM" on level 3 and there is no change.
It is still very slow I have not installed anything new at all, so this sudden change reasoning is unknown. This may be my last windows phone as I am growing tired of these random major failures.
Well verizon sent me a new phone.
*PHUCK*, its WM6.5 and I hate 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.
My tablet recently began entering a locked blue screen state devoid of text or icon. It holds there for one to three seconds and then reboots.
Prior to the start of this rebooting sequence trend I downloaded and installed the stock ROM listed on my signature, hoping that it would alleviate some issues with delay in screen tap response, some occasional heating during gaming along with what I perceived to be a little bit of driver related lag.
I haven't figured out when, why, or how it decides to reboot. But as far as I can tell it seems to be related to [behind the scenes machinery of] Google Play (GP). I suspect this because it has happened when I've launched GP or GP tried to do some updates or software installation.
Incidentally, though possibly unrelated, when I try to add an account via settings, at the sign in page, the device returns unable to sign-in message citing connectivity issues. I am in China, so I suspect this could all be related. To get around this issue, I log into a VPN service. This allows me to sign in and add the account to the device. However, in order to play any games, I must log off the VPN. But once the account has been added to the device, it more-or-less is able to access some of the Google services (at least the ones not outright blocked -such as drive and YouTube).
In my troubleshooting attempts, I have thus far done a cache wipe and factory reset from the boot menu. All to no avail.
At this point I need to live in constant fear of a sudden reboot, for I know not when it will strike next.
I would appreciate some suggestions on either what the issue might be, how to determine the cause, or how to solve it.
Thanks
Funny story...
So Kitkat has been released, for the TGY country code.. Yay!
P605ZSUCNE3_P605OZSCNE3_P605ZSUCNE1_HOME.tar
Is the md5 file to be put into the AP slot of Odin 3.09, for my tablet.
I was excited thinking this would address the issue.
Prior to flashing the ROM I factory reset from within the settings, then I went into the recovery boot menu and there I wiped the cache and did a factory reset once more.
Then I proceeded to setup and sign into my Google account, after flashing the ROM.
Naturally the tablet went ahead and started downloading and installing apps and updates from Google Play.
I was happy to see that it was progressing along swimmingly.
The screen dimmed down and then shutdown after period of inactivity (while downloading and installing apps in the background).
Occasionally, I'd click the home button to see tat everything was going as it ought.
I then noticed the screen turned black somewhat suddenly, without dimming first.
I thought little of it.But I went to check by pressing the home button... I figured maybe there's a little lag or the tablet is too busy installing, so I clicked the power button. Nothing; no response.
The tablet is deader than dead.
Now I don't know what to do.
After waiting a while, under the advisement of another user who apparently has also been having issues with his note 10.1 2014, I decided to try to long press the power button. The tablet came back on, and resumed downloading and updating from Google.
But now the tablet is going into this sudden blank blue screen and most of the time rebooting on its own (occasionally it needs a little help, by the pressing and holding of the power button to induce the reboot) ever so randomly. I have found absolutely nor rhyme nor reason for when or how it decides it's going to reboot itself. It tends to happen often if/when I launch some apps that require logging into Google services; but at times it happens without provocation -at all.
Recently it's been boot-looping -without the launching of any app... just from turning on, sitting idle, and then rebooting. But I'm no closer to figuring out how to consistently induce the reboot, either.
My tablet has never been rooted (and for obvious reasons, never will be), no custom ROM, no ROM from another region. Nothing that would give Samsung the excuse to void my warranty (not that it's worth much, here in China).
And yet, it still reboots at random intervals for no immediately apparent reason.
In any event, if anyone has any ideas on how to proceed, any suggestions on what to do with this POS, I'm open to suggestions.
I'm interested in general ideas such as take it to the Samsung shop (something I'm loathe to do because Samsung has terrible service -especially in China- and at best I'm looking at a month or something like that before I get it back), so some ideas on how to discover when/why/how this rebooting sequence is being triggered -and maybe troubleshoot it is slightly preferable.
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.