Hey guys,
So I've been running on stock EPD1 and everything had been running smoothly. Last night my phone randomly shut down, even though it was at full battery. After trying to restart it, I got stuck in almost a boot loop. It would boot, and during the Samsung animation, it would freeze and restart. This would happen twice until the phone gave up I guess and the phone stays at a black screen with either a constant blue LED, or a blinking whitish-purple LED. I have tried using ODIN to flash back to stock EPD1 and EPF1. Both were successful in ODIN, but didn't solve anything. I can flash TWRP, but flashing any ROMs doesn't help. Wiping Data, System, Cache, and formatting hasn't done anything as well. I also used the Smart Switch and Kies emergency software recovery and initialization features. Again, both said they were successful, but didn't change anything. Sometimes the boot gets to the point where it says "Android is optimizing apps," but once that finishes, it crashes again. Am I 100% screwed? Thanks to anyone that can offer some advice.
Small update: After using the emergency recovery feature in Kies once more, the phone booted to the green "Android is starting..." screen and it counted through 35 apps and said it was starting. It crashed at that point. Not sure if that's progress.
Related
The Gnex became very slow and there were apps and processes constantly crashing.
Did a factory reset, and the phone got bricked. The screen was just black, it didn't show a sign of life, not even the google logo.
Then I tried to unbrick it with OMAP flash or something, then it booted, showed the google logo, and then the nexus logo.
Then it crashed and rebooted.
I tried reflashing the stock rom using odin.
That didn't do a thing.
Next, I installed TWRP recovery and installed Cyanogenmod and Gapps.
And its still in bootloop.
I don't know what to do now, please help me!!
Is it still fixable??
Thanks in advance
DaanDeAap said:
The Gnex became very slow and there were apps and processes constantly crashing.
Did a factory reset, and the phone got bricked. The screen was just black, it didn't show a sign of life, not even the google logo.
Then I tried to unbrick it with OMAP flash or something, then it booted, showed the google logo, and then the nexus logo.
Then it crashed and rebooted.
I tried reflashing the stock rom using odin.
That didn't do a thing.
Next, I installed TWRP recovery and installed Cyanogenmod and Gapps.
And its still in bootloop.
I don't know what to do now, please help me!!
Is it still fixable??
Thanks in advance
Click to expand...
Click to collapse
"Did a factory reset, and the phone got bricked. The screen was just black, it didn't show a sign of life, not even the google logo." - Why did you think it was "bricked"? Did the battery die? Also, why did you use OMAPflash before trying to recover the device with fastboot/factory images (or even odin)?
That said...
Are you 100% sure it flashed TWRP? Did you wipe data/factory reset before flashing CM/Gapps?
Anyways... boot to fastboot (device turned off, hold down both vol keys+power until you see the android flying, big "START" letters at the top, small letters on the lower left corner), then flash factory images. Don't use any toolkits, learn fastboot if you have too.
Wel,I thought the phone was bricked because it wouldn't boot up properly. I tried omap flash because it was the first thing I found about fixing a bricked Samsung. I know the bith volume Keys + power but the phone wouldn't do anything. It didn't even boot in fastboot.
I'm having problems getting my phone past the bootup screen. It first loads the logo then goes to the animated logo then the rethink possible animation and then finally gets stuck on the glowing samsung logo. It then shuts off and redoes the loop a couple of times until it stops with the battery charge up screen and freezes there until I remove the battery.
History: Purchased an att phone for the mb to replace my original phones because it had the insane chip. Had to root it to be able to unlock the phone with my carrier(telus). Since I was in it I flash the DN4 custom rom and everything needed into the phone. The phone functioned fine for about a month and then frequent freezes and restarts started happening. Near the end, the phone was stuck in a boot loop, loading into the DN4 animation boot screen then shutting itself off then on again to endlessly repeat the loop.
Present: At first I was able to get into TWRP and tried some things in there but nothing happened. When there I notice it stated "internal memory 0"-not sure if this means anything.
I was able to flash the saved recovery file from TWRP. Once I did that I could no longer go in TWRP and now have to use the samsung install/recovery.
I have since flashed the stock rom several times with odin and also wiped data/factory reset many times still does the same in bootup. Tried flashing TWRP into phone using odin 3.07 but failed.
What should be my next move? Pretty new at this so I may be missing something very simple or perhaps a dead phone???
Finally got the phone to boot up and run fine. It seems everything was good except the battery was acting up.
Next step is to get the battery to charge when phone is off.
I'll post this question in new thread.
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
I tried reflashing it another few times and now I actually got into the setup screen and got to the home screen. It charges somewhat normally but it still boot loops when I start it. When I plug the charger in when it's looping it boots fully and I got to the point where I installed an update. Not I'm stuck in a loop on the T-mobile splash
Try a new battery.
Bell-wether said:
I was playing pokemon go and I got a facebook messenger message, and my phone just crashed and started boot looping at the Galaxy note ii screen. I tried going into the recovery and deleting the cache and factory resetting it, tried flashing it with ODIN, and nothing seems to be fixing it. I've tried flashing it to the stock rom too, but that seemed to make things worse? Now half the time when I try and turn it on it it wont turn on unless I plug it in or remove and put back the battery, when I try charging it when it's off it turns on and I can see the battery screen, but it freezes either when loading or when the animation plays. There's no red light and I'm not even sure it's charging.
I can get to the CWM menu and the recovery menu, I did have the Nandroid backup files but it seems like I mistakenly deleted it, so that's an option. I tried flashing it with different firmwares and it doesn't seem to make a difference. The first time I flash it it usually goes to the T-Mobile splash screen, which plays the little animation and sound but stays at that screen. Any Ideas?
Click to expand...
Click to collapse
Did you try Samsung Kies' emergency recovery option yet?
Hey all....I'm calling on the experts! I have a friend of mine's s8+ Sm-955U from Verizon. She woke up one morning and it was boot looping. I've tried using ODIN, reflashing the original rom, wiped cache, did a factory reset, and even used the pit file and repartition in ODIN to try to restore it. All it does is get stuck at the s8+ logo screen, goes black and you can feel a tiny vibration when it goes to black. It usually just sits there, sometimes it will just reboot over and over. I've done everything I know. Is it possible that the NAND would be bad? Or what wears out if it's hardware related? It boots just fine in recovery mode or download mode and ODIN always shows success when flashing. Anyone know of anything else to do?
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.