TL;DR - Installed bean's rooted kit kat, new safestrap, and Eclipse ROM 2.0.1. Phone essentially freezes when prompted to shut off or reboot and gets stuck there indefinitely. I also cannot install any apps via the play store reliably from Eclipse.
Hello everyone! I'm fairly new to rooting/flashing roms, and last night I used Bean's rooted kit kat to upgrade my N3 from 4.3 to 4.4. I went with de-odexed because from what I understood it was easier to change themes and whatnot that way (again, forgive me if I'm wrong, still new to all of this). Everything went great, I installed to stock rom slot, Odin detected my phone in DL mode, I installed the new firmware, it updated and loaded all the apps just fine, and I installed the new safestrap.
There was a problem however... Whenever I go to turn off or reboot the phone, the "shutting down" dialogue box comes up and it just gets stuck there. I timed it for about 20 minutes before finally just pulling the battery. It does this everytime I need to reboot the phone and I always have to end up pulling the battery.
EDIT: As of this morning the stock rom appears to no longer be having the reboot issue. My guess is that is just a bug in a Eclipse at this point.
Thinking it might be just a weird bug, I made a partition in ROM slot 2 (ROM slot 1 was where my 4.3 was and I hadn't deleted it yet) and installed Eclipse 2.0.1. When I booted into it and logged into my Google account to recover all my apps like I did just did with the stock rom slot, all the apps que'd up, but nothing showed as installing. I thought that maybe I had kinda just overwhelmed the phone with downloads and went into the play store to stop the que. I started installing about 3 apps at a time to see if it worked better, and I ran into the same issue. Usually when you click "install" on an app, it will show the download process and then start installing to your phone. Mine goes straight to install and gets stuck on an endless loading bar, with no way to cancel or stop it without a reboot.
Rebooting is also having the same issue as before. I cannot shut off or restart the device without it locking into the shutting down dialogue box.
1. Did installing a de-odexed version cause any problems that I wouldn't have had with an odexed?
2. If so, I can follow the same methods I did to install bean's kit kat and reinstall the odexed version? Or would I have to somehow go back to 4.3 first?
3. Are there any other known fixes I should try?
C3PH0 said:
TL;DR - Installed bean's rooted kit kat, new safestrap, and Eclipse ROM 2.0.1. Phone essentially freezes when prompted to shut off or reboot and gets stuck there indefinitely. I also cannot install any apps via the play store reliably from Eclipse.
Hello everyone! I'm fairly new to rooting/flashing roms, and last night I used Bean's rooted kit kat to upgrade my N3 from 4.3 to 4.4. I went with de-odexed because from what I understood it was easier to change themes and whatnot that way (again, forgive me if I'm wrong, still new to all of this). Everything went great, I installed to stock rom slot, Odin detected my phone in DL mode, I installed the new firmware, it updated and loaded all the apps just fine, and I installed the new safestrap.
There was a problem however... Whenever I go to turn off or reboot the phone, the "shutting down" dialogue box comes up and it just gets stuck there. I timed it for about 20 minutes before finally just pulling the battery. It does this everytime I need to reboot the phone and I always have to end up pulling the battery.
EDIT: As of this morning the stock rom appears to no longer be having the reboot issue. My guess is that is just a bug in a Eclipse at this point.
Thinking it might be just a weird bug, I made a partition in ROM slot 2 (ROM slot 1 was where my 4.3 was and I hadn't deleted it yet) and installed Eclipse 2.0.1. When I booted into it and logged into my Google account to recover all my apps like I did just did with the stock rom slot, all the apps que'd up, but nothing showed as installing. I thought that maybe I had kinda just overwhelmed the phone with downloads and went into the play store to stop the que. I started installing about 3 apps at a time to see if it worked better, and I ran into the same issue. Usually when you click "install" on an app, it will show the download process and then start installing to your phone. Mine goes straight to install and gets stuck on an endless loading bar, with no way to cancel or stop it without a reboot.
Rebooting is also having the same issue as before. I cannot shut off or restart the device without it locking into the shutting down dialogue box.
1. Did installing a de-odexed version cause any problems that I wouldn't have had with an odexed?
2. If so, I can follow the same methods I did to install bean's kit kat and reinstall the odexed version? Or would I have to somehow go back to 4.3 first?
3. Are there any other known fixes I should try?
Click to expand...
Click to collapse
I read your post a couple times and I think you may be using the wrong Safestrap. I could be wrong.
Use stable Safestrap 3.65 for jellybean roms and Safestrap 3.72 or 3.75 for nc2/nc4 roms.
I'm running Eclipse 2.0.1 on Safestrap 3.75 right now and have zero reboot problems.
Sent from my Eclipsed Note 3 using XDA Premium
Harleydroid said:
I read your post a couple times and I think you may be using the wrong Safestrap. I could be wrong.
Use stable Safestrap 3.65 for jellybean roms and Safestrap 3.72 or 3.75 for nc2/nc4 roms.
I'm running Eclipse 2.0.1 on Safestrap 3.75 right now and have zero reboot problems.
Sent from my Eclipsed Note 3 using XDA Premium
Click to expand...
Click to collapse
Yup! This was it. I installed 3.75 and re-flashed. I feel slightly dumb for not thinking of that but I'm so happy to have a functional phone again. Thank you very much!
C3PH0 said:
Yup! This was it. I installed 3.75 and re-flashed. I feel slightly dumb for not thinking of that but I'm so happy to have a functional phone again. Thank you very much!
Click to expand...
Click to collapse
You bet bud
Sent from my Eclipsed Note 3 using XDA Premium
Related
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
ATT Galaxy S4 currently running Goldeneye 6.0 and TWRP 2.6.0.0 (never installed MF3 base, but have tried both MF3 and MDL modems)
First odd thing...
[About->Status->Device Status] is listed as "Sd card" instead of the more common "Official" or "Custom".
Anybody know what that means or is telling me?
This is the latest thing I've noticed with my phone, which has been having all sorts of issues lately that I cannot seem to figure out. My main problem is, I can reinstall a new ROM, boot into the ROM, change settings around, reboot just fine, but, as soon as I install anything from the Play Store, the next reboot will hang on the initial Samsung splash screen. Wiping is the only fix I've found, and fixing permissions in TWRP errors out with an error that it cannot chown one of the new/updated .apk files.
Both Goldeneye 5 and 6 are doing this now (5.0 was installed and rock solid for several weeks before this all showed up...it started sometime after I decided to try out a couple of the aroma roms and then came back to GE).
Used ODIN to go back to factory rom, re-rooted/installed TWRP, then reinstalled GE6.0, but the same thing happened. Everything looked good until I ran updates from the store, then I was stuck again (note: used Root Explorer to check to permissions on the updated apks before rebooting and they were all correct (755)).
Other things I've noticed are:
1. Sometimes, on any reboot, the startup locks at the initial Samsung screen and I have to long press the power button to get it to reboot. It usually boots the second time around (this is before I install any additional apps and am completely unable to reboot).
2. Sometimes when wiping cache, davlik, and/or data, TWRP will seem to hang for up to a minute when trying to initialize the partition. A couple of times it even hard reboot my phone when I did a cache+davlik wipe.
3. I rolled back to a recovery image just fine; however, it was a couple months old. Everything started off looking great, but once I updated to a new ROM, my issues returned.
Trying Heimdall to go back to factory; however, I'm having issue with my laptop and getting the Zadig drivers installed. While I'm working that out, figured I'd see if anyone else has any suggestions on what else I should be trying or looking out.
thx
I would flash your phone back to MDL stock with odin using the mdl tar. This should format your paritions correctly. You could also reinstall MDL using kies since they still don't support MF3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Need serious help, been having the same issue the past 2 days!
I have a Samsung Galaxy S4 i337 AT&T with SafeStrap 3.71 installed. I have tried every possible solution known to man and my only other option is posting here. Bootloader being locked really blows more than anything, it would be my luck to have bought this phone with this issue. I installed a Touch-Wiz based rom, SafeStrap compatible, which was Hyperdrive at first then I tried GOLDENEYE ROM - http://forum.xda-developers.com/showthread.php?t=2313469&highlight=black+screen - I wiped everything off my phone, system, data, cache, and put the ROM's on my extsdcard to install. I went through Aroma installer and done everything correctly but after I reboot, it shows me the samsung galaxy s4 logo and then black screen of death. Nothing happens, I kept it on for about 30 minutes and nothing happened. The phone was getting hot so I knew something was running but nothing came on. I tried this with 4 Roms today and same thing every time. I was installing them to the Rom-slot1 and made sure I was doing everything the correct way. I re-wiped everything each time. I haven't seen that nobody else was having this issue and couldn't find help no where, of course my luck I would have this problem over and over. I have flashed the stock 4.4.2 kitkat software back on to it for now through odin and that is the only thing that has worked AT ALL. I hope someone can help me fix this issue so I can install a ROM to remove this laggy bloated stock software.
SafeStrap is a pain in every part of my butt
Brandon.Black said:
Need serious help, been having the same issue the past 2 days!
I have a Samsung Galaxy S4 i337 AT&T with SafeStrap 3.71 installed. I have tried every possible solution known to man and my only other option is posting here. Bootloader being locked really blows more than anything, it would be my luck to have bought this phone with this issue. I installed a Touch-Wiz based rom, SafeStrap compatible, which was Hyperdrive at first then I tried GOLDENEYE ROM - http://forum.xda-developers.com/showthread.php?t=2313469&highlight=black+screen - I wiped everything off my phone, system, data, cache, and put the ROM's on my extsdcard to install. I went through Aroma installer and done everything correctly but after I reboot, it shows me the samsung galaxy s4 logo and then black screen of death. Nothing happens, I kept it on for about 30 minutes and nothing happened. The phone was getting hot so I knew something was running but nothing came on. I tried this with 4 Roms today and same thing every time. I was installing them to the Rom-slot1 and made sure I was doing everything the correct way. I re-wiped everything each time. I haven't seen that nobody else was having this issue and couldn't find help no where, of course my luck I would have this problem over and over. I have flashed the stock 4.4.2 kitkat software back on to it for now through odin and that is the only thing that has worked AT ALL. I hope someone can help me fix this issue so I can install a ROM to remove this laggy bloated stock software.
SafeStrap is a pain in every part of my butt
Click to expand...
Click to collapse
Use safestrap 3.75
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Use safestrap 3.75
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much! That did the job.
It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.
You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app
Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!
I have now tried to install Hyperdrive ROM three times. The first time I had found an old thread written well before much of the S4 debauchery got as thick as it is now and it was definitely the wrong version. I`m on NI1 4.4.2 and downloaded the latest HD rom file (21?) as well as the UI. Followed the instructions to a T and wound up with it stuck on the orange HD/Kit Kat animation for eleven minutes. Finally got it to shut off, wouldn`t reboot. Tried a few times hoping to get it to at least get me in a position to restore a backup. Nope. It would get to the setup procedure but every action on the screen resulted in a "Samsung key lock has stopped working" message. Ended up just installing an older Odin stock rom (4.3), rooting and reinstalling Safestrap and finally getting to load my backup. I~m really interested in the HD rom, so can I ask for (a) what I might be doing wrong and (b) how do I do it correctly? I`m on NI1 again, rooted, using safestrap.