Dont be so impatient and stop the update. You will brick your phone.
Some people have had to wait 5-7 minutes before the phone restarted and finished the update.
http://androidforums.com/samsung-captivate/182923-dont-do-ota-update.html
I don't know about others, but my phone automatically reboots after 50%.
heliumhelicopter said:
I don't know about others, but my phone automatically reboots after 50%.
Click to expand...
Click to collapse
Yep reboot at 50% and then tells you that it failed with no way to start it up again.
A successful update is slow to start (it prepares longer).
Failed one usually races to 50% and displays "Update is Failed" and reboots.
It is not the patience of the user in question.
Related
My HD7 has started randomly restarting not just once but over and over , it gets to the HTC splash screen and then reboots over and over.
I just pul out the battery leave it for a bit and then its ok until next it happens.
Also It will not update it gets to part 7 of 10 and that completes 14% then I get a connection error I have tried it many times.
Anybody got any ideas?
confrontation said:
My HD7 has started randomly restarting not just once but over and over , it gets to the HTC splash screen and then reboots over and over.
I just pul out the battery leave it for a bit and then its ok until next it happens.
Also It will not update it gets to part 7 of 10 and that completes 14% then I get a connection error I have tried it many times.
Anybody got any ideas?
Click to expand...
Click to collapse
Sounds very similar to the problem I had with my Mozart. I ended up taking it back to the place I bought and they replaced the main board in it.
Mine is/was a standard ROM by the way.
I've just got my one x home and after setting the device up, went straight for the software update. its been at it for an hour now, and is just hanging on the install screen (green sync symbol with the arrow in the middle).
should it take this long? my old DHD never took this long to install updates...
That's strange. The whole installation took me about 1-2 minutes.
Do you have the charger connected? if you do then disconnect it, it says on the update info that the charger shouldn't be connected during the update as it may cause problems.
d.chatten said:
Do you have the charger connected? if you do then disconnect it, it says on the update info that the charger shouldn't be connected during the update as it may cause problems.
Click to expand...
Click to collapse
you're a star! unplugged it and its starting to boot as i type. i was crapping myself this whole time
edit: strangely enough, it didn't charge this whole time. its down to 7% battery now so need to charge before i can play with it some more
I have the same problem and I don't have the charger connected! Is there anything else I have to do to finish the update?
have u tried resetting the phone to factory settings and try the update again. some people managed to get it working this way
Argh, I have just custmized the phone... Is there any other way?
Hello,
I am an owner of HTC Sensation, rooted with Android Revolution 7.3.
My phone has ~1,5 years, since its first days i was using Android Revolution ROM, never had any problem.
Today, my phone first lost signal. Itcould not connect to any mobile network so I tried to restart it, when i got back to it after 5 minutes, the phone was stuck on beats audio logo and when i touched it, it felt very hot, it was never that hot even I used it for hours playing some games or browsing internet. (I think it was processor, down side of the phone, below battery, but because of that battery got a bit hotter too) I had to pull off the battery, I've waited till it got cold and tried to run again but rom was not working so i reflashed it from my sd card, after the next restart (phone did not get hot) when phone was checking installed apps, it simply turned itself off. Before battery showed around 80% charged, after reinstall 30% and it happened in max 10 minutes ,but after that shut down I could not turn it on. LED was not working, I tried pulling off battery, charging it, charging without abttery then connecting it, trying to reboot with abs but PC could not see the device.
The only thing I noticed, when i was trying tocharge it for the first time, processor was getting hotter but LED was not working, but then, it simply went cold.
I have no idea what I could do more here, it looks like hardware problem but te only thing i could not check was putting a new battery and try it then. Is there anything I can do more about it?
For any help, thank you.
PS: When the phone 'died' it was using faux123's 1,5 GHz kernel which came with the ROM. AsI said, before this event, everything was working perfectly, no sign of this incoming event. No restarts, freezes or crashes.
*If it matters, i was charging phone every 4-5 days, never let it go below 10%, bettery is from HTC EVO 1730mAh (original).
can you boot to the bootloader?
if yes do it and select from there reboot
see how it goes
rzr86 said:
can you boot to the bootloader?
if yes do it and select from there reboot
see how it goes
Click to expand...
Click to collapse
I can do nothing. No reaction.
MarcBliz said:
I can do nothing. No reaction.
Click to expand...
Click to collapse
try this
remove battery,sim and sdcard and charge as it is for 4-5 hours
put them back and switht it on
see how it goes
also give it a try with a different battery
if everything fails then try this
http://forum.xda-developers.com/showthread.php?t=1522351
i am not sure if you will have much hope but try it anyways
rzr86 said:
try this
remove battery,sim and sdcard and charge as it is for 4-5 hours
put them back and switht it on
see how it goes
also give it a try with a different battery
if everything fails then try this
http://forum.xda-developers.com/showthread.php?t=1522351
i am not sure if you will have much hope but try it anyways
Click to expand...
Click to collapse
Re-tried these methods, hoped I had done soemthing wrong before. I saw the artice before, was hoping there are different ways to revive the phone. Tried this, says device not found. Looks like the only method would be this JTAG box but it's a bit expensive or try to send it to repair.
Anyway thank you for your time, I appreciate it.
-And if I might ask, any idea why the phone heated up itself on nearly last startup as I mentioned in my thread? It would be allright if the phone just died before this event, now it just makes me think there might be bigger hardware problem which just caused the death and it's not worth repair.
This phone started rebooting frequently about 30 hours ago. Sometimes it won't power back on right away. Being plugged in makes no difference. It's sometimes rebooted mid-boot. Am on the PFD program. Haven't seen an update applied for at least a few days before this started happening. No new apps. I went through a factory reset earlier today but it's continued to happen in the last few hours. Any bright ideas what I could try at this point?
altintx said:
This phone started rebooting frequently about 30 hours ago. Sometimes it won't power back on right away. Being plugged in makes no difference. It's sometimes rebooted mid-boot. Am on the PFD program. Haven't seen an update applied for at least a few days before this started happening. No new apps. I went through a factory reset earlier today but it's continued to happen in the last few hours. Any bright ideas what I could try at this point?
Click to expand...
Click to collapse
You can try the hard reset.
You can also try reflash your Hardware Product Code (= origin ROM) with Nokia Software Recovery Tool software.
Careful: The two methods will remove your personal data.
It seems like it's worked itself out. It was happening for about 4 days. I restarted on my own (independent of its frequent self-reboots), factory reset it, pulled battery, tried everything I could and it kept rebooting, until it just kind of stopped. I have no idea what was going on.
altintx said:
It seems like it's worked itself out. It was happening for about 4 days. I restarted on my own (independent of its frequent self-reboots), factory reset it, pulled battery, tried everything I could and it kept rebooting, until it just kind of stopped. I have no idea what was going on.
Click to expand...
Click to collapse
I have something similar. I have Lumia 830. With Windows Update 8.1 Update 2. My Reboots are random:
* Sometimes reboots constantly for about 10-15mins.
* Sometimes few reboots and full startup of system.
* Sometimes using for different time periods, it reboots.
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Cappelletti said:
Hello, everyone.
I'm using an OPO since october 2014 and I had no intention of buying a new phone in the near future. But now I'm worried about it.
Abouth three weeks ago, my phone started to freeze and reboot. At the time I was using sultan's latest ROM. I thought the problem was the latest updates and, as I wanted to test Nougat, I decided to download Lineage.
To my surprise, I kept having random freezes and reboots.
While reflashing ROMs and changing kernels, I had some reboots. Yes, self rebooting while on recovery.
So I decided to get it totally back to stock and re-start fresh.
Phone froze and restarted on COS initial config. And, after that, rebooted again when updating Gmail apps.
During these three weeks, it kept on with no reboots for, at max, around 40 hours.
Is there any way I can test my phone to determine if it's a hardware issue? It all makes me think it is. :/
Any clue is welcome.
Thanx.
Click to expand...
Click to collapse
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Mr.Ak said:
Get your device checked at a local shop. Looks to me like a battery or logic board issue.If it's battery then you can get a replacement but if its logic board then yes,you should consider buying new device.
Click to expand...
Click to collapse
I'm fairly sure that there is no local shop that could check it.
Right now, before checking this thread, I let the battery completely drain and now it's on the wall recharging. I'll enter recovery when it's 100% charged and do a factory reset. Then install everything back and use it for a few hours.
Let's see it that helps.
Thanx for the reply.
- phone battery completely drained
- phone battery completely charged
- booted to recovery and factory reseted
- initial COS configuration done without any freeze and/or reboot
- updating Google Apps
So far, so good.
And it rebooted twice, during apps update.
Although it updated main Google apps, it was not supposed to reboot.
:/
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
iPusak Gaoq™ said:
Hmmm...if random reboot but able to boot normally afterwards then you need to tweak the kernel a little bit but if is random reboot and then stuck at 1+ logo or bootanimation then your battery is dying....
to check whether the battery is dying just wait until next reboot...if it stuck on 1+ logo or bootanimation, turn off the phone completely then plug in the charger...it it charge for 5 minutes in offline mode then turn it on while the charger still connected...if its boot normal then it is confirmed that the battery is dying...replace a new battery as quick as possible...
Click to expand...
Click to collapse
It does not get stuck. At times, it reboots during boot. Some times (rarely) it does that for two or three times and then turns off. But most of the time it freezes, reboots and I can use it normally for hours and hours.
seanwlk said:
I've been living with random freeze+ automatic reboot since COS13 it's a PITA but doesn't cost me anything to wait 1min until full reboot, only problem are lucky patch on boot which take longer but nothing that bad. I was never able to troubleshot the issue, usually happens to me when I receive some notification I see the LED and try to unlock but the phone stays blacked out (even though it's clearly on since notifications are shown on the LED) until I force reboot.
Over the years I tried insane amount of ROMs and kernels, nothing changed, adding to that the fact that 10% of the times when i put it in charge (original charger+cable) says 7h or 6h until full charge (and I actually have to wait all that time), I just have to unplug and try again until it fixes. It's not the charger because I tried it with other phones, so I started to assume my problems are the small board with the charging board + battery. But I never had the willing to change it. I'm "fine" with how it works.
Click to expand...
Click to collapse
I'm "almost" fine with the way it works for me. As most of the time it's fully operational.
I found a OPO with damage screen for sale here. He guy didn't want too much $ for it. I bought it and will receive next week. Will try to swap logic boards.
Let's see what happens.
Was able to have logcat running when the device froze (during game) and rebooted.
Is anyone able to see any error on the log that could make the device freeze and reboot?
Got the broken screen OPO two days ago. Yesterday my phone was impossible to be used. Rebooting like hell.
I swapped logic boards and all is fine. No freezes and reboots (of course, it's pratically another phone). I kept only my screen, housing and battery.
My logic board had a 2.5 sticker on it. The one I got now has a 2.1 sticker. Does anyone know what's that about?