Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
Related
I downloaded the SlimBean ROM and GAPPS, booted to recovery, and selected the ROM, GAPPS, LOKI DOKI just incase, and flashed it, which took what seems very little time. It then asked to fix permissions so I swiped it and it just shut down immediately and went into the loop. I have tried ODIN, with and without PIT file and it all does the same. Kies was unsuccessful as well. Also, is anyone here who could possibly make a flashable kernel and recovery via ODIN? I am willing to test some things on my phone since it is indeed bricked. Either Monday or Tuesday if I cannot get it up and working I'll be replacing it. It has happened to quite a few others and it seems to do with a AOSP Kernel on a TW ROM? I am not 100% sure and have tried to find an answer but none is found.
Tylor
Edit: SUCCESS!!!! After about working on my phone for 5 hours, it has finally booted!! After Kies did its thing, it started into the boot loop once more. So I just took out the battery and let it sit for maybe 5-10 minutes. I put the battery in and as soon as I did so I held down the 3 buttons to boot into recovery and amazingly it the logo and text appeared. However, at first it did not boot into the recovery, but restarted, but I continued to hold down the keys for recovery and BAM, IT BOOTED!!! So now my Galaxy S4 is finally up and running .
Edit 2 : Sorry about the posting, but it was originally a question that I was hunting for. I hope it helps some people with getting their devices restored.
You said as soon as Kies did its thing. What exactly did you do?
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!
First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340