I bought a used phone, knowing that it had a problem. This problem would cause it to stay stuck on the "three android skating" boot screen and after around 2 minutes, the phone would just turn itself off so I searched all over the internet for a solution and I came across this.
http://theunlockr.com/2010/03/16/how-to-root-the-htc-droid-eris
I followed the above guide with the utmost of care and it did not work. The problem was still persisting.
The only thing I could make it do from there is press volume up and end button. It brought me to system recovery (2e) and it gives me these four options.
Reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
Thus, I assumed that I had to go to apply the fix through the sdcard. However, it said it couldn't open /cache/recovery/command then it showed the information on why and it said (no such file or directory).
I was then told that if the above fix did not work, I could "use the fix that Verizon uses". (refer to the link below)
http://forum.xda-developers.com/showpost.php?p=6702102&postcount=1%3Cbr%20/%3E%3Cbr%20/%3EA
I downloaded this "fix" to the desktop and ran it, whilst carefully following these instructions: http://androidforums.com/htc-droid-eris/25944-how-manually-update-eris-using-ruu.html
Every step worked until I reached step 8/9, at this point it, it was 10% from completion when an error popped up onto the screen and it said "it cannot be completed", and it told me to reinstall the software.
However, I couldn't reinstall it because none of the buttons, the volume rocker nor the trackball was working so I was unable to go back to try and reinstall as it was stuck on a black screen. The only thing that I could see was the HTC logo in the middle and a status bar below it which was stuck at the same level as the program that was displayed on the computer screen. It seemed completely frozen so I had no choice but to disconnect it from the computer but this led to another problem which is what this post is about.
My phone is completely dead, it will not turn on despite holding the power button for long periods of time and when I try to charge it, the charge led light does not appear. I think that the phone is bricked and I don't know how it got to this because I followed the instructions word for word and the other users of the Droid eris on the above forums had successfully fixed their phone.
Can anyone help me fix my Droid Eris, or are able give me an idea on what is actually wrong with the phone? Thanks in advanced!
Do you know if the phone is/was rooted before? Are you able to get it to boot into recovery?
Related
well my phone is now stuck on the htc screen... help please
I was running meanrom 3.0 then dirty flashed 3.9. My phone would turn off randomly so i restored it to 3.0. Then my text messages wouldnt work couldnt send or receive. So then i full wiped, restored and still no text. Then I full wiped and hit reboot system. And now it is stuck. I guess it is stuck because i didnt restore or install a rom? I cant even get to the bootloader. So is this phone a paperweight now?
Hold power down, this will cause a simulated battery pull, the phone will turn off, wait a second or two then press and hold power button and volume down and you will boot to the boot loader. Be very careful next time
Edit so long as your phone responds there is almost always a way to fix it, you only worry when phone stops responding (screen off won't charge won't turn on)
I wish more people would read my guide I included problems (even this exact one) to help people avoid them
ok got to bootloader. THANKS
No problem I'm glad I helped.
Note: This exact problem and many others are in the troubleshooting section of my guide. (Sorry if I don't advertise no one will use it lol)
Yep.... you wiped the ROM and then tried to boot nothing.
yeah....this is clearly covered in my guide...lol
I have a Tmobile HTC One M7 that I paid $300 for. It was awesome! However, I wanted to root it. So I successfully unlocked the bootloader, installed TWRP and then proceeded to attempt to root. Something went wrong and now this thing is useless! I cannot tell you where it went wrong because when the first sign of trouble appeared I started doing all kinds of **** to try and fix it, none of which worked and I have lost track of what I did in the process of trying to root and then subsequently trying to fix. I know there were some wipe cache, wipe dalvik cache, install zip from SD, I may have even tried to flash a custom ROM without the thing being rooted. I have been reading for days, trying this, trying that to no avail. The phone is brand new, without a scratch. It will power up like normal, but when it gets to the lock screen where you swipe the little lock in the bottom tray to use the phone it will not respond at all! It recognizes the network because it is displayed in the notifications bar up top, it can see the signal strength, it knows what time it is, it knows what the date is, but it will not get past the damn lock screen. ADB sideload works. I was able to push a zip and flashed it, even said android is upgrading when I rebooted, but it did not solve my problem. It will not power off, but when I hold the power button down, to turn it off the back arrow < and home symbol flash and after about 10 seconds a dialog box pops up that says to restart your phone continue to press and hold the power button and starts a countdown. Once the countdown gets to zero it restarts. If I hold the volume down button while doing this it will go into the boatloader and I can get into recovery. Apparently there is no backup to restore because when I try a restore I get the same exact same thing. I thought I had done one, I must have erased it somehow. I have been trying to resolve this for weeks now and am at my wits end. Any suggestions please !?!? Will anyone on this forum take it if I ship to them and fix for a fee? Otherwise this things going in the trash.
Hi All,
So today I was messing around with a Led Zeppelin custom TTFont, I first tried installing it and changing the permissions and owner/group and rebooted. Rebooted fine, but no option in Display/Fonts to actually change it to that type. No biggie, I just edited the name to match Coffee font Regular, backed up the original of course and rebooted.
Now I am stuck in a boot loop. But here is what is weird (to me).
I go into the LG boot options screen (Hold down Power and Volume Down until LG screen appears, quickly release then reapply those two button combinations until screen appears) and cleared cache, no biggie, still boot looping. Again I go into the Boot options and this time I choose safe mode, still boot looping.
Now I am frustrated because I think I have probably load the .tot file and start over all my customizations, but before I do I restart the phone one or two times, hold the volume up while its bootlooping, then down, then all 3, then both volumes, basically just playing with different key presses while I watch the soccer match. No biggie and I have nothing to really lose at this point...
I pull the battery, hold the volume up key so I can start getting into download mode then all the sudden I feel the phone vibrate like it turned on but I get no screen, just black. So I plug in the USB thinking its waiting for me to start up the download mode since I never turned the phone on myself and all the sudden my windows machine which I have the USB plugged into shows the SDCard.... I double tap my screen and bam, phone is at my desktop never accessing the lock screen or showing the VZW logo.
So like the complete tool I am, I go back into /system/fonts and notice that I had renamed the Kashmir.TTF to the right file name (can't remember the exact name of the coffee font, but it was correct) but left the TTF in caps. I know from my linux days that things are case sensitive so I edit the file to "whateveritwas.ttf" check permissions, check owner and group again, and reboot. Now I am stuck in bootloop again and was wondering if anyone knows if I just hit some magical keystroke I didn't know about that bypasses the VZW file check @ boot which allowed the system to ignore the fact /system/fonts didn't match? Does the VZW G3 even do a file size check at launch like that? Could I have just let it sit there long enough and "thought" I pulled the battery but didn't and just after a while it worked itself out?
Anyway, I don't mind re-flashing that isn't the point of the post. I am more curious how I got it to boot without the VZW logo, bypassing my lock screen and allowing me to get to my phone without using safe mode. Any thoughts? If I can't figure it out in an hour or so I am just going to re-flash the tot file, but I wanted to mess with this for my own curiosity and wondered if anyone else has encountered this before I wipe my phone and start over.
Koroz said:
Hi All,
So today I was messing around with a Led Zeppelin custom TTFont, I first tried installing it and changing the permissions and owner/group and rebooted. Rebooted fine, but no option in Display/Fonts to actually change it to that type. No biggie, I just edited the name to match Coffee font Regular, backed up the original of course and rebooted.
Now I am stuck in a boot loop. But here is what is weird (to me).
I go into the LG boot options screen (Hold down Power and Volume Down until LG screen appears, quickly release then reapply those two button combinations until screen appears) and cleared cache, no biggie, still boot looping. Again I go into the Boot options and this time I choose safe mode, still boot looping.
Now I am frustrated because I think I have probably load the .tot file and start over all my customizations, but before I do I restart the phone one or two times, hold the volume up while its bootlooping, then down, then all 3, then both volumes, basically just playing with different key presses while I watch the soccer match. No biggie and I have nothing to really lose at this point...
I pull the battery, hold the volume up key so I can start getting into download mode then all the sudden I feel the phone vibrate like it turned on but I get no screen, just black. So I plug in the USB thinking its waiting for me to start up the download mode since I never turned the phone on myself and all the sudden my windows machine which I have the USB plugged into shows the SDCard.... I double tap my screen and bam, phone is at my desktop never accessing the lock screen or showing the VZW logo.
So like the complete tool I am, I go back into /system/fonts and notice that I had renamed the Kashmir.TTF to the right file name (can't remember the exact name of the coffee font, but it was correct) but left the TTF in caps. I know from my linux days that things are case sensitive so I edit the file to "whateveritwas.ttf" check permissions, check owner and group again, and reboot. Now I am stuck in bootloop again and was wondering if anyone knows if I just hit some magical keystroke I didn't know about that bypasses the VZW file check @ boot which allowed the system to ignore the fact /system/fonts didn't match? Does the VZW G3 even do a file size check at launch like that? Could I have just let it sit there long enough and "thought" I pulled the battery but didn't and just after a while it worked itself out?
Anyway, I don't mind re-flashing that isn't the point of the post. I am more curious how I got it to boot without the VZW logo, bypassing my lock screen and allowing me to get to my phone without using safe mode. Any thoughts? If I can't figure it out in an hour or so I am just going to re-flash the tot file, but I wanted to mess with this for my own curiosity and wondered if anyone else has encountered this before I wipe my phone and start over.
Click to expand...
Click to collapse
Interesting. It sounds like you may have found a button combination that allows full root access like custom recoveries regardless of minor changes to the integrity of the /system directory. This could be a major step towards a bootloader unlock or more likely a Loki exploit.
acparker18 said:
Interesting. It sounds like you may have found a button combination that allows full root access like custom recoveries regardless of minor changes to the integrity of the /system directory. This could be a major step towards a bootloader unlock or more likely a Loki exploit.
Click to expand...
Click to collapse
I know for a fact I bypassed VZW Logo and the lock screen 100% (or they just never displayed as the screen was black the whole time), the part I wasn't paying enough attention to was how it happened and I am really kinda irritated at it because its something I am usually paying attention to. I wish I had the old input recorders we had from Sony, anything we would key press during development would be recorded and when bugs would happen we could run them back.
I played with it probably for another 4 hours trying to recreate the situation again and it never happened for me. I then re-ran the tot file and put the Android L fonts on to see if it was just the Kashmir font (Led Zeppelin font) being size mismatched with the one I replaced, but all of the file sizes were the same on this L pack and it got through the VZW check, yet caused all sorts of UI problems and crashed upon load to the system shell. With that causing the systemui to crash over and over I was unable to do anything so I re-flashed again. I was going to re-create the bootloop tonight and see if I can do it again, but I went to hempfest instead. /shrug I have priorities man!
How the problem occurred
So a year or two ago I bought a Jiayu G4A/T/Whatever they're calling it and safely got it here. I've used the stock ROM for a bit but I wanted to get rid of the bloatware that was still on it, so I eventually ended up with a properly rooted phone with a ROM from Jiayu.es (Everything worked, have ClockworkMod as recovery, accessible via Mobileuncle Tools), which was essentially a stock Kitkat rom made to work for the phone. Now I got sick of the ROM and recently saw the new EMUI version on Huawei's P8 Lite, so I figured I'd look around for a tailored ROM running that, and ended up at "jiayu-emui-3-0-stable" from Needrom.
What I did
1. I downloaded a ROM from Needrom with identifier "jiayu-emui-3-0-stable" (I can't post external links)
2. Backed up my important files following a guide from androidcentral titled "[Guide] How to Backup and Restore Apps and Data when installing new ROMs" that I can't link,and did a full backup using CWM
3. Placed the ZIP on my internal SD card, went into recovery, wiped data/cache (not dalvik, since it wasn't described in the instructions, I think this might be a probable cause) and installed the new ROM from ZIP
4. Rebooted the phone and now it's stuck in the boot loop I mentioned.
What the problem is
Bootloops aren't that much of a problem usually, except this one is... I can't get into recovery mode. From there on it'd be cake, since I made the right preparations, but I can't get into it. While connected to my PC it keeps powering on, showing a splash screen from Jiayu.es briefly (which shouldn't be present anymore) and powering off after 10 seconds, only to come back to the splash screen.
What I've tried
I've unplugged it, removed the battery, waited to get a full power cycle and tried to hold my buttons in these combinations: [power button + volume up], [power button + volume down] - but neither work. It just keeps going with the boot loop. I can succesfully power it down, and when I plug it in from there it shows the low battery image. At the moment of seeing that I thought I could connect to it using ADB / Fastboot, but no luck there either. It keeps saying no devices found, and with fastboot it keeps on <waiting for device>.
My questions
What exactly can I do if there is no way for me to get into recovery mode? Are there any alternatives? How can I get my device to be recognized by ADB? Is that even possible? Why is this bootloop any different from others?
Update from the massive Q&A thread:
ZipAddict said:
Is it booting up on its own too after being off? This happened to wifes phone and it turned out the power button was stuck. I took a pencil and hit the power button with the eraser a few times and it worked then. Her case mustve dislogded it. I will keep my fingers crossed for u. If not send me a private message and i will look for an answer tomorrow and get back with u
Click to expand...
Click to collapse
Thank you for the reply!
Yes, it does. I took the battery out and let it lay disassembled for a night, after which I cleaned it a little and re-inserted the battery. With the case back on, nothing happened, so the power button wasn't stuck for sure. When I powered it back on with the power button (no USB attached) it showed the emblem for ~8 seconds and powered off. It then buzzes to show it's powered on again and up comes the splash screen again. Could it be that the ROM was just a rebooting falsehood? Why would it disallow me getting into recovery mode? I really hope there is something that can still force the device into recovery mode / interact with it somehow while in this state.
Oh, I also tried to see if the volume down button was broken but all the contacts seem intact, plus, they worked an hour before I started switching roms.
Hello and thank you for anyone bothering to read this.
I got a CAT S50 and was experiencing a bit of instability lately.
I've run LTE_S0201121.0_S50_0.023.00 without a hitch for a while, then it decided to crash several applications, from google play to any other app open.
That's when I decided to do a factory reset and see if it would help. Performed the rest without a hitch, but the errors kept coming back. At one point, the screen went black. I knew the phone was on because the backlit was working. I hard-reseted it (hold the power button for 30 seconds or more) and rebooted. The phone froze on the CAT splash logo screen and that's when I hard-reset it again. But when I tried to turn it on, the phone simply refused to work. No vibrate, sounds or anything. It's dead.
When I plug it on the computer's USB, the PC makes a sound as if it detected the device, but when I go to the device manager, I get this QHSUSB_BULK with the yellow exclamation mark
I want to know if it is possible to unbrick this phone and if so, if there is a tutorial or if someone can direct me to the correct procedure. I looked everywhere for the ftf file for this phone to attempt this with flashtool, but I simply can't find it.
ANY help of any form is greatly appreciated.
Sadly I had the same thing happen to me, just a black screen. It decided to delete recovery mode or I just cant get to it.
Power Off the Phone,
While pressing Press Vol Down + Cam Button insert a Powersource -- hold down Vol Down + Cam
Recoverymenu should start
Then flash the original rom via ADB Sideload or SD Card.
btw. i have flashed the LTE_S0201121.0_S50_0.023.00 but i want test older ROMs!
can anyone link or upload an older ROM ?
Guy i have the same issue, can you please help me
I got the same problem I search lots place but still nothing then normal update rom anyone can help?