• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root MikG Infinite Reboot

ndh777

ndh777

Android Expert
I'm wondering if anyone else is having this problem.

Yesterday, I was playing around with my girlfriend and gently threw my phone on the bed. It wasn't even hard enough to make a sound or to even move the bed. But when I came back a short while thereafter, my phone had rebooted. I just thought that was what happens sometimes because all of my Evos have done that whether they were rooted or not. But then it seemed to be stuck in the reboot. It would reboot again and then again and then again with that "MikRoms" boot screen with the rain and roadrunner. So I took out my battery, let the phone sit for like 30 seconds, then put the battery back into the phone and it was fine. So I thought that was the last of it until this morning.

I wake up and go into the shower and when I come back my phone is rebooting again. I take a close look to see if it just decided to reboot on its own or if its doing another infinite reboot. Sure enough, it is doing an infinite reboot. So I took out the battery and put it back in and now everything is back to normal.

But I'm worried that this may happen again and again. And I'm wondering if this is just an issue with my phone or if anyone else is having this issue.

When my phone would reboot before, it would just reboot out of nowhere but it would always come back to the home screen. Come to think of it, my phone did that on Friday while I was on the phone! (and yes I had MikG when it happened) where it just randomly stopped in the middle of the call and rebooted. That time it did do a full reboot without me having to take out the battery or it doing an infinite reboot.

So, anyone else?
 
ndh777 said:
I'm wondering if anyone else is having this problem.

Yesterday, I was playing around with my girlfriend and gently threw my phone on the bed. It wasn't even hard enough to make a sound or to even move the bed. But when I came back a short while thereafter, my phone had rebooted. I just thought that was what happens sometimes because all of my Evos have done that whether they were rooted or not. But then it seemed to be stuck in the reboot. It would reboot again and then again and then again with that "MikRoms" boot screen with the rain and roadrunner. So I took out my battery, let the phone sit for like 30 seconds, then put the battery back into the phone and it was fine. So I thought that was the last of it until this morning.

I wake up and go into the shower and when I come back my phone is rebooting again. I take a close look to see if it just decided to reboot on its own or if its doing another infinite reboot. Sure enough, it is doing an infinite reboot. So I took out the battery and put it back in and now everything is back to normal.

But I'm worried that this may happen again and again. And I'm wondering if this is just an issue with my phone or if anyone else is having this issue.

When my phone would reboot before, it would just reboot out of nowhere but it would always come back to the home screen. Come to think of it, my phone did that on Friday while I was on the phone! (and yes I had MikG when it happened) where it just randomly stopped in the middle of the call and rebooted. That time it did do a full reboot without me having to take out the battery or it doing an infinite reboot.

So, anyone else?
Click to expand...

i have not heard of any reboot issues with mikg. try another rom and see if it reboots. it possible that some thing within your mikg rom got corrupted causing the reboots. try wiping dalvik cache and cache first and see if that helps. if it still happens then try another rom. if it reboots on another rom, then you might have issues with your phone.

it has happened to me before. i tried different roms and i would still get random reboots like that. i even unrooted and still had reboots. so i took it in to sprint and they gave me a refurbished one. so hopefully yours is fixable.
 
I've been using MikG for a couple of months now and I've had the infinite reboot loop happen 2-3 times. Nothing out of the ordinary there.

I've never had it the infinite reboot happen on any other roms. Just the ocassional reboot here or there.

If it is happening often, say a couple of times a week, I would consider unrooting and trying to get a replacement phone.
 
geewhiz said:
I've been using MikG for a couple of months now and I've had the infinite reboot loop happen 2-3 times. Nothing out of the ordinary there.

I've never had it the infinite reboot happen on any other roms. Just the ocassional reboot here or there.

If it is happening often, say a couple of times a week, I would consider unrooting and trying to get a replacement phone.
Click to expand...

well i would try other roms before unrooting. and like rxpert says to make sure that setcpu is not overclocked too high first. if you are bootlooping on another rom, then i would consider unrooting and see if it still is bootlooping then take it in.
 
ocnbrze said:
i have not heard of any reboot issues with mikg. try another rom and see if it reboots. it possible that some thing within your mikg rom got corrupted causing the reboots. try wiping dalvik cache and cache first and see if that helps. if it still happens then try another rom. if it reboots on another rom, then you might have issues with your phone.

it has happened to me before. i tried different roms and i would still get random reboots like that. i even unrooted and still had reboots. so i took it in to sprint and they gave me a refurbished one. so hopefully yours is fixable.
Click to expand...

lol I should've done that before coming here ocnbrze [wipe cache and dalvic]. I wiped it and I'll report back to this thread tomorrow morning.

It happened again this morning but it was weird because it had to have happened some time in the night. When I woke up (about 6:40am) my phone light was bright in my eyes and was rebooting over and over again, just randomly.

Rxpert83 said:
Are you using SetCPU?

Having your phone overclocked too high can cause bootloops
Click to expand...

I have never used SetCPU or any overclocking/underclocking apps or methods to my knowledge. But thanks for the tip. I will remember if it I do in the future. I didn't even though I asked on these forums before just because I still don't fully understand how to overclock and underclock.

geewhiz said:
I've been using MikG for a couple of months now and I've had the infinite reboot loop happen 2-3 times. Nothing out of the ordinary there.

I've never had it the infinite reboot happen on any other roms. Just the ocassional reboot here or there.

If it is happening often, say a couple of times a week, I would consider unrooting and trying to get a replacement phone.
Click to expand...

I'll see how this works for now. I wiped cache and dalivc cache (found in Recovery "Wipe" options for Amon-Ra) and I'll see how it does by tomorrow. I wonder how rebooting my phone before going to sleep will do too. I am wondering if I reboot my phone at least once every 12 hours, will it stop from doing this? I say 12 hours because this seems to be something like the software is purposely doing this on a "timer" of some kind. Like every 8, 10, etc. hours, it feels a need to reboot for whatever reason. But that's just a guess of mine.


This is getting out of hand because I rely on my phone to wake me up and it reboots at night. It's getting a little frustrating.
 
Hmm weird. I too haven't heard of anything like this, but does anyone understand how our phones write to disk? Is it possible that it was writing when it got tossed?

Other than that, I'd try a different rom, and if that doesn't do it for you, may be time to take it to sprint.
 
9to5cynic said:
Hmm weird. I too haven't heard of anything like this, but does anyone understand how our phones write to disk? Is it possible that it was writing when it got tossed?

Other than that, I'd try a different rom, and if that doesn't do it for you, may be time to take it to sprint.
Click to expand...

I considered taking it to Sprint too. This seems like an issue that they wouldn't give too much thought to and just send me on my way with a new phone for free but I think I'll wait it out.

By the way, I have a scrape in the top left hand corner of my phone. Do you think they might not allow me a free replacement because it is damaged here even though this is a software issue?

I wondered if it was writing something when I tossed it. If I remember correctly, it was on the home screen not doing anything when it was tossed. I can't not say that the fall didn't cause it because almost immediately after it fell is when it began to do its first infinite reboot. I've never had this problem with any other ROM before so this is weird. I have where it will randomly reboot on me but never infinite reboot. It's even more weird because a simple cold boot temporarily "fixes" it. Normally when a boot acts up, its a sign that something happened with the flashing and could be an error.

I did get infinite boots but that was when I was a beginner on my first Evo and didn't do a Caulkin's wipe or wipe the data before flashing ROMs and they would boot for hours without ever getting anywhere.
 
well if the dalvik cache and cache does not work, then try and flash another rom. you can try the stock ota rom if you like and see if it it will bootloop. and if so then i would unroot and see if you still get random bootloops. and finally if that is the case then you just take it in to get a new phone.
 
Sounds like a good plan, thanks ocnbrze and everyone!

So my update is that it has not, at least to my knowledge, gone into an infinite boot all day today. This was after wiping dalvic and cache. I did not reboot the night before either.

So far, it seems like a fixed issue. I'll report back here if anything else changes.
 
ndh777 said:
I'm wondering if anyone else is having this problem.

Yesterday, I was playing around with my girlfriend and gently threw my phone on the bed. It wasn't even hard enough to make a sound or to even move the bed. But when I came back a short while thereafter, my phone had rebooted. I just thought that was what happens sometimes because all of my Evos have done that whether they were rooted or not. But then it seemed to be stuck in the reboot. It would reboot again and then again and then again with that "MikRoms" boot screen with the rain and roadrunner. So I took out my battery, let the phone sit for like 30 seconds, then put the battery back into the phone and it was fine. So I thought that was the last of it until this morning.

I wake up and go into the shower and when I come back my phone is rebooting again. I take a close look to see if it just decided to reboot on its own or if its doing another infinite reboot. Sure enough, it is doing an infinite reboot. So I took out the battery and put it back in and now everything is back to normal.

But I'm worried that this may happen again and again. And I'm wondering if this is just an issue with my phone or if anyone else is having this issue.

When my phone would reboot before, it would just reboot out of nowhere but it would always come back to the home screen. Come to think of it, my phone did that on Friday while I was on the phone! (and yes I had MikG when it happened) where it just randomly stopped in the middle of the call and rebooted. That time it did do a full reboot without me having to take out the battery or it doing an infinite reboot.

So, anyone else?
Click to expand...


YES! this exact thing is happening to me! it only happened after i used the patch from 2.55 to 2.56 and then from 2.56 to 2.59. before this i had cm7 loaded up on my phone and never had any reboot issues. i am using setcpu using the SA generator set at 128/1113. also running v6 supercharger with the hard to kill launcher. after each time this has happened (about 3 or 4 times in the ast 2 weeks) i have pulled the battery and wiped cache and dalvik and this will help for a few days but it always seems to come back. this evo was a replacement phone so this maybe what the problem is. let me know what you guys think.
 
I had it happen with mikg and it was my main reason for switching. No problems on any other Tom. It wouldn't usually do it randomly though, it was when I'd hard multitasking, say have navigation running, Pandora, and texting all at once.
 
badhabits727 said:
I had it happen with mikg and it was my main reason for switching. No problems on any other Tom. It wouldn't usually do it randomly though, it was when I'd hard multitasking, say have navigation running, Pandora, and texting all at once.
Click to expand...

What rom are you running now?
 
...it happened again today...I suppose that this is a ROM problem as others using the ROM have said here too.

Weirdly enough this isn't an issue being discussed on the official MikForums unless it is only for our HTC Evo 4G devices and/or most users don't use those forums to document their problems.
 
I'm sudden;y having bootloop issues with mik2.59. Then again, I am running setCPU O-clocked to 1130 and I just bought a new sd card, and partitioned it. So, I just changed a bunch of stuff and it's likely not the rom.
 
Just to follow up I just re-flashed Mik2.59 using this method.

I also am erasing my boot manager directory, my doubletwist directory, and my setCPU directory and re-installing those from scratch from market / no data.

I'll try to remember to report back, but going fishin', hopefully won't be needing my phone much. :D

-HN
 
Huge Noob said:
Just to follow up I just re-flashed Mik2.59 using this method.

I also am erasing my boot manager directory, my doubletwist directory, and my setCPU directory and re-installing those from scratch from market / no data.

I'll try to remember to report back, but going fishin', hopefully won't be needing my phone much. :D

-HN
Click to expand...

Good luck to you. Hopefully we can resolve this problem really soon and quickly.

This is one of the finest ROMs I have used. This and CM7 have been pretty stable except for screw-ups like this. It's a shame that these small things have to ruin an entire ROM for many of us. I hope you resolve the problem!
 
MikG is one of the most stable ROM's there are. With that being said, not everything works for everybody. I would suggest doing the full wipe just starting from scratch and if that doesn't fix it MikG just may not play nice with your phone.
 
rsoria1 said:
YES! this exact thing is happening to me! it only happened after i used the patch from 2.55 to 2.56 and then from 2.56 to 2.59.
Click to expand...

Is there a patch from 2.56 to 2.59? From what I understand there are onlypatches from 2.58 to 2.59. Skipping a patch version may have caused your instability.

This is why I always start with a fresh install with full wipes when Mik comes out with something new.
 
Folks,

Make sure when you flash any of the roms developed over at Themikmik, that you wait at least 10 minutes after you boot for the first time before you touch the phone. Don't unlock it, or power the screen on. Nothing. Just leave it alone.

This one little detail is often overlooked, but it apparently is a big thing for random glitches with their roms. I've read several times over there where peolpe were having issues and couldn't get them figured out. Once they let the rom "settle", pow, no more issues.

Maybe this is a common glitch caused from not letting things settle in?
 
Granite1 said:
Folks,

Make sure when you flash any of the roms developed over at Themikmik, that you wait at least 10 minutes after you boot for the first before you touch the phone. Don't unlock it, or power the screen on. Nothing. Just leave it alone.

This one little detail is often overlooked, but it apparently is a big thing for random glitches with their roms. I've read several times over there where peolpe were having issues and couldn't get them figured out. Once they let the rom "settle", pow, no more issues.

Maybe this is a common glitch caused from not letting things settle in?
Click to expand...

+1

I find I can't wait 10 minutes to start playing with it :D, but I've never had troubles. Nevertheless, that is what mik suggests so give it a try.
 
Reporting back...everything seems fine except when I was almost dead on battery...I got down to the auto shut-off point and instead of shutting down it started bootlooping. I pulled the battery, then charged it then wiped dv cache and cache and re-booted. Everything seems fine.
 
Rxpert83 said:
Is there a patch from 2.56 to 2.59? From what I understand there are onlypatches from 2.58 to 2.59. Skipping a patch version may have caused your instability.

This is why I always start with a fresh install with full wipes when Mik comes out with something new.
Click to expand...


no there is not what i meant is i patched from .56 all the way up to.59 my problem was probably too many patches! i ended up wiping the snot out of it and re flashing the complete rom and now it works like a charm:)
 
I did a fresh install of 2.59 (previously had 2.42). Prior to installing I did a VR Superwipe wiped all with Caulkin's Format All and used Amon Ra to wipe everything again. Never had a boot loop issue with previous versions of Mik until I went to 2.59. Stock kernel and Freedom still having same issue. Happened twice in the past 2 weeks and doesn't seem to be related to anything in particular. Ready to go back to another ROM until another release comes out as I cannot have an unstable phone.

Update - MikG 2.60 is now out. Going to give it a try. I wiped everything and went to Fresh using More Freedom Universal. Guess what? It boot looped after a few hours. I wiped cache/dalvik and flashed Freedom Aggressive and have not had any issues thus far. Each phone seems to have it's own little quirks. So now I'm asking myself...."self"...did I have issues on MikG 2.59 w/stock kernel or did I already flash More Freedom when the issues began. Well, I'm going to MikG 2.60 as overall MikG runs faster on my phone than Fresh and has some better bells and whistles. More to follow.
 
Im on MIKROM 2.60 amd I tried FREEDOM and CHOPSUEY (and one other that I forget the name) kernel and I have the random reboot issue.. I had it on 2.59 as well. I think it is a rom issue as no other ROM does the random reboots. I would like to resolve this..

it rebooted yesterday using the new sprint TELENAV and today I was using TAPATALK and it rebooted..

I am on EVO4g 0004 hardware with setcpu no profiles except main which is INTERACTIVEX 128/998 with CHOPSUEY 9.27 HDMIWIN EXPERIMENTAL

FREEDOM KERNEL killed my battery very fast.. someone said to try the STOCK KERNEL but trying 3 different kernels all with the same issue, lead me to believe it is the ROM an we need to get the fix....
 
You must log in or register to reply here.
Back
Top Bottom