Root uh oh.....what happened

[JrzDroid]

Guess who got another eris with hboot 1.47!!!!

 

[scary alien]

Guess who got another eris with hboot 1.47!!!!

Dude! You are living right! You might want to hit a casino or buy some lottery tix while you luck holds-out!

Seem's like lots of folks have been getting 1.49...(did you go to the store and hand-check the one you wanted?)...

 

[bjanow]

Guess who got another eris with hboot 1.47!!!!

Not too many details, but how?

 

[JrzDroid]

Dude! You are living right! You might want to hit a casino or buy some lottery tix while you luck holds-out!

Seem's like lots of folks have been getting 1.49...(did you go to the store and hand-check the one you wanted?)...

nope. He picked up my phone. Did everything to get it to turn on and said oh well. Handed me a new Eris. and as I walked out, rebooted into hboot and saw the magic 1.47.

maybe i should go buy some lottery tix!!!

 

[MrDangerous]

Good thing he didn't try to Hboot it and see Amon Ra.

 

[erisuser1]

JrzDroid,

just a reminder,

After applying the root-PB00IMG.ZIP, start phone with Send+End/Power, and

fastboot flash recovery recovery-RA-eris-v1.6.2.img

Don't "experiment" with the fastboot command unless you have complete confidence in what you are doing - it's a rather dangerous/powerful command.

eu1

 

[cableguynoe]

Guess who got another eris with hboot 1.47!!!!

WOOT WOOT!!!!

 

[JrzDroid]

Good thing he didn't try to Hboot it and see Amon Ra.

phone wouldn't even go into Hboot. It was cooked. The Eris could only handle 768 for so long

 

[hallstevenson]

Not too many details, but how?

I've been saying it for weeks, that going to a store for a replacement (may) improve your odds of getting an "older" phone, specifically one with 1.5. They won't move as many phones as VZW's warehouse(s), who clearly have current phones (w/ 2.1 software pre-installed). The ones in the warehouse are likely to be refurbished models too.

 

[hallstevenson]

phone wouldn't even go into Hboot. It was cooked. The Eris could only handle 768 for so long

How did you have SetCPU config'd ? I hope you -- and everyone else -- used "ondemand".

 

[JrzDroid]

yes, i used on demand. No set at boot and had it at 768.
It worked good, random reboots every once in awhile.
Then just rebooted one day and never left the boot screen.
then it was just game over

 

[doogald]

yes, i used on demand. No set at boot and had it at 768.
It worked good, random reboots every once in awhile.
Then just rebooted one day and never left the boot screen.
then it was just game over

Did you have a profile set for high temperature, to clock the CPU down to a slower speed? On my ROMs with SetCPU I go into profiles, turn them on, and set the high temp limit at 40C and set speed to 256-ish/128-ish.

 

[scary alien]

Did you have a profile set for high temperature, to clock the CPU down to a slower speed? On my ROMs with SetCPU I go into profiles, turn them on, and set the high temp limit at 40C and set speed to 256-ish/128-ish.

doogald,

FYI, I posted something in the http://androidforums.com/all-things-root-eris/98457-overclocking-hmm.html about how when I had my silicone rubber case on while charging, my temp got to 40-degrees (C) rather easily and quickly (9C degrees in 10 minutes)... I upped my temp limit on failsafe just a smidge from 41C to 43C. The temp dropped back down pretty quickly once I removed the phone from the case.

I'm also now charging with my case off of my device. Don't think it would hurt anything if failsafe kicked-in and dropped me down to 245MHz, but I'm sure I would initially be puzzled.

Cheers!