So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.
Related
So i was going to flash a rom I made a back up, I hit fixed permissions. and now all I have is Samsung Galaxy S4 logo and is just stuck there. I can get into twrp and have tried wiping and starting from a clean slate and restoring the back up but still get the galaxy logo? any suggestions ?
**have just tried to use odin and fails also*** How do I get back to stock please? Anyone please help
bump
Imprezive13 said:
bump
Click to expand...
Click to collapse
Have you tried flashing a stock ROM from TWRP?
-------edit----------
I just remembered. This used to happen on the Note 2 at times. If you're booting and get the Samsung splash screen, try going to TWRP and doing a Factory Reset a couple times. No idea if it will work, but with the Note that would usually clear whatever block existed and allow the ROM to boot past the splash screen. Good luck.
eakeller said:
Have you tried flashing a stock ROM from TWRP?
Click to expand...
Click to collapse
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Imprezive13 said:
what do you mean ? first time ever having a problem with this. are you talking about the SCH-I545_MDK_562219_Stock_Restore.tar file ?
Click to expand...
Click to collapse
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
eakeller said:
If it exists, it would basically be that ROM stuck into a .zip file which could be flashed from TWRP. I'm not sure it exists, was just browsing the Dev thread for you to see if anyone posted it. There is a version here http://forum.xda-developers.com/showthread.php?t=2292707 , but I'm not familiar with Loki enough to say whether or not you have it.
Click to expand...
Click to collapse
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Imprezive13 said:
Well for right now im trying to just get the phone back to its working condition. trying to using odin, but fails every time. and not sure what i should do.
Click to expand...
Click to collapse
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
-edit-
Sorry, just saw your OP where you said you wiped and tried. If I were you my next step would be trying a different ROM just to see if you can get something booting.
eakeller said:
If Odin isn't working for you, a solution might be had via TWRP since you can still get into the recovery. If you flash your ROM or try your backup, does the install complete or does it crash? Have you wiped cache, dalvik, system, and data before the flash?
Click to expand...
Click to collapse
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Imprezive13 said:
Trying again. First wiping wiped cache, dalvik, system, and data , then restoring back up. I've tried this multiple times before hopefully it works this time. But generally when i hit reboot system afterward it just hangs at the Samsung Galaxy IV boot screen and does nothing.
Click to expand...
Click to collapse
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Failed again stuck at Samsung Galaxy S4 boot screen
eakeller said:
After your backup restores, try using TWRP to do a Factory Reset a couple times before rebooting. Also wipe cache/dalvik again before the boot.
Click to expand...
Click to collapse
Stuck again
Imprezive13 said:
Stuck again
Click to expand...
Click to collapse
Sorry to hear that, man. I'm out of ideas and hopefully someone with more know-how can give the solution.
Sent from my SCH-I545 using Tapatalk 2
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
I would try downloading a ROM to your computer then copying it to a microsd, put the card in your phone and then try to flash the fresh ROM from TWRP. (After wiping everything again.)
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Ive been looking for the stock rom files no luck at the moment.
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Maybe this one?
http://forum.xda-developers.com/showthread.php?t=2292707
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
downloading now wish me luck
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
Good luck to you.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
got it working. on a deoxed rom. but is there a way to go completely back to stock using odin ?
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
slim6596 said:
http://forum.xda-developers.com/showthread.php?t=2289325
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Well went to restart the phone and now its stuck on a Samsung logo with a unlocked icon thats says custom underneath it and just sits there.
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
Sometimes if my phone freezes up and I need to do a battery pull my phone will randomly bootloop. This has happened to me about 3 or 4 times on all kinds of roms, tw and aosp. One time on a tw rom it ended up booting into the samsung setup wizard. It was weird because it didnt wipe my phone but all my apps were force closing if I opened them. The only fix was to wipe and flash again. This happened on Nephilim rom last. Also this has happened on several kernels. Has this happened to anyone else? Do you think this could be a hardware issue? Thanks in advance.
It's to my happened to me with certain ROM installs when I flashed dirty/without doing a factory reset prior to flashing.
Sent from my SCH-I605 using XDA Premium 4 mobile app
sbrownla said:
It's to my happened to me with certain ROM installs when I flashed dirty/without doing a factory reset prior to flashing.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No for me it had nothing to do with that. I could be coming from a clean install and pull my battery and my phone would just bootloop
HerroMoto said:
No for me it had nothing to do with that. I could be coming from a clean install and pull my battery and my phone would just bootloop
Click to expand...
Click to collapse
Odin to stock and see if you can make it happen. If it doesn't happen on stock then it's something you have done while flashing. Are you using sd swap?
Sent From My Sticky Note, Too?
BoostedB18C said:
Odin to stock and see if you can make it happen. If it doesn't happen on stock then it's something you have done while flashing. Are you using sd swap?
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
I mean I fix it by flashing another rom so I don't need to odin. Everything is okay so far. And no I'm not using SD swap. Just wanted to see too if anyone has experienced it. I have a feeling it has to do with my device I may get a replacement
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
I have a note 2 that I kept stock for a long time. And decided to root it about a week ago. I used the latest casual one click root. And it seemed all dandy initially until i went between a few different roms and it decided it wanted to shut off randomly and not boot back up past the note 2 screen on its own. But the odd part was it booted while connected to the wall or to the computer. So I flashed to 4.1.2 stock via odin and the issue still remains. I can only use it fine on charger. Is there something else im missing on flashing back to stock?
Sent from my SCH-I605 using XDA Free mobile app
Hmm when you installed 4.3 did you do so wiping everything could be an app causing the problem. Try it from brand new with no apps installed and see if that helps. Could be also a radio issue as well.
Sent from my XT1060 using Tapatalk
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I've found that even after using ODIN to go back to stock 4.1.2, that there's still leftover data on the phone from custom ROM's. I've read where others had the same issue. I don't know why Odin doesn't seem to fully wipe everything ... but this has been my personal experience.
The way I've fixed this (and all this may not be necessary).. . is that after Odin'ing back to stock 4.1.2, I boot into stock recovery, then do a full factory reset and wipe cache. Then I booted into the stock Rom and used the bypass setup trick (touch the left side of the screen right above Emergency... then right side, then left, then right again, and then volume up... this should bypass setup to save time).
Then went into phone's settings and performed a factory reset from within the stock Rom too...
Finally... (because I'm a bit OCD... so this is probably not necessary), but I ODIN'd back to stock 4.1.2 one more time and then proceeded with using CASUAL again to root /unlock the bootloader).
I know this is a pain in the butt... but this has worked for me. Maybe others will have some better suggestions.
(Edit : Forgot to mention that if you're not wanting to return to stock to start over again... check out this thread (http://forum.xda-developers.com/showthread.php?p=53624921) on how to flash a stock recovery for the purposes of doing a proper data wipe... then can you odin your custom recovery back to the device without having to fully restore to stock... this can be a real time saver. Please make sure to thank the OP for the helpful info).
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
This is totally a guess, but I'm thinking that you may have a battery problem... and it's just a coincidence that these problems started happening around the same time that you rooted. You may try replacing the battery to see if that fixes things.... (you can get one pretty cheap off ebay or Amazon).
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hopefully you'll have no more problems with it for a while.
:thumbup: