Database Info

[Q][HELP][ASAP] Multiple Random Reboots.. PLEASE HELP.

Just like the title, i have been experiencing some random rebooting in the past 9 days... at first i thought that i somehow held the on/off button inside my pocket and rebooted itself. my theory changed when i was charging it on that same night... i knew something was wrong few days after it would reboot itself from time to time.
also sometimes after rebooting (mostly when it is charging..) wifi connections start to goof off. i checked the wifi setting and it would say "error" under the "turn on/off wifi" area where you usually see the "connected/connecting/disconnected" letters, along with that some apps start to force close mostly the ones that needs the net get fc's.....
only yesterday it got worse. on the morning it had started to reboot. when i unlocked the lockscreen some apps started to FC. i usually get fc's in booting are the juice plotter, Google partner setup, and something with "wifi". now i manually rebooted it myself when it boots, it still shows those fc's. if it tried pressing some apps it tried to fc as well. manual reboot again, now messages fc's along with the three....
so i went to recovery and restored my safest backup. after restoring no more fc's in my boot. i thought it was all fine now but after a while it would randomly reboot!!!!
Styles of random reboots ive gotten:
1. on screen-off while charging after a while BOOM! reboot.
2. on screen-off not charging, after a while BOOM! reboot.
3. pressing the on/off button on the side when it was on screen-off, BOOM! reboot.
4. pressing the on/off button on the side when it was on screen-off, shows the lockscreen, shows "SD card unexpectedly removed" on status bar, BOOM! reboot.
*it wont reboot when you're using it unless it goes to screen-off for a while (like when using music player... when it goes to screen-off for a while it would reboot...)
--- i will add more of the reboots styles if i remember the others.---
i really need help. i cannot reflash to stock because my laptop got stolen since February. i would be receiving my new laptop in five days.... but i am worried that something worse would happen before even getting my laptop in five days.
Stats:
Samsung galaxy S i9003 (rooted)
currently unrooted
Firmware Version - 2.3.6
kernel - 2.6.35.7-CL709629 [email protected] #6
Baseband - I9003XXKPQ
Build # - GINGERBREADXXKPQ
*ics theme by Tarunagg update 18-
*restored phone to update 14 but same stats
SOMEONE PLEASE SHED SOME LIGHT INTO THIS. PLEASE!

normally when i experience random reboots, i just wipe cache and dalvik cache
if that dont work out then i flash back to stock kernel

its might me rom problem and one thing try to flash ur phone again but u said u don't have laptop but its only sol. according to me . if u want to be on 2.3.6 then acc to me don't install kernel and brother flashing again is the only sol
but for the mean while wipe everything and then deodex again it might help u .
after wipe all and formatting deodex it again
bcz sometime app FC and for that deodex again is necessary

sandeepsivia said:
its might me rom problem and one thing try to flash ur phone again but u said u don't have laptop but its only sol. according to me . if u want to be on 2.3.6 then acc to me don't install kernel and brother flashing again is the only sol
but for the mean while wipe everything and then deodex again it might help u .
after wipe all and formatting deodex it again
bcz sometime app FC and for that deodex again is necessary
Click to expand...
Click to collapse
Thanks sandeep. I am no longer flashing anythingbjust like you said...but what do you mean wipe all? dalvik, cache, battery stats and format? but wont that remove root and cwm? Give me step to step procedure so i can try what you are saying about wiping all..
also about your first paragraph, i will reflash fw to 2.3.6 and no longer flash diff kernel?

noypi_ako said:
normally when i experience random reboots, i just wipe cache and dalvik cache
if that dont work out then i flash back to stock kernel
Click to expand...
Click to collapse
Actually i have been clearing dalvik cache and cache.... but it does not work that much.. i want to flash to stock but i dont have comp. or stock kernel.

Wahaha123 said:
Thanks sandeep. I am no longer flashing anythingbjust like you said...but what do you mean wipe all? dalvik, cache, battery stats and format? but wont that remove root and cwm? Give me step to step procedure so i can try what you are saying about wiping all..
also about your first paragraph, i will reflash fw to 2.3.6 and no longer flash diff kernel?
Click to expand...
Click to collapse
so one thin i forot to tell u tha once along time ago like 6 or moths is installed theme and i did deodex 1st too but the process was aboard bcz of some prlm with deodex file then i installed theme without looking and i my did same rebooting and FC so u can wipe cache and dalvik and battery too then wipe data/ factory reset in recovery only then again deodex it and see the problem solved or not

Just set you min cpu feq back to stock.300mhz - 1.0ghz.
Remove any tweek.
Sent from my GT-i9003 DXKP9(UC-kernel 10) using Tapatalk 2

chongns said:
Just set you min cpu feq back to stock.300mhz - 1.0ghz.
Remove any tweek.
Sent from my GT-i9003 DXKP9(UC-kernel 10) using Tapatalk 2
Click to expand...
Click to collapse
Cpu in my is set to 300-1100. Thanks... hope it'll hold the phone till i get my comp.

Wahaha123 said:
Cpu in my is set to 300-1100. Thanks... hope it'll hold the phone till i get my comp.
Click to expand...
Click to collapse
Dont u think so that u are using too old kernel...use v10 version of UC kernel.

vishal24387 said:
Dont u think so that u are using too old kernel...use v10 version of UC kernel.
Click to expand...
Click to collapse
Yes I know . The latest uc kernel is v10. But my laptop was stolen since the first week of february. That time the best kernel suited for poseidon rom was the v6. So till now I am stuck with v16 since the time my laptop was gone until I get my new on in 4 days at least...

sandeepsivia said:
so one thin i forot to tell u tha once along time ago like 6 or moths is installed theme and i did deodex 1st too but the process was aboard bcz of some prlm with deodex file then i installed theme without looking and i my did same rebooting and FC so u can wipe cache and dalvik and battery too then wipe data/ factory reset in recovery only then again deodex it and see the problem solved or not
Click to expand...
Click to collapse
Sorry, I didnt see your post earlier. But I am wiping every thing now while im replying you. I will tell you the results when it is finished.
Edit: phone seems to work normally. But some apps get fc's... But i think i know why. Its because i forgot to move back apps which were moved to the sd card back to phone memory.(using app2sd).. I know so because i remember having 7 apps moved to sd which had taken alot of space due to its size.
Anyway, thanks bro! I guess i owe you my phone but i will still be monitoring the phone and see if it'll reboot randomly again... Till i get my laptop ill reflash my phone. Again, thanks alot sandeep!and good luck with your exams again!
RE-EDIT: it not kinda fixed yet... When i woke up and checked my phone it seemed to be normal but when i opened the lockscreen fc's starts flooding me... About 6 or 7 fc's they are google goggles, superuser,titanium backup, google play music, google setup sumthing (it was in the first post..) Emai and.messages... I also get fc on yahoo mail but it doesnt fc the same time as the others. I tries uninstalling rthem and other apps as well but some time while i uninstall it starts to freeze and reboot... But the reboot is different. I doesnt reboot the "samsung galaxy s 19003 " thing. Justs stars from the glowing samsing logo. When it boots, the uninstalled apps seems to come back. So i thought of removing mg sd card and then restart... Fc's lessened to superuser, email tbackup and email. And i can uninstall now without it rebooting. Now i know ext sd cards are somewhat along with the problem. My phones antivirus does not see any viruses in it tho.
... Oh im using my SE W8.. Kinda small, hard to type...

it sounds like a kernel problem to me just update your kernel if you cant because you dont have a laptop just use mobile odin
http://forum.xda-developers.com/showthread.php?t=1347899
Good luck

mR_ said:
it sounds like a kernel problem to me just update your kernel if you cant because you dont have a laptop just use mobile odin
http://forum.xda-developers.com/showthread.php?t=1347899
Good luck
Click to expand...
Click to collapse
Hmm.. I also thought if it could be the kernel as well. I researched last night on my arc and some say that it is the kernel that was doing this.i am downloading the kernel and odin on my new xperia arc as im making this post. Thanks.

Sounds like a hardware problem forme. I have this problem 4 months ago. I have random reboots. I have tried everything from flashing new roms and kernels and nothing seems to fix it. Have you tried clean flashing(xxkpe-xxkpq)? If that still doesnt work then you really have a hardware problem. The only thing you can do is to send it back to samsung service center for repair or replacement(I just hope you are still in warranty period)

earldroid said:
Sounds like a hardware problem forme. I have this problem 4 months ago. I have random reboots. I have tried everything from flashing new roms and kernels and nothing seems to fix it. Have you tried clean flashing(xxkpe-xxkpq)? If that still doesnt work then you really have a hardware problem. The only thing you can do is to send it back to samsung service center for repair or replacement(I just hope you are still in warranty period)
Click to expand...
Click to collapse
Like i said i dont have a laptop yet to reflash phone to stock and check. If it'll not work, im pretty sure they'll change the motherboard.. My warranty expires on july so there is still time. pretty sure my dad will get pissed and buy an s2 instead. This phone already went to the service center twice. And the service center is far from where i live. Though i am enjoying improving the capabilities of this phone :\
Anyway what i did now was flashed uc kernel v10 via odin mobile (thanks mR_ ). Then i wiped everyting again. So far there was no fc's yet and one reboot only when i was installing dolphin browser... And thats it. Nothing else suspicious happened yet.

This problem has happened to my bro before. I helped him change his rom to clean kpu and it was fixed.
Cheers
Sent from my GT-i9003 powered by Smooth and no lag vurrutRom

Looks like the infamous pseudo reset bug again! Well looks like it with some symptoms missing, the i9003 had a faulty board with faulty internal memory card, so when it goes to sleep the int card sometimes doesn't wake up again. I faced this problem personally myself, no amount of flashing can help you (though i suspect excessive flashing might have caused/triggered it, dunno) so make sammy change the board on this bad boy, hey! you might get 16gb inbuilt memory as a bonus!

Wahaha123 said:
Like i said i dont have a laptop yet to reflash phone to stock and check. If it'll not work, im pretty sure they'll change the motherboard.. My warranty expires on july so there is still time. pretty sure my dad will get pissed and buy an s2 instead. This phone already went to the service center twice. And the service center is far from where i live. Though i am enjoying improving the capabilities of this phone :\
Anyway what i did now was flashed uc kernel v10 via odin mobile (thanks mR_ ). Then i wiped everyting again. So far there was no fc's yet and one reboot only when i was installing dolphin browser... And thats it. Nothing else suspicious happened yet.
Click to expand...
Click to collapse
if dad is buying you an s2 then i wont fix it until i get the s2
swerte mo pre ... im so jealous

noypi_ako said:
if dad is buying you an s2 then i wont fix it until i get the s2
swerte mo pre ... im so jealous
Click to expand...
Click to collapse
Di naman. He will pay half for the s2 and ill pay the other half... And prices of s2 here are expensive still. About 27-35 k. I dont have that much money yet.

mzone1510 said:
Looks like the infamous pseudo reset bug again! Well looks like it with some symptoms missing, the i9003 had a faulty board with faulty internal memory card, so when it goes to sleep the int card sometimes doesn't wake up again. I faced this problem personally myself, no amount of flashing can help you (though i suspect excessive flashing might have caused/triggered it, dunno) so make sammy change the board on this bad boy, hey! you might get 16gb inbuilt memory as a bonus!
Click to expand...
Click to collapse
hmm... i hope not. also i dont really flash anything unless updates are available on the ics theme. well now that you mentioned it, while i was at the beach like last week, i put my phone on my pocket without screening of (which i always and should do..) and then when i checked back the all my messages and files in the internal sd card were gone.... though the apps are still there and were still on go launcher ex home..... i hope it was just am accidental reset. i want to bring it to the service center im going to get my laptop in at least 2 days! and i want to spend my summer with both of them.
anyway. is wifi working well on poseidon rom with the uc kernel v10? thats the only problem here. my wifi keeps going on and off. crashing the apps that needs wifi whenever i press it. its the same problem with amit cf root kernel when you use poseidon.

Strange problems with Galaxy r

Ok so it is like this:
I bought my galaxy r here in sweden 1 year and 3 months ago, it was working perfectly for around 1 year.
At the one year mark i started to have some problems with the touchscreen where the phone would feel a pressure in the middle of the screen, to get rid of this i simply locked and unlocked the phone or rubbed a bit with a cloth on the screen.
Recently when I saw there was a cm10.1 rom with nightlies I rooted my phone and later installed the cm10.1 rom. Now the most anoying thing. I have a problem with my battery where the phone just shuts down randomly (mostly when playing games) even though it sometimes have up too 80% battery remaining. Then when I restart the phone it usually have 0% battery left and therefore shuts itself down again, sometimes it restarts with just a 20-30% batteryloss. This have occured more often recently and it shuts itself of 3-4 times a day. I can't remember if it was like this when i was on stock, before I started to flash and root, but i think it was.
A few days ago i flashed stock ics from odin and I confirmed that both of these problems still were there, so i have hard to belive that it is the modding of the software that have caused this.
Do you guys have any suggestions to how i can be able to use my phone normally again?
Im just a poor student so i don't want to waste money on a new phone after just 1 year :/

wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta

Will this help with the battery?

kataria.vikesh said:
wipe data and cache..i think after flashing u restore ur data back.
Sent from my GT-I9103 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Will this help the crashing/battery?

DippN said:
Will this help the crashing/battery?
Click to expand...
Click to collapse
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.

kataria.vikesh said:
It may be help you but first tell me, are you restoring data from titanium backup or something related to that..??
Also if you want to take backup then take it using Super backup application.
Click to expand...
Click to collapse
Nope, im not takeing backup of anything.
And one other thing i forgot to mention earlier, the phone now also thinks it is charging itself evrn when it is not. It think the usb cable is still connected.

I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!

paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.

DippN said:
Im just glad im not alone with this problem, and as you said, its barely unusable without having it plugged in.
Click to expand...
Click to collapse
paKS7 said:
I hope OP doesn't mind that I'm joining his thread, I'm experiencing the same problems on my gfs phone and don't know what to do.
I just installed the fresh CM 10.1 nightlies (did Cache/Data/Dalvik Wipe) and she is experiencing pretty much the same problems:
After 1 or 2 hours of unplugging the phone gets stuck and shuts down. After restarting the battery percentage is pretty low and the phone shuts down again (even if the battery says ~10%). The battery percentage then changes every restart, but is always between 0 and 20%. The phone is barely usable in this state :/
I couldn't wipe the SD card (.android_secure) because the swapped paths, could this be related?
Thank you in advance!
Click to expand...
Click to collapse
Both of you install CM10.1 using Procedure no 2 from OP.

kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Will try that when i get home, thx.

kataria.vikesh said:
Both of you install CM10.1 using Procedure no 2 from OP.
Click to expand...
Click to collapse
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.

paKS7 said:
Thank you, vikesh! I'll be able to try Procedure II tomorrow afternoon.
Click to expand...
Click to collapse
Sadly, I can confirm that this did not change anything.
The problems are still there :/

DippN said:
Sadly, I can confirm that this did not change anything.
The problems are still there :/
Click to expand...
Click to collapse
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium

kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?

DippN said:
I'm definitely going to try this, but as it seems now i think it is more about a faulty battery/hardware that software?
Or have these kind of problems been fixed software before?
One other thing, if i have rooted my device, does the root dissappear when i flash stockrom using odin?
Click to expand...
Click to collapse
May be hardware or software too..when you will vanish all data & cache then Software issue may be gone but if problem still persist, means you have hardware problem.
Also, root will be lost after flashing Stock ROM from ODIN.

I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!

paKS7 said:
I'm able to also confirm, that Procedure II didn't help the problem. I really doubt it is a hardware fault, because of us two having the exact same problem after flashing the same rom.
@Dippn: Do you know which nightly build you used? In my case it was the nightly build "20130405". Also could you check which baseband you are on? (Under About Phone -> Baseband Version) Over here we have i9103NEKI1
The only special thing we did I can think of is flashing a modem file (when we were still on the unofficial cm10.1 without these kind of problems, but massive battery drain), because there was a call problem going on for customers of the austrian provider 3 and CM10.1.
I could analyse the problem a bit more today: It seems as soon as the phone gets busy (for example from the browser loading pages or in DippN's case processing a game), the touch screen gets unresponsive and everything starts to lag and delay or freezes completely until it shuts down the phone. Could be either CPU or RAM related, I guess. I just wonder what caused this, even if the nightly had a faulty kernel, this should be fixed as soon as we flash another ROM, right?
I will be able to try a different ROM on monday. It would be great, if you could report, if the downgrade to GB helped the issue. I'd like to try a different baseband, if you are on the same right now too.
Greetings and thank you so much for trying to help us, vikesh!
Click to expand...
Click to collapse
Well, we are not on the same baseband. I'm on I9103XXLQ3.
About the cm verison im not quiet sure, the latest i flashed was "20130406" but since the problem were there the time before that when i flashed cm I cant answer exacly but i have a cm version "20130305" on my desktop and it could be that one that I used.
I never used cm before it was on nightlies so the modem file flashing i dont know anything about.
The thing you mention about that it shuts of when the phone gets busy and touchscreen gets unresponsive I can kind of confirm too.
I will flash GB now, will report back in an hour how it went.

kataria.vikesh said:
It shouldn't be happened. But if u are feeling so, just flash any stock GB using odin v1.87. Then just wipe all data and cache. Install cm10.1 over that using method 2.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.

DippN said:
Are you sure i should do it using v1.87?
I'm having problems finding it and v1.85 seems to be in everyones links.
Click to expand...
Click to collapse
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?

DippN said:
Flashed GB using v1.85 and now I am stuck in bootloop, after 10 sec at the samsung logo it restarts and repeat. >.>
When the phone restarted after the flash and after it says "-updating application" it says:
Installing Multi-CSC
Can't access to '/system/csc/NEE/system/'.
Successfully applied multi-CSC.
I have no idea what this means but could it mean anything?
EDIT: I got it to start by wipe cache and data. (thought i should do that when cwm was installed)
Unfortunately already in the startup options when u write wifi password the touchscreen became very unresponsive and when i after a few min had succeded writing the password the phone shut of when it tried to connect to it! :,(
I can also confirm that it still thinks it is charing when it is not becuase the symbol in the statusbar flicked from battery to charging symbol.
Is there anything else softwarerelated that I can do?
Click to expand...
Click to collapse
Wipe data again.. If possible after wiping data Just reflash the GB.

Reboots all the time since the latest OTA update

I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?

You can try a factory reset.

ShadowLea said:
You can try a factory reset.
Click to expand...
Click to collapse
I know I probably should after an update anyway, but I'd hate to have to set up the tablet all over again, so I'll give it a few more days. I was wondering if anyone came accross this problem and found a different solution. Some people mentioned their ATT version crashing and how un-disabling an app has fixed it. I don't have an app called My Magazines though, so that's no good. I have a bunch of apps disabled though. Could any of them cause such funny behaviour?

I think it is a problem on several firmwares, and the devices are rooted.
I fixed it using the Xposed Framework and the Wanam addon.
Or you can try the http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046 add-on.

Thanks, this seems to be it. It looks like I'll be rooting my tablet when I get home today I should have done it ages ago anyway, if only to set the desktop user agent in the browser and get rid of adds.

Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!

Tintinnuntius said:
Well, CF Autoroot didn't work for some reason. Now the system won't load at all (I can still get into download mode). Anyway, I described the problem here, if you can help, please let me know!
Click to expand...
Click to collapse
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.

Makoto1 said:
I've been there. Follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2794996
Then install SuperSU from the app store. Then try to flash CF Autoroot again. Good luck. And let me know if the file CyberDie1 referred to us worked for you.
Click to expand...
Click to collapse
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!

Tintinnuntius said:
Thank you so much, you just saved me a trip to the service centre. I've followed through with the first three steps and it booted back into the system I wish I could give you more than one "Thanks".
I don't have time to go through the rest of the steps today since I still have some stuff to do for work, but if the tablet keeps "rebooting" I'll be back in a few days to root and report how it went with the Xposed module.
BTW, I haven't been able to find the file "openrecovery-twrp-2.7.1.0-v1awifi.img.tar" the guide mentions as no. 4, and no other twrp version for P900 (only P905) on their site. Do you maybe have a link for that?
And big thanks again!
Click to expand...
Click to collapse
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.

Makoto1 said:
I'm also at work so I'm not at my computer. I think I found that file by doing a Google search for it. Yes, let me know if it keeps rebooting. I have my own tablet rebooting issues (as you can see in one of the other threads, heh). I lost my root by reinstalling SuperSU one too many times... I blame it on trying to change settings before reinstalling because I was trying to achieve something.
Click to expand...
Click to collapse
I tried googling, but like I said, the official TWRP site did not have a file for p900, only p905. Here's the list of all the supported devices on their site, I only see p905 and 3g variants.
Then there's this site. I didn't realize that "v1awifi" is the part that refers to p900. I'm going to use the latest version from here today and try to get root again. If I succeed, I'll then try the Xposed package. I only had three reboots in the last 24 hours though (which is much less than before my first root attempt), so it might be a while before I can be certain the reboots are gone.
EDIT: I rooted in a few minutes without a single problem. Xposed and module installed, starting the clock for reboot-watch now I'll report back immediately if I get a reboot, or in 24h if I don't.
EDIT2: It looks like Xposed with the Samsung SystemServer Crash Fix works. The app posts notifications when a crash is prevented, and I've just had three in the last hour, with no crashes.

Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).

Makoto1 said:
Best of luck. I tried that Xposed and Wanam module combo and it seemed to work for most crashes. However, I still get reboots when I wake it up from sleep after a full charge (from my experience).
Click to expand...
Click to collapse
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.

Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
I also installed the System Server Crash Fix, but it didn't prevent the reboot. Hopefully it works for you!
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.

Tintinnuntius said:
Try the other app, the SystemServer Crash Fix. I've just charged up my tablet for the day, and when I woke it up while still plugged in, I got a crash notification. I've also had a few more yesterday. So far, not a single crash, it worked every time.
Click to expand...
Click to collapse
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...

Makoto1 said:
I purchased Titanium Backup and froze all the Knox related processes and apps, but I still got a reboot. So, I just did a factory wipe on the tablet and rerooted. This time it prompted me and asked about disabling Knox. This time I chose cancel instead of disable. Crossing my fingers now. If I still see a reboot tomorrow morning I will probably forget about rooting my tablet.
Click to expand...
Click to collapse
I went halfway between your approaches. I chose to disable Knox when asked, but I did not freeze any of the apps with Knox in the name in TB. First, I reset the default apps settings and then used TB to freeze a bunch of bloatware, but nothing with Knox in the name. The only such app currently frozen is Knox Notification Manager 1.0. Also, I never installed Wanam module, just SSCF.

Tintinnuntius said:
I've just received an OTA for my P900 (bought in UK, completely stock, not rooted, P900.XXUANI1). Since then the tablet has been rebooting randomly several times a day. It's a funny sort of reboot where the tablet is back up and running almost instantly, not like on a usual startup. The screen goest black, the "Samsung" logo flashes for a half a second and it's back at the lockscreen. No blue-lines-logo animation that goes with a usual startup, but all the apps I was using are closed and the recent apps list is empty.
Is anyone having the same problems? Any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem, since I upgrade my T900, I have the same behavior you described.
Read a lot and tried everything, even Xposed Installer. Nothing corrected it.
I didn't test this firmware version it without root (can't live without it!).
If what you said that you have the random reboot without root, I really think that this firmware release is buggy.
I will now return to the previous firmware.

fdu123 said:
If what you said that you have the random reboot without root, I really think that this firmware release is buggy. I will now return to the previous firmware.
Click to expand...
Click to collapse
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago

arcadia2uk said:
Just adding in. The SystemServer Crash Fix is an Xposed module why you also need to install the Xposed Installer. First validate Xposed, then the crash fix app, finally reboot and you're done. Finally, just pray that your issues are gone...
Click to expand...
Click to collapse
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
Tintinnuntius said:
There's no doubt that Samsung is at fault. My tablet was stock, unrooted, in no way modified, and it still crashed several times every hour, usually when screen timed off and was turned on again, but also on other occasions. I would flash an older version too, but then I might have to do a clean install and set it up again, so I tried root + Xposed + SSCF first, and fortunately it worked. With the added benefit of Desktop User Agent in Chrome, no ads and a much snappier tablet. I should have rooted months ago
Click to expand...
Click to collapse
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...

Makoto1 said:
Which app did you use for no ads? Adblock Plus and Adaway didn't seem to work for me...
Click to expand...
Click to collapse
Adblock Plus version 1.2.1.325 works fine for me. It allows some unobtrusive ads through by default. If you want to block all you can, but you have to manually enable it in app settings.
If a particular app is still showing ads it sometimes helps to clear the cache.

Makoto1 said:
I installed the SystemserverCrash Fix app first, then the Xposed Installer... is that why it didn't work for me? Thanks in advance.
Click to expand...
Click to collapse
You could always try installing them the right way round to see if it will make a difference. I think I installed both apps at the same time, but then I opened Xposed, activated it, rebooted the tablet, then activated the module (which showed up in Xposed automatically, IIRC).
First, you should double-check that the SSCF is activated in Xposed, if it is not, it won't stop the crashes.

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?

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.