Just did the usual "disconnect & reset" with a new phone. Normally, this triggers a couple of updates, but not this time. Has ASUS shut down the update server or something?
Related
Hi,
A few days ago, I updated my HTC Titan (bought in 2011 in France as a sim-unlocked device) to the official Tango update (+ firmware update) through Zune.
Then, after doing a hard reset, the usual setup assistant is displayed, but at the end of it there is a new step that wasn't there before the update (titled "Almost Done") telling me that the phone is going to launch some kind of htc specific utility in order to configure my data connection for my carrier. Then after clicking on "continue", I see a black screen for about 15 seconds (like when an app doesn't manage to load properly and WP7 kills it because it took too long to start), then the start screen appears (but I don't receive the usual fake welcome SMS from Windows Phone).
I can launch apps, but the capacitive Back button, Start button, Search button don't react (they cause the phone to vibrate, but WP doesn't react to these commands).
After shutting down the phone and restarting it, I'm greeted by the setup recovering screen (titled "Welcome Back") telling me that Windows Phone will resume my setup where I left it (that explains why the capacitive buttons don't react: they were software disabled because Windows Phone considered it was still in first setup mode. Same for the fake welcome sms I didn't receive). Of course the same problem happens again when I tap on continue, and when I restart my phone.
I tried several hard reset through the usual methods (either through the about menu, or through the menu displayed using VolUp+VolDown at startup). Still the same problem. I guess it's a bug that should happen on many Titan devices. I contacted the HTC support and they told me to send my phone back to HTC for repair
Of course Zune won't let me restore the backup because of the firmware update not longer compatible with the backup.
Did anybody have the same problem with a stock htc titan rom?
I'm also wondering what is the new "HTC Log disable" command on the "CUST APPSBL" screen? I'm sure it wasn't there before the update. Is there some kind of htc specific logging that is enabled by default (since it is a "disable" command). What is being logged?
Also, the red diode (indicating when the battery is charging) is being lit during startup, which didn't happen before the update. Does that mean something?
Hi,
It is quite normal for the new Tango ROM to display that extra HTC specific step, even though it doesn't work!
I experimented with the Titan a bit and found that as soon as the Start screen appears after setup, before doing anything else, long press the Connection setup app in the app list and uninstall it.
It will enable normal functionality.
If needed you can always download it again from Marketplace.
「 Jai Hind 」
Sent from my GT-N7000 using xda app-developers app
It happened to me too!!!
Moreover, after a hard-reset the HTC Market disappeared in the market!
I disabled the pin to the sim re-formatted, and connected to electricity, and aftew few times HTC market reappeared (!), immediately updated ALL the htc software (even the connection wizard) and everything is OK now... exept the possibility to install INSIDER (by Microsoft)... it is said that the app is not available for my device (!!!) ... I used it until yesterday on my Titan with Mango... I REALLY DO NOT KNOW
BYE
link8506 said:
Hi,
A few days ago, I updated my HTC Titan (bought in 2011 in France as a sim-unlocked device) to the official Tango update (+ firmware update) through Zune.
Then, after doing a hard reset, the usual setup assistant is displayed, but at the end of it there is a new step that wasn't there before the update (titled "Almost Done") telling me that the phone is going to launch some kind of htc specific utility in order to configure my data connection for my carrier. Then after clicking on "continue", I see a black screen for about 15 seconds (like when an app doesn't manage to load properly and WP7 kills it because it took too long to start), then the start screen appears (but I don't receive the usual fake welcome SMS from Windows Phone).
I can launch apps, but the capacitive Back button, Start button, Search button don't react (they cause the phone to vibrate, but WP doesn't react to these commands).
After shutting down the phone and restarting it, I'm greeted by the setup recovering screen (titled "Welcome Back") telling me that Windows Phone will resume my setup where I left it (that explains why the capacitive buttons don't react: they were software disabled because Windows Phone considered it was still in first setup mode. Same for the fake welcome sms I didn't receive). Of course the same problem happens again when I tap on continue, and when I restart my phone.
I tried several hard reset through the usual methods (either through the about menu, or through the menu displayed using VolUp+VolDown at startup). Still the same problem. I guess it's a bug that should happen on many Titan devices. I contacted the HTC support and they told me to send my phone back to HTC for repair
Of course Zune won't let me restore the backup because of the firmware update not longer compatible with the backup.
Did anybody have the same problem with a stock htc titan rom?
I'm also wondering what is the new "HTC Log disable" command on the "CUST APPSBL" screen? I'm sure it wasn't there before the update. Is there some kind of htc specific logging that is enabled by default (since it is a "disable" command). What is being logged?
Also, the red diode (indicating when the battery is charging) is being lit during startup, which didn't happen before the update. Does that mean something?
Click to expand...
Click to collapse
Yes, exactly the same problem happened after hard-resetting on tango. I simply waited a bit with the phone on the main menu and the softkeys not working. After a while, I received the WP7 welcome text, and the softkeys started to work again.
maTTeo
Hi all,
I made a new hard-reset.
As suggested by maTTeo I simply waited even with softkeys not working... I only disactivated the pin on sim so that the Titan could find an internet connection.
After receiving the SMS of woelcome on WP7, I immediately upgraded all the HTC apps
Everythings seems fine for the moment...
BYE
Another user in this forum had made a suggestion for what they did to receive the ability to reject the 2.06 update while on stock, non - rooted, locked, S-ON. I followed the same steps and was presented the "Reject" option as well.
When the update notification appeared and presented the option for OK or Defer, I have been selecting Defer. This time I selected OK. I immediately powered down the handset, then started up again. When the phone was fully booted up, a new notification appeared, but this time it included the option to Reject. I selected Reject, and it said "Download Canceled" and directed me to go to the software update menu if I wanted to apply the update.
That's it, no more complicated than that, and hopefully I won't get the nag screen for the update again. I'd be glad to hear from the others who have done this - has the update screen reappeared eventually, or does this seem to be a permanent fix?
Thanks to those who shared their experience and told how they did this, it certainly wasn't my idea.
Sent from my HTC6435PC
I tried this twice, didn't have the same results.
Clicked the OK instead of defer, held down the power button to shut down the phone, and when it rebooted I didn't get any update notification.
The next day the notification was back, still without reject.
Finally, I just went into settings and did an update check, and when the update notification popped up reject was listed as an option.
I will update this if the notification shows up again on it's own.
andyd273 said:
I tried this twice, didn't have the same results.
Clicked the OK instead of defer, held down the power button to shut down the phone, and when it rebooted I didn't get any update notification.
The next day the notification was back, still without reject.
Finally, I just went into settings and did an update check, and when the update notification popped up reject was listed as an option.
I will update this if the notification shows up again on it's own.
Click to expand...
Click to collapse
Good call. I just booted up a second DNA on 2.04, and went to Software Update --> Check New. The notification immediately showed up with the opportunity to Reject. Woot!
I posted this in the A500 forum as well, but it's probable that this is not a problem limited to my device, and it's also possible that there is a rom that might help me out.
I purchased my tablet on the day it came out, so it's long out of warranty. Everything has been fine with it until three nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts. At that point, any app I opened would also crash immediately. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. Installed apps also disappear, the wallpaper resets...basically nothing I do sticks once I restart. I tried to factory reset using the button combination required for my device, and the screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", the button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice? If no one has any ideas one how to fix it, is there a way to bypass the main os completely with a rom? I have absolutely no idea how those work, so it may be obvious that it won't, but I figured I'd check.
Thanks in advance! And thanks for reading this far, even if you have no advice!
Bought it new a couple of days ago. Its all running fine.
There just one thing in notifications that I can't complete... "Android setup" Basically it does a few things then gets to "adding the finishing touches" then gets stuck in this loop of restarting this part for about 2 mins until it stops amd dissapears until it pops up in notifications again.
I have tried clearing the cache and data of "android setup". Forced stop and restarted phone immediately after but doesn't help.
I realise it is not a major issue amd I could probably disable the notification for this but I would like to see it complete. Any ideas?
I imagine it may be tied to some other processes or something that may also need attention.
The phones firmware is fully up to date btw.
PS have just realised i am not allowed to post my link unfortunately. Maybe can message me for it.
** This post should be in the "Help & Troubleshooting" section of the Nexus Player - ooops. **
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
ggregor said:
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
Click to expand...
Click to collapse
There are a couple threads on this already. Mine is bricked too at the moment.
https://forum.xda-developers.com/nexus-player/help/stuck-google-screen-t3044191
https://forum.xda-developers.com/nexus-player/help/nexus-player-suddenly-dead-t3814519