Database Info

[Q] All services on Wp 7.5 just stopped working.

This started happening last night. Can't figure out how to fix it, and I really don't want to have to hard-reset my phone :crying:
Here's whats happened so far...
1. Metrotube wouldn't launch (insta-crashed) even after a reboot... so i uninstalled the app.
2. When i attempted to re-install metrotube, it went into the queue, but is stuck on "pending"
3. Attempting to cancel or retry the download = nothing happens
4. Feeds in the People hub refuse to update. Instantly fails with an error.
5. messenger refuses to sign in.
6. "Me" tile is stuck on "3 new items" even though Ive already read everything in there.
7. Attempting to install any other app from the marketplace = error message.
8. Rebooting the phone multiple times has done nothing to help the problems above.
What happened, and how do I fix it? Since when does WP7 randomly just fubar itself?

Still having this issue guys. Any help?

Try pulling the battery if you can for 60 seconds and then try. Otherwise, given what your phone is doing, all I can think of is a hard reset as it sounds messed up.
P.S. If you have a recent backup try using Zune to restore to that.

Device? ROM? Version?
Sent from my HD7 using Board Express

pvt_nemesis said:
Device? ROM? Version?
Sent from my HD7 using Board Express
Click to expand...
Click to collapse
Nokia Lumia 900, OS version 7.10.8779.8

Finally went ahead and hard-reset the phone. Everything is working again...going to take ages to get my handset set back up the way I like it again.
What happened and how do I keep it from happening again!?

Tell us everything you did in the past 3 weeks, and we can say what happened after that.

mcosmin222 said:
Tell us everything you did in the past 3 weeks, and we can say what happened after that.
Click to expand...
Click to collapse
Can you narrow that down slightly? I'll gladly list everything I can, but "everything" is a bit broad.
Does the list I gave in the first post give you any clues? Seems weird that the entire OS would just screw up like that, when it was working fine just minutes before hand...

It sounds to me like a potential hardware failure, either in the NAND Flash itself or in the SD card storage (for phones which use that instead of soldered-in storage). That's just a first guess, though.
As for things to tell us about, were you messing with any high-privilege apps? Either apps that use privilege elevation hacks, like WP7 Root Tools or things like Windowbreak for Samsung, or apps which you marked as "Trusted' in Root Tools?

Leapo said:
Can you narrow that down slightly? I'll gladly list everything I can, but "everything" is a bit broad.
Does the list I gave in the first post give you any clues? Seems weird that the entire OS would just screw up like that, when it was working fine just minutes before hand...
Click to expand...
Click to collapse
Well not quite everything. We don't need to know whom you're texting or stuff like that. Nice info would be if you tried rooting, sideloading some unknown app, attempting to charge without your battery, stuff like those...or if you tried some high privileges stuff, like the guy above me asked.

GoodDayToDie said:
As for things to tell us about, were you messing with any high-privilege apps? Either apps that use privilege elevation hacks, like WP7 Root Tools or things like Windowbreak for Samsung, or apps which you marked as "Trusted' in Root Tools?
Click to expand...
Click to collapse
mcosmin222 said:
Nice info would be if you tried rooting, sideloading some unknown app, attempting to charge without your battery, stuff like those...or if you tried some high privileges stuff, like the guy above me asked.
Click to expand...
Click to collapse
Like I said earlier, this is a Lumia 900. This phone can't be rooted by any known method, and mine wasn't even developer unlocked.
No high-privileges, no root tools, nothing. Totally stock and unmodified with only marketplace apps. It just decided to screw up one day and the only way to fix it was a hard reset...
Also can't charge a Lumia 900 without the battery, because it's sealed inside.

[Q] Rebooting

I've followed directions in the following two forums (and sifted through many, many others here):
http://forum.xda-developers.com/oneplus-one/general/fix-carrier-wifi-wrong-date-time-t2922849
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I've contacted OnePlus support and received new persist.img and other 38R files directly from them. I've flashed EVERYTHING in any number of ways. I've even tried CM nightly's...
But no matter what I do this phone constantly reboots. All the friggin' time. Randomly. Sometimes up to a few dozen times a day. It'll just be sitting there and it'll reboot. It'll happen when I'm using Chrome, checking my email, or when I look at it wrong. OnePlus keeps telling me it'll be fixed with the next update, but I have my doubts (since they said that before 38R was pushed).
Does anybody have any ideas on how to debug this? I am not new to android, but I'm also not all that knowledgeable about it. I'd love to see some system logs or something that'll point to what is causing these crashes, but I'm at a loss. Beyond debugging does anyone have any ideas about what could be causing it? Bad spot of memory, storage, anything? I'm at my wits end. I love the device, but can't stand these reboots that seemingly nobody else has to suffer.

Have you tried any other ROMs apart from CM?
Transmitted via Bacon

No, and I don't particularly want to. If it doesn't work with what it is supposed to then I would rather have my money back and move on to a different device. Personally I can't stand most ROMs. I like plain android and CM, but otherwise I haven't ever used one I liked. As far as it goes I may try another one just to see if the issue persists, but that's a whole lot of hassle over what would ultimately have me ask for a refund anyway.

Why not try Paranoid Android?

I'll give that one a try. Assuming the issue continues to happen, what then?

revjtanton said:
No, and I don't particularly want to. If it doesn't work with what it is supposed to then I would rather have my money back and move on to a different device. Personally I can't stand most ROMs. I like plain android and CM, but otherwise I haven't ever used one I liked. As far as it goes I may try another one just to see if the issue persists, but that's a whole lot of hassle over what would ultimately have me ask for a refund anyway.
Click to expand...
Click to collapse
revjtanton said:
I'll give that one a try. Assuming the issue continues to happen, what then?
Click to expand...
Click to collapse
There really isn't very much difference between CM and other ROMs anyway. If it continues then I'd suggest starting the RMA process.
Transmitted via Bacon

I just tried Paranoid Android. I couldn't even get past the Welcome screens without a reboot.
goddamn it.

[Q] Reliable fix for random reboots?

I have a rooted stock 11s ROM with TWRP recovery. I can't stand the random reboots anymore. I've seen the plausible explanation that the problem is driver-related, probably wifi. There are claims that the factory sent out ROMs with a defective system partition. I've seen purported solutions for that theory including total wiping (including system) and reflashing stock. I've seen claims that flashing a kernel is the answer. Most of this seems to be speculation. And a lot of it takes place outside XDA. I know this is the best place to come for smart answers.
Please propose any solution that might have worked for you. And-- if you reach me by 18:30 Pacific time (US) with a rational message, I have something to convey that a non-owner would love to have.
Thanks folks!

Are you on the latest CM11s? Never had a random reboot, maybe try factory resetting it and installing apps fromplaystore all over again? Restoring apps from Titanium Backup can cause weird issues sometimes. Esp if its a new device.

goattee said:
I have a rooted stock 11s ROM with TWRP recovery. I can't stand the random reboots anymore. I've seen the plausible explanation that the problem is driver-related, probably wifi. There are claims that the factory sent out ROMs with a defective system partition. I've seen purported solutions for that theory including total wiping (including system) and reflashing stock. I've seen claims that flashing a kernel is the answer. Most of this seems to be speculation. And a lot of it takes place outside XDA. I know this is the best place to come for smart answers.
Please propose any solution that might have worked for you. And-- if you reach me by 18:30 Pacific time (US) with a rational message, I have something to convey that a non-owner would love to have.
Thanks folks!
Click to expand...
Click to collapse
The problem with this situation is that there can be way too many causes for random reboots, we're talking dozens and dozens and dozens. So pinpointing exactly what's causing your particular device to reboot is virtually impossible. Your best solution? Go to this thread and use that automated tool to perform a wipe and bring your phone back to an entirely stock state.
Transmitted via Bacon
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
SilentRazor said:
Are you on the latest CM11s? Never had a random reboot, maybe try factory resetting it and installing apps fromplaystore all over again? Restoring apps from Titanium Backup can cause weird issues sometimes. Esp if its a new device.
Click to expand...
Click to collapse
Not really. I've flashed thousands of times and I restore my apps with Titanium every single time, I never, ever have problems. As long as you don't do something stupid like restoring system data then TiBu is perfectly safe to use.
Transmitted via Bacon

I'm having the same issue.
44S, rooted, TWRP. No Xposed, no themes, no icon packs and each day the reboots are getting worse. I've read the same thing about a faulty partition being a culprit and am going to try the tool linked above to see if that has any impact.
If you are still inside the 45 day window of purchase, I would suggest opening a ticket with Oneplus. It would be worth getting the issues documented as early as possible so you can have a valid claim for a warranty repair if it comes to that.

Psichi said:
I'm having the same issue.
If you are still inside the 45 day window of purchase, I would suggest opening a ticket with Oneplus. It would be worth getting the issues documented as early as possible so you can have a valid claim for a warranty repair if it comes to that.
Click to expand...
Click to collapse
Thanks for your wise suggestion! I just followed your advice. At least it gives me one possible option. I love the phone when it's not rebooting. But it's already rebooted a couple times just as a call was coming in!!!

Don't attribute the problem to Titanium Backup
Psichi said:
I've flashed thousands of times and I restore my apps with Titanium every single time, I never, ever have problems. As long as you don't do something stupid like restoring system data then TiBu is perfectly safe to use.
Click to expand...
Click to collapse
I agree.
I have used Titanium Backup on numerous Android devices from a variety of manufacturers-- including CyanogenMod 7 on my Nexus One. It's never been the cause of problems. And I also agree that the only reason Titanium restores would cause a problem is if you're restoring "foreign" system apps.

I don't have any confidence that using the official tool would solve the problem-- especially if the theory about the defective system partition image is the correct one-- I might just be reinstalling the same problem.
I'm more inclined to try the solution by echew010 in this thread:
https://forums.oneplus.net/threads/random-reboot.232446/
But I am not sure how bold I want to be. I'm not afraid of the concept of totally wiping the system partion. And it wouldn't be the first time I've had to rebuild a device all the way up to restoring apps from Titanium Backup. But it's such a pain. Maybe this weekend if nothing else turns up.
Two hours until my invitation expires. Anyone interested? Private me.

goattee said:
I don't have any confidence that using the official tool would solve the problem-- especially if the theory about the defective system partition image is the correct one-- I might just be reinstalling the same problem.
I'm more inclined to try the solution by echew010 in this thread:
https://forums.oneplus.net/threads/random-reboot.232446/
But I am not sure how bold I want to be. I'm not afraid of the concept of totally wiping the system partion. And it wouldn't be the first time I've had to rebuild a device all the way up to restoring apps from Titanium Backup. But it's such a pain. Maybe this weekend if nothing else turns up.
Two hours until my invitation expires. Anyone interested? Private me.
Click to expand...
Click to collapse
I'm not sure who's saying it's a corrupt system partition, I really don't think that's the case, if it were corrupt your phone wouldn't boot at all. Plus, the tool I linked to is perfectly fine, if there were something wrong with it then all of the people who have used it would be suffering all kinds of problems. You won't be reinstalling the same problem. That is your best option.
Transmitted via Bacon
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
Plus, that fix you linked to one the OnePlus forum is almost doing the same thing, but it is missing some steps, and it would take longer. If you don't have confidence in the official tool then by the same logic you shouldn't have confidence in this other fix either, they both install official builds of CM11S onto your device. The official tool is more thorough, it is quicker, it is what you should be doing.
Transmitted via Bacon

I haves the same Problem with 44s. I try to revert back to 33r so I don't have random reboots

timmaaa said:
I'm not sure who's saying it's a corrupt system partition, I really don't think that's the case, if it were corrupt your phone wouldn't boot at all. Plus, the tool I linked to is perfectly fine, if there were something wrong with it then all of the people who have used it would be suffering all kinds of problems. You won't be reinstalling the same problem. That is your best option.
Transmitted via Bacon
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
Plus, that fix you linked to one the OnePlus forum is almost doing the same thing, but it is missing some steps, and it would take longer. If you don't have confidence in the official tool then by the same logic you shouldn't have confidence in this other fix either, they both install official builds of CM11S onto your device. The official tool is more thorough, it is quicker, it is what you should be doing.
Transmitted via Bacon
Click to expand...
Click to collapse
You've convinced me with your logic that the official tool is the preferable approach of the two. I probably will try it in the next few days.
By the way, I followed advice to open a support ticket with OnePlus. Someone got back to me within 24 hours. I was asked to send them a video showing a random reboot. Am I supposed to keep a camera pointed on my phone 24 hours while waiting for a reboot?

Chikamru said:
I haves the same Problem with 44s. I try to revert back to 33r so I don't have random reboots
Click to expand...
Click to collapse
How long ago did you revert? Did the random reboots stop completely? Or do they just happen less frequently?

I'm on the same boat. Support is totally useless. For the past month or so they keep asking me to send them a video showing that my phone is rebooting randomly and all kinds of similar stupid requests.
I saw people talking about racing conditions when the device's storage is encrypted. For me this is a must or I won't get corp email. But I went through the various tools that would make me 100% "factory clean" and yet, the phone reboots just by sitting on my desk.
When I had encryption enabled, I'd come back home from work and find it beeping at the enter your password to decrypt screen. Now I keep it super clean, and don't encrypt it, don't do anything but enter my google ID/passwd to setup the device as new. When I check it, uptime is rarely more than an hour or two, so it reboots again, but comes back to a working state. I wonder if people, generally not encrypting, don't even notice when their device reboots.
I've finally got forwarded to some RMA person who said he'd send me the papers to get a new phone. Unfortunately, that has also taken days of silence now.
Very frustrating I can't use the OPO with its original ROM, after many years of flashing all kinds of ROMs to anything from Nexus One to my the N5 I went back to until the OPO gets fixed, to several Samsungs, LGs and HTCs and having FCs, some reboots, very stable builds, but never anything like this.

timmaaa said:
The problem with this situation is that there can be way too many causes for random reboots, we're talking dozens and dozens and dozens. So pinpointing exactly what's causing your particular device to reboot is virtually impossible.
Click to expand...
Click to collapse
Of course you are correct that there are many variables that can be the immediate cause of the reboots. But what cannot be denied is that so many users are experiencing the problem across various CyanogenMod versions. Because there are so many users, it's hard to believe that it's a few buggy user-installed apps causing the problem.
My favorite theory is that OnePlus has defective drivers. It reminds me of the effort to create custom ROMs for the Samsung Galaxy Tab 7.7 (GT-P6800). Samsung would not or could not release the wifi driver into the developer community. Same story with the ASUS Transformer TF101. ROM developers created pretty good ROMs but their degree of success depended heavily on whether they could scavenge drivers from cousin products. The Transformer efforts succeeded. The Galaxy Tab 7.7 custom ROMs still have some anomalies.
marvinandro said:
I'm on the same boat. Support is totally useless. For the past month or so they keep asking me to send them a video showing that my phone is rebooting randomly and all kinds of similar stupid requests.
Click to expand...
Click to collapse
I created two videos.
One shows a UI freezing issue that I experience periodically. I'm guessing it's a defect in interfaces to the Android System UI module.
The other demonstrates how the phone has rebooted on a few occasions when it receives an incoming call.
I saw people talking about racing conditions when the device's storage is encrypted. For me this is a must or I won't get corp email. But I went through the various tools that would make me 100% "factory clean" and yet, the phone reboots just by sitting on my desk.
Click to expand...
Click to collapse
I am betting that it's not the encryption itself that's the underlying cause. My guess is that the encryption/decription software layer is just more intensively interacting with an underlying bug or defect. Could it be a defect in physical memory? A poorly formed system partition? (One of the contributors here made a credible dismissal of that theory.)
I've finally got forwarded to some RMA person who said he'd send me the papers to get a new phone. Unfortunately, that has also taken days of silence now.
Click to expand...
Click to collapse
Please keep us updated when/if OnePlus does follow up on this.
Very frustrating I can't use the OPO with its original ROM, after many years of flashing all kinds of ROMs to anything from Nexus One to my the N5 I went back to until the OPO gets fixed, to several Samsungs, LGs and HTCs and having FCs, some reboots, very stable builds, but never anything like this.
Click to expand...
Click to collapse
We agree. I have had quite a stable of Android devices. But nothing like this coming direct from the manufacturer. I really like the phone when it's running properly. The display could be better in daylight but I could live with that. I suspect that the next OnePlus handset will benefit from lessons in their first release. I just don't want to suffer because I voted for a promising startup.
OnePlus would be wise to humbly acknowledge that there are two widely experienced problems: random reboots and periodic UI freezes. And then if they want to stick around they have to release a ROM that completely eliminates those two showstopper defects.

goattee said:
How long ago did you revert? Did the random reboots stop completely? Or do they just happen less frequently?
Click to expand...
Click to collapse
Last week Wednesday. Until now I have no reboots.

About 12 hours ago I did a clean flash to the official SlimROM 4.44. I followed the instructions on the official website. (I've linked to the site in the previous sentence.)
Immediately the phone seemed to be running smoother. No UI freezing and no random reboots so far. I can't be sure whether simply wiping the partitions solved the problem or whether it was something about 11s. But I like the features of SlimROM well enough that I don't feel the need to test other ROMs yet.
I'll come back here if the problems come back.

goattee said:
About 12 hours ago I did a clean flash to the official SlimROM 4.44. I followed the instructions on the official website. (I've linked to the site in the previous sentence.)
Immediately the phone seemed to be running smoother. No UI freezing and no random reboots so far. I can't be sure whether simply wiping the partitions solved the problem or whether it was something about 11s. But I like the features of SlimROM well enough that I don't feel the need to test other ROMs yet.
I'll come back here if the problems come back.
Click to expand...
Click to collapse
It's the end of the business day. The phone has not caused any problems or surprises. If this phone came out of the box in this new state, I would have been a much happier person for the past three weeks!

Well i've also tried echew010's solution and so far it seems promising! To anyone suffering from random reboots this is what i did: http://forum.xda-developers.com/one...us-one-stock-cm11-t2839870/page5#post59362462

Why my OTA updates installation is so slow?

Hello there, I tried to find an answer to this question but I was not able to!
Pixel XL, Project Fi everything is stock, not rooted and I didn't unlock the bootloader...
The first OTA update (the one with 60 mb) took like an hour to install (I thought that the device was stuck and I restarted it, but after reboot same thing, downloaded the file from scratch and took the same time!)
I got the 7.1.1 notification today, downloaded in no time, but installation took a lot of time!
Step 1 like an hour, and Step 2 still happening and didn't finish yet!! (more than an hour!)
I don't have any problem with the device, running smoothly (except this OTA thing)
Ideas?

Same here, installing the updates took a while. Plugging into power and using WiFi makes it faster but they still take a while.

donslade said:
Same here, installing the updates took a while. Plugging into power and using WiFi makes it faster but they still take a while.
Click to expand...
Click to collapse
so is it normal? the phone didn't finish Step 2 yet!

depending how many apps you have installed it can take a while... but you can use your phone normally....
this is the new feature that preloads your update to be ready for the next update... it eliminates the previous versions "android is upgrading" or "optimizing apps" that used to show up after updates
I'm not sure mine took an hour but I run a very lean set of apps it might have taken an hour from start to finish

Definitely intended to go slow. This is so you don't see any performance issues as you are able to use your phone normally.

Last update took my phone almost 2 hours to complete.

Updates are done differently than before. Remember before how after rebooting you'd have to wait forever for apps to prepare? All of that is now done in advance, kinda. Lots of changes but I think what you're seeing is due to the new way updates are installed. Overall it's a good change but the time delay is now before rebooting but at least the phone is very usable during this period.

That's great guys, thanks for sharing this! I didn't think it will take that much, but it took more than 2 hours!

What is the latest update version for Pixel phones?

7.1.1 with December 5 security updates

Charkatak said:
What is the latest update version for Pixel phones?
Click to expand...
Click to collapse
7.1.1 (NMF26Q)
You don't have to wait for the OTA, just download it when a new version is available.
https://developers.google.com/android/ota#sailfish
Install via: adb sideload

krelvinaz said:
7.1.1 (NMF26Q)
You don't have to wait for the OTA, just download it when a new version is available.
https://developers.google.com/android/ota#sailfish
Install via: adb sideload
Click to expand...
Click to collapse
Is this 7.1.1 (NMF26Q) build for US Pixel phones as well? I read somewhere that this update corrected some LTE issues for EU carrier.

Obviously lies
troy` said:
Definitely intended to go slow. This is so you don't see any performance issues as you are able to use your phone normally.
Click to expand...
Click to collapse
Yes there is something wrong with your phone. Your phone is supposed to update only once with the latest, not go through sequential updates that take forever. If you bought this on eBay, or especially a Chinese seller, It probably has some irremovable malware on it. Do not accept people's answers on the internet as a solution. If it's behaving abnormally and you notice it is behaving abnormally, there IS something wrong with it regardless of what people are saying on the internet because they probably know about this malware but are trying to disguise your symptoms.

AndroidInitiate said:
Yes there is something wrong with your phone. Your phone is supposed to update only once with the latest, not go through sequential updates that take forever. If you bought this on eBay, or especially a Chinese seller, It probably has some irremovable malware on it. Do not accept people's answers on the internet as a solution. If it's behaving abnormally and you notice it is behaving abnormally, there IS something wrong with it regardless of what people are saying on the internet because they probably know about this malware but are trying to disguise your symptoms.
Click to expand...
Click to collapse
Lol. Way to resurrect an old Post... You are delusional. This was the way they worked 2.5 years ago, and it's the way they still do things today. I've continued to use Pixel phones this whole time. 1, 2, and 3. All non XL models. Also, the Earth isn't flat.

troy` said:
Lol. Way to resurrect an old Post... You are delusional. This was the way they worked 2.5 years ago, and it's the way they still do things today. I've continued to use Pixel phones this whole time. 1, 2, and 3. All non XL models. Also, the Earth isn't flat.
Click to expand...
Click to collapse
This is because a malware used to run on android that had been reduced to the size of one pixel on the android screen, making it virtually undetectable to the human eye, hence the name, The Google Pixel. Regardless, it still performs poorly.

Android OS corrupting itself?

Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.

iceman4357 said:
Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.
Click to expand...
Click to collapse
For me this sounds like a hardware failure and I'd try to get the phone replaced.

Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.

dirtyreturn said:
Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.
Click to expand...
Click to collapse
I agree and think it could be hardware. I have Factory reset the phone twice already.

The firmware flash may have become corrupted therefore factory resets are useless.
Flash data has a limited lifespan usually this doesn't become an issue but it can.
Reflash and see if it holds. Otherwise it's likely a memory chipset or mobo failure.

This happened to me. Was running one of the developer previews and chalked it off to that. lost everything I didn't back up the night before (out of habit from messing with my phones I do daily backups of the important folders and phone data). The only thing that worked for me was re-flashing factory image and start fresh. Hasn't happened again for me.,

I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.

EvilRubberDuck said:
I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.
Click to expand...
Click to collapse
For the system to go corrupt by itself is rare unless there's a hardware fault.
More than likely it was 3rd party software that caused it. Launchers, power management apps are prime suspects.
Androids are typically a very stable platform.