Related
Hi guys,
I have a huge problem. I had a stock GB firmware customized by Optus (carrier in Australia) on my S2 I then decided to change to the new ICS 4.0.4. I downloaded the stock unbranded firmware from SamMobile (Australia 2012 September 4.0.4 I9100XWLPW, I9100XSALP6, XSA) I updated using Odin. Before I did the update I reset the phone, did the update, it all went smoothly. After the update I reset the phone again and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
The phone works and all functions on it work, however now very randomly the phone would totally freeze. The phone would be in standby, the screen would come on and it would be frozen. The screen stay on all the time and it does not respond at all. It will stay frozen until I restart the phone by pressing Home+power buttons to restart it.
After restart it all works fine for a few hours, sometimes a day and would just lock up again. The phone is not rooted and as I said i just changed the firmware from the Optus branded GB 2.3.6 to unbranded stock ICS 4.0.4 by using Odin.
Is there a way to find out what is causing the phone to lock up like that? Any suggestions would be helpful.
and then proceeded to reinstall all my apps and restore my contacts, sms, etc.
Click to expand...
Click to collapse
I hope you haven't restored any data app?
przemcio510 said:
I hope you haven't restored any data app?
Click to expand...
Click to collapse
I made sure that I didn't restore any data apps. The only apps that got restored are the ones that get automatically restored by Play store.
I have disabled the live wallpaper that I had and it seems to have stopped the freezing for the moment. I will report on what I find out.
In the mean time if anyone else has a similar issue or has a definite solution please let me know.
Thanks
i know this is a resurrection, but don't see it has been resolved.
also found same/similar problem on another topic, but no resolution either.
couldn't find any resolution anywhere on the net, but possibly i'm just missing it (searching for wrong parameters?)
anyway, a friend of mine bought second-hand (third or even fourth hand to be precise) i9100 with 2.3.6 (stock KI3) on it. the guy who sold it to him said something like: "it works best on 2.3, on 4.x it's buggy".
it was working fine, but friend wanted newer OS, so we tried update. it didn't work, and i found out CSC was broken/missing. somehow i managed to repair it, and update was finally working, but was unable to find any for our location.
so next step was to find stock rom that would work on the device, and then i tried four different 4.1.2 stock roms from this topic.
after flashing it through odin, every one was acting fine, until couple of minutes after it started freezing or rebooting randomly.
then i tried flashing CWM, and flashing from sd card, but it was all the same.
wiping data, cache and dalvik cache, prior to flashing. wiping data after flashing...
nothing seemed to work.
GB works rock solid, ICS works better than JB, but stills it freezes or restarts randomly.
tried CM10, but all the same, except it works a bit faster then official JB. but who cares about speed if it freezes/restarts constantly?
back to who knows which build... freeze... samsung galaxy s2 - i9100... with yellow triangle... booting stopped.
so i decided to dig deeper, trying to find hungarian stock build (country we were told the phone came from) not being sure that KI3 is what the phone came actually with. i found 4.0.3, put it on SD card, wiped data, cache, flashed CWM, wiped data, cache, dalvik cache, flashed 4.0.3 from sd, wiped data, booted, entered location for updates - hungary. update found, hooray... downloading... installing... rebooting... working?
nope... it's worse than ever. trying to log onto google account. typing in email add.... freeze... switching phone on - freeze... thinking about... freeze.
i couldn't sit still. yellow triangle, all those reboots/freezes... at least i wanted that triangle gone, and without a JIG, there was only solution for me was to try triangle away. it wasn't available for download in my country from play store, so luckily xda was there.
somehow i managed to download it from the device, install it, click remove the triangle... it did it's magic, rebooted... and miracle happened!
no more freezes.
so i started torturing poor phone, benchmarking, playing games, listening to music.... it seemed stable for about an hour.
so i said to myself:
- it's possible that previous owners tried to upgrade it to newer firmware, and somehow screwed up the bootloader, which was fixed by this app? maybe that was all there was from the beginning? why not try putting 4.1.2?
and i did... took 4.1.2 spanish build from already mentioned page above, flashed it... and voila. working JB... torturing the phone... playing with it... hour passes, another hour...
friend wakes up... takes his phone in awe, starts playing with it.. we talk a bit... and then that look it just froze again!
from that moment on, the phone again starts restarting or freezing randomly...
and, yes, i still have no clue what could be the cause. it doesn't matter if wifi is on or off, if you're talking on the phone or not, bluetooth and gps are always off. only thing that he noticed is that it usually happens while he's using the phone (meaning: operating the digitizer or buttons). if he starts music playback and not touching buttons or screen, it will probably play for hours.
one more thing, but i doubt it would be the case. the battery in the phone is not original one that was shipped with it, but a quality replacement.
it doesn't feel as if the phone is overheating... so i don't know what else i could do with it.
for now, it's back to 2.3.6.
we both lost a week, torturing ourselves with this problem.
i don't know is there anything i could add more?
all suggestions are welcome.
cheers
Maybe try kernel cleaning script and try philz or siyah kernels.
You shouldn't have to flash a custom kernel so your phone won't freeze, but yes, you could run a nuke script in order to wipe clean all custom ROM's leftovers.
Try flashin' jb via mobile odin, see if it keeps freezing up on you. If so, nuke it up.
Sent from the little guy
i'll try them out.
probably for the weekend, if not sooner. will report back here with info.
any other suggestions are also welcome.
thanks a lot.
cheers
ok, so here are some updates.
i finally got my hands back on my friends phone, and tried nuking remains of older flashes.
following that, i flashed stock spanish rom from above mentioned page, updated after installation to spanish update... and after a few minutes, sudden reboot...
so, went back to nuking, and flashed stock hungarian 4.0.3 i found elsewhere (mentioned in my earlier post. don't remember origin... if i find the link on another computer where i downloaded it on, i'll post the link). tried updating, says no updates found.
started torturing the device. it seemed solid, but battery reported it level was low, so hooked it up onto charger and all seemed well. but phone seemed a bit too hot.
after few minutes (this was all about half an hour to hour after flashing to 4.0.3), again freeze.
after rebooting the phone, battery was at 9%, as if processes were draining battery faster than charger recharged it.
so, i figured i gotta try original battery. so i switched his battery with genuine from my phone.
phone seems stable and less hot, for now.
still checking if it is going to freeze or reboot again.
it's about one hour since battery change. still on charger and using wifi and playing around with apps.
i'll check in with news later.
cheers
I have the same issue.but my battery is original.
What I noticed that the phone stuck when I receive an update notification.
Can I stop softwsre to ask for updates? ???
Sent from my GT-I9100G using xda app-developers app
^go to settings, about device, software update and detick auto update. that should stop it from trying to self-update.
ok, so here is an update to my friend's phone status.
currently on hungarian 4.0.3. about 3-4 freezes/reboots a day. sporadic connection breakups during calls. also, when we talk i can hear myself back. this brings me to conclusion it has to do with modem firmware. i found this topic, so i'll try putting that and see what will happen.
if that doesn't solve anything, my question is this: is there any way of knowing which firmware/rom was originally put on the device, since i don't know the real background of the device? i.e. some way of entering IMEI and finding out what should be on it?
cheers
EDIT: tried KH3 modem, no changes... i could still hear myself while talking to my friend on that device. also, it froze couple minutes later. going back to 2.3.5-2.3.6 for now.
so after couple of months, i finally got my hands back onto this phone...
gave my friend my phone, so i could play a bit with this faulty one.
i have played with it for a couple of days now, and here are things i've tried.
i received it from a friend with 2.3.5 on it which had triggered custom binary counter. he's been using it for couple months without any problems.
so i rooted it and installed triangle away again... reset counter, cleared and flashed hungarian stock (telenor) 4.1.2... random freezes again.
tried several stock roms, mostly hungarian ones (4.0.3, 4.1.2). even reformatted with .pit file... random freezes.
reformatted again with .pit and put XXLSJ, installed stability test and let it run...
cpu stability test 15.5 hours no problems, no freezes. then i realized it didn't have a sim card, so i rebooted phone and installed sim card. let it test cpu+gpu for 9 hours... no errors, no problems, no freezes.
so i thought, maybe it's all fine? but it wasn't! as soon as i took phone into my hands and started going through menus it froze!
so i tried SGII_repair, rooted and did "repair"... but nothing changed... still random freezes.
if i just let it do the stability test, it'll probably work forever.
things i've noticed:
- serial number is wrong format (14 hex digits instead of 11 alphanumeric)
- during stability test, cpu frequency dropped from 1200 to 800 mhz (maybe because it was getting warmer? 42-43C during cpu only+charging battery, and about 39-40 during cpu+gpu test)
i tried to find out which firmware is latest according to serial number via kies, but it gave me error.
i know it's from hungarian market, but don't know which exact part of it (branded or not).
don't know what previous owners did to it, and don't have backups of original efs or anything original.
i just want to make it work, don't care much about custom firmwares. i'd be happy even with unrooted stock... just for it to work!
i have no ideas what else to do.
anyone?
finally, as i couldn't resolve the problem, i returned phone to 2.3.5 and sold it as is.
thanks to all people who tried to help.
cheers
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Daimao1984 said:
Hello, guys. First of all, I'd like to apologize in advance for my bad english. If there is any part of the message that isn't very clear, please inform me so I can correct it.
Here's the deal: I've been using for some time the Jelly Bean Ressuction Remix Rom from Westcrip.
Since about a month and a half (since version 3.9, I believe), I've been getting some weird and random signal drops. Back then, I had to manually reboot my phone so the data connection would come back. At the time I thought it was because the rom was still a nightly build, not very stable, so I coped with it.
This problem has worsen considerably since one or two weeks ago: those "signal drops" have become more and more regular. And following the signal drop, the screen would flicker a little and then the phone would automatically turn off. When I turn the phone back on, the battery is almost depleted, even tho it was full right before the crash. Again I'd blame the RR from Westcrip (by the time I was using the version 3.1.0). When version 3.1.2 came out, I did a clean installation (wipe data/factory reset/format system partition/wipe cache and dalvik, etc), even changed the kernels (used both Dorimanx and Siyah), a lot of modems, and still got this same problem: signal drop (usually when the phone is under a relative amount of stress, like playing Angry Birds, browsing the web, and even while using whatsapp!!!) followed by the phone turning itself off.
I then thought: what the hell, the problem has to be with the rom, not my phone. Then, I tried installing different roms (Paranoid Android and Slim Bean), and still got the same results. If anything, the phone is rebooting even more often now than before. I can't use it for 15 straight minutes and I get that problem,
Since this has happened with all these different roms I dont believe its related specifically to any of those.
Another strange thing: this "signal drop" followed by the rebooting only happens when the phone is disconnected from any power source and being actively used by me. If I'm recharging it, for example, the phone wont reboot at all. Also, if it is over my desk but I'm not using it, the phone also wont reboot. However, if I take it out from the power source and starting using it, I'll get another reboot in about 5-10 minutes of use.
I searched the forum and didnt find anyone with a similar problem... have any of you guys seem this happen before? I'm beggining to think that my phone is gonna die on me anyday now.
Regards!!
Click to expand...
Click to collapse
Hey,
pls backup ur apps and then do this:
0) Do a nandroid Backup via recovery
-- backup and restore
-- backup to internal (or external) sd card
1) Download Rom
2) Put it on internal sd card
3) Go into recovery mode
4) DO A FULL WIPE!! (U won't loose ur backup on sd card [but u can copy it to PC, too, if u want])
-- wipe data/ factory reset
-- wipe cahe partition
-- advanced > wipe dalvik cache
-- mount and storage > format data/system/cache
5) Then flash Rom
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Then flash Gapps
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
7) Recovery > wipe cache partition
8) Recovery > advanced > wipe dalvik cache
9) Then flash Dorimanx
-- install .zip from sd card > choose .zip from sd card
-- Select the downloaded Custom Rom and flash it
6) Reboot and u r done!
Links:
ROM: U should have already the newest one, or at least u know, where u find it.
Dorimanx Kernel
Gapps
Much success,
CHEERS
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Updating: I've been restoring my old nandroid backups for the whole day to see if the problem had anything to do with Jelly Bean. Well, I've gone back to the old ICS days and every version of it had the same random and constant rebooting. Even versions that didn't have any problem before.
I'm beggining to think I have a hardware failure of some sort. Do any of you guys know what could cause this kind of hardware failure? Since the phone has been getting hot for no apparent reason, it seems to me its a problem with the SGS2 cooler. Is that even possible?
OK so I have this problem but only when using my backup battery. (Not official). When It gets around 30% it begins to make my screen flicker and loose signal and just die.
So maybe you haven't got an original (official) battery in your s2?
Sent from my Galaxy SII
I dont think I have an unofficial battery. Its the same battery that came with the phone (bought from Amazon), and also, mine says Samsung on the back. Dunno if its enough to assume its official. Is there another way to check if my battery is official?
Daimao1984 said:
Hi, thanks a lot fot the help.
I did all the steps above and I'm still getting the same results...
Another thing to notice is that yhe phone gets really hot for apparently no reason at all (like booting up, running aLogcat and other minor apps), and when that happens, I usually get a signal drop (if the phone is plugged in it wont reboot, if its not, it will reboot).
Is there anything else I can try?
Click to expand...
Click to collapse
Do u check if u r using the correct Roms for u phone? (i9100, i9100p, i9100g,etc)
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
Hi I am also facing the same problem. Mobile is getting hot near the camera lens.
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
TheDigitalSlacker said:
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
Click to expand...
Click to collapse
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Hälftebyte said:
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Click to expand...
Click to collapse
Thanks,
I'll be doing that today. How can i tell whats waking it up? The wakelock detector i have been using isn't ready for 4.4 yet.
Turns out it was noon walk that was doing it
Sent from my SCH-I605 using xda app-developers app
Haha good. How'd you find out?
Sent from my SCH-I605 using Tapatalk
Hello people.
I have a problem device and I have post this under Tab 7.7 section, yet still no reply until today, and i decided to post here, in case anyone of you hv any idea on this.
Device : TAB 7.7 P6800
ROM : Carbon ROM build 12/12/14
ROOTED
CWM 6.0.3
Ok so I woke up few days ago to found out that my Whatsapp suddenly fc. And when i open it back, it shows that my chat backup are messed up and i need to restore it.
And while doing that, it started to reboot by itself.
I thought it will be okay after that.
It not.
It keeps rebooting, then Dropbox fc. Few seconds after that, reboot again.
power on, another apps fc. after few seconds, reboot again.
It keeps rebooting into the same state when i woke up that morning. Wifi turned on, few notifications on panel, (thou i keep clearing it everytime when it power on)
Now ive tried wipe data , wipe cache, everything in CWM. but it keeps rebooting into the same state!
Ive also tried flash with stock rom via ODIN.
Guess what?
It appear PASS on ODIN, but when the tab powered on, is still went back to the previous same state.
Ive google around and some said it is the sign of memory flash fail or smthing.
anyone maybe could tell me what am i dealing with here?
im on dead end.
THANKS