My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Did you have any undervolt settings applied?
The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago
Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!
himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?
okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?
bump! really need help with this guys!
Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse
It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed
I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.
Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.
Hello Peeps,
I was trying to flash a rom yesterday and had something strange happen to me.
The rom featured Aroma installer and I had flashed this particular rom roughly 5 or 6 times with no issues.
Yesterday, I did a full wipe and tried to do a new install of this rom.
There was an option screen in aroma that allows you to choose your own mods and features or use the developers defaults.
I was on this screen trying to choose the developers defaults option and Aroma simply froze up.
It would not let me choose with version to flash.
The touch screen wouldnt respond and I didnt know what to do.
I searched google and found nothing.
I decided to do a battery pull.
I know that a batter pull during a flash is something we should never do as it will brick our phones.
In this case, as the flash had not actually started yet I decided to try it.
I pulled battery and booted into recovery and was able to restore a nanroid.
I am just curious if anyone else has had this issue?
How dangerous was it to pull my battery?
Could I have bricked my phone?
Phone has been working just fine, I am just wondering if there is another way to resolve an issue with Aroma like that?
Thank you,
I never had that problem as for the pull battery it is fine as long as you're not flashing.
I was installing a ROM on my sister's s3 when the aroma installer completely froze. I pulled the battery and it boot looped but wouldn't go into recovery until around the 10th or so time (vol up + home + power). Flashed it again and it worked fine...really weird.
As for bricking your phone I agree with above poster, it should be fine if you aren't flashing anything.
Sent from my SCH-I535 using Tapatalk 2
I've had this same issue happen a couple of times. It usually happens when I try to install the Jelly 'Beans' rom...sometimes it will work, sometimes it will freeze. I usually have to do a battery pull and recovery will come right back up. I've noticed this seems to happen the most when the phone has grown hot...so maybe it has something to do with RAM, etc.
I have a verizon S3 on MB1 it was rooted on beans for a while it worked fine. Got a new phone and my girlfriend wanted the S3 so i odin restored it back to stock verizon MB1. The phone rebooted earlier today and now its about every 5-10 mins i found a different stock verizon odin file and restored to it still reboots randomly so now im going to try and flash beans again to see if it works like it did before anyone have any other options the phone seems laggy and locks up at random times and if it randomly reboots more than 3-4 times it tries to reactivate again which makes it sit in the activation screen and it continues to reboot until i boot to manual stock recovery and wipe data. Also no apps are installed but the verizon factory ones
New Update: I rooted/unlocked/ and installed beans rom now it locks up black screens and reboots any help would be great thanks guys!
I would boot into recovery, factory rest, wipe dalvik, and wipe system. Then flash MF1, as MB1 is outdated now.
Sent from my Last Ever Samsung Device.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed