Related
Hi,
I'm having trouble with my OpO since I rootet it. Here is the history:
-Day One: Just stock 25R, installed all Apps via google play, no problems whatsoever.
-Update 30O still no problems.
-Then I rootet the phone and flashed TWRP recovery to install the Titanium Backups of my old Nexus 4. Thats when I had the first random reboots. Some while Browsing in Chrome, Some on Youtube, Some while listening Music on Hedphones.
Since I have no Sim-Pincode activated a reboot just means, that I'm Offline for about 20 seconds but having that about 5 times a day just isn't acceptable.
-Then I got the 33R OTA update, which made my root and TWRP recovery disappear because I forgot to make a check in the developper settings, but that did not make the reboots disappear
-Today I flashed the 25R stock Image of the Firmware via Fastboot to set my One to real Factory status. I only installed apps via google play and recovered the app data of 2-3 apps via helium backup without root. I got the two OTA updates, and another reboot.
-Then I rootet the thing again, to use a logcat app, and now I have two logcats ending with a reboot.
I really hope that you can help me since I allready sold my old phone and expect that it will take really long until I get a new OpO here in Germany.
The next thing I will do is flash the 25R Image again and install the apps without using helium at all and leave out the goolors icon pack that I used before. But after that I'm absolutely out of ideas.
UPDATE: Yeah so it's definitely a HW defekt or something I cannot solve. I just wiped everything via TWRP, then flashed the factory image 25R without root and just installed some apps via google play. But after one hour I read an email and it rebooted....
Unfortunately I cant post the links to the logcats due to my low post count.
Logcats don't help you when it comes to finding out what is causing your phone to reboot. It is last_kmsg that is responsible for debugging reboots.
A hardware defect would not be causing your phone to reboot, its something to do with the way your phone is configured / set up.
I would highly recommend you to start from scratch completely and do the following,
- Flash XNPH33R http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed-fastboot.zip from scratch. Make sure you do wipe.
(OR.. flash a custom ROM after wiping)
- List all of the apps that you currently have installed.
- Are you using Xposed?
- Whats your set up? ROM/Kernel/Gapps/etc.
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Ord3r66 said:
I am not using any custom Rom, root, custom kernel or xposed module.
I just wiped everything in TWRP and flashed the 25R factory image. After about one hour of installing apps in Google play and loging into account i got the first reboot.
I can try flashing the image that you postet tomorrow but thats the same Rom that Im using now
Click to expand...
Click to collapse
I meant, you can try a custom ROM and see if you can reproduce the problem. Custom ROMs are running on code that is much newer than CM11S.
Ensure you're on XNPH33R when it comes to OTAs.
I just wanted to add my frightful experience. I've had the OPO for two weeks now without problems and no random reboots. Had my first reboot today and just now my phone powered off and wouldn't turn back on. I plugged it back into the wall charger and it turned itself back on but was stuck on the boot logo. I tried holding down the power button to turn it off but nothing. Pressing the power button only turned the display on and off but still stuck on boot logo. Eventually I held down the power button and volume down and the phone buzzed and went to recovery. I'm on stock 33R and Franco's kernel. Haven't tweaked anything. Now I'm afraid my phone is going to brick itself.
Sent from my A0001
Yeah so this is definitely getting worse. At first I had 1-2 reboots a day but today after unplugging I already had 3 reboots in one hour.
I think I am definitely going to send it back when I'm back home next Week.
I already flashed stock Firmware 3 times and did what feels like 10 full wipes in one Week.
This cant be normal. Apps that I installed that arent in the top 50 in the play store are: Dailyme, yatse for xbmc, line, Wolfram aplha and ogyoutube.
That really sucks. I already sold my nexus 4 and have no other phone left
Btw: I'm on 33R for the third time this Werk. Everytime via OTA
Try a different Rom like crDroid + AK Kernel. Running this 2 things since 2 weeks and i only got one reboot just because my camera stopped working because in undervolted my phone ^^
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Ord3r66 said:
THX but I just want a functioning phone. And since I have errors that nobody else has I think that it is a Hardware issue. At the Moment I am waiting for a answer from one plus so i can send it back
Click to expand...
Click to collapse
ok I understand your frustration but to fully test your phone you will need to run stock and stock only with no outside apps loaded. Try and do this for a day or half a day or so and see what your results may be. Its your phone and of course do what you like but testing your phone and doing the same thing every time as in reloading your apps is not a good way of fully testing.
also did you do a last_kmsg report as recommended.
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
Yes you need root. After a reboot just pull the last_kmsg file from /proc/ using adb, file Explorer of your choice, etc.
Sent from my One A0001 using Tapatalk
Ord3r66 said:
Okay will do that. Is there a tutorial to do a last_kmsg report? Do i need root?
Click to expand...
Click to collapse
of course there is a tutorial there is a tutorial for everything.... Got to utilize google my friend.
OKay it's me again. Meanwhile the Oneplus support answered my mails and told me to flash custom Kernels to resolve the issue.
Since Yesterday I tried three Kernels (Franco, Heeroluca and AK) and nothing changed, so now I start to gather some Last_kmsg files name it after the APP where the reboot occured and upload it here. Ofcourse I'm also sending those files to the Oneplus Support
Here is the first one:
https://dl.dropboxusercontent.com/u/43103242/1_Line_Messenger_last_kmsg
https://dl.dropboxusercontent.com/u/43103242/2_standby_screenoff_last_kmsg
Have the same problem. Using wi-fi -> reboot. Don't know how to fix this defect. I hope a solution will be found
Had a random reboot while browsing chrome. I was scrolling down the page and received a text at the same time when my screen froze. After freezing for a few seconds, it rebooted itself. I tried getting the last_kmsg but it tells me that it isn't found. The code I used was: "su" followed with "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" in terminal emulator. Let me know if there is anything else I can do. Thanks!
I have also problems with chome beta browser. I get freezes. Is this issus only with chrome or with all browers?
Gesendet von meinem A0001 mit Tapatalk
Hi,
I just flashed my device with the new Android 5.0 stock image, only now i have multiple problems:
* mic doesn't work (i noticed since ok google detection setup doesn't work)
* no sound
* a lot of UI hangs/ crashes
* YouTube video's wont play
* calling doesn't work.
i already reflashed it multiple times, problems still persist.
i wiped my device before i flashed so i didn't dirty flash, and flashed all the .img separately.
Can anyone help me with this?
Update:
flashing this one with TWRP worked for me:
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Multiple Android 5.0 problems on Nexus 5
I can't really help you much, but I wanted to express the fact that I also flashed the stock firmware image of Lollipop into my Nexus 5 and I am
experiencing a plethora of issues: Besides the ones you mention, please add CAMERA not working, show distorted image on screen, both back and frontal camera.
Shame on Google to release such a buggy and crappy firmware.... Truly expected it to be pristing.
On the other hand, have had on my other Nexus, a 4, the port of Android L and AOSP Android 5.0, pretty much flawless.... just barely minor issues...
_davidd_ said:
Hi,
I just flashed my device with the new Android 5.0 stock image, only now i have multiple problems:
* mic doesn't work (i noticed since ok google detection setup doesn't work)
* no sound
* a lot of UI hangs/ crashes
* YouTube video's wont play
* calling doesn't work.
i already reflashed it multiple times, problems still persist.
i wiped my device before i flashed so i didn't dirty flash, and flashed all the .img separately.
Can anyone help me with this?
Click to expand...
Click to collapse
There are issues:
- Battery dies in 4 hours. Battery stats aren't even refreshing to find out what is causing it. Phone is hot and eats like 1% in few mins. It actually discharges faster than I can charge! GSam battery monitor says it's Exchange Services that is eating all battery.
- Smart Lock loses connection to Windows 8.1 laptop
- Unable to unlock device, screen shuts down after you type in unlock PIN, after few retries it works
piensa said:
I can't really help you much, but I wanted to express the fact that I also flashed the stock firmware image of Lollipop into my Nexus 5 and I am
experiencing a plethora of issues: Besides the ones you mention, please add CAMERA not working, show distorted image on screen, both back and frontal camera.
Shame on Google to release such a buggy and crappy firmware.... Truly expected it to be pristing.
On the other hand, have had on my other Nexus, a 4, the port of Android L and AOSP Android 5.0, pretty much flawless.... just barely minor issues...
Click to expand...
Click to collapse
It's not crappy as I have no issues at all but that's not to say there are a few bugs here and there but mostly graphical bugs really. Functionality is flawless on my N5
Not even encountered a single crash, 8 hrs+ since installed. I wiped everything and didn't restore any apps. All freshly installed.
No solution I'm afraid, but just to let you know that I'm having exactly the same problem with the Microphone... so no phone calls, voice search etc. Just doesn't pick up any sound.
i reflashed the developer preview for now, that one does work without any problems (only the battery drain bug)
What method did you use to flash. Through a tool kit or by fastboot
i used fastboot, also tried it with a toolkit, both same result.
_davidd_ said:
i used fastboot, also tried it with a toolkit, both same result.
Click to expand...
Click to collapse
Failing that then you could flash this?:
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Oh hell... that's... so embarrasing.
I have a Pressy.... I forgot I had it plugged in.... for some reason Lollipop saw it as a heaphone and mic.
I'm gonna just go sit in the corner now.
Guys, here's a thought - as it's a new base perhaps doing a FULL RESET is the way forward
I always do a complete reset and flash from fastboot (not bloody toolkits) and never have any issues so I'm going to assume everyone with issues isn't wiping the phone first (I know the OP says they did a full wipe but in general, most don't)
Thinking this was a problem with the factory images... Didn't make any sense at all.
DirkGently said:
Failing that then you could flash this?:
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Just flashed it, works great now! thanks
EddyOS said:
Guys, here's a thought - as it's a new base perhaps doing a FULL RESET is the way forward
I always do a complete reset and flash from fastboot (not bloody toolkits) and never have any issues so I'm going to assume everyone with issues isn't wiping the phone first (I know the OP says they did a full wipe but in general, most don't)
Click to expand...
Click to collapse
i did a full reset multiple times, so that isn't the problem for me.
EddyOS said:
Guys, here's a thought - as it's a new base perhaps doing a FULL RESET is the way forward
I always do a complete reset and flash from fastboot (not bloody toolkits) and never have any issues so I'm going to assume everyone with issues isn't wiping the phone first (I know the OP says they did a full wipe but in general, most don't)
Click to expand...
Click to collapse
You mean factory reset??? After all is done?
Imranhakro said:
You mean factory reset??? After all is done?
Click to expand...
Click to collapse
No, after you've flashed all the images, go into the stock recovery and do a factory reset and then allow it to boot up and set the phone up as normal!
DirkGently said:
Failing that then you could flash this?:
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
This worked for OP but I just tried to flash this image and it did not work. Still no MIC SOUND. THis all happened After I flashed Xtrasmooth ROM from the xda dev section. Man this is depressing, is there anything else I can try ? I did a full wipe prior to installing it. Phone does not pick any sound. Only pick sounds during call in speakerphone mode....
I notice a lot of people having issues with the stock image. Flash the custom Roms...they seem to be working MUCH better..
Sent from my Nexus 5 using xda premium
_davidd_ said:
Hi,
I just flashed my device with the new Android 5.0 stock image, only now i have multiple problems:
* mic doesn't work (i noticed since ok google detection setup doesn't work)
* no sound
* a lot of UI hangs/ crashes
* YouTube video's wont play
* calling doesn't work.
i already reflashed it multiple times, problems still persist.
i wiped my device before i flashed so i didn't dirty flash, and flashed all the .img separately.
Can anyone help me with this?
Update:
flashing this one with TWRP worked for me:
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Did you erase and flash userdata.img also during the flash, because i have none of your problems mate after a clean flash-all install.
Yes, i did erase and flash userdata.img, multiple times.
G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app
bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)
UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective
UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)
Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.
UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.
UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).
hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?
My opo fell in water so its screen was not working. My father gave it to a mobile repair shop who repaired it for 4k. When he checked the phone everything seemed alright.He was able to call me etc etc. Then he couriered me the phone. When I got It... It had cos13 latest version. I checked everything except calling. Then I rooted my phone. Flashed oreo. I inserted my sim. It was able to detect that it was an idea sim and import contacts from it but it showed no service. I thought it was the rom. I flashed Tugapower N49. Same problem. So I thought restoring it to stock might solve the problem. Used oneplus one recovery tool to restore it to 4.4 . Still the same problem. It can detect the sim but can not catch any signal. I check my Imei number. Its still there. But I was not able to run the ping test. Then I thought of using this phone for checking roms only and use my Lumia(I hate Lumia) for calling. Rooted it again. Flashed oreo. Flashed its gapps. It show installation complete but its stuck there...... Waited for half an hour. Forced restart. oreo opened but It was nt factory reset although I had wiped it and it shut down after some time. after that my phone reached the android screen only and cant proceed further. I thought maybe force closing my phone during gapps installation did this. Tried to install tuga power.. error executing update binary. Had one more nougat rom. Installed it. Again it didn't show that starting google screen which u see when ever u open a new phone. Basically It was again not factory reset, Wiped everything except system. still this happened. Returned back to stock using recovery tool. Now I tried to install multirom so that I can install the oreo rom. after rooting multirom wasn't able to download anything. Downloaded it manualy. Flashed multirom twrp using fastboot. opened recovery . Not working. phone rebooting. Flashed the previous recovery which I was using before multirom one, That one is working properly!!! What is wrong with my phone???!!!!!
Ritvikx1998 said:
My opo fell in water so its screen was not working. My father gave it to a mobile repair shop who repaired it for 4k. When he checked the phone everything seemed alright.He was able to call me etc etc. Then he couriered me the phone. When I got It... It had cos13 latest version. I checked everything except calling. Then I rooted my phone. Flashed oreo. I inserted my sim. It was able to detect that it was an idea sim and import contacts from it but it showed no service. I thought it was the rom. I flashed Tugapower N49. Same problem. So I thought restoring it to stock might solve the problem. Used oneplus one recovery tool to restore it to 4.4 . Still the same problem. It can detect the sim but can not catch any signal. I check my Imei number. Its still there. But I was not able to run the ping test. Then I thought of using this phone for checking roms only and use my Lumia(I hate Lumia) for calling. Rooted it again. Flashed oreo. Flashed its gapps. It show installation complete but its stuck there...... Waited for half an hour. Forced restart. oreo opened but It was nt factory reset although I had wiped it and it shut down after some time. after that my phone reached the android screen only and cant proceed further. I thought maybe force closing my phone during gapps installation did this. Tried to install tuga power.. error executing update binary. Had one more nougat rom. Installed it. Again it didn't show that starting google screen which u see when ever u open a new phone. Basically It was again not factory reset, Wiped everything except system. still this happened. Returned back to stock using recovery tool. Now I tried to install multirom so that I can install the oreo rom. after rooting multirom wasn't able to download anything. Downloaded it manualy. Flashed multirom twrp using fastboot. opened recovery . Not working. phone rebooting. Flashed the previous recovery which I was using before multirom one, That one is working properly!!! What is wrong with my phone???!!!!!
Click to expand...
Click to collapse
I understand the frustation,but two threads on same topic gonna make any good?
From what I can see,you basically messed up.
You need this:https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Mr.Ak said:
I understand the frustation,but two threads on same topic gonna make any good?
From what I can see,you basically messed up.
You need this:https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
Thanks.. it worked..my still the Sim problem persists. My
Imei number is still there.. whenever i insert my idea sim it recognizes it but shows no service. I can import contact from sims. If i goto mobile networks and search for connection it displays error.I tried changing apn too. Also running the ping test displayed error.
Ritvikx1998 said:
Thanks.. it worked..my still the Sim problem persists. My
Imei number is still there.. whenever i insert my idea sim it recognizes it but shows no service. I can import contact from sims. If i goto mobile networks and search for connection it displays error.I tried changing apn too. Also running the ping test displayed error.
Click to expand...
Click to collapse
What does it say in baseband in about phone?
Mr.Ak said:
What does it say in baseband in about phone?
Click to expand...
Click to collapse
Screenshot
Ritvikx1998 said:
Screenshot
Click to expand...
Click to collapse
Okay,so both baseband and imei are there and still network doesn't work.Did you try using carriers other than idea?
Mr.Ak said:
I understand the frustation,but two threads on same topic gonna make any good?
From what I can see,you basically messed up.
You need this:https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
Mr.Ak said:
Okay,so both baseband and imei are there and still network doesn't work.Did you try using carriers other than idea?
Click to expand...
Click to collapse
Yeah
Ritvikx1998 said:
Yeah
Click to expand...
Click to collapse
It must be something with the hardware then.You've to disassemble your device and check if network antenna's broken.Follow the tutorial on YouTube.
Has anyone else had any of these problems with their oneplus 6?
-files disappear after each reboot
-keyboard stops functioning on lock screen and I can't unlock the device
-apps randomly losing their data such as Snapchat/Instagram and I have to log back in
-can't use any other keyboard with a password since the device comes encrypted. My s7 used default keyboard before being decrypted.
I have factory reset at least 3-4 times since I have owned the device.
Oneplus customer support said in regards to my files being randomly deleted, "You should just backup your stuff with google drive". Is that really the solution? Just expect my files to be erased and have to recover from backup after each reboot? Most of the customer support people never understand my problems that I am trying to tell them and I can hardly understand them either. Sorry for ranting a bit. I was excited to get rid of my galaxy s7 and try something new that I was told has good rom support and little no bloat on stock ROM, but I've been very disappointed. I guess after seeing their customer support is partnered with Acer it makes sense.
Try a factory reset. I haven't heard anyone report such issues on OP6 before. If it still doesn't work after a factory reset, I would look for a warranty replacement
Pat123 said:
Try a factory reset. I haven't heard anyone report such issues on OP6 before. If it still doesn't work after a factory reset, I would look for a warranty replacement
Click to expand...
Click to collapse
I've factory reset 3-4 times and still have the same issues. Corrupted ROM perhaps? I have seen a few people on one plus forums talk about how their files are being deleted, but those threads disappear magically. I talked to two people today who have the same issue.
user9340 said:
I've factory reset 3-4 times and still have the same issues. Corrupted ROM perhaps? I have seen a few people on one plus forums talk about how their files are being deleted, but those threads disappear magically. I talked to two people today who have the same issue.
Click to expand...
Click to collapse
I've been using it for almost a week with 0 issues... It's probably a faulty unit you're having, make sure it's running the latest 5.1.8 software.
Try installing a custom rom and see if it sorts things out
ramqashou said:
I've been using it for almost a week with 0 issues... It's probably a faulty unit you're having, make sure it's running the latest 5.1.8 software.
Try installing a custom rom and see if it sorts things out
Click to expand...
Click to collapse
Yeah I always do the updates. I started having issues after I updated. Particularly the no keyboard on lock screen happened two updates ago.
Save method: send it back, claim warranty; do it yourself method: https://forums.oneplus.com/threads/oneplus-6-oxygenos-5-1-8-official-download-links.836441/
Download full zip and flash it via system update
which files is it deleting and from what directory? never had any issues, really think a fresh install is best way, start over and don't do any fancy crap at first (root, etc). Root I used to do to every phone, fight and cuss it out because I was not careful, now I never ever root and I'm much happier
jabbermacy said:
which files is it deleting and from what directory? never had any issues, really think a fresh install is best way, start over and don't do any fancy crap at first (root, etc). Root I used to do to every phone, fight and cuss it out because I was not careful, now I never ever root and I'm much happier
Click to expand...
Click to collapse
DCIM, Downloads, whatever directory downloaded Spotify music goes to, Some screenshots would disappear, but not all. I turned on logs and am going to give it another week or so.
Lightbird said:
Save method: send it back, claim warranty; do it yourself method: https://forums.oneplus.com/threads/oneplus-6-oxygenos-5-1-8-official-download-links.836441/
Download full zip and flash it via system update
Click to expand...
Click to collapse
Should I just switch to Android P?
P is still beta with lots of bugs. Some have said it's stable enough for a daily driver but ymmv.
user9340 said:
Should I just switch to Android P?
Click to expand...
Click to collapse
No, too many bugs
user9340 said:
Yeah I always do the updates. I started having issues after I updated. Particularly the no keyboard on lock screen happened two updates ago.
Click to expand...
Click to collapse
It's possible you had a bad flash or bad download. Download a fresh copy of 5.1.8, check the MD5, and install from the system updater (not twrp). If the problems persist, you may have a faulty unit. In nearly a month, I haven't had any of the problems you describe.
iElvis said:
It's possible you had a bad flash or bad download. Download a fresh copy of 5.1.8, check the MD5, and install from the system updater (not twrp). If the problems persist, you may have a faulty unit. In nearly a month, I haven't had any of the problems you describe.
Click to expand...
Click to collapse
I think I just realized I may have done reset system settings instead of factory reset.