Hey,
I've been looking around here quite a while now to find a solution, but I can't find one. So that's why i made this post.
My N-910C was running Sweet Rom 17.1 and Googy Max Kernel, everything worked fine. But after 3 weeks my phone starts to crash immediately after locking my phone, or after it automatically turns its screen off.
I've tried flashing the stock rom, that didn't work, after flashing it's crashing when it says 'installing system update' and after a few times it says 'No command'. After that I flashed Googy Max Kernel back on my phone and it boots, but when my screen turns off my phone will crash again.. My options in recovery are limited due to the fact it reboots after a while without any reason.
Is there anyone here that knows how to fix this? Or is it possible to do something to get it fixed with warranty?
Thanks for your help
Update: Tried to flash stock rom with the newest firmware(N910CXXS2CPB3_N910COXA2COJ5_N910CXXU1COJ5_HOME.tar) with Odin 3.10.7(with Phone bootloader update on), passed, when rebooting it said 'Installing system update', but before it was finished it said 'Erasing...' aaand a reboot again. But than it showed the Samsung logo animation and it crashed at showing the first 4 letters. After that I flashed Philz 6.58.9 to flash Googy Max 2.0, the phone now works, but is still crashing when the sreen turns off.
Related
In advance, I normally try to fix problems myself thus I dont post much, so I'm sorry if this is in the wrong area. I have already spent about three hours researching and trying to figure this out.
I've gotten sick of the loads of Verizon bloatware slowing down my phone, so I finally pulled the trigger to try safestrap. I'm using the ME7 build so that was the only option.
Safestrap installed without a problem. I flashed Hyperdrive successfully, but the ME7 modules available here would fail to flash even after I checked the MD5. I flashed from another source here successfully.
After all of this, when I boot the phone into that module, it will go to a black screen after the "safestrap enabled" logo. After about a minute, the phone will vibrate, show the Samsung logo, and then go into ODIN download mode.
The only thing I can do now is hold the volume down during start up. This loads a warning about how installing a custom OS will catch your phone on fire with a continue option (which results in the ODIN block), or a Cancel option (that restarts the phone and shows the safestrap logo before going to the black screen etc.) From this I can change the boot default to the stock OS if I choose, but I still cant use Hyperdrive. I have already tried deleting the ROM slot and starting over, but that didnt help.
Thank you so much for the help!
Edit: I tried bonestock and just got a black screen.
Edit 2: I also tried google edition and it would go to a black screen, restart, and loop again.
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
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.
Hello,
I suddenly started to have big problems with my Note4.
Everything went fine for about a half year (I bought the device from ebay).
Then, suddenly without reason, the phone rebooted.
Each day I got more and more reboots (it starts with freezings and then turns off), and eventually the device rebooted every 5-10 minutes.
From time to time, I got the message "kernel panic!" with "emmc read fail".
So I tried my best with google, nearly everyone said that the emmc flash is corrupted and has to be fixed by Samsung - but because my decive has knox 0x1 triggered, this is no option for me.
I already flashed the Stock Rom again with Odin, after a full wipe of everything.
This didnt change the problem.
So I've read about PIT files and repartitioning, and flashed the PIT file for my SM 910F DBT. The reboots cycles changed from every 5-10 minutes to every 30-60 minutes, sometimes everything was fine for some hours, but there still were these suddenly reboots, and everytime I had to remove the battery to got android booting up again.
I cant remove the battery so many times a day, I thought, so I searched for another solution again - thinking of something like checkdisk, to find the corrupted flash cells and maybe exclude them from use, so they couldnt crash the phone.
I found a description with android adb and "fsck" and thought that this may fix my problem - I tried and it failed, because I needed to root my phone again (maybe).
This is why i flashed twrp again. My phone booted in the new, custom recovery automatically. I wanted to put the zip file for superSU and the file for the custom Kernel (think I need that for root?) on my internal SD, so I wanted to shut down and boot normally - TWRP said "heey you dont have root, should we root your phone now? swipe for yes!" or something like that, so I did as they said.
From now on, I werent able to boot into normal android again. Neither into the recovery mode, the screen just stays black.
I can still boot into download mode - but everytime when I try to flash something with odin, odin starts and after a few minutes, he gives a red line : "flash write failure".
I'm totally upset and dont know what to do anymore. Is my note4 dead now, forever?
If you have any suggestions, please write something. I will be very thankfull, I need my phone very badly :/
Edit:
If I try to boot normalley, I got the message "Firmware upgrade encountered an issue. Please select recovery mode in Keis & try again."
Kies troubleshooting says that it doesnt support my device..
Chocsy
no idea, everyone? still stuck
Look at http://forum.xda-developers.com/note-4/help/note-4-freezing-restarting-t3348821 , installing wake lock worked for me
Update 2018: emmc chip died later.... Needing wakelock is an indication emmc is going south appearantly
My Galaxy S4 VE (GT-I9515) crashed. (the screen went black) It was not rooted and ran the latest Andoid 5.0.1 ROM.
When I turned it on, it went into a bootloop, randomly crashed during booting, or turned on normally. I removed sd and sim card and tried a different battery. Furthermore I tried to boot into recovery mode and wiped the system data and the cache. It did not help.
Sometimes it was not possible to get into recovery mode because the phone's screen went black and it rebooted.
Then I tried flashing multiple stock ROM files using Odin, but it did not solve the problem.
After that i tried rooting the device and installed a custom recovery (TWRP), but i still got random crashes during booting and sometimes it got stuck showing the samsung boot animation. The only things that work reliably are the Download Mode and the charging animation.
Now, what can I do to fix my phone?
I read a bit about flashing a .pit file but I don't think that will help?
Is this a hardware or a software issue?
How can I find out, what caused the problem?