Hello!
I own a Galaxy s3 GT-i9300, android 4.3 (currently).
I rooted it, and then installed cm12.1 on it. It worked great for some time, and then one day, it suddenly froze, and after some seconds it rebooted. After it successfully booted, it got stuck, and rebooted again. It kept doing that until I decided to shut it down.
I booted the recovery (TWRP), and the same thing happened over there.
when the device was shut down, it didn't boot up suddenly, which means it's not the power button problem. I think that its a hardware problem, because it looks like the CPU or whatever it is gets overloaded. Or could it also be a kernel problem?
Its twrp or the rom causing it.
Flash back to stock and start over. Here is my collection of useful stuff for the btu variant only https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
Sent from my HTC One M9 using Tapatalk
ghsucbyuc said:
Hello!
I own a Galaxy s3 GT-i9300, android 4.3 (currently).
I rooted it, and then installed cm12.1 on it. It worked great for some time, and then one day, it suddenly froze, and after some seconds it rebooted. After it successfully booted, it got stuck, and rebooted again. It kept doing that until I decided to shut it down.
I booted the recovery (TWRP), and the same thing happened over there.
when the device was shut down, it didn't boot up suddenly, which means it's not the power button problem. I think that its a hardware problem, because it looks like the CPU or whatever it is gets overloaded. Or could it also be a kernel problem?
Click to expand...
Click to collapse
Samething happened to my device I am flashing the fully Stock Firmware to see if all ok, I dont think its going to be a Hardware issue Because I can boot to download mode successfully.
Related
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
MatWho said:
Hello everyone!
I have a Lenovo a820 with Lambda rom 2.4v.
I'm using it for a couple of weeks now with this last version, and everything was fine, until suddenly it froze for a while, I unplugged the battery and plugged it again, and what I notice was that the phone restored itself to when after I installed the rom (meaning all of the apps were gone).
So I tried going into Google play, installing some apps back, and I get this error -24 telling me its unable to install the app, happened with any app I tried. so after trying a few suggestions from the internet about this error, I decided to format it and install the rom all over again.
I go back to recovery mode with CWM, try to install the lambda rom like I did before, and in the middle of the installation it reboots and gets stuck in the "lenovo" screen like when you boot it. so after waiting for a long time I unplugged and plugged the battery again, went through the procedure again this time it installed it 100% rebooted so it would boot with the mod, and again, it freezes at "lenovo" start screen unable to boot.
went on recovery mode, formatted system, data, emmc, everything... I think that's the issue here. but im not sure.
After that, tried to install again with the same problem.
The problem now is. it won't even start I press the on/off button to start it normally, and I dont even get the "lenovo" screen, I tried going into recovery mode and no luck.
It's like the phone is dead! Although I have another Lenovo A820 and I tried the battery, and its 60% so that's not the battery.
Do you guys know any tricks? or any tools that I could use to get my phone running again?
I would appreciate it very much, any help you can give.
Matt.
Click to expand...
Click to collapse
The boot.img must be wrong try rom for your phone.
Sent from my Moto G
Started two days ago. Phone would randomly power off and boot back up. Finally it shut off and would not power back on. I had Cm11 installed with CWM 4.0.4.6. The phone powers on after inserting the battery. The Samsung logo flashes and then it shows the "Galaxy S3" logo with the CM logo below it. The phone the powers off. I have done a factory reset, cleared both caches, formatted the system folder, flashed SlimKat from recovery and tried another known good battery. At this point I figured I would reflash CWM but if I put the phone into download mode, it powers off after just a few seconds as well.
If I boot the phone into CWM, the phone stays on as long as I want it to so it makes me think this might be fixable. Just need some help.
Ask in your device forums.
My apologies. Didnt realize there was another S3 board. Found and posted there.
Soo... I have a S2 and S3. I use the S2, today I woke up for my phone freezing on Samsung Logo. I tried booting Recovery, froze on Team Win logo, so I guessed that something is the software went wrong. I decided to flash some Recovery from Odin and boot into Recovery. I Googled, downloaded one recovery, flashed it via Odin, didn't work, tried another one, didn't work, I would put out the battery every time between tries. And boom it wont turn on, only gets warm in the camera region. So I tried all the combinations of putting it the power with and without battery, pushing all the button combinations etc. I told myself I'll deal with it later, need a phone right now. So I used a spare phone my brother game me, an S3. It had a stock ROM and I wanted to flash JB on it. I rooted the S3, downloaded TWRP for Odin, flashed it with Odin, it didn't work, it booted me to a stock recovery, so I rebooted the phone, it went to Samsung logo, I removed the battery to go faster to Download Mode and try something else, and it wont turn on. What happened and what can I do to fix that? I really need a phone for tomorrow. Please help.
Hi guys,
first of all thank you for taking your time and reading through this. I'm not completely new to android, nor using fastboot and recovery. I flashed a few phones over the past years I even resurrected bricked ones. However I have no idea what is happening to my Honor 8. One thing to mention, it's the latest Nougat update, and a STOCK ROM.
It all started this afternoon. The phone suddenly reboot while using it. After that, the android screen came on, then Honor animation and.. freeze. Completely. I had to reboot using the long press method since it was stuck between the bootloader and the rom itself. It started up ok after that.
An hour passed, and while I was typing a message, it froze again. I could go back to home but the phone was really slow. After opening up Messenger again, it froze completely. Had to restart again with the long-press reboot method. It started up ok, entered the sim pin and upon entering the screenlock code it froze again, completely. Long-press reboot, again.
Since then, the phone won't boot. It gets stuck every time on "Honor powered by Android" for about a minute, then it reboots itself. I even got some weird green screen with a blue and a red rectangle, but that just stopped after a few reboots.
I mentioned that I know how to recover and fix stuff when something acts weirdly, but that's not the case, I can't do ANYTHING. No fastboot, no recovery, no button combinations, I can't even turn off the phone. It just keeps rebooting on and on, and yes, the battery will eventually die, but I have no access to any recovery options. I even tried dload but no luck.
It's still under warranty so I can send it back but I just rather fix it at home (without taking it apart), because I don't want to wait 3 weeks to get fixed. But it seems like that is the only option right now, I have never ever seen anything like this happen.
Any help or comment is appreciated. Even if it's not possible to do it at home (hardware issues?), I am really curious what can be the cause of this issue (damaged rom, filesystem permission issues?).
Thanks.
Hi guys, i need help.
was using my phone this morning and suddenly it restarted itself.
the phone passed through boot icon and went to "almost" into launcher screen.
my phone is rooted and thought that it might be due to software, hence i flashed stock firmware into it.
so now it is in stock rom and stock recovery.
but the phone still restarts.
it will still pass through the boot icon and since it is fresh installed, it goes to the setup screen, but from the the phone restarts again.
it seems like it restarts everytime it finish boot.
thinking that it might be screen issue, so i go into (stock)recovery mode, i try to navigate around in it by going to wipe phone, install from storage, and the phone doesnt restart.
please advise what might be the cause or issue since i had already flashed stock rom, so i guess rom isnt a problem, and phone doesnt restart when it is in recovery mode...