Hi all,
Been using these forums for awhile to get help rooting devices, but I've finally got a problem I can't get resolved after searching for days. My T-Mobile S4 (testing with CM12) randomly froze last Friday, and upon rebooting it wouldn't stay in the OS for more than a few seconds before freezing and rebooting again. I went into recovery and cleared cache/dalvik but it didn't make a difference. It got to the point where it would freeze before letting me even unlock the screen. I chalked it up to running CM12 before it was stable so I wiped the phone and tried CM11. The flash succeeded fine, but the phone froze right after going through the initial setup wizard. Since then, I've tried:
Flashing various recoveries (CWM, TWRP)
Various ROMs (CM10, CM11, Paranoid Android, Samsung Stock)
Sideloading ROMs without an SD card inserted in case mine had issues
It seemed to be the most stable when I booted up a new ROM without a SIM card or SD card inserted, and left WiFi off. It still froze, but not as fast. I've since bought a used HTC One m7 to get by with but would really like to get the S4 straightened out so I can sell it. I managed to install logcat and get it running before a freeze but after inspecting the logs I couldn't find any trace of kernel panics or other errors.
Should I assume the phone has a hardware error? I'm open to any suggestions anyone might have. Thanks guys.
Well, since it happesn on various roms then it is most probably a hardware problem.
Or it has a fault in a partition that is unaffected by rom flashing.
GDReaper said:
Well, since it happesn on various roms then it is most probably a hardware problem.
Or it has a fault in a partition that is unaffected by rom flashing.
Click to expand...
Click to collapse
That's what I was afraid of. Couldn't find any kind of bootable hardware diags for the phone either
drew_t said:
That's what I was afraid of. Couldn't find any kind of bootable hardware diags for the phone either
Click to expand...
Click to collapse
Don't know if it might help, but try a different bootloader and modem
Related
Hey guys. I'm trying to figure out what's going wrong with my Transformer. I'm not experienced with Android development/ROM's so please bare with me.
Rooted my first Android device about a month ago. Made a stupid mistake placing the ROM I was planning to use on the external SD card & didn't backup the install I wiped. Recovered with an official Asus ROM & after about two hours fiddling around I managed to root & load my first ROM (Revolver, whoot!). Very pleased with myself!
Have been using the Revolver ROM for a month without any problems. No deep sleep etc, everything worked perfectly. Using the latest version of Clockworkmod, also no issues so far. Strange thing is that since last monday everytime I (re)boot the device it loads CWM instead of the Android OS. I can get back into Android bij holding volume down during boot & choose to cold boot. Not a big issue but very annoying & can't seem to find the fix.
Searched Google & XDA for a solution. Updated Revolver to 1.3.1 beta, also found the repack by Koush for CWM. Tried fixing permissions, clearing cache, clearing dalvik, wiping & starting over, etc. Everything I tried so far does not fix the CWM-loop I seem to be stuck in.
Would really appreciate some help, I'm probably looking in the wrong direction here. Thanks in advance.
Found something
Finally got out of the CWM loop, found a solution here: http://forum.xda-developers.com/showthread.php?t=1622814&page=2
Strange thing is that after I flashed it with the fix CWM changed to the touch mod I recently installed but never seemed to work. If I understand correctly the fix only deleted the first few lines in the config where the boot in recovery flag should be.
Afterwards I factory wiped the unit & flashed it with a clean ROM. Currently re-installing my apps. I do not have a good feeling on this, tablet seems sluggish last couple of days & I can hear a soft click when the unit reboots. Same sort of click a laptop hdd would make.
Think it's dying on me...
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.
PAST SITUATION
I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.
PRESENT SITUATION
This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.
HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.
WHAT I TRIED TO FIX IT
1) A clean installtion, did a task 29 and installed everything again. Same problem happens.
2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! Even with that version it still gets stuck on the Android logo screen.
I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
did you get things sorted?:cyclops:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
I'll post my results here soon.
SpoonyVoid said:
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
Click to expand...
Click to collapse
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
SpoonyVoid said:
Well not yet. I am working on it. Does anyone
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
Click to expand...
Click to collapse
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.
WHAT I DID THEN
I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.
So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.
Nigeldg said:
Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
Click to expand...
Click to collapse
Thanks for the reply. I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.
And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.
I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated.
I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant I don't have any actual experience with Windows Phone though, so I wouldn't know.
As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
SpoonyVoid said:
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
Click to expand...
Click to collapse
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Nigeldg said:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Click to expand...
Click to collapse
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
SpoonyVoid said:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
Click to expand...
Click to collapse
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.
As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
Sent from my Nexus One using xda premium
A logcat would be really useful when:
-ever your ROM gets stuck after a reboot.
- You face any random force close.
I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.
Was the market working prior to this problem?
Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)
You could also give cLK a shot, and see if the problem persists.
So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!
Try a different kernel, also, pull the battery for 5 min, it will boot.
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash
id try odin
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//
Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.
fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up
fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.
samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok
fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear
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).
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?