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

Lock-up during boot (stock, no root)

junion

Lurker
May 17, 2010
2
0
Ok, first off...this is my work issued HTC Droid Eris. 100% bone stock facory everything, no root, no flashing, nothing (not even really sure what all that stuff is anyway lol)

Yesterday got the phone off the charger, hit the power button to start up. Phone vibrated and the three skateboarding droids came up as usual and there the phone stayed. Pulled the battery, tried again and same thing...locking up on the three skating droids.

Next I did power+vol dwn. It goes right to the fastboot, recovery, clear storage, simlock menu. I selected RECOVERY and hit power. Phone vibrates and the three skating droids pop back up for about 5-10 seconds and the I get a picture of a Droid Eris with a red triangle and exclamation mark over it.

From this screen I hit power+vol up. This gets me the Android System Recovery menu with Reboot System Now, Apply sdcard:update.zip, Wipe Data / Factory Reset, Wipe cache partition. Down at the bottom, in yellow letters it says "E:Can't open /cache/recovery/command" So I select Wipe Data / Factory Reset and hit power. "confirm wipe of all user data?" Yes...does it's thing for a couple minutes. "Data wipe complete" and Android System Recovery menu comes back up. Select Reboot System Now and hit power.

Now the phone reboots, white screen with three skating droids.....still locked up on that screen. After noticing the "Apply sdcard:update.zip" menu option I downloaded the July 2010 OTA from here. I put it in the root folder of my sd card and the selected "Apply sdcard:update.zip". It started the install from sd card and after just a couple seconds pops up and says "E:signature verification failed Installation aborted."

So my phone is still locked up on the skating droids...Can anyone please offer any help?

Thanks in advance!
 
Welcome to AF, junion.

There are a lot of reports of Erises getting stuck at that screen; often the remedy is to first wait an extraordinary amount of time, say 10 minutes or so, or failing that, to pull the battery out and try again.

The recovery function requires a backup image to have been saved, usually via "nand backup."

When you invoked recovery, the device saw nothing and gave you that error message.

When you performed the wipe functions, you likely destroyed your existing operating system, probably the 2.1 with OTA (not sure what they gave you).

Your next step depends on the expected responsibility from your company: do they leave it to employees to get their phones fixed, up and running, repaired, exchanged, etc? Or do they take care of those things once you return the non-functional device to them?
 
  • Like
Reactions: junion
Upvote 0
First off...Thanks for the replies! I asked my employer this morning shortly after my original post what they wanted me to do. They said call Verizon. No questions asked they sent me to the local Verizon store and now I have a new (refurb I'm sure) Eris. This phone must have it's share of problems...they barely even looked at the phone, just yanked the sd card and battery, tossed them into another phone and I was out the door in under 10 minutes.

Frisco..."nand backup", is this an app?? The only backup app I had was Lookout Mobile Security, which is actually kinda useless for me as a backup because all of my contacts and such are on our Exchange server here at work.
 
Upvote 0
First off...Thanks for the replies! I asked my employer this morning shortly after my original post what they wanted me to do. They said call Verizon. No questions asked they sent me to the local Verizon store and now I have a new (refurb I'm sure) Eris. This phone must have it's share of problems...they barely even looked at the phone, just yanked the sd card and battery, tossed them into another phone and I was out the door in under 10 minutes.

Frisco..."nand backup", is this an app?? The only backup app I had was Lookout Mobile Security, which is actually kinda useless for me as a backup because all of my contacts and such are on our Exchange server here at work.

junion,

I think Frisco was under the impression that your phone was rooted. Since you asked about the Nandroid backup that Frisco mentioned, I can gather you were probably not rooted?

A Nandroid backup is a full phone backup that you can perform when you are rooted via a custom recovery (vs. the stock recovery that you invoked). These backups are protection / insurance to allow you to completely restore your phone should something go awry. This is available only if you are rooted, however.

I also think that the wipes that you did were essentially the same as the wipes that we do in custom recovery to prepare the phone when about to flash a new, custom rooted ROM. Basically, a factory reset. You likely had another issue with your phone that caused your boot to hang, especially since you were stock, unrooted.

I'm actually a little curious for erisuser1 to weigh-in and see what he thinks about this (especially if I misrepresented something in the above)...he would likely have some interesting and illuminating things to say. eu1, are you out there?

Thanks and glad you are back up and running with a new phone.
 
Upvote 0
junion,

I think Frisco was under the impression that your phone was rooted. Since you asked about the Nandroid backup that Frisco mentioned, I can gather you were probably not rooted?

No.. I was giving the OP a "backup" scenario to show why his recovery mode attempt failed (he'd selected recovery).

Looks like he got lucky with a good running refurb.. good to see. ;)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones