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.
Related
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?
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
Hello everyone ... I think I dun goofed, but perhaps someone knows something that I don't :\
So today I wanted to switch to a new Custom ROM... standard procedure I guess. Without doing anything, btw, apart from using my phone, I got several random reboots into bootloop today, especially while texting, which I didn't get at all, but didn't mind because they ceased after several times.
So I get home and get cracking ... backup my Contacts, try to make a NANDROID backup, which gets stuck while backing up /data ... which I didn't get, but unfortunately CWM didn't wanna react after this, so I had to hard reset, and lookie lookie, it rebooted into Android. Now, however, nothing works.
I put in the battery, the bootloop begins, not even a press of the Power Button is needed, I press the combination for Download Mode, actually SEE THE WARNING SCREEN, can't however proceed because the reboot begins immediately after, and CWM won't load either
Does this mean I'm pretty much f'd in the a?
EDIT: Welp, seems like removing the battery right when the loop starts makes it so that I have to press the power button again which makes me able to access both Android and CWM, I literally have no clue how this could have come.
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!
Hello.
I hope someone here can help me.
I successfully flashed Leedroid on my HTC One M9 today. I still wanted to try another ROM, so I installed that one and then decided to go back to Leedroid. As I was flashing Leedroid again my phones screen suddenly turned black (I think at about 80%, didn't see it exactly though...) and after trying different things (combinations of buttons, charging and waiting some time) it won't turn on again. I can tell that the phone somehow boots up, because I can access all the files from my PC when I connect it via USB, also adb shows the device with "adb devices", but as offline. I selected a clean install of HTC_M9-port_LeeDrOiD_10_V4.0.0-R119_rev.78.zip from https://forum.xda-developers.com/one-m9/development/rom-leedroid-one-m9-v7-0-0-rc1-march-t3068468.
It seems like the phone only starts in some way if I press the power button and volume up and volume down, at least then I see the files on my computer.
UPDATE: I seem to be somewhere in the Setup (I guess), if I press Volume Up to turn up the sound and then press power and volume down I can hear the screenshot sound.
UPDATE 2: I figured out a way to get to the twrp recovery adb shell and tried restoring my backup (System, Data, Boot), but the screen stays black. I'm now hearing the default HTC boot sound, so my backup seems to be restored...
I can't post the install.log because I'm not allowed to post links and the text would be too long if I just posted it here...
Also I'm new to custom roms...
Does anyone know anything I can do right now? I have a full backup with twrp from before I installed any ROM, but I can't even see if the phones boots to some menu like the bootloader oder download mode, because the screen stays black...
Any help is greatly appreciated!
Update
If anyone finds this thread and is interested how it turned out:
Since I could not get the screen working again I sent my phone to a repair shop. They tested the phone and told me that a circuit board is broken and they can't repair it.
I'm still not sure how this whole thing happened, but it seems like I'm going to buy a new phone...