I've been on my way to turn in my Nexus 7 were I originally bought it in July 2013 due to several issues: the famous screen problem where the tablet seems to live a life on its own and where your only option is to do a hard reboot and also that it's been charging awfully slow the latest months.
Hower, a few weeks ago, it suddenly wouldn't start up normally. It always gets stuck on the Kitkat animation.
Just half an hour ago, after managing to charge it full via my computer, I booted it to recovery mode and emptied the system cache partition. That didn't solve the problem. I'm not even able to get to the recover menu anymore.
The reason why I'm not turning it in is because i'd like to do a backup on my files that are on it. Oh, and I should mention that the tablet is completely original and not rooted.
Any ideas? It'd be too bad to loose images etc...
Anyone?
N4 boots only with external power. On Battery it Turns Off. At first, it only happened if there was a SIM card inserted. The Battery never had any issue before this update. Any idea what could cause this issue? Did the 5.1 Update fry my precious phone? It did get really Hot.
Phone Details:
Nexus 4
Unlocked bootloader, Not Rooted, Stock
Installed factory image of Android 5.0
Sideloaded 5.0.1 using adb
Installed 5.1 using OTA with 750MB free space.
Solutions Tried:
1) Factory Reset in 5.1
2) Flashed factory image of 5.0.1 successfully
3 )Safe Mode
4) Wipe& Clear Cache/Factory Reset
5) Upgrading to 5.1 OTA using adb sideload cmd
Update: Also Tried the following using NRT
6) Re-locking Bootloader (OEM Lock)
7) Downgrading to 4.2.2 (JDQ39)
8) Upgrading to 4.4.4 (KTU84P)
9) Unlocked Root and installed TWRP
10) Unrooted Bootloader and flashed Stock 5.1
11) Drained the battery by leaving it at the bootloader screen.--> Result: Red Light of Death.
Observations:
Managed to boot the phone after the Red Light Of Death while plugged in to 2A port of an external battery. Its been over an hour still says 5% Charge and 3 Hrs until Full.
While trying to do a Nandroid backup with compression in TWRP running on battery, CPU temperature increased from 45C to 55C and it shutdown. The same options with external battery works even though CPU temp goes up to 63C. Battery was at 93%.
The Issue:
After Installing the 5.1 OTA from 5.0.1, My Nexus 4 keeps shutting down even if the battery is charged 100%. There is no battery drain.
At first, I thought it happened only when the phone switched from 3G to 2G network. Since, It worked fine using 3G network or Airplane Mode. But Now, the phone doesn't get through the Google icon at the bootloader and just shuts down if its running on battery.
Unless Its plugged in to a charger or external power source there’s no way of getting the phone started. The phone worked fine if there is no SIM card inserted or in Airplane mode even if you disconnect the external power. But, if you try to restart again it fails to boot up on battery power.
Upgrading Process:
I received the OTA notification for 5.1. Due to insufficient space, phone would not download the update file. So, I deleted ~150 photos while it was downloading. I had approx. 750MB free space and 70% battery. This caused the phone to heat up (deleting/downloading) and reducing the battery power. I used an external power bank while the phone started the upgrading process. I disconnected the power when it completed. The phone successfully booted up and started optimizing applications after which it shutdown immediately. I powered it up and was checking what’s new in 5.1 when it shutdown again even though there was like 30-40% charge. After this “The Issue” started.(Refer above)
It was the Battery!!!
I'm guessing, It ignores the battery temperature sensor while upgrading or it could leave the device bricked. Thus, leading to The End of Days of my battery
It was the weekend, so the only option I had was to pull my hair and try all possible software methods.
So good to have my phone back. Only wish I had taken a Nandroid backup
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!
Please help! My S5 Neo was in a drawer for a few months after the LCD got smashed. I recently bought a new LCD assembly and connected it to make sure it worked before fitting and it was fine. However, the phone immediately started doing a software update but was interrupted after a few seconds as the battery was dead. Now the phone won't power up or boot into download mode or recovery. When I plug the phone in to its charger, the LED flashes red but nothing is displayed on the screen. I had a new battery for it and charged it in another device but still no joy. I've been messing around with old galaxy phones for a couple of years now, flashing custom ROM's etc, so I wanted to just re-flash a stock ROM into it but there's no way I know of performing this without getting the device into recovery or download mode. Does anyone have any ideas? The device is totally stock and hadn't even been rooted. I'm currently using an S4 Active running Lineage OS 17.1 so I'm not desperate for a phone, but I loved my S5 and really would like to get it up and running again. It never once had any problems.
Even before I had issues it would stay relatively warm when just charging it at 5W (it still does that when it's turned off) so I started suspecting liquid damage (prior experience) or the battery starting to show its age even though it's only been charged about 300 times. This all started after I flashed LOS on it where hwc was disabled. The phone had pretty much stayed unused until late 2021 and was meant as a dev/backup phone.
After a second hard crash it stopped trying to boot and will now only enter Download mode and nothing else. Prior to this I only had to reflash it, but this time it's not looking so good.
I'm too facing the same, tryin to revive my cousin's s8, which is not even rooted once. Tried flashing stock fw using odin. It just doesn't show samsung logo but still goes to download mode. Any help devs?