It is ok yesterday.
And I installed about 10 apps today and found that it will reboot if I lock the phone (the screen goes dark).
I don't remember the name of those apps.
So, how can I find out the problem of the certain app?
Must I uninstall all the apps to find out the problem?
THX!
If u go to the market and download a app called (instant uninstaller) it lets u choose to show the apps by date installed
Sent from my ADR6400L using XDA Premium App
thx！ let me try it.
So did this fix your issue? I am having the exact same problem.
I'm rooted (using ADB method), running Das BAMF 2.1 with Imoseyon's 2.54test4 kernel .
I can reproduce the a reboot everytime by doing this:
1. With the phone unplugged from the charger, press the lock button so the screen goes off. Once the screen goes off, in about 10 seconds it will reboot everytime.
2. Or, if I leave it set and the screen goes off by itself, it will reboot in about 10 seconds (after the screen goes off) everytime.
If I leave it on the charger, or never let the screen go off, it has never rebooted on me. I got this phone 2 days ago and have been battling it ever since.
UPDATE:
I have eliminated the following as a potential issue.
1. I wiped everything and flashed a new ROM, Kernal, and Radio, and still the exact same results.
2. I tried a new battery, and still the same results.
3. Tried two other kernals with each of the two ROMS, and still the same results.
Out of ideas at the moment.
Thinking of trying to flash back to stock so I can see if it still does it then.... Lost.
Solved my problem for now. Here is what I did.
1. Flashed back to these radios
CDMA: 1.13.605.7
LTE: 1.12.605.6
2. Flashed back to Froyo based ROM, Das BAMF 1.8.
Of course, I wiped everything before doing so. I've been up for about an hour now with my phone resting comfortably with no reboots at all.
Will try again in a few days to flash back to a gingerbread based rom, as I would really like to have Netflix.
If anyone has a gingerbread ROM and radio combo that they have working well together please let me know. You might also shout out which kernal you are using too.
UPDATE:
So I have obviously done some more troubleshooting on this, and I may have something to make sense of.
Since I flashed the GB MR2 radio and ThunderstickGB rom using the kernal provided with it. After bootup, I again had the reboot issues everytime the screen timed out or was locked. Just like before, It would reboot everytime unless the screen was kept on or plugged in to a charger.
I flashed back to the original Froyo radio just to see if that would make a change. Of course, I had no signal, but it would at least tell me if it were the newer MR2 or MR2.5 radios giving me fits. Even with the original radio, it still gave me the same reboots on screen timeout or locked.
So, I started over and this is what finally worked:
Flashed MR2 radio and ThunderstickGB rom again. This time, I flashed the stock GB kernal, instead of using a modified one. Bingo.... no reboots at all.
My feeling is that for some reason, some of the Kernals are undervolting the unit to a point that it shuts off or reboots. I am completely technically illiterate when it comes to the inner workings of Kernals and such, but the one common demoninator between my working Froyo and GB roms was that there was no Governor or Speed Tweak controlling the processor other than what comes in stock form.
Oh and by the way, thanks for eveyone's help with this.... I couldn't have done it without you.
Related
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Ruwin said:
My O1 shuts down every few hours by itself. As everybody told me, i removed the sd card to see if that is the problem, but it still shuts down. Al this "shutdown frenzy" started after i flashed the first custom rom, Void.
I flashed back via nand recovery, i did all possible stuff, but nothing. As i tried reinstalling the original firmware i found out that i coudnt, theres no firmware for Romania, and the KDZ crashez on my machine...
Any suggestions on this one?
Click to expand...
Click to collapse
Strange... it's really hard way to resolve, but what about some logging on SDCARD? Problem is that it can be really huge file. And Murphy law... it definitely will not restart for many hours...
I just bought a class 6 sd card, i'm testing it, maybe it's the card that shuts down the phone... i'll post the result tomorrow.
Lol man , I have the V10B for romania . I can give it to you on messenger if you add me : zerobarat1 .
Cheers
I had void with gapps, gingerbread, kernel, a2sd, blink, tapps folders on sd. Then I flashed milk_os kernel. Everything was fine.
Then I created stage fright and hwacc folders for quadrant testing. Something happened my neocore score was only 9 fps (though quadrant was 1100). I deleted stage fright, hwacc and kernel folders. Phone was fine again. But was going to sleep of death after some time of non usage. Didn't reboot even from power button. Had to take put and reinsert battery.
So I created the kernel folder again and rebooted. Went into recovery again and applied milk_os kernel again and rebooted. Everything is fine now.
Something remotely similar happened to me a while ago. I found the phone turned off without any particular reason and it refused to power on until I removed and reinserted the battery. It had me worried, but fortunately this didn't happened again ever since.
My problem seems unsolved. I also found my phone dead two times again only in last 4 hours.
Guys any solution. I have void with a2sd enabled and with mik_os kernel 1.1
Did you have the same problem when you were on stock? It might be a physical fault rather than the rom. Also, I believe the latest void already have mik_os kernel 1.1? So there was no need to flash it again.
a2sd maybe? I read quite a lot of issues with that thing.
Miks kernel 1.1 has some scrolling bugs, flash 1.0 and maybe problems solved
I applied mik_os v 1.0. Now everything seems ok for last 16 hours. Will notice further.
Everything ok till now. May be it was something related to mik_ os 1.1.
With 1.0 problem seems to be fixed as of now.
Try dev kernel v3, it's enhanced version of mik's v1.0 kernel
Sorry to say, but this damn bug stroke again. I just found my phone dead, unwilling to reboot unless I took out the battery (which, by the way, was 94% full).
I'm using void #alpha with a2sd and mik_os kernel 1.0 and I don't have the sdcard unmount problem. I can't tell if this also happens on stock ROM since I don't intend to go back to stock ROM until LG rolls out the 2.3 version.
Waiting for some stock ROM user input, but my guess is that this is hardware related.
Any help?
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Hit the search button on phone and if search screen appears, type settings in it. If you are able to reach settings, you can do everything from there. Try playing with the search button on the phone.
If this does not help, you will have to do a factory reset. You can do a factory reset by the pressing the combo of home + vol down + power on buttons if you are on stock rom. If other rom, do via recovery.
winnie34 said:
That happens to me all the time!! I took it to LG center and they said it's because of software problem. Anyway, now my phone has one problem. I accidentally made the locker apps to make default screen and it totally black out my home screen. I can't access to my setting to get rid of this apps or can't make even calls. I tried restarting again and again but it doesn't work. How can I uninstall the apps on phone storage by using PC? Or any better way to solve it. I'm a beginner to Android. So, please kindly help me. It is so annoying.
Click to expand...
Click to collapse
same here too .... (when the phone turn off the screen automatically...or auto suspend...is the same) i have the #echo and .... i have the random power off and... some times... it keeps on the boot loop when it supous to suspend... butn when i suspend the phone whit the power button ... the phone keeps working fine... i dont know what to do... XD
I got the class 6 SD and since then i had no problems with shutdown. Though at the time i'm writing, my O1 is at service. It seemed that the shutdowns are related to the sd, even if you don't get any unmount errors. My logs say that each time the phone shut down, it was trying to access a service from the sd memory, and, guess what, there was no sd! So it closed all the services.
could it be unmounting sd card?
After a long time of checking how to fix this, I, finally found it.
I had this error several times, and, I always tried to check where it was the error. I did a factory reset and, suddenly this error stopped. But I needed to know exactly by "doing what" this error appeared.
This error appears in one of this two:
- if you dissactivate the "rotation" in your phone.
- if you dissable bluetooth in your phone
One of those two. If I dissable this two, my phone, in about 1 hour, it suddenly shutdown. But inmmediatly if I enable this options, its stops to crash.
You can toogle this options with the "battery" widget in your phone.
I hope this will help you, as it helped me. Plz, tell all the ppl about, how to fix this.
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
First let me talk about how I got into this mess. I had used the thunderbolt as my phone previously and had rooted it, installing custom roms often. After getting a new phone, I decided to unroot my thunderbolt and give it to a family member. At first, everything was working fine; I had no problems unrooting the phone. However, a month or so later it started having problems.
Upon booting, the phone goes straight to hboot where it displays a security warning. But this only happens occasionally. Sometimes it will actually boot but take about 20+ minutes to start up where it come to the homescreen with a solid black background, soon to freeze and turn off.
I have tried fixing the phone based off methods others used to fix similar issues, but to no avail. For example, I have tried flashing the 2.11.605.19 firmware through hboot only to have the same problems occur. Perhaps I did not use the right version. Do you guys have any idea on how I can fix this? Could flashing an ruu (if there is one) for the latest ics build solve this?
When I try to unlock the bootloader through htcdev, everything works fine up until the confirmation screen on my phone asking if I want to unlock the bootloader or not. For some reason, the power button won't work to press yes. It does work normally for saying no and everything else though. I have tried using the adb to force it to use the power button, but in its "unlock the bootloader" state it isnt connected.
some relevant info for the phone:
hboot version - 1.05.0000
radio - 1.49.00.0406w_1 - should be the radio from 2.11.605.19
I'm hoping someone on here can help me. I've had a few lingering issues that I can't seem to resolve. I run AOKP, but at this point, I may go completely back to stock to see if the issues resolve.
- The main issue is the random freezes on boot. It is really random, but definitely has gotten worse over the past few months. Basically, the phone freezes at the first boot screen about 60-75% of the times I reboot. I've had to pull the battery sometimes once (if I'm lucky), and sometimes 3-4x, just to get it to boot past the Samsung screen. This is compounded by the second issue I'm having:
- Loss of data. Actually, more specifically, it is data not coming back when I leave a no-signal area. I live in a no-signal area and depend on a VZW home tower. I don't get a solid signal until about 2 miles out from my house, just after I leave the neighborhood. After I clear the area, I get a strong cell signal, but data never becomes available. Toggling mobile data or cycling airplane mode does not resolve it. I have to reboot, which can bring me to the stuck boot screen, where I'm pulling my battery to get back up and running (often when I'm driving... which really sucks).
This weekend, I wiped the phone as fully as I could. I don't believe I restored it completely to stock, as the phone still showed the unlocked icon when booting. I did, however, restore the phone to the stock MDK ROM, re-rooted, reinstalled TWRP (through GooManager), and reinstall the 11/14 AOKP ROM. It did not seem to help.
Shortly after wiping the phone, I was 99% sure I had figured out the boot issue. For some reason, I got the idea to pop out my sdcard while it was stuck at the boot screen. As soon as I popped the card out, it moved past the Samsung screen and changed to the Google "X". The card was a SanDisk Ultra 32GB, which some people have had dismounting issues with, so I thought I hit the jackpot. I tested it several times, and as soon as I popped the card out, it would start booting each time.
I was excited when I hit the road this morning. Unfortunately, the data bugged hit me as soon as I got out of the neighborhood. As before, I had to reboot to get it back. That is when it stuck on boot again. I did not have an sdcard in, though. It took for cycles of pulling the battery before I finally booted up.
I'm stuck. I really don't know what else to do. I've tried every ROM/radio/kernel combination out there, except for bone stock. I used a combination of different guides to get as close to stock as I could, but I still didn't get there. I'm sure I missed something, but I'm not sure what. The steps I took to restore are below.
Is there a PIT file I can use to repartition the phone? I know that is frowned upon unless the phone is completely bricked, but I don't know what else to try. Just from experience, I'd doubt it's a hardware issue... but who knows:
Steps I took to "restore" phone:
- Flashed SCH-I545_MDK_562219_Stock_Restore.tar.md5 in Odin
- Rebooted, then went back to Odin to install MD2 kernel
- Booted into stock ROM, enabled dev options, USB debugging, etc...
- Rooted, rebooted, installed GooManager
- Installed TWRP through GooManager
- Installed 11/14 AOKP, gapps, faux 0123m, and MJ7 radio
Hi all, hoping to get some help. I rooted my phone the other week and was using viperrom. I had no problems whatsoever, no glitches that I could remember. That is, until I decided to trade my m8 with a friends Note 3. I factory reset it and give it to her, I left the viperrom on because she didn't mind but then the glitches started to happen. The onscreen bottom 3 buttons disappeared for her (home, back,etc.), So I reset it again but the problem persists. I searched for an at&t stock rom and sideloaded that after master resetting, wiping the dalvik cache and all that... now a different problem popped up. It hangs at the HTC logo for what seems like forever, but then I noticed the volume up and down make a noise as if the phone is loaded up. I pressed the power button a few times and eventually the screen turned on and I could see the home screen. This happens every time I restart the phone and I have tried reinstalling the stock rom a few times. I am now in the process of trying a different stock rom.. the first was odexed and this new one is deodexed, I dont know if that makes a difference in my situation but does anyone know what could be causing this? Any help would be appreciated.
Nvm, after a few more master resets it seems to have sorted itself out... not sure what it was but its gone now.
If its the latest version of Viper, based on 2.22 software, you need to update the firmware package, otherwise the long boot times will continue.
Details here: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592