Hello everyone,
Please help me solving this problem:
My X10i always stuck in boot loop whenever connect to 3G.
I've tried different SIM, ROMs and Google it but still no solution
Thank you!
Still no help?
Waiting...
I have a similar problem with my phone.
Regardless of the rom I'm using, my phone will go into a boot loop. Anywhere from 3 to 10 times before booting fully.
It doesn't seem to be any particular app or action and I don't use a task killer. Sometimes connecting to 3g will crash my phone and boot loop; other times it's attempting to delete an app or replying to a text message. Any sort of daily use can cause my phone to crash into a boot loop, which is usually remedied by taking my battery out, waiting, and putting it back in again. I'm fairly certain it's not an over heating issue because the battery and phone don't feel hot to the touch.
There seems to be no way to know when it will crash, however, it is more likely to do so if it's charging or I have my headphones in.
I've had this problem while using WB 2.2 rom, WB 2.3 rom (all versions) and EWjet 2.3 rom. I've Formatted everything I can, including the SD card.
I'm currently on a fresh install of WB 2.3 v3 and still getting the boot loop issue. This only started happening a month or so ago, so I'm beginning to think that this is a hardware issue and I may need to get my phone replaced.
Other information, I'm on Rogers and have owned my x10 for a little over 1 year, BaseBand 2.1.71, Kernel 2.6.29-00054-g5f01537, Build Number 3.0.1.G.75
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.
<testing J's CM7> [Q] Constant rebooting; was annoying, now critical - X10 unusable
So I had an occasional spontaneous reboot problem which was annoying and inconvenient, but not crippling. Then I thought I'd fix it by upgrading my ROM.
Turns out I have no idea how to get xrecovery going (tried install through flashtool, through apk, etc., but no matter how many times I press "back" during the boot sequence, the SE logo always shows up to ruin my day) and that ruled out any newer, better ROMs.
So I used SEUS to "upgrade" back to 2.1.A.0.435 - still shaky.
This morning I tried the tweaks listed in the guide to flashtool (clean, optimize, etc.) and deleted every app that I don't think I need, but since I went to work, the battery has run out due to constant booting.
Sometimes I can check my SMS, and sometimes the screen turns on only to go dark for another reboot.
What can I do??
--EDIT--
So I got into xrecovery, now I must find a suitable ROM and cross my fingers...
--update--
11PM EST Mar 8: J's CM7 RC1 is running well so far, but I'll update after hours and days have passed.
10AM EST Mar 9: It has been running smoothly (and is a nice upgrade), but I've seen one spontaneous reboot
However, one is a lot better than every 5 minutes!!!
9:30AM EST Mar 15: I get a shutdown a few times a week, but I'm worlds better than before. GB is sweeet!!! Gonna wait for release 10 to upgrade.
Thanks J!!!!!
(and all those, such as Z, who made this ROM possible)
If I'm not the only one who failed to get xrecovery right, reply and I'll try to help!
Yea i've been having the same issue too, i found that it would reboot almost every 5 minutes when using the phone when i plug it in. especially when streaming youtube videos.
I tried multiple roms and also went back to stock rom by doing a repair. I was playing around with the fresh repair install and it is still rebooting.
Hopefully you have better luck with your device. I'm taking mine to rogers soon for a replacement.
I could find no pattern to my reboots. Sometimes I could use the thing for a while, and other times I'd hardly even see the screen before it quit.
I'm hoping FW is the answer because I got it used, so there is no hope of repair if flashing doesn't fix it...
I'm experiencing this reboot from J's latest CM7 rom with the custom kernel. Every 3 mins or so and the screen turn dark, no idea what to do.
zazazombie said:
I'm experiencing this reboot from J's latest CM7 rom with the custom kernel. Every 3 mins or so and the screen turn dark, no idea what to do.
Click to expand...
Click to collapse
Hi, try this guide, maybe it's helpful to you....
http://forum.xda-developers.com/showthread.php?t=1073859
Sent from my X10 using XDA App
michaeljordam said:
Hi, try this guide, maybe it's helpful to you....
http://forum.xda-developers.com/showthread.php?t=1073859
Sent from my X10 using XDA App
Click to expand...
Click to collapse
I got it by installing the older vers of miniloader from the custom kernel dev thread but thanks! I'm doing a fresh install again with the instructions from the thread you linked.
I've had ENOUGH!Now I can't even charge it.It turns off after 5 minutes of recharging and then the battery discharges because of the constant reboots.So I've decided to try and start flashing and stuff(install custom roms).
Dfan can you please give me a few advices,pointings , etc... for what am I about to do?
Thank you for your time.
@OP, from what I have understood from your post, your phone has a fault before you have 'updated' using SEUS.
Try the 'repair' function in SEUS to restore everything into factory settings?
dude, stop using j's ROM till he fixes it. I recommend Trip's GB MiUI. make sure your phone is fully charges when installing a new ROM, or else you'll get boot loops, and FC's. once you have your xrecovery installed(I recommend manually install it) you should never have to reinstall it, unless you use SEUS.
Sent from my X10 TripNMiUI using XDA Premium App
Hi to everyone..well..as the title says my phone keeps freezing after seconds it boots. i was on PA v3.6 and decided to flash the newest release so i did.. after that it's been only problems. i did the wipes, but it constantly freezes.. so i decided to go back to stock and try again.. so i did with odin, but it keeps freezing even when the first settings pops out. i don't even install any apps. it just freeze, even if i reboot the phone and leave it to deep sleep i find myself with the same problem. i've been flashing custom roms since i bought the galaxy s1 and i never had any problems. i tried the dummy file thing but it keeps happening. does anybody knows how can i fix this?
Freezing is usually the memory controller working around bad memory blocks. Try reading the 'unusual freezing' thread in the general forum.
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!
So, since the past few days my i9300 keeps randomly rebooting. At first it was not that much of an issue but today it started to go into a boot loop.
Sometimes it finishes booting but before I can go into the settings to factory reset it, it crashes.
I also tried to get into TWRP but as soon as the logo shows up, it crashes.
I can't even use the download mode because, guess what happens: it crashes.
I really don't know what to do right now. I still have a spare motherboard but I'm not able to access it for another week. It would be a shame to throw away a perfectly fine motherboard if it is just a software thing.
Currently it is running the last version of SlimKAT that was released, I don't know which version of TWRP it is running, but I updated it just a few weeks ago. It is not using the original battery fom Samsung but one from Anker which should be fine.
If anyone needs more or specific information, I'm more than happy to provide it.
Hi,
just want to ask, you're stuck in bootloop at the "samsung" Logo or where?
Because I am having bootloops, too since 2 days. Phone kept restarting one or 2 times since last 3 days and when i got home on 1. november i put my phone to the charger and got back 20min later and saw it was rebooting.
Mine is stuck in optimizing apps or if i wait long time then it is at starting android: starting apps and i see when the color temperature of the phone changes (i think of the light sensor) it gets stuck and reboots.
just for docu (even if its not the same problem):
i have a 2nd spare s3 for testing here and to test ag. hardware issue i made a twrp backup and both are dying. after facory reset and installing apps i recognized that it is dying at the installation of telegram app and after that its going to the same bootloop on both phones. i checked telegram and seems to fit in, they updated their app at 1. november. and date code of last changes before the bootloop: telegram was modified. so for my problem it seems to be caused by telegram.
I am using bliss rom 6.1 (Andoid 6 Marshmallow, CM13 based) at i9300
sorry for maybe not beeing a help. I now found out that it happens to other app installations, too. so seems to be a problem deeper in android/interfering with this specific rom - maybe its play store . So far since it happens on 2 identical s3 with this rom I will have to change the rom now. :crying: (was stable >1year)
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Niggyminator said:
It is stuck on the Samsung Logo. I've been testing multiple ROMs for stabillity because after some time it will randomly crash (most of the time after 2 - 3 weeks of usage) but it was never this bad. I thought it was due to the fact that newer versions of Android need stronger Hardware, so I switched back to KitKat.
But Telegram could be a reason for this. I too use it and if you say they updated it, the timeframe would match.
I know that my spare motherboard is fully functional, with stock rom, not rooted or anything. I will swap it out as soon as I can and will install Telegram to try to confirm that this could be the reason.
Click to expand...
Click to collapse
good luck!
But if you'r stuck at the samsung logo, sounds even worse than mine. if your having a new board could at least be an option to check if its really not a hardware issue (you mentioned that its getting again unstable after some time)
for my problem I managed to backup most things out of the nandroid image and moved to ressurection remix with android nougat. the new rom is running fast and so far without any problem - hope it stays like that .