Related
It tried to install the update, got to 50%, rebooted and told me that the update failed and that nothing happened to my phone. Why did it fail and when will the update work, if ever?
Well the first time I tried to download, my stock rom was Rooted and Bloatware was removed and the update failed to install at 99%. Then I one click back to stock and I got to 50% and failed! I just installed the rom from samfirmware and no issues, I just need to get a hold of an old version of titanium backup!
HTH,
Charlie
anyone? 10char
I tried again to update, it got to the update screen, after a while it said "Perparing" then "update failed phone will reboot". Whats wrong?
i got to 100 and then said failed,
im rooted
caelestis2 said:
anyone? 10char
I tried again to update, it got to the update screen, after a while it said "Perparing" then "update failed phone will reboot". Whats wrong?
Click to expand...
Click to collapse
im having the same problem and i cant find anything on how to fix it
caelestis2 said:
It tried to install the update, got to 50%, rebooted and told me that the update failed and that nothing happened to my phone. Why did it fail and when will the update work, if ever?
Click to expand...
Click to collapse
Same thing here. I am rooted with the one click root from these forums.
One thing I have noticed in general is my reception is worse with the Captivate than with my old iphone 2g. Also battery life is worse as well.
I hate Apple and love the Captivate. But if this keeps up any longer I am off to verizon and the Droid X. A coworker has it that sits right beside me and its great. He just got the 2.2 update yesterday and everything went fine. Also he can check for an update whenever he wants instead of every 24 hours like ATT. I will pay to get out of my contract and either put this phone on ebay or chunk it.
Maybe this phone can be the first test of my new rock skip app. Here's the idea... you skip your phone like a rock across the water and it records how many skips it took! LOL
I know how you feel, but you have to try to keep a sense of humor through all this!
I mean think about it, we are all driving ourselves crazy trying to figure out how to get the phone to install an update. Hours and hours wasted trying to figure out why the install fails.
And if we ever do get the update to install, no one really even knows for sure if it does anything beneficial....you know you may have a point....another phone is sounding better and better...umm where do I download this rock skip app...
failed at 99 then at 50
I had same experience as another user, rooted, failed at 99%, now gets to 50% then fails. However firmware listed as new version. Also, GPS fix is now SCARY FAST, 3 second inside a building supper accurate, no, error bubble. Quick office for captivate now shows up in market. Media scanning is at least 5 times faster. I think the update actually succeeded for me even though it said fail.
I'm having the same problem. I download the update but it gets to preparing and it fails. Anybody know a reason why? I'm rooted and removed bloatware.
Sent from my SAMSUNG-SGH-I897 using XDA App
You guys got farther than I did. I have not received the push notification. Yesterday I initiated the pull for the update over wifi, and the download never started -- it just said connection in progress and hung... no error message. Then I had to wait 24 hours. Today, I initiated the pull over wifi, and after about 30 minutes the download started, but the download hung at 14% an hour ago. I called AT&T, and they said they had no info, please call Samsung. I called Samsung, and they said they had no info, please call AT&T. So nobody can tell me why I cannot get a measly little download to complete, nor can the tell me when or if I will get the OTA push. I guess I can try the download every 24 hours and maybe one day it will work.
You may have better luck if you try to use Edge or 3g to download the update. I can't get the update to install but I can get it to download not on wifi but on 3g. Might help.
I have a Samsung Galaxy S I897 running GB 2.3.5 on the AT&T network.
Here is my problem:
I upgraded from Froyo to GB. Everything was fine except that nagging force close of the tethering manager. After much researching, I had to do a hard reset and the phone worked fine.
I then decided that I would try Easy Battery Saver. Without researching this further than customer reviews, I figured it would be helpful. I decided it was a P.O.C. app and got rid of it. Then the problems really started. (DO NOT USE APPS LIKE THESE, for anyone new reading this post.)
The settings remained after deleting the app and I noticed that my battery life was worse. Once I got below 50% battery, I would lose all data connection. My 3g would disappear, then the bars, then I would be left with circle and line. Sometimes my phone would just shut off and show that I had no battery left, this after having the phone charging all night, and after about 5 minutes of use.
I called AT&T... not much help there. I got a new SIM, I did a few battery cycles to bring it back to normal, hard reset the thing like 5 times. I gave up!
Now, I downloaded ODIN3-one click and tried a complete ROM restore. It worked great! I got back to eclaire. I re-installed Froyo then GB. I hoped this would solve the problem. I went ahead and re-installed my apps. One being the Opera Mobile Browser. I went to use my browser. SAME ISSUE AGAIN! I lost my data connection within 2 minutes. OMFreakinGoodness already!!
I'm frustrated and do not know what to do next other than throw this phone out the window doing 90 on the freeway.
Here are my questions:
When running ODIN, should I have used the master clear option after it said it was done? All I did was hit start and it said it was done, so I figured it did what it needed to.
Is Opera Mobile the culprit? I only started using it about a couple of days before using the battery app.
Do I need to format my internal SD? Will Master Reset with ODIN3 do this for me? (Once all was said and done, everything is still on my internal SD.)
Please help. I am a N00b when it comes to working with Androids completely and I am just starting to delve into the modding portion of being an android owner.
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:
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 can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.
You paid to root your phone?
This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.
ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.
You can't OTA update a rooted phone
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update
Can u explain further how to freeze the updater service?
Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.