Root uh oh.....what happened

[JrzDroid]

SO, I'm running Aloysius Snow with Sense removed and JIT enabled. Everythign was cool until about 45 minutes ago, my phone rebooted and stayed on the three Androids on skateboards screen. I've done some battery pulls and tried to get into recovery but, it still just stays on the skateboard screen.
I sent a text and the phone just rebooted.
I got into fastboot and selected recovery but it just goes to the skateboard screen still.

Am I f*cked?
i mean bricked?

 

[erisuser1]

SO, I'm running Aloysius Snow with Sense removed and JIT enabled. Everythign was cool until about 45 minutes ago, my phone rebooted and stayed on the three Androids on skateboards screen. I've done some battery pulls and tried to get into recovery but, it still just stays on the skateboard screen.
I sent a text and the phone just rebooted.
I got into fastboot and selected recovery but it just goes to the skateboard screen still.

Am I f*cked?
i mean bricked?

Will it go into HBOOT? (Vol-down+End/Power)

If you can get the bootloader running, you can get your phone back (unless the phone got fried from to much OC'ing).

Just curious, were you starting SetCPU right at boot? If so, what do you think the ondemand Max Clock was set to?

eu1

 

[JrzDroid]

no, was not Set at boot, yes i can get into bootloader
max clock was 768

 

[scary alien]

no, was not Set at boot, yes i can get into bootloader
max clock was 768

Was (is) the phone running really hot? (i.e., do you need to let it cool down for a bit?)... just a thought...

 

[erisuser1]

no, was not Set at boot, yes i can get into bootloader
max clock was 768

Well, the rescue procedure of last resort is to.... wait for it... wait for it... re-root your phone (without using the battery pull trick!), and re-install the recovery partition. Allowing the full flash rather than just the bootloader allows the flash memory on the phone to be completely reconstructed.

I think you know where the instructions for that are

Before you go down that route, though, you might want to try to just reflash the recovery only, and see what happens from there.

If you get back up and running you might consider backing off from 768 Mhz. The thing about timing errors (which happen when OC'ing gets too high) is that they are statistically dependent on clock rate - so if you are just "a smidge" too fast, you can run for weeks without errors, and then all of a sudden, the phone glitches.

eu1

 

[JrzDroid]

eh i don't think its incredibly hot, but I'll turn it off for awhile and let it cool

 

[JrzDroid]

Well, the rescue procedure of last resort is to.... wait for it... wait for it... re-root your phone (without using the battery pull trick!), and re-install the recovery partition.

I think you know where the instructions for that are

Before you go down that route, though, you might want to try to just reflash the recovery only, and see what happens from there.

If you get back up and running you might consider backing off from 768 Mhz. The thing about timing errors (which happen when OC'ing gets too high) is that they are [I}statistically[/I] dependent on clock rate - so if you are just "a smidge" too fast, you can run for weeks without errors, and then all of a sudden, the phone glitches.

eu1

i'll try it out and let ya know =]

 

[JrzDroid]

reflashing the recovery was a fail

trying to re-root the phone now

Just wondering, if this thing is fried, if i call verizon and tell them that the phone just rebooted and would never leave that screen, would they be able to tell?

 

[reinert012]

This happened to me once...i let it go for like 30 minutes at the boot screen and it just finally worked.

 

[JrzDroid]

i'm still on the boot screen. I've been letting it sit for awhile
I think its bricked

 

[erisuser1]

reflashing the recovery was a fail

Sorry, please elaborate: it would or wouldn't boot into recovery after the reflashing? Or did the actual process of reflashing fail somehow? (Did you see any error messages during the flashing process?)

BTW, I left it out because I thought it would be apparent - I was anticipating that if you got the recovery to boot, you would be restoring a Nandroid backup.

Just wondering, if this thing is fried, if i call verizon and tell them that the phone just rebooted and would never leave that screen, would they be able to tell?

Hard to say. The thing you need to keep in mind is that when a customer's phone dies, it is pretty unlikely that they dispatch a team of computer forensics experts to diagnose what went wrong. More likely they just chuck it in the trash and chalk it up to the cost of doing business. (HTC or VZW probably do *sample* a small quantity of handsets that have failed to see if they notice similar failure behaviors. Think of it as being like the "audit rate" with the IRS).

trying to re-root the phone now

Did anything happen that was unusual during this procedure? Any strange messages zip by on the screen?

eu1

 

[JrzDroid]

no unusual messages or anything
I'm gonna hit up VZW to see if i can get a new Eris

 

[erisuser1]

no unusual messages or anything
I'm gonna hit up VZW to see if i can get a new Eris

A new unrootable Eris.

 

[JrzDroid]

well as long as its free I'll be alright
I was planning on going DroidX next month

 

[erisuser1]

That is truly bizzare

Well, here's a couple more last-ditch voodoo kinds of things you could try:

Pull the battery out, leave it out for 2 minutes. Make sure USB is unplugged so there is no source of power to the phone. Depress every button one at a time while the battery is out.

Pull the SD card, re-insert the battery and see if you can reboot.

It occurs to me that if flashing seems to work OK, and you decide to return it to VZW, the last thing you might do before you hand it over is to flash Leak-V3 in place. That eliminates your worries above. I would try everything in your power to see if it will come back to life first, though, as you may not receive a rootable phone as a replacement.



eu1

 

[erisuser1]

Oh - one more thing.

While it is sitting there at the three skating droids, can you get an adb shell?

If so, see if you can do a "logcat" - many times the source of the error will be apparent if the phone is partly booted, but stuck in a bootloop right at that point.

eu1

 

[JrzDroid]

maybe I'm not doing something right.
I reflash by doing the fastboot usb: fastboot flash PB00IMG.zip

correct?

 

[erisuser1]

maybe I'm not doing something right.
I reflash by doing the fastboot usb: fastboot flash PB00IMG.zip

correct?

OMG NO!

Don't try to do this from memory. Pull up the original thread where you rooted your phone and walk through it in exactly the same way - it will all come back to you that way.


eu1

 

[erisuser1]

Start from where you started last time - it will be way faster the 2nd time around because you will recognize everything:

http://androidforums.com/all-things...placement-eris-root-questions.html#post827552


Remember that all your Nandroid backups are still on your SD card - you've been backing up regularly, right?


eu1

 

[JrzDroid]

well idk what i did, but the phone is gone. She won't turn on
I'm gonna go to a verizon store tomorrow and show them.
Hopefully they just hand me a new Eris and I walk out and continue life.
July 19th can't get here fast enough

 

[erisuser1]

 

[JrzDroid]

RIP rooted Eris
maybe I'll get lucky and Manage to grab a 1.47 hboot phone

 

[alprazolam]

RIP rooted Eris
maybe I'll get lucky and Manage to grab a 1.47 hboot phone

That just sucks! I hope that you get 1.47.

 

[cableguynoe]

RIP rooted Eris

NOOOOOOOOOOO!!!!

Today we lost a truly hot avatar

I will always think about you Jrz... always

 

[JrzDroid]

NOOOOOOOOOOO!!!!

Today we lost a truly hot avatar

I will always think about you Jrz... always

aww your so nice =]
my heart will always be with the Eris thread
no matter where I may travel