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

Root MikG 3.1 Hot Reboots - My Problem/Findings - Your Thoughts??

Anthrax wouldn't work if you had a specific H-boot.

I'm V004 and everythings jolly on my end. I'm not sure what the other members of the family are that are experiencing problems.
 
Scudder, before blaming the SD card have you tried a different Rom?

Most of them utilize the partition on boot up so maybe that would help figure this out?
I'd go to a Sense 1.0 Rom first. Either a stock rom or one of the newer ones since Mikg 2.61 is so old.

This is the newest OTA 4.67 that is stock. It has been optimized to run a little quicker and everything works. I've run it and was very happy.

[ROM] 4.67 - Rooted - Optimized - Sharing means caring - xda-developers

Or NoLimit06's Rom is also off of 4.67 but is stripped down so it's very small but fast. It's missing most HTC widgets and Sprint apps.

http://androidforums.com/evo-4g-all...aked-v1-2-0-02-08-12-a.html?highlight=nolimit

Or what I'm running currently is TommyTomatoes Classic 0.6
It isn't updated to the 4.67 rom but has some tweaks and is Sense 1.0.

http://classictomatoe.net/android/classic/beta/classic-v006-01-11-preview-signed.zip


I'd rather try flashing a quick rom than changing a SD card. I just did mine and it took forever.



Naters

I had heard reports of other people having this problem from No-Limits ROM when it was first released, and I'm not sure if he ever got them figured out. It may be due to how stripped down it is. I would repeat the test with Tommy's Evo Classic. I havent heard of any reboot issues with it.


Bottom line: Others have found nolimits ROM to be a little buggy, it would be better to use a more stable ROM to use as a test base.

Nothing against his ROM, but go with something more "stable" before drawing conclusions

Go with the Classic 5 Finale build.

Gave a shout out to Rxpert83 over at the "Very Disgruntled" tread pointing me toward the Tommy's Classic v005 ROM as the first ROM that has worked for me this entire week but also wanted to THANK NaterTots as well as he also mentioned the Tommy ROM as one of three to try! :D
 
Yeah, quick little flick of your finger over the "default" checkbox and you're done! Glad it worked.

And as a "thanks" ;) please, PLEASE let us know if the undervolt helps your/our/my reboot issue!! I'm currently running MikG 3.11 for the LONGEST period of time I have in the past week WITHOUT a reboot but not quite confident enough to disclose what I'm doing. Actually I'm not quite sure whattheHELL I'm doing so THAT is why I'm disclosing it!! :eek::D I gotta collect my thoughts and really see if I'm in better shape than before. Also a couple other lose ends I'm not so sure I can make conclusions about...yet. We'll see what's up tomorrow.

Let us know about the undervoltage!!

Definitly have a question for you now.

Have you been running 3.1 or 3.11 this whole time?

so if you were on 3.1 and went to 3.11 did you full wipe 3.11 or just do the update?

i have been on 3.1 having this issue. Just realized from this post of yours about 3.11. Went to his site and seen the 3.11.

i am going to stay on 3.1 for now and see what the undervolting does.

just trying to find that program that was mentioned above to change the voltage. i thought setcpu would but i guess that is cpu speed only.

if anyone has a hint to under volt let me know. i do not care if i damage my phone by trying something out.
 
I don't think I updated wimax or nv, how can I tell what version I have?

and here is a handy page if you know what you are doing, which I don't claim to.

HTC EVO 4G Downloads - RootzWiki

Can anyone confirm the LATEST Radio version?? I'm getting some "conflicting" information as I look at various pages...

The above RootzWiki link indicates the latest Radio as 2.15.00.08.08 as does this XDA thread:

[ Radios ][ 9-5 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers

However, this link from theMikMik has latest Radio as 2.15.00.12.19:

Radio Update - 1/21/2012 - 2.15.00.12.19

And the RootzWiki also interestingly indicates that the last digits correspond to the release MONTH and DAY of the Radio so although "12.19" seems like a "higher" number than "08.08" and therefore "newer" that isn't necessarily the case because the YEAR is not indicated, i.e., 12.19 could be released in 2010 and 08.08 in 2011!
 
Can anyone confirm the LATEST Radio version?? I'm getting some "conflicting" information as I look at various pages...

The above RootzWiki link indicates the latest Radio as 2.15.00.08.08 as does this XDA thread:

[ Radios ][ 9-5 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers

However, this link from theMikMik has latest Radio as 2.15.00.12.19:

Radio Update - 1/21/2012 - 2.15.00.12.19

And the RootzWiki also interestingly indicates that the last digits correspond to the release MONTH and DAY of the Radio so although "12.19" seems like a "higher" number than "08.08" and therefore "newer" that isn't necessarily the case because the YEAR is not indicated, i.e., 12.19 could be released in 2010 and 08.08 in 2011!

12.19 is the newest one. The others havent been updated because our EVO's are .........old.

The above links havent been updated in a long time
 
Definitly have a question for you now.

Have you been running 3.1 or 3.11 this whole time?

so if you were on 3.1 and went to 3.11 did you full wipe 3.11 or just do the update?

Sorry for the confusion even *I* cannot follow myself at this point! :eek::D

The answer is yes and no!! :D:D I first flashed 3.1 and had reboot problems. I then got into wiping and reformatting the card and reflashing 3.1. Then 3.11 came out and since I was in the thick of wiping and reformatting, I just FULLY WIPED and installed 3.11 FRESH. I did not update 3.1
 
Ok, I HAVE AN UPDATE on my trials and tribulations with MikG 3.11!!

Last you all left me, Tommy's Classic v005 was the ONLY ROM that was working for me without reboots (tried MikG 3.1, MikG 3.11 and NoLimit06). With a working version of Tommy's Classic v005, I made a nand backup and then rewiped and reflashed MikG to play around and try the following...

There was suggestion over at theMikMik forum and some debate about trying to reformat the card with a "non-LBA" formatting rather than an "LBA" formatting. What this means, I really have NO CLUE WHATSOEVER, however, as it relates to my personal situation, this was a PROBLEM because the only way I could find to format in "non-LBA" method was with Windows and I have a MAC.

NOTE: if indeed a "non-LBA" method might be an answer to some reboot issues, here is the link to the Windows information for non-LBA formatting as posted by an Admin Jadeboy7 at theMikMIk forums:

Fix: LX Series MicroSD Problems on Android phones

Back to my situation...

Some people tried to help me with finding a Mac solution providing this farkakte "non-LBA" thing and I couldn't find anything. Someone gave me a terminal command set to use on my computer but the command wasn't working :(

So, I basically said SCREW IT in the interim and decided ON MY OWN to format the card WITH MY MAC. I had previously formatted the card on my computer with software from the internet called SD Formatter as was also suggested to me but I decided to try the built-in Apple "Disk Utility" software. In that software is an option to erase a disk, SD card included, with various formats including mac-specific options as well as "MS-DOS (FAT 32)" So, like I said, I said SCREW IT, nothing else was working and I couldn't get the non-LBA thing tried with my setup, so try this reformatting while I had a few DOZEN HOURS to kill!! :D:D

Anyway...long story long...I reformatted using my computer, dragged ONE SINGLE FILE to a SINGLE folder I created on my SD card while plugged into the USB port of my computer: THE MIKG 3.11 ZIP

Well...I flashed the sucker and have been REBOOT FREE FOR 12+ HOURS!!!!!

I did a nand and now, HOPEFULLY, I might have a "stable" situation with MikG 3.11

But here are SOME ISSUES/VARIABLES to consider and should probably get answers to...

Why on this night do we recline?? (kidding...some Jews here will get the joke! :D:D)

Seriously...

(1) Why did this recent sd card erase and reformat work?? Was I lucky and the flash-gods were on my side?? Or is there SOMETHING IN THE MAC REFORMAT that worked?? Was it actually the non-LBA format that has been suggested?? I DO NOT KNOW!!

(2) My currently stable phone state is (a) without ANY DATA from my card on my reformatted card (b) without ANY TITANIUM BACKUP FOLDER DATA and (c) WITHOUT a partition and a2sd use!!

It isn't such a shocker that my phone is stable without the data I left off the card. In fact it was suggested NUMEROUS times that one is PLAYING WITH FIRE if one restores data, especially if moving like I did from ROMs of different architecture (e.g., MikG 2.56 to MikG 3.XX). However, remember that I had reboots with MikG AND with the NoLimit ROM with NO DATA INSTALLED so, to me, it could NOT be "the data" that was causing the reboots...

THAT BEING SAID....do you guys know what I'm going to do??? You DO don't YOU??

I'm gonna take my perfectly-good-so-far phone, REFORMAT the card AGAIN and WIPE my phone and REFLASH MikG 3.11!! WHY you might ask?? Because I NEED some stuff backed up on Titanium AND I need to partition and run a2sd....THAT is how I want to run my phone. I plan on "recovering" the APKs of various apps that are no longer available that I have backed up with Titanium and then TRASHING the Titanium Backup data and building it up again.

It was suggested...and much, much easier...to NOT complicate everything and drag back GIGs worth of Titanium backup data onto the card or run a2sd while I was troubleshooting MikG in case I was having an SD card issue.

Soooooooo...I'm going to reformat AND partition AND drag my Titanium folder to the cleaned SD card and try this over again. My HOPE AND PRAYER is that everything goes smoothly...in which case...we GOTTA FIND OUT WHAT MY APPLE DISK UTILITY "ERASE" REFORMATTING OPTION DID (in a GOOD WAY!!) TO MY CARD!!

ONE THING about my Apple Disk Utility reformatting and this "non-LBA" format to consider...

The Admin Jadeboy7 over at theMikMik was trying to help me figure out how to get my Mac to format in the non-LBA format and said the following:

If you can find a "full format" option that does a FAT32 partition with 32K allocation sizes, I think that may be the same as that command I linked to earlier. I'm not completely sure though.

Edit: I just read something about using "0x0b" (CHS) as opposed to "0x0c" (LBA).
Link to the above information can be found here: Random Hot Reboots - Page 15

POSSIBLY, the "default" MS-DOS (FAT 32) format option in my Apple Disk Utility is PRECISELY this "full format" and/or non-LBA format that was needed?? Again, NEED TO CONFIRM what exactly the Apple Disk Utility "Erase" function does.

So, few variables to think about and I have a BIIIIIIIIG test tomorrow with the reformat, partition and Titanium Backup data...wish me/us luck!!! :eek::D
 
hey scuds i just want to thank you. i love your post and threads. they are very well thought out and i love how you think. i find very cool that you are able to sometimes come up with answers even as you type out the post. and i love the fact that you try to find the answer and reasoning behind it all.

i would have never guessed that it could be your sd card. your deductions have pretty much proved that it was the sd card all along. i will have to keep this mind in the near future.

and i'm not really sure what lba is or how that translates to the sd card. i can google it but man there is a lot of tech stuff that is way above my pay. lol

and thanx for keeping us updated on what you find.

good luck with your test tomorrow;)
 
hey scuds i just want to thank you. i love your post and threads. they are very well thought out and i love how you think. i find very cool that you are able to sometimes come up with answers even as you type out the post. and i love the fact that you try to find the answer and reasoning behind it all.

i would have never guessed that it could be your sd card. your deductions have pretty much proved that it was the sd card all along. i will have to keep this mind in the near future.

and i'm not really sure what lba is or how that translates to the sd card. i can google it but man there is a lot of tech stuff that is way above my pay. lol

and thanx for keeping us updated on what you find.

good luck with your test tomorrow;)

OCNBRZE, thank you VERY MUCH for the kind words...mean A LOT as you have been VERY helpful to me over the course of many months!! :D:D It's a combination of my thought process and the fact that I can type pretty fast. Blessing and a curse...for ALL of us!! :eek::eek::D ...but I DO hope that my posts and information help those who take the time to read! :D

I still have my testing to do tomorrow so all is not resolved but step in the right direction. And yeah, that LBA stuff is waaaaaaaay above my pay grade. I just wanted something that might automatically and without my knowledge format the card howeverthehell it was needed and perhaps this Apple Disk Utility is doing just that...MAN do I hope so!!!!:eek:

BTW, feel free to the move this post to the correct "Mushy Gushy Awww Thanks for Being there Man" Forum!!! :D:D;)
 
hey scuds i just want to thank you. i love your post and threads. they are very well thought out and i love how you think. i find very cool that you are able to sometimes come up with answers even as you type out the post. and i love the fact that you try to find the answer and reasoning behind it all.

And HOW FITTING!!...that NOVEL of a post up above was my 1000th post!! Damn, if I only wrote less per post and spread it out a bit, I'd be up to post numbers surpassing yours!! ;);)
 
scudder

glad everything is working fine for you.

i found out that my pri was version 1.9 something and baseband was really old also. i updated and will see how it turns out.

will reports back later tonight when i get off work.

haven't found an app yet to undervolt. just curious to try it out.
 
scudder

glad everything is working fine for you.

i found out that my pri was version 1.9 something and baseband was really old also. i updated and will see how it turns out.

will reports back later tonight when i get off work.

haven't found an app yet to undervolt. just curious to try it out.

So far...still haven't gotten the time I wanted today to test the way I wanted to but we'll see...

And SOMEONE has to have a info about how to undervolt?? I haven't had a chance to search the forums...maybe try that...
 
Haven't had as much time today to troubleshoot but trying a couple things.

Was wondering if anyone knows of an app or some widget or something that could someone "keep track" of the number or reboots?? Perhaps one of those graphical battery trackers or logs?? And what would one look for to confirm a reboot in either a graph or log??

I might be way off but it appears to me at least that the reboots are happening only (1) when my screen is on and (2) when I'm not doing anything. Fortunately or otherwise, my experience has been that if I'm doing anything on the phone...texting, browsing, scrolling....actively doing something with the phone, I'm not rebooting. But when I put it down with my 2 minute screen timeout setting, I notice the reboots. I want to see if the phone is doing anything while the screen is off in locked/sleep mode.

Any apps I/we could use to keep track??
 
I was on 3.11, achieved by wiping cache and d cache and flashing update zip for a while with no problems. I didn't make a nand of it before I waltzed off to try something so the highest level nand I had was of just 3.1.

I had been reading and saw reference to the full wipe 3.11. I went to the Mik's op to check on it. I saw where he said not to wipe anything to flash the 3.11 upgrade zip or to wipe normally to do the full 3.11 zip.

I still have the update zip on my phone so I jumped in and flashed it without wiping anything.

i had like 3 full blown reboots in a very short amount of time. I restored 3.1 and have run it all day with no problems. that really surprised me.

I am going to flash it again but wipe first, like I did it before, and see what happens.
 
I was on 3.11, achieved by wiping cache and d cache and flashing update zip for a while with no problems. I didn't make a nand of it before I waltzed off to try something so the highest level nand I had was of just 3.1.

I had been reading and saw reference to the full wipe 3.11. I went to the Mik's op to check on it. I saw where he said not to wipe anything to flash the 3.11 upgrade zip or to wipe normally to do the full 3.11 zip.

I still have the update zip on my phone so I jumped in and flashed it without wiping anything.

i had like 3 full blown reboots in a very short amount of time. I restored 3.1 and have run it all day with no problems. that really surprised me.

I am going to flash it again but wipe first, like I did it before, and see what happens.

Yeah the "don't wipe anything" is very misleading. You should still wipe dalvik and cache to prevent force closes/ect
 
Guys, per someone else's suggestion on here (MizzouBrent) I tried fixing permissions and that completely solved my hot reboot issue.

If you're not aware how to do it, this is what he told me to do:

"Just boot into recovery, go to "Other" and select "Fix apk uid mismatches" and let it do its thing and then reboot."

He said you might have the following issue (but I did not have this issue):

"I noticed after fixing permissions that all my contact photos disappeared in the stock messaging app. To get them back, get Terminal Emulator from the market (not sure if it came with the rom or not...it's a free download though).

Then type in the following two lines:

su
chmod 666 /data/data/com.android.providers.contacts/files/*

Then reboot your phone and they'll be back."
 
Guys, per someone else's suggestion on here (MizzouBrent) I tried fixing permissions and that completely solved my hot reboot issue.

If you're not aware how to do it, this is what he told me to do:

"Just boot into recovery, go to "Other" and select "Fix apk uid mismatches" and let it do its thing and then reboot."

Interesting that this worked for you...hope it sticks!!

I didn't mention but I have been fixing permissions ALL ALONG but didn't really see any effect on my phone. But that's just my situation.

However, you and MizzouBrent are not alone with the permission fix suggestion and that working for some people. A thread written as a "[Guide] to Fix Hot Reboot Issues" lists, among other things, fixing permissions:

[GUIDE] - How to fix Random Hot Reboot Issues

I always used that to fix force close (FC) issues but hasn't quite been the holy grail for fixing my hot reboots here lately...
 
Hey I havent been an mikg in a while but after all the reading ive been doing im about to do a fresh flash of 3.11. How ever im going to format the sd first and start clean.The only restore Im gona do is sms. Im HW V0004. I will report back on any problems.


Ok what I did so far
wipe everything except sd card 3 times
flash zzzvrsuperwipe 3 times
wipe sd card 3 times
un part sd card
re part sd card (swap-0 sdext-1024 remainder fat32)
upgrade ext2 to ext 3
usb toggle and move sms back, nandroid folder, zzzvrsuperwipe and mikg v3.11 to sd.
flash zzvrsuperwipe 3 times again (OVERKILL i KNOW)
flash mik g
 
Hey I havent been an mikg in a while but after all the reading ive been doing im about to do a fresh flash of 3.11. How ever im going to format the sd first and start clean.The only restore Im gona do is sms. Im HW V0004. I will report back on any problems.


Ok what I did so far
wipe everything except sd card 3 times
flash zzzvrsuperwipe 3 times
wipe sd card 3 times
un part sd card
re part sd card (swap-0 sdext-1024 remainder fat32)
upgrade ext2 to ext 3
usb toggle and move sms back, nandroid folder, zzzvrsuperwipe and mikg v3.11 to sd.
flash zzvrsuperwipe 3 times again (OVERKILL i KNOW)
flash mik g

Hey Mike....COOL that you're gonna try some things out. Looks pretty similar to what I have been trying except my sdext is 2048 and didn't use superwipe at all.

Not sure how your hardware version 0004 fits in...just another one of about 80 variables trying to sort through :(...but would be very interested in what happens...PLEASE let us know!!
 
Hey Mike....COOL that you're gonna try some things out. Looks pretty similar to what I have been trying except my sdext is 2048 and didn't use superwipe at all.

Not sure how your hardware version 0004 fits in...just another one of about 80 variables trying to sort through :(...but would be very interested in what happens...PLEASE let us know!!
I listed that because there was a problem a while back that only afected v0002 and v0003 hardware not V0004. I dont know what changes were made to the hardware but figured id include all the info i could.
So far im just about set up all apps downloaded fresh and no problems but only been 45 mn.
 
Ok so Ive been on the phone setting things up and testing and deleteing. Running wifi 4g hbo go netflix texting web and phone at same time. screen on time 2 hours and the only problem i had was bad 4g speeds but after updating prl and profile the correct way im getting 7 to 10m per sec so its running flawless for me so far. Ive even rebooted manualy 1 time just to check it. So Ill report back again after work tomorrow if there is any changes.
 
I listed that because there was a problem a while back that only affected v0002 and v0003 hardware not V0004. I dont know what changes were made to the hardware but figured id include all the info i could.
So far im just about set up all apps downloaded fresh and no problems but only been 45 mn.

Yep, yep...that's why I mentioned and asked about the hardware version. I don't recall the specific issue where v0004 but yes, there was something, somewhere where v0004 worked and v0002/v0003 had problems.
 
So late yesterday...I'm talking LATE like 1am in the morning...I added a bunch of apps and changed some settings on my at-the-time running smooth MikG 3.11 that I said up above was going good with NO reboots.

Just before 5am (yep...5am...don't ask!!) I made a nand and swapped batteries to put in a fresh 100% charged battery and went to bed. On my card I had my Titanium Backup folder with ALLLLL my crap in it but no other folders that I backed up with other settings (like Jorte's folder or ChompSMS folder). MY INTENTION during the day today was to reinstall Titanium Backup and then weed through the crap I had backed up but NEVER got around to it.

I used my phone in its "normal course"...texting, calling, installing some new apps...and I turned around FIFTEEN (15) HOURS later and had 60% of my battery left....GOOD battery life for me, ESPECIALLY for me with this MikG 3.11 lately. I must be honest, I did have 3 or 4 reboots during the ENTIRE day but nothing too bad.

I did a couple other changes, made another nand, and my battery got down to around 40 and the reboots became a bit more common...probably in the last hour or so I've had "a few" that I've noticed.

I think that the formatting of my card using my Mac HAS HELPED...since first trying the ROM back on March 3 the phone has been running ITS BEST after the Mac reformat. But then again, there are a bunch of reboots...especially, oddly, more frequently when the battery gets lower...it is as if the phone "strains" a bit with lower battery strength and causes the reboots. I'm pretty sure the phone doesn't "strain" more at 40% battery vs 80% battery but just odd circumstances...

ISSUE TO CONSIDER
: Also something else I noticed...it appears that I have a BUNCH of reboots while my phone screen is ON and the phone sitting an IDLE but WITHOUT the screen locked. I've made a conscious effort to turn my screen OFF but I'm not sure if reboots can occur when the phone is locked and screen is off...can it??? I've just NEVER SEEN IT...only when my screen is ON do I look over and see the "ANDROID" boot up screen and/or feel the little "vibrate" from the reboot.

So, I'm gonna move forward and install Titanium, reinstall a bunch more apps and even some data for a few apps that I have "important" (to me) settings that I want to see if they stick and not cause reboot problems. I STILL need to update my radios and PRI so we'll see if that helps do.

IN SUMMARY...I can probably "deal with" the reboots that I have seen...they seem to be less frequent. I hope going forward they don't increase...and hope that perhaps an update of my radios and PRI must help as well.

Will report book...

----------
Edit:
I just realized I wrote above I will report "book"...guess I, myself, am realizing how much I write!!:eek::eek::D I will report back...!!
 
Back
Top Bottom