I was running Cyanogenmod on a Note 4G. For the past month, however, the battery was draining very quickly and the phone would shut off randomly, many times a day. I decided to roll back to MIUI. During the process, something happened to the internal memory, which went from 2/3 full to about 10% full. Recovery disappeared. I tried to use a couple of different MiFlash tools, but those didn't work (it showed it was flashing MIUI but the process went for 3 seconds and then it said it was done. I tried flashing recovery - that didn't work. Tried various methods of flashing a ROM (MiFlash, fastboot, ABD) and those didn't help.
[update] Boy do I feel like a dimwit. I was trying to flash the phone as if it was a Note 4G LTE when it was a Note 2. It's my wife's phone that is the 4G. After pulling out some my diminishing hair the light went on. I then flashed a recovery and now am installing MIUI using the recovery. Yay.
Related
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?
I've been having a lot of battery issues recently and was told by Verizon to reboot my system. "Android System" was taking up 40%+ of my battery, resulting in my battery life plummeting before half the day even ended.
I rebooted my device several times now, and I just did so again in hopes of renewing my battery life.
Now it won't even turn on.
I reboot it, feel the vibration, then see the SAMSUNG logo. It should move on to a screen that says "optimizing applications, please wait", but instead I am getting VERIZON. it never starts up.
I've done this repeatedly for the past 10 minutes, nonstop, and I have gotten no positive results.
Help please!
What can I do?
Have you tried pulling the battery out, waiting a few seconds then putting it back in and switching back on? If you haven't modified your Note in any way I expect this would do the trick.
Do you have the stock recovery that came with the device or have you flashed a custom recovery? If you have a custom recovery you could try erasing the cache then reboot.
Hopefully someone with more experience will be along shortly
Try flashing your latest carrier branded stock firmware from Samsung updates. Do not flash anything else except Verizon stock
Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I am pretty new to this rooting community, been trying alot of things. But recently I have been flashing alot of ROMs, and clearing memories alot. I installed DotOS 8.1 Oreo, worked fine, but after sometime I flashed Pixel Experience 9 not realising its still unofficial, so I reversed. Yesterday, it started to shutdown (or Black out- unresponsive) every time I turn it on. I thought it was the battery, saw it at 5%. I charged it full. Now it does turn on, but shutdowns suddenly at any point. Sometimes, also on TWRP when flashing Gapps or anything else. I am currently using a
Samsung Galaxy Note 3 SM-N9005 HLTE, with a Chinese fake battery (If that is a possible cause - although it worked fine for a long time). I would really appreciate some help.
Thank you.
EDIT 1: I tried using my old original battery, which kind of inflated and broken, but it did boot up. But now it reboots instead of shutting down. Maybe it is the battery? or something with the device?
Flash stock rom via Odin.