I recently saved my phone from a brick with the test point, I have managed to get into the system, however at the time I receive an update of the December patch I update it and at the end of the update and give it to restart so that it is installed it stays in a restart loop, it reaches the screen android one and it reboots.
In the ROM that worked for me, it was the "tissot_images_8.1.10_20180110.0000.00_8.0_8ea503201b" however does not recognize the sim, I try flash with mi flash the last update but the screen of "Android One" is displayed and it is restarted, without being able to enter in the system.
Related
Hi, I installed the latest update but I have a "slight" problem.
The update went ok, I pressed finished and the phone rebooted. But it stays frozen on the HERO in booting screen. Left it like that for 10mins, then removed the battery, rebooted, and same thing.
I pressed back and powered it up to fastboot, connected to pc again and run the installation once more. It recognised it as having the latest update but i reinstalled it anyway. Now i have it frozen again for the last 20mins
Any idea what could be wrong, or I just bricked my phone?
Did you apply the "official" update or a mod of it?
It was the official update from HTC's site. Tried to boot to the recovery image in case i could use a nandroid backup i had, but it won't let me upload it to the phone soit can boot. I guess it's the new loader with the update
Change the sim you are using and it wont freeze .
Ever since receiving an OTA update a few days ago, my phone was never able to successfully reboot again. Instead, it does exactly this when I turn it on: Samsung logo appears when booting, then the At&t logo with the word "installing..." or "updating..." along with a loading bar at the bottom appears. The loading bar reaches 100%, but then it will say "update failed", and it reboots and the same process happens again. I've let the phone run on it's own for several ours to see if it'll ever snap out of the loop, but it just stays in the same never-ending cycle of constant rebooting and updating. My phone wasn't rooted and worked perfectly fine before the update, so I suspect something went wrong while it was updating. I tried pressing the home, volume, and power buttons in attempt to initiate a recovery boot and do a factory-reset, but nothing happens. And I've tried replacing the battery, SIM card, and micro SD card, but there's still no change. I still am, however, able to set it in ODIN mode, but I'm not sure what to do since I'm not techie/literate. Please help, I don't know how to get my phone properly working again.
I have a Note 4 and I was very satisfied with the performance until a few weeks ago, an upgrade to Android 6.0.1 was downloaded and applied.
It seems the update failed and despite I'm now in Android 6.0.1, the phone is working very erratic. Sometimes it freezes for a while (10 seconds, 30, 1 minute, 2 minutes) and then just continues as normal (when it freezes for more than a minute, it goes directly to lock screen ). Sometimes it says some app or system process (touchwiz and the like) has failed and sometimes it simply reboots without any reason. I have restarted it in secure mode but there is no difference.
I have uninstalled all downloaded apps but there is no difference. I have reset it to factory defaults but keeps failing.
I have downloaded latest 6.0.1 Firmware from Sammobile and flashed it with Odin but the fail is still there.
One thing I have noticed is when I start in recovery mode (power+home+vol up), instead of the recovery menu, the android robot appears and the text installing update. It goes for a while, then crashes (robot with red triangle) and then the recovery menu appears. This happens every time I start in recovery mode so it looks like there is some update that was applied (since I have 6.0.1 instead of 5.x) but only partially.
Any help?
is there a way to revert it back to Lollipop?
Hi!
Same thing happened to me. Connect to a computer and use Samsung Smart Switch to do an emergency recovery.
But the phone will be erased.
After that, my Note 4 got even better than before!
Good luck!
Tried Emergency Recovery but phone doesn't show up in the list, so I tried Update Firmware. It told me the firmware I have would be replaced by current version (The SAME version) but I went ahead anyway. Firmware was downloaded from internet, phone booted in Download mode and Smart Switch copied the firmware to the phone, then restarted, installing... Error Message: "No Command", nothing else.
I removed battery, rebooted and error message appeared telling there was a problem with firmware update and I would need to use emergency recovery from Kies (I understand I have to use Smart Switch, no Kies). So I connected it again to Kies and opened Emergency Recovery but once again, it doesn't appear in the list. So trying again with Firmware update. If this doesn't work, I'm afraid I have a very expensive paperweight
Failed again. At 25% update, Download screen showed:
ODIN: flash write failure
A window in Smart Switch tells me something went wrong and offers me Emergency Recovery. It also tells me I have to write a recovery code if using another PC. The recovery code is blank. not a good signal.
Again, Emergency Recovery is showing nothing in the list of devices
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
jedikalimero said:
Ok, I finally downgraded to Firmware 5.1.1 using Odin and the phone is alive again, but I don't think everything is OK. First time I tried to update the firmware with Odin, it failed at the middle of the process, just like Smart Switch did. But second time it completed the process and rebooted. I will leave it as is a few days for testing and if no issues appear, I will allow it to update OTA. In any case, if update OTA fails again, I always can go back to where I am now.
Restarting in recovery mode now shows the android guy with the blue thing spinning (no text) and after a while the fallen android guy with the danger signal and then the recovery menu. That's not what should appear. It should go directly to recovery menu, so I think it is still not 100% good.
Click to expand...
Click to collapse
please keep posting your observations, i am on the verge of trying flashing 5.1.1 myself.
would be great to know if this resolves our issues.
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
I went to the repair service. The guy there didn't know how to fix it an told me to send it to Madrid for repair. But I haven't sent it yet for two reasons. The phone is still under warranty (as ANY OTHER Note 4 bought in the EU), but first, he told me it would take 25 days to repair (this is Spain, you know. In UK it would take 3 days) and second, my front glass cracked so I had to take it to a repair shop to replace just the glass for 30 euros instead of the 200 euros it would have costed to replace the whole (and totally functional) screen officially. So I'm afraid they would find out the glass was replaced and take this as an excuse to void my warranty. In older models you could replace the glass and nobody would notice it, but in the Note 4 you have to break a copper heat dissipation foil that lies between the back of the screen and the metal frame in order to disassemble the phone.
jedikalimero said:
Phone kept failing also with 5.1.1 so it was not a problem of the Android version. The difference is that while at first phone freezing was the regular thing and reboots were the exception, now reboots are the regular thing, so the situation is worse.
Since it was failing with 5.1.1 and the situation was not better but worse, I didn't wait anymore an installed the OTA update that obviously appeared as soon as the phone booted in 5.1.1
After the phone said it would reset itself, it didn't turn on again. I had to turn it on manually and the the installation began without any incidents. then a new OTA update appeared (this time only ~350 MB). I'm not sure if this was a new update that appeared yesterday or was already applied when mi phone updated to 6.0.1 before the problems started.
So I accepted this update and it was downloaded but then failed to install and the phone told me to contact the repair service.
So now I am just as in the beginning, with a failing phone that freezes and reboots frequently.
Click to expand...
Click to collapse
so sad!
I have a stock moto x play whose hardware sku is XT1564. It's on android ver 5.1.1 and system version is 23.21.25.lux_lra.en.US
I have not performed any soft mods or alterations, be it root or bl unlocking.
The only thing that I would think is different than normal is that the phone is encrypted, so it asks for password whenever it boots up.
I got a notification to update to 24.74.5.en.US a few days ago and decided to try doing it today.
It downloads the update fine and when I press on the notification for it to start the update process where it says it needs to perform a reboot to update it goes into a "phone will reboot in 10 seconds" screen and when countdown finished it shows the "shutting down..." popup that appreas when you try to shutdown the phone.
Then the phone stays with that popup until it finally shutsdown like 4 minutes later on what appears to be a hard shutdown because it doesn't reboot. I have to manually power it on and then the phone starts up normally asks me for my password and about a minute after android fully loads the phone tries to shutdown again without any input. And then it just keeps doing that until I boot the phone into fastboot and try to get it to bootloader, where it shows the dead android logo with a red yield sign and promptly shutsdown. Then when I start the phone normally it shows an "update unsuccessful" screen.
Anyone have any idea what might be the problem?
I've been thinking it might be the encryption but IDK. Also I've checked the thread with the firmware versions and couldn't find mine there. Is there a way I could dump mine for backup in case I **** something up trying to get OTA to work.(without unlocking bootloader and rooting, of course)
Now the update has stopped appearing and I can't get it to recognize there being an update for this device.
Fudge!
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!