Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Theoutbackdream said:
Hi HTC inspire users,
I have a HTC inspire 4g on AT&T that was purchased around last year of March that has never been rooted (too worried about rooting), and a few weeks ago(just found this forum), my phone, to my belief, updated by it self over night. The next morning I found my phone not working at all, and was not able to start up to the home screen. However, the screen was black and lit and kept going through a boot loop. I freaked out, and asked for help on another forum (not phone related forum), and was told to turn off, and factory reset. I did this after removing the SD card so my personal data wasnt wiped. After I did the Factory reset, my phone continued to do the boot loop which has gotten me lost.
Ive been told to do a recovery from the menu by holding down the volume button while turning on the device. Even doing so my phone will not work.
Is there Any way possible to make the phone work again?
Thanks,
Matt
Click to expand...
Click to collapse
ok, pulling the sdcard to avoid deleting personal data is useless. When u do a factory reset all information is wiped except the sdcard..anyway, you have to flash this in fastboot usb.
To boot in fastboot you have to do this: pull the battery, then press volume down + power until you get a white screen with 3 androids at the bottom. Then press power to choose fastboot. Plug the phone to the PC and you should see fastboot usb in red in the cell. Run this exe file (is the official AT&T ruu):
http://dl4.htc.com/RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
If you are not having a hardware issue, then the phone it should reboot normally when done.
Thanks Glevitan!
Ill give this a shot, if something pops-up ill be sure to ask.
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Theoutbackdream said:
Got it working Thanks Alot!!!
However, when i did do the process, i had issue where I couldnt get into the Fastboot menu.. However, I left the phone charging all day and it seemed to cure it. And then the first time I tried to flash the software, it didnt work, second time it had no issues. Could this mean something?
Edit:
After using my inspire 4g for awhile one thing that does not go away is the immense lag from the App Drawer, with no new programs from the market, but the Factory apps.
Click to expand...
Click to collapse
Att Firmware Is a buggy as all the others. It Is weird that You end up in boot loop being stock.....maybe there's something in the hardware that Is messed. Just try to use it and assess the bebaviour of the device for a while, then if nothing Is failing You can try root it and run a custom ROM.....
Glad to have it back....:laugh:
Hey guys,
I just picked up my Nexus 5 and I noticed especially on cameras my camera stops responding and I can't even click "OK" or "Cancel" it's just frozen and i have to reboot it. THis happened to me 10 times in the last hour now... any ideas?
did you do anything to the phone?
root anything.
everything is stock?
Mine does the same thing. It was doing this from day one and now it keeps doing it after I rooted..
Not sure what the issue is, but I probably have to restart my phone about once every three days.
Oh btw, I use face unlock so its really annoying when the camera stops working
I would suggest using this
http://forum.xda-developers.com/showthread.php?t=2513937
or this toolkit: http://forum.xda-developers.com/showthread.php?t=2517778
restore to stock completely, break the root and see what happens.
edit: this one as well I think it will be easiest and then try again. http://forum.xda-developers.com/showthread.php?t=2525026
need more information if you are loading a custom rom/ kernel etc. I know you probably are not but we cannot assume anything.
My Nexus 5 does this even after a full refresh mainly when not touching it. I updated to 4.4.1 and still no luck. Did you resolve yours?
ssconceptz said:
My Nexus 5 does this even after a full refresh mainly when not touching it. I updated to 4.4.1 and still no luck. Did you resolve yours?
Click to expand...
Click to collapse
My Nexus 5 is constantly rebooting itself every 5 seconds. There's no time to try any recovery option while it is turning on because it turns off immediately. Do you have any possible solution for this issue as well?
THANKS!
hello,
my android was acting weird last week, apps acting weird, rebooted on its own many times. i have 4.1.2 on a tmobile gs3 that i no longer have service on (wifi only). i checked and there was an update.
downloaded the 350 mb update. install failed and it said it was going back to the original OS version. i tried updating again. it downloaded the update all over again. install failed again. said it was going back to original OS version but i don't think it finished.
now it won't boot. there are usually 3 boot screens... Galaxy S3 screen, Samsung screen, and android blastoff. my phone gets to the first galaxy s3 screen, then reboots. if i let it, it will show the screen, reboot and repeat until the battery dies. i have to take the battery out to stop it.
i have not tried to reset it yet because i have data i would like to get off of it.
1) is there a chance of getting data off?
2) will i at least be able to use the phone again?
3) what do i do/who do i take it to? i don't have a reliable computer right now to do any diagnostics. my phone was my computer.
i am in the los angeles area if you have any suggestions as to any good places to take my sick phone.
thanks in advance.
jane
umm... what is a bump?
hello
bump?
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Ashleyware said:
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Click to expand...
Click to collapse
Since you've already wiped data, have you tried unlocking the bootloader and flashing the Google factory image
I haven't because I can't. I'm on a Macbook and the Nexus 5 drivers aren't compatible with Macs apparently =/
Wait okay, so I misread what I looked at this morning.
So it says I have to flash a new rom to my phone O.K. but every website says I have to turn on USB debugging--how am I supposed to turn on USB debugging to unlock the bootloader if my phone is bricked to begin with? This doesn't make any f***ing sense!
HELP.
Also, my Mac doesn't recognize my device in fastboot mode; what am I supposed to do?!
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
ldubs said:
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Don't you understand? I can't enable USB debugging because I can't ACCESS my phone! It's stuck in bootloop! I can't unlock the bootloader to begin with! Unless you know how to unlock the bootloader from the fastboot menu, you saying that you unlocked your bootloader doesn't help me. I tried everything in that thread and nothing works, I tried the terminal bull**** and the only thing that happens as I can get into the folder where the factory rom is, but I can't get it to flash, I can't get anything to happen--I don't know what the hell I'm doing.
Is there a way to start over without all of this stupid bootloader crap?
As far as I know ADB is not active in fastboot, it is not recognized. In fact I just flashed TWRP again with ADB off. You do need the fastboot drivers on your Mac installed correctly but that's no big deal. If you have access to your phone in fastboot it is simply fastboot oem unlock to unlock your bootloader.
PROGRESS REPORT
So last night I stayed up trying to fix my issue, and I've had no success. I've managed to flash back to Kitkat 4.4.4 but as soon as the phone boots into set up, immediately I get the error messages "unfortunately Camera has stopped working", "unfortunately Gallery has stopped working", and "unfortunately Google Playstore has stopped working". After setting up, my phone has NO service! It doesn't even recognize if there's a SIM card even inserted, or if I remove it.
I cannot open Playstore, it immediately crashes and my phone believes that it has no storage now, even though I see 12GB of space free. I tried flashing multiple roms and nothing beyond Kitkat will work, otherwise I get caught in a bootloop.
I tried installing Cyanogen mod and although it worked, I had the same issue--no service, no Playstore no storage.
I tried clearing the cache, the Dalvik and factory resetting several times and nothing works. I just flashed 4.4 and I'm updating it to 4.4.3 as we speak.
Also I think it's worth mentioning that every time I got caught in bootloop after flashing a new rom (and I tried all of them, including Lolipop, which always hangs) that when I boot in Recovery mode it says something along the lines of:
Invalid arguement couldn't mount blahblahblahgeniusspeak
Invalid arguement blahblahblahgeniuspeak
and so on. Does this have something to do with my lack of service, camera not working, Playstore not working and storage not working? I'm desperate people.
Have you got an imei number?,settings/about phone
Usually you just flash factory ROM, extract the file and then the second archive and flash each individual file and it should boot, factory reset and wipe cache to fix storage
I do this on my mac
If you can't do this then you may have a hardware issue
How did you try to turn off proximity sensor. There would be another way to keep screen on while skyping (keep screen on wake lock)
Also it sounds like you flashed custom roms without flashing gapps...
Sent from my Nexus 5 using Tapatalk
Definitely sounds like no gapps.
What's gapps? And I have no IMEI number (unknown), it says my (with my SIM inserted) Network is: Unknown
Mobile Network Type: Unknown
Mobile State is disconnected
Out of Service
Phone number is unknown
IMEI SV is unknown
IMEI is unknown
Not roaming either
What's the second archive? Every guide I used said use the flash-all.script and that's all you have to do, what're all these extra steps? How do I flash gapps, I don't even know what that is; I don't see the file anywhere in the factory image folder.
=/
I flashed again (back to stock; 4.4) and did everything manually instead of using the script, I even flashed the cache.img, recovery.img etc . . . and it's still the same issue. No service. No external storage available. No Google Playstore.
=/
I didn't flash a custom rom, I only flashed the official factory image from Google. Why doesn't anything ****ing work.
Is gapps going to return my storage and service?
Gapps is only for custom ROM. Since your imei etc is unknown seems like you have bad efs partition. I am not 100% sure. May be others can help.
Sent from my Nexus 5 using XDA Free mobile app
I've just experienced a strange spontaneous reboot. I noticed my Nexus 5 was indicating 'optimizing application n of nn' exactly like what happens with an update. I thought - looks like it's decided to OTA to LMY48M. But no, after 'updating' all the apps it's still on LMY48I. What's going on? I can understand a spontaneous reboot but not one which goes through the process of updating the apps.
Trev
Same here
Well, I don't have a solution for you but it looks like I have the same problem. Mine has been doing the same as you describe for the past 2 or 3 days. In addition I get hard boot loops many times before it finally decides to boot up (accompanied by the apps updating like you describe). It continues to hard boot loop even if I kick it to the bootloader, at least it does a bunch of times and then suddenly stops and seems to work for a little while.
Just FYI I was able to just now initiate a factory reset from the settings menu. It seemed to be working for a while. It took a long time to erase phone but then booted and walked through initial setup. All was well and it was about halfway though restoring apps when it suddenly hard reset and began boot looping again. So I guess it's on to more difficult procedures now.
ccjb100 said:
Well, I don't have a solution for you but it looks like I have the same problem. Mine has been doing the same as you describe for the past 2 or 3 days. In addition I get hard boot loops many times before it finally decides to boot up (accompanied by the apps updating like you describe). It continues to hard boot loop even if I kick it to the bootloader, at least it does a bunch of times and then suddenly stops and seems to work for a little while.
Just FYI I was able to just now initiate a factory reset from the settings menu. It seemed to be working for a while. It took a long time to erase phone but then booted and walked through initial setup. All was well and it was about halfway though restoring apps when it suddenly hard reset and began boot looping again. So I guess it's on to more difficult procedures now.
Click to expand...
Click to collapse
Sounds to me like your power button may be going out buddy
Sent from my Nexus 5 using Tapatalk
crazymonkey05 said:
Sounds to me like your power button may be going out buddy
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I guess time will tell. It was looping very fast though, too fast for just a stuck power button. That also doesn't account for the apps updating as if there was an android update when there was not. At least I don't think so. Button could be in it's way out even so.
To update the OP: I seem to have fixed it, at least so far. Since I was able to eventually get into the bootloader with enough stability to do something (by holding down vol/power, and trying a few times), I was able to to fastboot flash Cyanogen recovery. Rebooting to CM recovery I was able to wipe reset, adb push CM12 and gapps, install.... and try again. Since then I have been stable. I have gotten though a full restore of 70+ apps, and phone currently syncing. I've manually rebooted a few times and it seems ok for the moment. Just thought I'd let you know where I'm at.