Got two brand new OnePlus two's a day apart probably from the same batch.
On first launch it always got stuck on the checking connection
Tried both with
Vodafone lte
EE lte
bt hotspot
Vodafone hotspot
Multiple restarts did nothing
My guess was that some initialisation step happened at the factory and something funky was in the cache or data so I factory reset both devices (one day apart) and that solved it for me.
. After the reset and booting up it ran the updating android process which it did not before and then it worked flawlessly connecting to the networks
Hope this helps anyone and hope OnePlus fix this!
Got that as well when I received my Oneplus Two yesterday. I solved it by skipping that step, after that Internet worked flawlessly. After I updated to Oxygen OS 2.0.2 and unlocking the bootloader, the problem was gone completely.
Yep
dansou901 said:
Got that as well when I received my Oneplus Two yesterday. I solved it by skipping that step, after that Internet worked flawlessly. After I updated to Oxygen OS 2.0.2 and unlocking the bootloader, the problem was gone completely.
Click to expand...
Click to collapse
Same.
Sent from my OnePlus 2 using Tapatalk
Theshawty said:
Same.
Sent from my OnePlus 2 using Tapatalk
Click to expand...
Click to collapse
My guess is that unlocking the bootloader ran the factory reset. Maybe the problem was on 2.0.1 builds
Let's see when people get the next batch with 2.0.2 preinstalled
It's annoying because for non tech people like my fiance it would have been a straight send back to factory if I wasn't around lol
LOGMD said:
My guess is that unlocking the bootloader ran the factory reset. Maybe the problem was on 2.0.1 builds
Let's see when people get the next batch with 2.0.2 preinstalled
It's annoying because for non tech people like my fiance it would have been a straight send back to factory if I wasn't around lol
Click to expand...
Click to collapse
Unlocking the bootloader wipes the entire data partition.
Yeah, I'm willing to bet .02 fixed it.
Sent from my OnePlus 2 using Tapatalk
My OP2 is from de 4th of september batch, i´m from Portugal and had the same problem! Resolved after the bootloader unlock.
I had this problem, skipped that step, updated to 2.0.2 and did a factory reset.
It was virgin again and ran flawlessly without this error.
So this was a 2.0.1 bug.
Same for me, skipped and everything went smooth.
Related
Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!
I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset
I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.
i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?
same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4
This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse
EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.
Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.
Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
could try reinstalling the factory image but if you havent messed with anything on the phone maybe its a hardware issue... i dont know
If the bootloader is still locked, i would definitely go through the replacement hassle. Should have no issues whatever after only 3 months and 100% stock.
DejektedZ76 said:
Hi guys,
So I had been using my Moto X Pure (3 months approx) and it had been perfectly fine. Except just a couple of days ago while I was on snapchat the phone suddenly shut down. While I tried to restart the phone it got stuck on the boot screen and didn't go past that. I initially tried to wipe cache partition & factory reset but nothing happened, it was still getting stuck on the boot screen.
My phone is unrooted and I haven't tried experimenting with the kernel or anything, mind you.
I left it alone for a couple of days and it started to boot up again, it was working perfectly, no issues whatsoever. But just yesterday the same situation occurred yet again :/ not while I was using snapchat but I unlocked the phone but the screen didn't turn on and it restarted by itself and got stuck onto boot screen again.
Is this an issue with the software or the hardware?
I talked to Motorola and they said they will issue a replacement phone, but I live overseas so it could be a hassle. Should I just send it in for replacement or try and reinstall the rom using factory image?
Thanks guys, really appreciate your help
Click to expand...
Click to collapse
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
bmeek said:
Have you tried a simple factory reset? Basically a data wipe?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, tried a factory wipe and cleared cache but didn't seem to work.
DejektedZ76 said:
Yes, tried a factory wipe and cleared cache but didn't seem to work.
Click to expand...
Click to collapse
Yeah - I haven't heard of stock unrooted phones getting their system image corrupted such that a reset doesn't get back to proper "stock". Maybe a botched OTA, but if you've got that warranty option, probably be wise to take it.
I don't know this phone and Motorola well enough to say that unlocking your bootloader and starting from scratch, as I would be sorely tempted to do in your situation, won't void your warranty option.
Sent from my One using Tapatalk
USA user of Russian version yotaphone 2. Got notified three days ago of the 1.1.124 update but every time I tried the phone would reboot, fail to update, reboot back to android and re-download the update to try again. I made a video of what it did. After two days of trying and an unanswered tweet and support email later it magically corrected itself.
https://youtu.be/kG4tyuoOq0M
I did try copying the update from cache and sideloading. I'm rooted but with stock recovery. Recovery at least gave me a better understanding of what could have happened. Seems there was a problem with the zip. Apparently there was a problem with ALL of them since I re-downloaded it about 8 times before it worked!
I post this here as a reference.
Sent from my YD201 using Tapatalk
UK user of the same. Tried the OTA but was still on TWRP, didn't work. Then flashed stock recovery. Now it downloads, and that's kind of it: I press 'restart & install', it count down to restart then just switches to prior screen saying "your system is up to date". Going to try pulling it from the cache and adb sideload weh I get a chance.
How'd the sideloading go?
Sent from my YD201 using Tapatalk
radbme said:
How'd the sideloading go?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Any decent new features / battery improvements?
Just updating to say have got a new phone. Loved the Yota for the first year and it's use when outside is outstanding but have spent far too long trying to update and fix things, it doesn't really last more than a month without getting intolerably slow so I've upgraded. Might get around to sorting the Yota out but probably more likely to just reset it and save it for sunny days reading in the park or summit.
Hi all. Coming from a Nexus 6 with a click and forget it tool I am quite spoiled. With the PH-1 there seems to be conflicting information out there. I had my bootloader unlocked and rooted via Magisk running stock 7.1.1
Then, I signed up for the 8.1 Beta OTA update. That downloaded and installed without incident. Running fine right now. Calls and texts on Verizon worked fine and then I joined my WiFi network.
I was pretty surprised that installing 8.1 did NOT wipe my phone or even do a factory reset. Anyone else out there running the OTA update? Any issues? Should I do a factory reset?
I have seen posts explicitly stating to NOT re-lock the bootloader. And advice on that?
The real reason that I took the update was because my PH-1 had suddenly been acting badly. Freezing, rebooting etc. I was really wanting a fresh start which this did not give me. Just wondering how far I should go. If I should lock bootloader, kill root, factory resset? Some or none of the above?
If it works great, don't touch it.
Sent from my PH-1 using XDA Labs
chiadrum said:
Hi all. Coming from a Nexus 6 with a click and forget it tool I am quite spoiled. With the PH-1 there seems to be conflicting information out there. I had my bootloader unlocked and rooted via Magisk running stock 7.1.1
Then, I signed up for the 8.1 Beta OTA update. That downloaded and installed without incident. Running fine right now. Calls and texts on Verizon worked fine and then I joined my WiFi network.
I was pretty surprised that installing 8.1 did NOT wipe my phone or even do a factory reset. Anyone else out there running the OTA update? Any issues? Should I do a factory reset?
I have seen posts explicitly stating to NOT re-lock the bootloader. And advice on that?
The real reason that I took the update was because my PH-1 had suddenly been acting badly. Freezing, rebooting etc. I was really wanting a fresh start which this did not give me. Just wondering how far I should go. If I should lock bootloader, kill root, factory resset? Some or none of the above?
Click to expand...
Click to collapse
If the boot loader is unlocked.
Install Magisk to root it and hide the unlocked BL status so you can use Google Pay.
Don't lock anything.
I decided to try out the new BETA OS for my 6T and it worked great for a while. Today my screen suddenly began to turn off for no reason and it brings be back to the PIN screen over and over again. I tried to go back to stable ROM by wiping the phone via recovery and then installing the latest stable OS via local upgrade in the settings menu but when the phone restarts it still says its the BETA os in the phone status screen. Plus the problem still persists.
Does anyone know how to get the stable OS back on the phone once you've flashed the BETA?
I am interested too.
Sent from my ONEPLUS A6013 using Tapatalk
I had the same issue. I wiped data and cache and set the phone as new again. Seems like the issue has resolved itself. No more reboots or pin required screen.
himmatwala said:
I had the same issue. I wiped data and cache and set the phone as new again. Seems like the issue has resolved itself. No more reboots or pin required screen.
Click to expand...
Click to collapse
I had the same issue and confirm that a wipe resolve. But after two days i got the same problem again. So i decided to revert back to stable but the bootloader options for load flash from storage does not appear. Any ideas?
Max
That worries me, I'm on Beta-1, phone not acting so stable anymore, and I believe you are doing the exact procedure on how to go back to stock.
Here we go, that's what I'm doing right now : https://forum.xda-developers.com/sho....php?t=3862516
Edit: It worked, took a few steps (unlock, flash-all, oem lock) but I'm off of beta and back on 9.0.10
Can you explain to me every step? How can I go back to the stable version?
zSh4dow_Runn3r said:
Can you explain to me every step? How can I go back to the stable version?
Click to expand...
Click to collapse
Have you tried updating to beta 2 first?
Sent from my crosshatch using XDA Labs
Yes I did, now I'm on open beta 2