Got hyperdrive installed fine on a locked boot loader (nc2) using ss. I made my backup first just in case btw.
Ended up with the wifi issue so I tired flashing various modules to no avail. So I googled around a bit and found the att compatibility pack and flashed that. Ended up getting stuck on the boot loop after flash. Did a factory reset to get past that one and finally got hyperdrive booting. But upon boot I immediately get a ton of force closes from com.Android.phone to the point that I can barely access menus quick enough to restart before another fc appears.
Did another factory reset, no help there, and the install of hyperdrive wiped safe strap so I have no way to restore the backup. Tired using kies but it says this version can't be updated when I try to restore firmware. I'm assuming my last hope is an odin flash but i'm having a hard time finding the correct file to flash.
It's a 16gb sgh-I337, on att. And it was originally the nc2 build however now the 'about' menu shows unknown as build number. Have to assume that's part of my problem but i'm not entirely sure at this point.
I did search around but I didn't find anything that seemed to describe this exact issue. Any help is greatly appreciated, thanks!
Sent from my LG-D850 using Tapatalk 2
Odin to stock did it. re flashed everything and i'm running hyperdrive fine now
Sent from my SCH-I545 using Tapatalk 2
Related
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
I really hope someone here can help me. I'm running an SGH-1337M (Rogers). I rooted the device a number of months ago with Motochopper and installed Foxhound ROM GT-i9505 (which every guide says works with the SGH-1337M). I've been running this rom for quite a while without issues. Yesterday I I installed Cyanogenmod (cm-10.2-20131102-SNAPSHOT-M1-jfltecan) which worked, until I rebooted the device. When I reboot the phone gets stuck on the Samsung Galaxy S4 boot logo. I've booted into TWRP and tried to reinstall the Foxhound rom which was working but end up with the same results. I've used Kies Firmware upgrade to try and set everything back to default without sucess. Using Odin I tried to reinstall a factory image of my phone, which is sucessfull except nothing changes.
Currently, if using TWRP I do a full wipe of my phone and then install Cyanogenmod it'll work, so long as I don't reboot. If I reboot I need to do a full wipe, reinstall the rom and start all over.
I'm at a complete loss here. I've spent the last 5 hours looking for a solution to this problem without success. Any help is greatly appriciated.
Thanks
jer007 said:
I really hope someone here can help me. I'm running an SGH-1337M (Rogers). I rooted the device a number of months ago with Motochopper and installed Foxhound ROM GT-i9505 (which every guide says works with the SGH-1337M). I've been running this rom for quite a while without issues. Yesterday I I installed Cyanogenmod (cm-10.2-20131102-SNAPSHOT-M1-jfltecan) which worked, until I rebooted the device. When I reboot the phone gets stuck on the Samsung Galaxy S4 boot logo. I've booted into TWRP and tried to reinstall the Foxhound rom which was working but end up with the same results. I've used Kies Firmware upgrade to try and set everything back to default without sucess. Using Odin I tried to reinstall a factory image of my phone, which is sucessfull except nothing changes.
Currently, if using TWRP I do a full wipe of my phone and then install Cyanogenmod it'll work, so long as I don't reboot. If I reboot I need to do a full wipe, reinstall the rom and start all over.
I'm at a complete loss here. I've spent the last 5 hours looking for a solution to this problem without success. Any help is greatly appriciated.
Thanks
Click to expand...
Click to collapse
After you did odin, you must do a factory reset. This should clear up the problem. And, are you using the correct kernel for cyan?
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...
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.