Database Info

Nexus S Not Connecting to Network on Reboot

My dad's Nexus S keeps disconnecting from Wind and will NOT automatically reconnect to Wind. I've set it to Automatic. On top of this, *every* time I enable Wifi or Bluetooth on his device, his Wind connection drops and remains dropped until I manually reconnect.
The only way around this issue is if I manually select Wind's network in the settings menu, thereby avoiding 'Select automatically'. The problem here is that when the phone needs a reboot, it doesnt remember the last network and it needs to be manually selected *again*.
I've done a quick search via Google and there are others having the same/similar problem;
http://www.google.ca/support/forum/p/Google+Mobile/thread?tid=34411ac78e8a4ff6&hl=en
Apparently the 2.3.6 update doesn't fix this either. Is there a 2.3.7 release? I'm even thinking of rooting and flashing the phone to use a custom ROM (MIUI, its much cleaner with better shortcuts which my dad would like).
Does anyone know of a solution to this? I'm thinking of going into Wind and having it replaced (its less than a week old). Question is, if he's racked up more than 30 minutes, can he still get a straight exchange for the phone? Would it still be eligible for exchange/replacement if I tried the ICS update to the phone?

Did you guys root the phone? Ans if you did, did you installed custom rom? If so, it just might be the incompatibility with the Nexus S. If you didn't root it, the phone just might be defected. Try updating the os. It always doesn't hurt to update os. If that doesn't work, I guess you should return it and get the new one it somethign :/
Sent from my Nexus S using XDA App

At the minimum, I would try updating to 2.3.6.

Yeah try to update to newer os. And if that doesn't work, I guess you should exchange your phone or something??
Sent from my Nexus S using XDA App

kyokeun1234 said:
Did you guys root the phone? Ans if you did, did you installed custom rom? If so, it just might be the incompatibility with the Nexus S. If you didn't root it, the phone just might be defected. Try updating the os. It always doesn't hurt to update os. If that doesn't work, I guess you should return it and get the new one it somethign :/
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I've updated my original question with more details.
But no, its not a rooted phone. Everything is stock Android 2.3.4. The phone is only about 5 days old, we got it for him on the 27th of December (or 26th, cant remember). I have installed a few applications (cnn news, wp.pl, bbc news, unit converter, etc). I've updated all the applications as well.
How can I obtain 2.3.6 and install it? Is the process difficult and would it render the phone non-returnable to his carrier for fixing/replacing?

If you have stock, the process is easy was snap if there's a avaliable ota update to your phone. Go to setting-about phone-system update (I'm pretty sure) and if there's an update for your phone, you can download and install the new rom from there.
Sent from my Nexus S using XDA App

kyokeun1234 said:
If you have stock, the process is easy was snap if there's a avaliable ota update to your phone. Go to setting-about phone-system update (I'm pretty sure) and if there's an update for your phone, you can download and install the new rom from there.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Will it give me the option to update to Iced Cream Sandwich Android 4.0 as well?

Um probably not. Depends on what model you're using. It probably promt you to update to later version of gingerbread :/
Sent from my Nexus S using XDA App

Hi, I have the exact same problem as the original poster, except worse.
I lose my data connection when I turn on wifi, or after I reboot my phone. And once I lose the connection, I have to power off and take out the battery for it to work again. My phone was already rooted when this problem start about 4 days ago, was using stock rom (2.3.6) I downloaded for my I9020T (don't ask, minor hiccup when I was rooting my phone...)
So far I've tried the following:
1. boot to CWM recovery -> factory reset, wipe cache, unsuccessful
2. *#*#4636#*#*, changed preferred network to WCMDA preferred or only, unsuccessful (I also had issues with sending SMS, so I also updated the SMSC, which is 07916174080001f6 for Mobilicity in Canada). Also selected "Automatic" in "Select radio band".
3. I flashed the OS to cyanogen, still same problem.
4. In mobile settings, tried changing apn, toggle data connection, 2g/3g, "Select automatically", doesn't work.
5. a whole bunch of other voodoo I found on the web, but none worked.
The only thing I haven't tried yet is flashing with a stock sbf, because I can't seem to be able to find one.
The error message I see in *#*#4636#*# -> Phone info is something like DcInactiveConnection...: unknown data error (sorry can't remember the whole thing).
Also tried asking mobilicity to refresh my service, but that also didn't help.
I ran logcat in terminal emulator and searched through the log for "error" or anything suspicious, the only thing I saw were these,
1. Error loading keycharmap file '/system/usr/keychars/herring-keypad.kcm.bin'
2. caused by: java.net.SocketTimeoutException: Connection timed out
I/TelephonyRegistry( 188): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=apnSwitched interfaceName=null networkType=3
I/TelephonyRegistry
3. onErrorResponse: Failed to send 5 events because of [com.android.volley.TimeoutError]
D/Volley
Tried googling all of them but didn't find anything useful.
I've been at this for the past 4 days and still haven't been able to fix this. I tried swapping in another mobilicity sim card and it also had the same behaviour, so it's definitely something with my phone.
Also, after I power down and remove the battery and power it back up again, the connection still doesn't come back automatically, but I have to toggle the airplane mode to get it to connect.
At this point, what else can/should I try? Or should I just ask them to send it for warranty?
Any help/advice will be VERY much appreciated!!!! And apologies for the essay.
Thanks!

NM, I reread your post. I have nothing for you. Sorry.

Weird lag issue

I just picked up a bad esn sprint phone. Its pure stock, locked bootloader and all. I did a couple factory resets. And cant for the life of me figure out whats causing the lag. For a minute or two after boot its tolerable app drawer speed but whenever I open something (any app at all) it will hang anywhere from 5-30 seconds. Then once the app opens it will hang up again. Sometimes popping up the not responding wait or force close box. I hit wait and almost instantly its useable but laggy. Anyone have any ideas
Sent from my SPH-D710 using XDA Premium 4 mobile app

31ken31 said:
I just picked up a bad esn sprint phone. Its pure stock, locked bootloader and all. I did a couple factory resets. And cant for the life of me figure out whats causing the lag. For a minute or two after boot its tolerable app drawer speed but whenever I open something (any app at all) it will hang anywhere from 5-30 seconds. Then once the app opens it will hang up again. Sometimes popping up the not responding wait or force close box. I hit wait and almost instantly its useable but laggy. Anyone have any ideas.
Android 4.1.2
Build JZO54K
Baseband D720SPRLF2
Screwed edit up sorry for double post
Edit: im running a hardware monitor and its pretty much running at 1000mzh constantly. This is after a fresh reboot no additional apps started.
Click to expand...
Click to collapse

No ideas? I've been googling since starting thread found emmc bug info. Appears this phone doesn't have it. So far 7 minuted to get this much typed.
Sent from my Nexus S 4G using XDA Free mobile app

31ken31 said:
No ideas? I've been googling since starting thread found emmc bug info. Appears this phone doesn't have it. So far 7 minuted to get this much typed.
Sent from my Nexus S 4G using XDA Free mobile app
Click to expand...
Click to collapse
Backup your stuff. Unlock bootloader. Flash factory image. Report back if it solves the problem.

smit.sanghavi said:
Backup your stuff. Unlock bootloader. Flash factory image. Report back if it solves the problem.
Click to expand...
Click to collapse
No working pc at the moment. And why should you need to reflash the image on a factory unrooted device. It seems after i clear memory with clean master it speeds right up again for 15-20 minutes. It gets down to 11% available memory. I don't have really anything installed except xda and some tools. My hope for this phone is to try and learn how to port a ROM and want this phone to run smooth pure stock before i start so if it has a lag when i port i will know its my fault. And when flashing stock image can i downgrade without any issues
Sent from my Nexus S 4G using XDA Free mobile app

31ken31 said:
No working pc at the moment. And why should you need to reflash the image on a factory unrooted device. It seems after i clear memory with clean master it speeds right up again for 15-20 minutes. It gets down to 11% available memory. I don't have really anything installed except xda and some tools. My hope for this phone is to try and learn how to port a ROM and want this phone to run smooth pure stock before i start so if it has a lag when i port i will know its my fault. And when flashing stock image can i downgrade without any issues
Sent from my Nexus S 4G using XDA Free mobile app
Click to expand...
Click to collapse
Factory images are one of the best sources to start afresh. Flashing a factory image (4.1.2 in this case) will wipe EVERYTHING and you will be able check if the lag is still present.
And since, you are working on porting a new ROM which I thing is > 4.1.2, you will not face any downgrading issues.

[Q] About this newly introduced wifi problem

Hello guys,
my brand new nexus 5 just came back from replacement and worked flawlessly for a week or two,
The thing it that after the update, i had this strange "Stuck at turning wifi on bug".
I tried everything i saw on all the forums i managed to find and google usually tell users to replace their devices.
The thing is i just flashed the radio-hammerhead-M8974A-1.0.25.0.17 Radio, and at reboot i was able to turn wifi on.
The main problem now is, that the device freeze 15 second after succefully showing me nearby wifi networks, and then proceed to reboot.
I think many users are in the same situation, has someone managed, somehow, to patch the error ? I can't even tell if this is a software or hardware related glitch, but more and more users are experiencing troubles and i think google should talk more about it.

The majority of users don't have this problem. I don't. What else have you done to the device? What have you flashed?
Sent from my Nexus 5 using XDA Free mobile app

no such issues here.

I've seen this issue on various phones and it's always been either:
1) Dodgy /data (user data, apps etc)
2) Hardware problem.
I have not had this issue on the N5

jd1639 said:
The majority of users don't have this problem. I don't. What else have you done to the device? What have you flashed?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Of course i did not mean that all users where on the same case,
what i said, is that i already found many thread of people experiencing the same "undefined behaviour", which mean this is not a random bug, and that it can definitly happen to anybody's device.
My phone was using the last stock rom, the bootloader was locked and it never was altered in any ways when the problem started to appear.
Then, i did a hardreset, i unlocked the bootloader, i flashed custom roms (PA, MIUI, CYANNOGEN), then i flashed an older rom's radio image and the wifi started to activate again, but to reboot 15 sec after.
then i went back to a PA rom, and exactly the same bug occur.

weacd said:
Of course i did not mean that all users where on the same case,
what i said, is that i already found many thread of people experiencing the same "undefined behaviour", which mean this is not a random bug, and that it can definitly happen to anybody's device.
My phone was using the last stock rom, the bootloader was locked and it never was altered in any ways when the problem started to appear.
Then, i did a hardreset, i unlocked the bootloader, i flashed custom roms (PA, MIUI, CYANNOGEN), then i flashed an older rom's radio image and the wifi started to activate again, but to reboot 15 sec after.
then i went back to a PA rom, and exactly the same bug occur.
Click to expand...
Click to collapse
Flash a full factory image back to latest stock. If it still happens, send it for repair

rootSU said:
Flash a full factory image back to latest stock. If it still happens, send it for repair
Click to expand...
Click to collapse
Already done, guess i have no choice.
Then i would like to tell all the peoples who are experiencing the same experience to replace their phone using google's warranty service.
Some peoples managed to fix the bug for a time with a lucky trick, but it always end to come back.

weacd said:
Already done, guess i have no choice.
Then i would like to tell all the peoples who are experiencing the same experience to replace their phone using google's warranty service.
Some peoples managed to fix the bug for a time with a lucky trick, but it always end to come back.
Click to expand...
Click to collapse
If it comes back while on stock rom then it's a problem with the device and you should rma it. That's what warranty is for
Sent from my Nexus 5 using XDA Free mobile app

I'm having random reboots.

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

OnePlus One Malfunction? Help please

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?