Related
hello everyone,
I bought a Nexus s from a friend of mine
it had a little problem of multiple rebooting.I though I will flash it and everything will be okay.It didn't go that way.
Specification:-
Nexus S
Fastboot Mode
Product name - HERRING
HW Version - REV 52
Bootloader Version - 19020XXL1
BaseBand Version - 19020XXL1
Carrier info - EUR
this is what it says in bootloader
Problem:-
My new Nexus s reboots just in middle of nothing.(I'll explain what i mean here)
Q:-while it get rebooted what activity caused reboot
A:- it happens in number of occation
*sometimes I open market(play google now) browse some app and click on install button-rebooted
*sometimes I put mobile on chargin and open call log - rebooted
*sometime I open camera to click pic - rebooted
* sometimes I click on message - rebooted
*sometimes I just unlock the screen lock and rebooted
*most irritating - someone calling me it gets rebooted and the callers number dosent even save in call log
basically there is no pattern for rebooting
* sometimes even it just idle and getting charged it multiple times reboot itself
-and this happens several times a day
this problem was reported on many places before me
system didnt allowed me to post outside links where it was reported
and google has released fix for that as read somewhere where it was reported this bug in android 2.3.4 (atleast they said like that),
Solution I tried :-
downloaded stock rom where the uploader said it works fine and has no reboot issue it was android 2.3.6. so i assumed that reboot issue should not bother anymore
before installing Stock rom I followed guide to root on nexusshack.com and I did not forget to wipe all data/factory reset, wipe dalvik cache,battery status
still problem exist
then I tried new ICS consider there will be no chance for this error
but again I failed to fix the reboot error
here is specification of Roms I tried, I used each of these ROM for more than 3 days,just to be ensure, that problem still persist
ICS 4.0.3 -
Baseband version - 19023XXKI1
Kernel Version - 3.0.8-gb55e9ac
[email protected]#1
Build number - IML74K
Android 2.3.6
Stock rom I tried -3 different stock rom download from different sites having same specification
Baseband version - 19023XXKF1
Kernel Version - 2.6.35.7-gf5f63ef
[email protected]#1
Build number - GRK39F
after this didnt worked I tried changing kernel...thinking that may fix this problem
I dont know how this could fix the problem ..but I was so desperate to fix it, I just give it a go,as I was and I am ready to do anything which is possible to do to fix it,
Kernel I tried-
netarchy-1.3.7-bfs-2.3.4-signed
netarchy-1.3.7-cfs-2.3.4-signed
netarchy-1.3.7-bfs-2.3.4-universal-signed
I will be very glad if any expert give me advice to what else I should do?
or this problem is due to faulty board and I have to pay to replace it?
I'm totally confused
can someone please help me out solving my problem, if it can be fixed
P.S:- for those who get angry and reply in tone everything works good on my nexus there is no such problem exist when someone says my nexus has reboot problem (saw this happening on many places where the bug was reported).I'm glad that your device works without problem, unluckly my device dosent, and I want to fix it, will be nice if you guys will be co-operative,rather than just mocking and spamming
Thanks in Advance
-Shree
reserved
Reserved in case needed
Try data/factory reset, format /system and format /boot. Now try flashing a Stock ROM. If this doesn't help it is probably a hardware issue and needs the SoC replaced.
Harbb said:
Try data/factory reset, format /system and format /boot. Now try flashing a Stock ROM. If this doesn't help it is probably a hardware issue and needs the SoC replaced.
Click to expand...
Click to collapse
I'm not very much expert in these things...
from the above things what I know is factory reset..
will he very nice if you provide a link to guide describing how to,
format / system and format /boot.
You have to go into recovery and you'll notice the options
Sent from my Nexus S 4G using xda premium
Recovery --> Mounts and Storage --> Format /system, Format /boot
Thanx a lot.....
I did format system,boot,cache,data,
then wiped fata/ factory reset,dalvik cache,cache partition,battery status (all wipe option)
now installed a stock rom.
I'll try this for couple more days....and see if problem still exist
if it still exist....that is for sure its hardware problem...and first I'll have to detect which hardware is faulty, causing the problem..hope I dont have to do that
Thanx a lot guys
I tried it the way you said it,
the problem still exist...but the reboot amount frequency is reduced...not it reboots just 2-3 times a day
I just got my infinity a few days ago, and before I unlocked and rooted I wanted to ask if the stock 4.2.1 rom was susceptible to random reboots? It's rebooting while running an app at least once a day, with limited use. I don't know if this is common or if I've possibly got a lemon. Before I void my warranty, I wanted to see if this was the norm. I don't have this problem with my phone or my old tablet (both running a cm10.1 rom) , which is why I'm a little concerned. Thanks in advance for any thoughts
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
psudeke said:
I just got my infinity a few days ago, and before I unlocked and rooted I wanted to ask if the stock 4.2.1 rom was susceptible to random reboots? It's rebooting while running an app at least once a day, with limited use. I don't know if this is common or if I've possibly got a lemon. Before I void my warranty, I wanted to see if this was the norm. I don't have this problem with my phone or my old tablet (both running a cm10.1 rom) , which is why I'm a little concerned. Thanks in advance for any thoughts
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
My Cromi 4.6.5 is fine. What custom rom do you use?
Bone stock, just came out of the box about 3 days ago. I upgraded to 4.2.1 but have yet to do anything else. I want to root and unlock to truly enjoy my tablet (i'm a "crack flasher" on my other devices), but the possibility of a hardware issue makes me not want to void my warranty yet
psudeke said:
I just got my infinity a few days ago, and before I unlocked and rooted I wanted to ask if the stock 4.2.1 rom was susceptible to random reboots? It's rebooting while running an app at least once a day, with limited use. I don't know if this is common or if I've possibly got a lemon. Before I void my warranty, I wanted to see if this was the norm. I don't have this problem with my phone or my old tablet (both running a cm10.1 rom) , which is why I'm a little concerned. Thanks in advance for any thoughts
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Factory reset and see if it runs OK without any additional apps added. Often, not always, but often enough people have issues with an app(s). If it frequently crashes in that state, I don't imagine it will hurt to exchange it.
faustus1005 said:
Factory reset and see if it runs OK without any additional apps added. Often, not always, but often enough people have issues with an app(s). If it frequently crashes in that state, I don't imagine it will hurt to exchange it.
Click to expand...
Click to collapse
+1 factory reset and report back.
Unfortunately some of the random reboots are issues with the stock kernel and some apps misbehaving. It'll be a software issue.
sbdags said:
Unfortunately some of the random reboots are issues with the stock kernel and some apps misbehaving. It'll be a software issue.
Click to expand...
Click to collapse
Without seeing a couple of last_kmsg, it's impossible to know.
Thanks for the advice, I'm going to try the reset first and see if it helps. As for the last_kmsg file, from what I've read it sounds like I can pull that via an without being rooted, is that correct? The first method I saw called for the su command in terminal emulator, which I'm assuming won't work without superuser access.
Thanks again, I'll report back on the reset in a couple of days
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
_that said:
Without seeing a couple of last_kmsg, it's impossible to know.
Click to expand...
Click to collapse
sbdags said:
Unfortunately some of the random reboots are issues with the stock kernel and some apps misbehaving. It'll be a software issue.
Click to expand...
Click to collapse
faustus1005 said:
Factory reset and see if it runs OK without any additional apps added. Often, not always, but often enough people have issues with an app(s). If it frequently crashes in that state, I don't imagine it will hurt to exchange it.
Click to expand...
Click to collapse
** Update **
I did a factory reset, however i did go forward with reinstalling my apps from the playstore, and immediately upon selecting "Nova Launcher" as my launcher, it crashed. I grabbed the last_kmsg and have attached it below. I'm new to the Transformer so I apologize if i've included too much or too little, The entire file was larger than what XDA would allow me to upload, so I took my best shot at it based on what i imagine is a time stamp. If you need more i've got the original, i can split it in half and upload it that way. I should also point out, I did also go ahead and root, initially i tried this in order to back up my apps with Ti, but wasn't able to successfully root until after i did the factory reset (overlooked a setting in security for MotoChopper to work). If Nova Launcher is the problem, I can live without it until i switch to another rom/kernel.
Thanks again for looking at this, I appreciate it tremendously. I'm ready to unlock and satisfy my flasher habit
psudeke said:
I did a factory reset, however i did go forward with reinstalling my apps from the playstore, and immediately upon selecting "Nova Launcher" as my launcher, it crashed. I grabbed the last_kmsg and have attached it below.
Click to expand...
Click to collapse
That doesn't look like a (kernel) crash, it's a usermode-induced reboot:
Code:
[17914.684201] Restarting system with command ''.
Interesting is this one, a few seconds before the reboot:
Code:
[17899.372183] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
Usually I get this message when I remount /system as rw (read/write), however that requires root access. I've read that if you try to overwrite certain files in /system with root access, the device would reboot.
There are also some situations in which Android decides to reboot by itself, e.g. when a critical service process fails to start, or crashes too often. I thought that this will always reboot directly to recovery, but I may be wrong.
So until now, it looks like a software issue, but not a common one. Maybe someone else knows more. Keep checking last_kmsg after the next unexpected reboot to see if it's the same pattern.
psudeke said:
** Update **
I did a factory reset, however i did go forward with reinstalling my apps from the playstore, and immediately upon selecting "Nova Launcher" as my launcher, it crashed. I grabbed the last_kmsg and have attached it below. I'm new to the Transformer so I apologize if i've included too much or too little, The entire file was larger than what XDA would allow me to upload, so I took my best shot at it based on what i imagine is a time stamp. If you need more i've got the original, i can split it in half and upload it that way. I should also point out, I did also go ahead and root, initially i tried this in order to back up my apps with Ti, but wasn't able to successfully root until after i did the factory reset (overlooked a setting in security for MotoChopper to work). If Nova Launcher is the problem, I can live without it until i switch to another rom/kernel.
Thanks again for looking at this, I appreciate it tremendously. I'm ready to unlock and satisfy my flasher habit
Click to expand...
Click to collapse
Highly unlikely that it's Nova causing the crash - it would be common knowledge by now if Nova was incompatible with the TF700.
It has to be some other app you have installed, maybe in conjunction with Nova (or any other launcher?) that is causing the crash.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
Highly unlikely that it's Nova causing the crash - it would be common knowledge by now if Nova was incompatible with the TF700.
It has to be some other app you have installed, maybe in conjunction with Nova (or any other launcher?) that is causing the crash.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Yeah, it did crash another time yesterday when Nova was not running. Unfortunately I wasn't able to pull the last_kmsg file at the time, but if it happens again, I'll post the file. Thanks again for everyone's help.
I had another crash last night, it had been running relatively smooth for a few days, although i wasn't using it much. I believe this is the section of the last_kmsg that details the error. Let me know if this sheds any light, the previous errors noted were not found again
[ 3026.029216] Kernel panic - not syncing: Fatal exception in interrupt
[ 3026.029285] [<c0016438>] (unwind_backtrace+0x0/0x144) from [<c0711110>] (dump_stack+0x20/0x24)
[ 3026.029395] [<c0711110>] (dump_stack+0x20/0x24) from [<c0713290>] (panic+0x88/0x1b4)
[ 3026.029502] [<c0713290>] (panic+0x88/0x1b4) from [<c0013418>] (die+0xec/0x100)
[ 3026.029564] [<c0013418>] (die+0xec/0x100) from [<c0013454>] (arm_notify_die+0x28/0x60)
[ 3026.029669] [<c0013454>] (arm_notify_die+0x28/0x60) from [<c00082e4>] (do_undefinstr+0x148/0x16c)
[ 3026.029774] [<c00082e4>] (do_undefinstr+0x148/0x16c) from [<c000edc8>] (__und_svc+0x48/0x60)
[ 3026.029830] Exception stack(0xc0acfd68 to 0xc0acfdb0)
[ 3026.029931] fd60: c1712070 c1712070 00006000 c1712070 c0ace000 00000102
[ 3026.030036] fd80: c0bc1fe4 c0ad0080 c0ace000 c1712070 c1710060 c0acfdec c0acfdb0 c0acfdb0
[ 3026.030095] fda0: c0085900 c1712088 60000113 ffffffff
[ 3026.030197] [<c000edc8>] (__und_svc+0x48/0x60) from [<c1712088>] (0xc1712088)
[ 3026.030257] Rebooting in 10 seconds..
[ 3036.043426] Restarting Linux version 3.1.10-g9827b9a ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease)
Thanks again for your help, and let me know if there's anything else i can provide.
psudeke said:
I had another crash last night, it had been running relatively smooth for a few days, although i wasn't using it much. I believe this is the section of the last_kmsg that details the error.
Click to expand...
Click to collapse
Usually the lines before these contain more relevant information.
psudeke said:
I had another crash last night, it had been running relatively smooth for a few days, although i wasn't using it much. I believe this is the section of the last_kmsg that details the error. Let me know if this sheds any light, the previous errors noted were not found again
[ 3026.029216] Kernel panic - not syncing: Fatal exception in interrupt
[ 3026.029285] [<c0016438>] (unwind_backtrace+0x0/0x144) from [<c0711110>] (dump_stack+0x20/0x24)
[ 3026.029395] [<c0711110>] (dump_stack+0x20/0x24) from [<c0713290>] (panic+0x88/0x1b4)
[ 3026.029502] [<c0713290>] (panic+0x88/0x1b4) from [<c0013418>] (die+0xec/0x100)
[ 3026.029564] [<c0013418>] (die+0xec/0x100) from [<c0013454>] (arm_notify_die+0x28/0x60)
[ 3026.029669] [<c0013454>] (arm_notify_die+0x28/0x60) from [<c00082e4>] (do_undefinstr+0x148/0x16c)
[ 3026.029774] [<c00082e4>] (do_undefinstr+0x148/0x16c) from [<c000edc8>] (__und_svc+0x48/0x60)
[ 3026.029830] Exception stack(0xc0acfd68 to 0xc0acfdb0)
[ 3026.029931] fd60: c1712070 c1712070 00006000 c1712070 c0ace000 00000102
[ 3026.030036] fd80: c0bc1fe4 c0ad0080 c0ace000 c1712070 c1710060 c0acfdec c0acfdb0 c0acfdb0
[ 3026.030095] fda0: c0085900 c1712088 60000113 ffffffff
[ 3026.030197] [<c000edc8>] (__und_svc+0x48/0x60) from [<c1712088>] (0xc1712088)
[ 3026.030257] Rebooting in 10 seconds..
[ 3036.043426] Restarting Linux version 3.1.10-g9827b9a ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease)
Thanks again for your help, and let me know if there's anything else i can provide.
Click to expand...
Click to collapse
Kernel Panic - basically the OS has detected a fatal error from which it can't recover so the only option is for it to force a reboot...
We can't see the bit above to see what it was doing before that....
sbdags said:
Kernel Panic - basically the OS has detected a fatal error from which it can't recover so the only option is for it to force a reboot...
We can't see the bit above to see what it was doing before that....
Click to expand...
Click to collapse
_that said:
Usually the lines before these contain more relevant information.
Click to expand...
Click to collapse
Sorry, still am new to this type of issue and have a lot to learn. Assuming that the beginning of each line is a time stamp, here everything that happened immediately before what i posted earlier. Let me know if you need more and thanks again.
psudeke said:
Assuming that the beginning of each line is a time stamp, here everything that happened immediately before what i posted earlier. Let me know if you need more and thanks again.
Click to expand...
Click to collapse
Thanks, this is the relevant part (and yes, the number is a timestamp).
[ 3026.027729] [<c0085900>] (call_timer_fn+0x50/0x190) from [<c008665c>] (run_timer_softirq+0x150/0x2a8)
[ 3026.027837] [<c008665c>] (run_timer_softirq+0x150/0x2a8) from [<c007e3a8>] (__do_softirq+0xdc/0x278)
[ 3026.027938] [<c007e3a8>] (__do_softirq+0xdc/0x278) from [<c007ea6c>] (irq_exit+0xa8/0xb0)
I know this bug (but not how to fix it) - looks like corruption in the timer list, so the kernel jumps to an incorrect address and crashes. I've had the same crash every few weeks with 10.6.1.14.4, but not yet with 10.6.1.14.8 (both my own near-stock kernels).
_that said:
Thanks, this is the relevant part (and yes, the number is a timestamp).
[ 3026.027729] [<c0085900>] (call_timer_fn+0x50/0x190) from [<c008665c>] (run_timer_softirq+0x150/0x2a8)
[ 3026.027837] [<c008665c>] (run_timer_softirq+0x150/0x2a8) from [<c007e3a8>] (__do_softirq+0xdc/0x278)
[ 3026.027938] [<c007e3a8>] (__do_softirq+0xdc/0x278) from [<c007ea6c>] (irq_exit+0xa8/0xb0)
I know this bug (but not how to fix it) - looks like corruption in the timer list, so the kernel jumps to an incorrect address and crashes. I've had the same crash every few weeks with 10.6.1.14.4, but not yet with 10.6.1.14.8 (both my own near-stock kernels).
Click to expand...
Click to collapse
Thanks for the info! This is my third android device and i've never had to look into kernel issues before, so I greatly appreciate your help! I guess this is really the best possible news, as its my intent to unlock and test out some other ROMs and kernels. I'm going to stay on stock for another week or so and keep an eye on any crashes, and post the kmsg if they do (and are different from above).
Thanks again :good:
_that said:
Thanks, this is the relevant part (and yes, the number is a timestamp).
[ 3026.027729] [<c0085900>] (call_timer_fn+0x50/0x190) from [<c008665c>] (run_timer_softirq+0x150/0x2a8)
[ 3026.027837] [<c008665c>] (run_timer_softirq+0x150/0x2a8) from [<c007e3a8>] (__do_softirq+0xdc/0x278)
[ 3026.027938] [<c007e3a8>] (__do_softirq+0xdc/0x278) from [<c007ea6c>] (irq_exit+0xa8/0xb0)
I know this bug (but not how to fix it) - looks like corruption in the timer list, so the kernel jumps to an incorrect address and crashes. I've had the same crash every few weeks with 10.6.1.14.4, but not yet with 10.6.1.14.8 (both my own near-stock kernels).
Click to expand...
Click to collapse
So, two more crashes to report. One happened last night, i pulled the last_kmsg but couldn't find anything to suggest that it even crashed. today, on my way home from work, it did it again. when i pulled the last_kmsg i was surprised to see that instead of the normal 900kb file i've been getting, this one was only 16k. not sure when it resets the file, but i've attached the entire file to the post. i'm starting to think i've got a defective device, given the constant lag and reboots (its often slower than my old kindle fire) let me know what you think and much thanks for all your help.
Another crash and not much in the last_kmsg file (attached). I'm assuming the file is getting wiped on reboot? Is there any other files that might be useful? I did an adb debug, but there's so much information i don't know if there's anything in particular that i should be looking for. Any one have any thoughts?
Thanks!
Updated to v9 today...after receiving a call (did vibrate), I found that all kinds of vibration stopped working, even in recovery mode.
I googled it and find https://forums.oneplus.net/threads/vibration-suddenly-not-working.76462/page-2 that someone else is having the same problem with franco. I am so frustrated as it seems that only full reflash can fix the problem.
Anyone has others solution on it?
ROM: Stock CM 11S
Kernel: franco.Kernel v9
I did change according to http://forum.xda-developers.com/showpost.php?p=54571945&postcount=271 today. Not sure if it relates to the issue.
PS Don't have the permission to ask in franco thread so I better post it here...
Solved:
My solution is to accidentally drop the phone on the ground and make a scratch on the silver edge. And the vibration is back. It is a hardware problem. But maybe it is triggered by a software issue...
knzzz said:
Updated to v9 today...after receiving a call (did vibrate), I found that all kinds of vibration stopped working, even in recovery mode.
I googled it and find https://forums.oneplus.net/threads/vibration-suddenly-not-working.76462/page-2 that someone else is having the same problem with franco. I am so frustrated as it seems that only full reflash can fix the problem.
Anyone has others solution on it?
ROM: Stock CM 11S
Kernel: franco.Kernel v9
I did change according to http://forum.xda-developers.com/showpost.php?p=54571945&postcount=271 today. Not sure if it relates to the issue.
PS Don't have the permission to ask in franco thread so I better post it here...
Click to expand...
Click to collapse
I have has problems with vibrations too, It worked in recovery but not in Cm 11s, I installed Pacman rom and now it works, also works with Franco kernel but use aosp.
Try updating to r10 and see if the problem still occurs.
Sent from my One using Tapatalk
I am on r10 now but still no vibration in any circumstances...I have once restored the vibration after many trials of wipe (in recovery mode) and reflash but when I signed in my google account with "backup & restore" box checked, it lost again. So i think it should be a software problem. Unfortunately I couldn't restore the vibration again as I forgot my actual steps at that time.
I will try flashing asop when I am free. Thanks.
knzzz said:
I am on r10 now but still no vibration in any circumstances...I have once restored the vibration after many trials of wipe (in recovery mode) and reflash but when I signed in my google account with "backup & restore" box checked, it lost again. So i think it should be a software problem. Unfortunately I couldn't restore the vibration again as I forgot my actual steps at that time.
I will try flashing asop when I am free. Thanks.
Click to expand...
Click to collapse
How many other kernels have you tried as well for troubleshooting purposes?
playya said:
How many other kernels have you tried as well for troubleshooting purposes?
Click to expand...
Click to collapse
I just tried stock. I used to think to fix the problem I can only wipe everything and do full reflash via fastboot posted in OP. However I just can't format 'userdata' as I mentioned in my other post http://forum.xda-developers.com/oneplus-one/help/help-fail-to-wipe-using-fastboot-t2839512.
Again I will try to flash another kernel to see if it works. Thanks.
knzzz said:
I just tried stock. I used to think to fix the problem I can only wipe everything and do full reflash via fastboot posted in OP. However I just can't format 'userdata' as I mentioned in my other post http://forum.xda-developers.com/oneplus-one/help/help-fail-to-wipe-using-fastboot-t2839512.
Again I will try to flash another kernel to see if it works. Thanks.
Click to expand...
Click to collapse
That's a lot to do to try and fix issue. I would restore my nandroid that was working prior to flashing kernel and flash another kernel for testing.
Solved!!!
My solution is to accidentally drop the phone on the ground and make a scratch on the silver edge. And the vibration is back. I should thank the maid who bumped into me.
So I am wrong it is a hardware problem. But maybe it is becoz the vibration strength was low and somehow break the vibrator.
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
First of all sorry for my English....
Flyme OS and the experimental port of Sense are the only android based roms that works on my (i guess) hardware bricked Nexus 5 (moisture maybe); Sailfish, B2G and Ubuntu Touch works too (everythig that can work), but the stock rom and other android based roms screen locks as soon configuration starts (usually touching in "next" after selecting language) and the power button no longer unlocks. I'm trying to find the differences between Flyme and other Roms, especially in the framework-res.apk, to port this to a stock or cm rom (on which is based flyme) but I'm a little lost...
Flyme Os is stable and daily use, the only error message that it shown when boot is "cannot load native library cpu arch invalid for this build", but then use it normally
Thanks in advance, for any idea
Have you tried flashing stock with fastboot?
Yes, of course, in every way, even with the flashtool lg and factory original image .tot and D820 DLL (process that also closes the bootloader)...
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
KJ said:
So you've done this... With fastboot?
http://forum.xda-developers.com/showthread.php?t=2513701
And what errors did you get?
Click to expand...
Click to collapse
Yes, same error: the screen locks when i touch "next" in language selection and no longer responds.
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
KJ said:
So fastboot installed everything without error?
Just wanna be sure you successfully installed stock. Which image did you use?
Click to expand...
Click to collapse
yes, entire process without error
I use any official found in https://developers.google.com/android/nexus/images
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Very strange, yes. I also think it's an issue of partitions, damaged sectors or any where the stock image using to store settings or something...
I asked in a thread Flyme, about major structural changes that i can carry a stock rom, but no response yet
KJ said:
So after flashing stock, it freezes during setup? Very strange. I can only guess that those other OS's messed up your partitions.
I'm not sure what else you can try. Did you fastboot erase system, user data and cache first?
And have you asked others in the threads for those oddball OS's if they had issues like yours?
Click to expand...
Click to collapse
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
ferozzzz said:
Sorry, i don´t undertand. Such other operating systems were installed once the problem was presented. First the original stock android (from the box, only updated by ota) started having problems, autolock randomly. Then reinstall the factory image (in every way) and still failing so I went back to using my Nexus 4 and began to try other Roms and OS's. Until I arrived at the only functional rom based on android that not autolock, Flyme...
Click to expand...
Click to collapse
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
nbite said:
What you have is DOA, look at the logs after you installed flyme os and check sd card for errors/repartition (mentioned before). But i would just change the device using DOA warranty. Dont forget to reset the tempered flag afterwards.
Click to expand...
Click to collapse
Its not DOA, it works for over 7 months, I think that are bad sectors
attached logcat
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
nbite said:
Im not sure whats happening but it looks like your lollipop preview isnt booting with multirom. I can see the i/o error but im not sure whats causing it.
sd 0:0:0:0: [sda] Unhandled error code looks like drive is failing. Also some wifi problems but dont think thats the reason. 70% sure its the drive. Check reformat or replace. Good luck man!
Click to expand...
Click to collapse
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
ferozzzz said:
Already formatted it, ran e2fsck (with verbose: no bad sectors), I'll wait for the final version of lollipop, if I keep using FlymeOS until I get a motherboard at reasonable price in Argentina
Click to expand...
Click to collapse
It either the nand or the nand controller or software thats causing bad block (going to stock, flashing everything correctly, reflashing kernel, radio etc). Very little chance of it being a software fault since it persists on different roms. Good luck!