Hi,
I have a Note 4 t-mobile that is "brick" right now. and I hope if anyone offer assistance.
It is running Android 6. Ever since the last upgrade the phone would freeze and reboot on its own. I fixed that problem by installing Wake Lock. After that it would still experience sluggish at time but the phone is still very much usable.
Lately, after watching a bit of streaming video the phone would slow down so much that a reboot is needed. But yesterday my last reboot turned my phone into a brick. After that reboot the phone rebooted itself to the download mode. So I took the battery out, waited for a few minutes and put the battery back in and started the phone. Instead of booting normally the phone displayed the message including "set warranty bit: recovery" and then followed by the flashing TWRP splash screen. By "flashing TWRP splash screen" I mean the TWRP splash screen ( with the TEAMWIN logo) would be shown on the screen for a second, then the screen black out for a couple of seconds, then the splash screen is back on for a second, and the screen black out for a couple of seconds, etc, and never successfully boot into TWRP recovery. I had left the flashing splash screen overnight and nothing changed. Connect the phone to my pc via usb and fastboot wouldn't recognize my phone when phone was flashing the TWRP splash screen. So I tried to flash TWRP again by starting my phone in download mode "volume down + power". When I connected my phone to my pc Odin recognized my phone. But when I tried to flash a custom recovery (TWRP or CWM) it seems the download started but never finished (on the phone I could see the progress bar started but never progress further).
Any suggestions would be greatly appreciated1
Additonal info
I just wanted to add that my phone is still running the stock ROM.
Problem solved
Problem solved. Once I used a different cable and the download process actually worked and I was able to flash stock ROM using Odin.
Related
Hi,
I have a N4 that was new but the screen cracked on it and eventually the battery died as well (wouldent hold a charge). I got the battery and screen replaced but as soon as this happened I could not boot into any rom. I had twrp installed but everytime I tried to install a rom such as CM it would install but would stay stuck in the boot loader. I then used NRT to try and kick it out of bootloader and I tried several different stock firmwares, 5.01, 4.4.4, and 4.2. The only rom that was able to get past the boot animation was 4.2 it went to the welcome screen to choose a language but I could not select anything via touch screen. In that screen I could lower and raise the volume via the rockers and turn the screen on and off. I had twrp installed and the touchscreen worked fine in twrp. I also tried this: http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060 and it also let me get into the developer firmware but of course it is encrypted so I could do nothing. The phone has not had contact with water etc. Do I have any other options? Can I get some type of diagnostic such as logcat or something?
Thanks!
This morning I was in bed browsing Reddit when my phone suddenly crashed and rebooted.
I put it aside to let it boot up, but after a few minutes when I looked at it the screen was just white. Rebooted it again, it then went into boot loop at the splash screen.
I attempted to get into recovery, but to no avail.
Attempted a few more restarts to get the phone up and running but no luck.
So I decided I must flash stock firmware onto it. Did that through Odin, seemed to be successful according to Odin, but my phone stays on the splash screen while it says "recovery booting" in the top left corner. After a while it boots up again, this time only the splash screen, no text in the top corner. But its stuck in a boot loop.
Flashed firmware and PIT file, then flashed philz touch recovery and still stuck on the splash screen.
Tried older firmware versions and still no luck
I'm at a loss as to what steps to take next..
Well, something must have caused that crash. Maybe hardware failure. Reason why it wont boot up. It can't be software related since it wont even boot up any software, except for recovery and download mode.
You might try flashing a different bootloader, since that's the thing that controls the OS booting.
This problem started when I moved back to Arya from a 5.1.1 port few days ago. I didn't bother much, cause I keep my phone on always, but whenever I wanted to go to Recovery or reboot the phone it would not boot, would stuck at the Note 3 N9005 logo and I had to do a battery pull to solve the problem, so yesterday I thought about flashing a stock ROM via Odin, and now the phone won't boot at all regardless of the battery pull method!
I can't enter recovery either, it stays at the Entering recovery (SELinux status screen) for a few seconds and then just a black screen with nothing at all. I did flash the TWRP tar image via Odin after flashing stock ROM yesterday, so that I can do a complete wipe, but nah, can't enter TWRP. Download mode however works after a battery pull.
Here is a video, probably the worst quality video you have seen lately, but it still does show the problem :laugh: So kindly tell me what to do! I have a non working phone for over 12 hours now, and I am realising how much I depend on a phone now, that feeling is inexpressible.
how did you solve it ?
Hi Guys,
I am facing a peculiar kind of problem in my phone (G900F) since yesterday.
What happens is that, if I tried
i) To restart my phone from the phone (reboot menu), the phone stuc in boot screen and then vibrate twice then after 5-10 sec the phone start rebooting all along once again with 2 vibration and this process keeps repeating until I pull out the battery.
ii) To access recovery (both hard- key combination or from reboot to recovery option in phone), the phone reboots and it stays in the initial screen for about 45 seconds and then the screen went black and freezes there until I pull out the battery.
iii) To access download mode ( both hard- key combination and reboot to download mode option in phone), there seem no problem.
The weirdest part is that, if I remove the battery for 5-10 min and re-insert the battery and do any of the above options; the phone reboots and i get the home screen loaded successfully with no problem . I can also get into my recovery after this 5 mins switch off just like the above. I also found the phone lags a bit in this home screen.
I almost did all the combination to get off this problem (stated below) but I keep getting this problem again and again.
I was in Sixperience v 3.1 with Pheonix Kernel v 10 and Philz CWM recovery and tried the below to try to fix the issue
1. Re-flashed Kernel from Recovery (Also, tried to re-flash kernel after uninstalling Xposed but no use)
2. Re-flashed Modem and Bootloader from ODIN once again (G900FXXU1CPF7_BL_G900FXXU1CPB8_MODEM_LTE.tar)
3. Reflashed ROM once again as a fresh install through Philz recovery.
4. Restore the cwm backup from recovery (which was backed up a week before.)
5. Flashed Samsung Stock MM ROM (G900FXXU1CPFH_G900FPHN1CPFD_PHN.tar.md5) as a fresh install.
After this stock ROM installation is done, the phone struck at SAMSUNG flashing logo and the blue LED keeps glowing for more than 30 mins)
Nothing works. ? Any idea on what is to be done to fix this issue? I am not sure, what i did but this problem keeps coming even after trying of all of the options since yesterday.
Please help to with your expertise.
Device was working fine until OTA update to 6.0.1 (MMB29M.G900FXXU1CQDA). It wouldn't boot past the Samsung logo.
I downloaded that same firmware (and the one before) and flashed it via Odin 3.12.7, however situation remained the same.
Flashed TWRP 2.8.7.0 and then PhoenixROM 15.0 and device booted fine. However it would always reboot after display stays off for 3 seconds.
Flashed TWRP 3.1.0-1 and then LineageOS 14.1-20170802 and device booted fine again. The reboot problem remained the same.
The reboot problem is NOT present while device is connected to a PC, however it is present while connected to an AC wall socket.
Each time the display goes off the device stays off for 15 seconds before booting again.
Anyone got similar experience, any advice?
eqagunn said:
Device was working fine until OTA update to 6.0.1 (MMB29M.G900FXXU1CQDA). It wouldn't boot past the Samsung logo.
I downloaded that same firmware (and the one before) and flashed it via Odin 3.12.7, however situation remained the same.
Flashed TWRP 2.8.7.0 and then PhoenixROM 15.0 and device booted fine. However it would always reboot after display stays off for 3 seconds.
Flashed TWRP 3.1.0-1 and then LineageOS 14.1-20170802 and device booted fine again. The reboot problem remained the same.
The reboot problem is NOT present while device is connected to a PC, however it is present while connected to an AC wall socket.
Each time the display goes off the device stays off for 15 seconds before booting again.
Anyone got similar experience, any advice?
Click to expand...
Click to collapse
Flash stock lollipop and report back.
godkingofcanada said:
Flash stock lollipop and report back.
Click to expand...
Click to collapse
Did. Same case as with Marshmallow.
However there has been further issues, seems the phone can't be saved.
After flashing Lolipop the phone wouldn't boot via power button, but instead I need to boot it to Download mode and hit cancel.
This however makes it go to Recovery mode. Trying to boot the system from Recovery makes it power off.
Tried flashing TWRP back and when I enter it, the device keeps choosing random options rapidly, as if it's constantly detecting touch across the screen.
Therefore I'm no longer able to flash LineageOS back.
Gave up on the device in the end, seems to be defective.
eqagunn said:
Did. Same case as with Marshmallow.
However there has been further issues, seems the phone can't be saved.
After flashing Lolipop the phone wouldn't boot via power button, but instead I need to boot it to Download mode and hit cancel.
This however makes it go to Recovery mode. Trying to boot the system from Recovery makes it power off.
Tried flashing TWRP back and when I enter it, the device keeps choosing random options rapidly, as if it's constantly detecting touch across the screen.
Therefore I'm no longer able to flash LineageOS back.
Gave up on the device in the end, seems to be defective.
Click to expand...
Click to collapse
It sounds like the touch screen is going wonky. Or the mobo has an issue. You could get it diagnosed at a shop reasonably cheap