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?
__________________ WARNING Posts May Contain Anywhere between 30 - 100% SARCASM PM me if you need any further help, i'm here to help Google+ 4 Life
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?
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.
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.
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?
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.
Quote:
Originally Posted by JrzDroid
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).
Quote:
Originally Posted by JrzDroid
trying to re-root the phone now
Did anything happen that was unusual during this procedure? Any strange messages zip by on the screen?
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.
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.
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.
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
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.
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.
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
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.
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!
Last edited by scary alien; June 21st, 2010 at 07:27 PM.
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More
uh oh.....what happened
