Hey all, having a very odd issue here. I flashed Flinny's 4.2.1 AOSP rom a few days ago, worked absolutely perfectly, today when I turned the radio to use 2g for an app I was testing then rebooted it just bootloops constantly. I have tried wiping/flashing the same rom again, a build of CM10 and another rom in the forum (a sense build), same issue on all, it boots to the welcome screen on AOSP and CM10, and to the home screen on the other rom, then just reboots. I flashed AOSP again without gaps and managed to get to the home screen, I enabled aeroplane mode and it is absolutely fine (as in it doesnt reboot), then if I enable a data connection it just reboots as it had been doing.
Anyone else experienced this as I cant really pin it down to be anything other than a radio issue, even though I have not changed radio image.
This is the link for the logcat, initiated when I disabled aeroplane mode to when the device reboots. http://pastebin.com/R6SpZwWz
Any help very much appreciated.
Cheers
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.
Hello!
A few days ago, I used CM12 Unofficial with Android 5.0 and ArchiKernel, and it worked fine. While I was using it, the phone turns off and reboots. Showed the "Samsung Galaxy SIII" logo and rebooted, in a bootloop.
I flashed the rom back, wiped all, and nothing, the bootloop still happened. I flashed it with Odin, to Android 4.1.2. The phone works, but when I use it some minutes turns off and goes into a bootloop. When I run an Antutu Benchmark also turns off.
Researching and playing with kernels, adb, and roms, I discovered that turns off when the processor runs at over 1200MHz. This happens with every kernel, also stock.
What happens and how can I make it work normally again? Thanks
Click to expand...
Click to collapse
The problem was the battery. After changing the battery the phone worked fine again.
It's obviously a hardware fault, you can't fix it.
I have a Moto E first gen, i keep getting bootloop, i've already tried lineage and stock rom, the phone works normally but in a day or two apps start to fail and after this when the phone reboots it gets stuck in bootloop, what is weird is that i went back to stock, flash all the motorola stock files with adb and the phone was working i even turn on and off several times and there was no issue, then again today whatsapp was crashing i reboot the phone and now is in bootloop again. Do you think it could be a hardware failure?
maujavier91 said:
I have a Moto E first gen, i keep getting bootloop, i've already tried lineage and stock rom, the phone works normally but in a day or two apps start to fail and after this when the phone reboots it gets stuck in bootloop, what is weird is that i went back to stock, flash all the motorola stock files with adb and the phone was working i even turn on and off several times and there was no issue, then again today whatsapp was crashing i reboot the phone and now is in bootloop again. Do you think it could be a hardware failure?
Click to expand...
Click to collapse
Flash stock KitKat or marshmallow ROMs
I'm getting the same problem here... in two or three days after ROM installation it gets stuck in a bootloop... I tried stock rom, lineageOS and Mokee... same thing happens every time.... Now I'm downloading the Official Pixel Experience and going to see what happens. I'll update here after a couple of days.
rafaelmaltez said:
I'm getting the same problem here... in two or three days after ROM installation it gets stuck in a bootloop... I tried stock rom, lineageOS and Mokee... same thing happens every time.... Now I'm downloading the Official Pixel Experience and going to see what happens. I'll update here after a couple of days.
Click to expand...
Click to collapse
So, it's been two days since I installed Official pixel experience and the ROM is great! But the problem persists...just now my moto e got into a boot animation loop....
Same issue
I am also facing same issue. From 6 months. I am on lineage and also tried Oreo ROMs. I think our device is old now and can't enough to handle nougat , Oreo ROMs.
I am now thinking to bury it in grave yard with respect.
Solved
So people,
I was reading an article on the forum, later I'll put the reference here... but it was about moto e rebooting... and that was a problem tha I was also facing. The explanation was that moto e first gen has a phisical problem on the power button, so the solution to avoid constant rebooting was to activate volume keys to be used to turn on the screen and activate the option to double tap the home button to turn off the screen. I did it and the rebooting problem was solved and it's been six days and I got no bootloop this time. I don't know how to explain but I think that the power button problem was related with the phone getting into the bootloop...
It's not about power button
rafaelmaltez said:
So people,
I was reading an article on the forum, later I'll put the reference here... but it was about moto e rebooting... and that was a problem tha I was also facing. The explanation was that moto e first gen has a phisical problem on the power button, so the solution to avoid constant rebooting was to activate volume keys to be used to turn on the screen and activate the option to double tap the home button to turn off the screen. I did it and the rebooting problem was solved and it's been six days and I got no bootloop this time. I don't know how to explain but I think that the power button problem was related with the phone getting into the bootloop...
Click to expand...
Click to collapse
We are already using volume button/ double tap for power on/off but lineage ROM causes this issue at anytime.
praveen139 said:
We are already using volume button/ double tap for power on/off but lineage ROM causes this issue at anytime.
Click to expand...
Click to collapse
I forgot to mention. I flashed stock rom via ADB Fastboot, reflashed twrp, and after that I flashed LineageOS14.1 and gapps via twrp, maybe this was the real issue. It's ok now. Today I'm instaling aosp extended to see how it works, and I'm going to flash the stock rom again before doind that
I woke up with a black screen and unresponsive I soft reset and booted back up just fine, fast forward 2 days, apps are constantly crashing and often seemingly randomly the phone will restart and go into a bootloop anywhere from 1-5 minutes before it finally boots. Sometimes I get lucky and can use my device just fine for a few hours, then apps will crash and stuck back in bootloop.
I have factory reset in recovery, and also flashed latest stock rom via odin, I am new to this and this was my first time I might add, it passed but it hasn't resolved the issue, is there anymore steps with odin or anything else I can do to repair this? The device isn't rooted if that helps.
I think that's a motherboard issue
You could try installing a custom rom