Ok, started a new post so that I can put everything in one place. Dev's please feel free to delete other one.
I have one of the first gs4's, it was rooted with TWRP installed. I was running Liquidsmooth rom when I founf the GPS to not be functional.
I trying flashing some different modems, none of them fixed that. (Mk2, Nb1)
Tried multiple different ROMS, also did not fix the problem. Ended up CM 11, liked the rom so I left it on. Everything working fine.
This morning I rebooted the phone and it hung on the SAMSUNG GALAXY S4 screen. Won't go past it. Booted into recovery. Tried to restore a backup, but after it too hung at SGS4 screen. Went back in, reflashed, wiped, still stuck.
Tried flashing the uvamdl.tar in odin, and that failed every time saying secure check fail SB12 on the phone.
Went back to playing with TWRP, because I am stuck. Found that if If I do a full wipe, including data (where you have to type yes), then flash CM11 I can get it to boot into the phone, but only once. If I reboot, it hangs again, and I have to go in, wipe, and start all over.
Here is what is weird, it only works with CM11, not any other ROM.
Obviously I can't format every time I want to reboot the phone, so I am looking for a way to get this back to normal.
attached current specs with screenshot
I am using a win 8.1 laptop right now, but when I get home I would have access to a windows 7 machine.
I am currently traveling and desperately need the phone, so any help you could offer would be most appreciated.
is there anyone who can help me decipher this issue?
There was a bug a while back where CM11 would hang sometimes on reboots, but you could always just reboot a couple more times and get it to boot. Why are you having to reboot? Just get CM on there, get it booted, and leave it be until you get back. You could try a newer nightly, but I'm not sure it would fix your problem.
im actually veery very suprised u got a cw rom to work period on a nb1 device...
Sent from my Venomous Droid Blue Chrome Edition S4 (team: @Venom0642 @ted77usa @rebel1699) ~ 20GB free cloud https://copy.com?r=vtiraF
Your android version 4.4.2. It appears you are leaving some information out of your post. If you have an AT&T phone you must be using Safestrap? MF3, MK2, etc.. can only use Safestrap as a recovery. I am also assuming your baseband...NB1 is due to the modem flashing, but that really won't make a difference because CMxx will not run on Safestrap. Your best option now is to Odin back to your original firmware version, re-install Safestrap, and stick with the compatible TW ROMs listed in the safestrap thread. If you don't understand what I am saying you will need to search and read about it all. You really should have known all of this before attempting to do anything to your phone. Good luck.
kevp75 said:
im actually veery very suprised u got a cw rom to work period on a nb1 device...[/url]
Click to expand...
Click to collapse
scott14719 said:
Your android version 4.4.2. It appears you are leaving some information out of your post. If you have an AT&T phone you must be using Safestrap? MF3, MK2, etc.. can only use Safestrap as a recovery. I am also assuming your baseband...NB1 is due to the modem flashing, but that really won't make a difference because CMxx will not run on Safestrap. Your best option now is to Odin back to your original firmware version, re-install Safestrap, and stick with the compatible TW ROMs listed in the safestrap thread. If you don't understand what I am saying you will need to search and read about it all. You really should have known all of this before attempting to do anything to your phone. Good luck.
Click to expand...
Click to collapse
I would venture that he still has MDB or MDL bootloader as to HOW and WHY he can run CM11.
To OP I also would suggest flashing the STOCK firmware that MATCHES what bootloader you have and start fresh. Just MAKE SURE to reinstall TWRP immediately, then flash CM11 or whatever ROM you want. This IS ASSUMING you still have the MDB or MDL bootloaders.
To check/verify which bootloader you have installed.
1. Download Terminal Emulator
2. Open Terminal Emulator app and hit OKAY to give it Root Rights.
3. Close Terminal Emulator
4. Re-Open Terminal Emulator and type "su" Enter (WITHOUT THE QUOTATION MARKS)
5. Type "getprop to.bootloader" (WITHOUT the quotation marks).
6. See the screenshot where mine shows I337---MDB as that is where your phone will show which bootloader you have installed.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
RockRatt said:
I would venture that he still has MDB or MDL bootloader as to HOW and WHY he can run CM11.
To OP I also would suggest flashing the STOCK firmware that MATCHES what bootloader you have and start fresh. Just MAKE SURE to reinstall TWRP immediately, then flash CM11 or whatever ROM you want. This IS ASSUMING you still have the MDB or MDL bootloaders.
To check/verify which bootloader you have installed.
1. Download Terminal Emulator
2. Open Terminal Emulator app and hit OKAY to give it Root Rights.
3. Close Terminal Emulator
4. Re-Open Terminal Emulator and type "su" Enter (WITHOUT THE QUOTATION MARKS)
5. Type "getprop to.bootloader" (WITHOUT the quotation marks).
6. See the screenshot where mine shows I337---MDB as that is where your phone will show which bootloader you have installed.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
thanks to all, i am on mdb bootloader, sorry, thought i put that in the text, i am not safe strap.
when i try to odin the original file image i get the error message, any ideas why i cannot odin?
Don't select "YES" in TWRP before rebooting--:good:
If you can't solve anything reformat your cards--backup first
Doesn't OP have to be on MDL "not MDB" to flash some roms?
aawshads said:
thanks to all, i am on mdb bootloader, sorry, thought i put that in the text, i am not safe strap.
when i try to odin the original file image i get the error message, any ideas why i cannot odin?
Click to expand...
Click to collapse
Did you try redownloading it? Otherwise make sure your phone cable is good and try different USB ports, maybe a different version of ODIN if you want
Sent from my SGH-I337 running Blackbox 3.0
rugmankc said:
Don't select "YES" in TWRP before rebooting--:good:
If you can't solve anything reformat your cards--backup first
Doesn't OP have to be on MDL "not MDB" to flash some roms?
Click to expand...
Click to collapse
I am not positive as I haven't flashed any aosp based Roms, I am still on MDB bootloaders as well. So far never needed to flash the MDL bootloaders though for any Roms I have run. It is possible that CM needs the MDL bootloader though.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
RockRatt said:
I am not positive as I haven't flashed any aosp based Roms, I am still on MDB bootloaders as well. So far never needed to flash the MDL bootloaders though for any Roms I have run. It is possible that CM needs the MDL bootloader though.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
Yeah Rock, I forget--too many roms that I flash. I do remember a dev saying that you must be on mdl for something. But, it was way back early on. I did a lot of CM when I started flashing years ago. But, started with mostly TW when I got the s4. So, seems it would have been TW. My "old" brain don't remember as good as it use too-- Oh well, hope the OP gets it sorted--
i wanted to thank everyone. after multiple attempts, downloads, etc, I finally got odin to work. so I flashed an original image, rooted, installed flash and then cm11, and everything (including GPS!) seems to be working. I appreciate all of the help and advice that was given.
aawshads said:
i wanted to thank everyone. after multiple attempts, downloads, etc, I finally got odin to work. so I flashed an original image, rooted, installed flash and then cm11, and everything (including GPS!) seems to be working. I appreciate all of the help and advice that was given.
Click to expand...
Click to collapse
Glad you got it
Sent from my SGH-I337 using Tapatalk
Related
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
amishbobinc said:
So yesterday I decided to install TWRP and installed this rom: http://forum.xda-developers.com/showthread.php?t=2356429
Well, once I loaded up wifi wouldn't work, so I tried restarting the phone. Phone now stay stuck at the GS4 load screen. I tried switching to clockwork mod, installed this rom: http://www.androidfilehost.com/?fid=23032113221600575
Wifi wouldn't work, restarted. Same thing. Wiping stuff, reinstalling, etc doesn't work.
Do I need to go back to stock? Is there a kernal issue?
I've done this on my note II without issue, so not sure what problem would be.
Any help is appreciated.
Click to expand...
Click to collapse
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Cytality said:
Only thing I can think of is if you flashed the MF9 version to an MDL phone, or vice versa.
Double check the version compatibility, do a wipe from TWRP and then reinstall the ROM. That's my opinion.
Click to expand...
Click to collapse
I think I did....is that bad?
amishbobinc said:
I think I did....is that bad?
Click to expand...
Click to collapse
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Cytality said:
I don't know if I'd say "bad." It just won't work right lol.
Just look at what version you downloaded before, was it MF9 or MDL? If it was MF9 then download the MDL version of that ROM and try that. Remember you should always be doing TWRP full backups of cache and ROM, so you have something to fall back on if you screw up.
Click to expand...
Click to collapse
What about the stock MDL, if I flash that rom it should work - right?
amishbobinc said:
What about the stock MDL, if I flash that rom it should work - right?
Click to expand...
Click to collapse
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Cytality said:
Any MDL ROM should work if you KNOW you're on MDL baseband. I can't tell if you are or not, only you would know that. Did you ever do the new MF9 update? If not then you're probably on MDL.
So if you download any MDL ROM, doesn't have to be a stock one unless you want it, then it will probably work.
Click to expand...
Click to collapse
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
amishbobinc said:
I'll give that a shot. The internet here at work is awful, so its going to take a while.
Also, what if I the mf9 kernal got flashed at some point? Does that make any difference?
Click to expand...
Click to collapse
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Cytality said:
You can always flash an MDL kernel back, like the KT kernel. Whatever ROM you pick, it will come with the appropriate kernel (unless you're doing a stock ROM.)
I'm assuming you're running MDL modem and baseband, because your post implies you just flashed TWRP for the first time yesterday as if you just bought the phone or something.
So let's assume for all intensive purposes that you are MDL. Then you need to find a kernel and a ROM that are MDL, not MF9, and flash those via TWRP after you do a wipe of everything (also from within TWRP).
An alternate option is you could attempt to just upgrade yourself to MF9 right now... download the updated modem and stuff from noobnl's post, Odin flash it as per the instructions, when done boot back into TWRP recovery and then install a new MF9 ROM, like TriForce or something.
Click to expand...
Click to collapse
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
amishbobinc said:
Ok so I flashed the stock kernal and then tried flashing a MDL rom. The phone now starts up, but after logging into my google account I only get a black background screen, like the launcher is missing. I CAN hover use my notification bar to turn things on and off but I can't get to settings.
Click to expand...
Click to collapse
Whats the rom you are using?
Cytality said:
Whats the rom you are using?
Click to expand...
Click to collapse
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
amishbobinc said:
ROM | MDL & MF9 | iNTriNsiC | Simplicity is Performance | Odexed | 7/16/13
http://forum.xda-developers.com/showthread.php?t=2356429
I downloaded the MDL version.
Click to expand...
Click to collapse
While you have the phone turned on, go in settings and see what your baseband version is. If it ends in MDL then you're good.
After that, I don't know. I've never used that rom personally, it could be an issue with the rom itself, nothing really wrong with your phone. You can try to wipe and reinstall, or just try a different ROM.
Ok got it!!
TWRP and clockworkmod were both NOT formatting like they said they where. I had to manually go in and erase everything except the external SD. Then I did a clean install and everything works great.
Thank you for your help!
So Im running i337 At&t Mf3 s4
Safestrap will not unzip any of the ROMs i try yet they work for everyone else. I have no idea whats going on does anyone have any ideas???
this is soooooo annoying that nothing works on my phone it all just fails! yet everyone else gets it to work (
You should better outline the exact steps you've taken so that someone with more safestrap knowledge than myself can see if you've missed a step.
sorry, my device was rooted and safestrap was installed properly.
I download both gravitron and MDOB put them on my external sd card
entered safestrap mode made a rom with 1 gig space then installed the downloaded rom that is on my sdcard and thats when i get the "fail"
unable to unzip file.
every single time i get this message no idea what is wrong.
optimizedd said:
sorry, my device was rooted and safestrap was installed properly.
I download both gravitron and MDOB put them on my external sd card
entered safestrap mode made a rom with 1 gig space then installed the downloaded rom that is on my sdcard and thats when i get the "fail"
unable to unzip file.
every single time i get this message no idea what is wrong.
Click to expand...
Click to collapse
I haven't read anything in this but is the ROM bigger then 1gig?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Everyone's i337 phones are 99.99% the same.
When something doesn't work for one person but does for everyone else, it's because of user-error, corrupted download or the fact that you just need to start over from scratch (odin stock).
Wish I could help more instead of saying what I just did, but I know nothing about safestrap.
CZ Eddie said:
Everyone's i337 phones are 99.99% the same.
When something doesn't work for one person but does for everyone else, it's because of user-error, corrupted download or the fact that you just need to start over from scratch (odin stock).
Wish I could help more instead of saying what I just did, but I know nothing about safestrap.
Click to expand...
Click to collapse
Im trying to try and start over but im getting real confused on stocking my phone with odin :/
best buy has no idea of smart watch so they wont reflash my phone
optimizedd said:
Im trying to try and start over but im getting real confused on stocking my phone with odin :/
best buy has no idea of smart watch so they wont reflash my phone
Click to expand...
Click to collapse
You have mf3, you can't use Odin. Don't try it you could mess up your phone worse.
optimizedd said:
So Im running i337 At&t Mf3 s4
Safestrap will not unzip any of the ROMs i try yet they work for everyone else. I have no idea whats going on does anyone have any ideas???
this is soooooo annoying that nothing works on my phone it all just fails! yet everyone else gets it to work (
Click to expand...
Click to collapse
I suggest you do some reading before you hard brick your phone. Start by reading the "pinned" threads in the general and q&a sections. Then, completely read the threads that have MF3 in the title. Make sure to read the entire original SafeStrap thread as well. If you do what I suggested, you should be OK.
Yeah, I did a factory reset, then rooted, then installed safestrap. Up until now, everything was going fine. I can boot into the stock rom just fine, and get into ss recovery fine, but when I try to flash the gravitron .zip to slot one, I get the "can not open zip" message. I guess I will stick to stock for now.
5>4 said:
Yeah, I did a factory reset, then rooted, then installed safestrap. Up until now, everything was going fine. I can boot into the stock rom just fine, and get into ss recovery fine, but when I try to flash the gravitron .zip to slot one, I get the "can not open zip" message. I guess I will stick to stock for now.
Click to expand...
Click to collapse
same exact thing!!!!
5>4 said:
Yeah, I did a factory reset, then rooted, then installed safestrap. Up until now, everything was going fine. I can boot into the stock rom just fine, and get into ss recovery fine, but when I try to flash the gravitron .zip to slot one, I get the "can not open zip" message. I guess I will stick to stock for now.
Click to expand...
Click to collapse
Did you check the md5? Could be a bad download.
jd1639 said:
Did you check the md5? Could be a bad download.
Click to expand...
Click to collapse
'twas a bad download. But now that I redownloaded it and flashed it, after the SS recovery screen, the phone just turns off. Not sure what I did wrong now.
Hmm. I flashed SHOstock to the same slot, and it works perfectly. I did redownload the kernel mods, I guess it must have been a bad download too. I am still a noob to Android, but I already like being able to flash new ROMS.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Have you tried copying the ROM's to your internal storage? I've successfully flashed several different ROM's using SS and have had no trouble. Don't know if having the ROM's on your external SD card matters or not, but I've always copied them to my internal storage before installing.
So I was originally on MDL. AT&T S4 of course. Rooted it, installed custom ROMs, everything good. But recently it seems to have issues. Seems like Original Android ROMs just refuse to start up, like Beanstalk or ShoStock. Shows the Custom Lock boot screen thing, then just restarts to recovery. One of the few that worked fine and just booted normally was Alpha ROM from Android, now on the Tmobile forum I believe and Miui ROM.
So I gave up and tried restocking. Installed the MDL stock ROM again, motochopper, used ROM Manager to install Clockwork Recovery (Touch.), and then another problem. The recovery showed the android mascot laying down and that small red box. It seems to have defaulted to some Android Recovery thing with limited options. Rebooted and tried Clockwork Recovery normal edition this time. Same thing.
Honestly not sure what's wrong. Did I miss something and should have updated something or...?
gerard0986 said:
So I was originally on MDL. AT&T S4 of course. Rooted it, installed custom ROMs, everything good. But recently it seems to have issues. Seems like Original Android ROMs just refuse to start up like Beanstalk. Shows the Custom Lock boot screen thing, then just restarts to recovery. One of the few that worked fine and just booted normally was Alpha ROM from Android, now on the Tmobile forum I believe and Miui ROM.
So I gave up and tried restocking. Installed the MDL stock ROM again, motochopper, used ROM Manager to install Clockwork Recovery (Touch.), and then another problem. The recovery showed the android mascot laying down and that small red box. It seems to have defaulted to some Android Recovery thing with limited options. Rebooted and tried Clockwork Recovery normal edition this time. Same thing.
Honestly not sure what's wrong. Did I miss something and should have updated something or...?
Click to expand...
Click to collapse
Did you use LOKI?
scott14719 said:
Did you use LOKI?
Click to expand...
Click to collapse
Yeah. Had a recovery with auto loki. But I believe a few of the ROMs I tried were lokied already too. Still didn't work.
I just tried using the stock recovery. Restocked, and went straight to recovery. No motochopper or anything.
Still shows the error droid and under the limited option'd "Android system recovery <3e>", it says, in yellow,
"# Manual Mode #"
"-- Applying Multi-CSC..."
"Applied the CSC-code : ATT"
"Successfully applied multi-CSC."
I'm guessing I broke something somehow...but I REALLY hope this is fixable. This recovery lets me reboot system, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, and apply update from cache.
Restocked again and used the new CASUAL root. TWRP installed fine from it and works fine, but I tried Beanstalk again and still just reboots into recovery. Even flashed loki twice. What am I missing? Stuck at rooted stock for now.
Bumping this up. Still seem unable to install other ROMs.
gerard0986 said:
Bumping this up. Still seem unable to install other ROMs.
Click to expand...
Click to collapse
No ROMs have worked at all? Have you tried installing a different kernel?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
DeadlySin9 said:
No ROMs have worked at all? Have you tried installing a different kernel?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Seems most I try from the "Original Android" section don't work at all. Starts up, waits at the Custom Lock boot image thing or the stock Samsung logo, and eventually reboots into recovery. Select ones from the "Android" section will work. Alpha I think so far was the only one that I tried and worked fine.
I'll try the kernal thing though, but would that affect the recovery like I mentioned before? Or am I dealing with multiple problems perhaps?
gerard0986 said:
Seems most I try from the "Original Android" section don't work at all. Starts up, waits at the Custom Lock boot image thing or the stock Samsung logo, and eventually reboots into recovery. Select ones from the "Android" section will work. Alpha I think so far was the only one that I tried and worked fine.
I'll try the kernal thing though, but would that affect the recovery like I mentioned before? Or am I dealing with multiple problems perhaps?
Click to expand...
Click to collapse
Kernel shouldn't affect the recovery, just make sure the kernel is patched for loki.
When you are getting back into recovery what recovery is showing? The TWRP recovery or 3e recovery? Kind of sounds like it is defaulting back to the 3e recovery.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
RockRatt said:
When you are getting back into recovery what recovery is showing? The TWRP recovery or 3e recovery? Kind of sounds like it is defaulting back to the 3e recovery.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
With the old Motochopper it defaulted to 3e recovery (But didn't before all of these problems.). With the new Java based one it loads TWRP normally again.
I switched to Task's AOKP just fine it seems. Maybe it was just the kernel. This problem is solved for now I guess.
Problem is back. I tried to restock and it seems to have worked, but now it just gets stuck at the AT&T globe logo right after the melody. It just freezes and starts to get hot.
Sunday, I ignored the one rule for flashers: always make a back up. And now I'm being royally screwed. I had tried to flash the 4/13 nightly of AICP, but it wouldn't go past the boot screen, and I had deleted all the other roms on my sdcard because I was running out of room. So, I tried going back to the previous buid I had, the 4/9, but it never went past the boot screen there either. So I set about trying to put my phone back to stock by flashing the NAE modem, Philz, and Negalite's latest rom, but for whatever reason, it was so buggy and glitchy I couldn't really use it, which I've never had happen with their work. So I downloaded omnirom, which I'm on, and it's working fine, but now I have no sound whatsoever. I also used RomToolbox Pro to flash TWRP. Any suggestions on how to fix this would be greatly appreciated.
Additional Information
I'm on TWRP 2.6.3.1 because 2.7.0.0+ don't work for me
Flashing the Modem was successful, not sure where it all went wrong.
I also followed Mudavo's guide for updating to NAE modem and firmware while keeping the MF9 bootloader. The only thing I didn't do is flash the MK2 rooted stock ROM before updating to the Negalite.
Any expediency in resolving this matter would be greatly appreciated.
Phone calls are a bust, as well. Anything related to sound except haptic feedback either causes DSP Manager to FC, or the process itself FC's. I had noticed that on the Negalite as well, because whenever I hit the volume keys, everything froze, not to mention the fact it didn't register MP3s as MP3s, and also refused to play anything from play music or YouTube.
Sent from my SPH-L720 using xda app-developers app
imactuallynot said:
Phone calls are a bust, as well. Anything related to sound except haptic feedback either causes DSP Manager to FC, or the process itself FC's. I had noticed that on the Negalite as well, because whenever I hit the volume keys, everything froze, not to mention the fact it didn't register MP3s as MP3s, and also refused to play anything from play music or YouTube.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
If you're truly on the MF9 bootloader then PC Odin the MF9 full .tar and reset your phone.
imactuallynot said:
Sunday, I ignored the one rule for flashers: always make a back up. And now I'm being royally screwed. I had tried to flash the 4/13 nightly of AICP, but it wouldn't go past the boot screen, and I had deleted all the other roms on my sdcard because I was running out of room. So, I tried going back to the previous buid I had, the 4/9, but it never went past the boot screen there either. So I set about trying to put my phone back to stock by flashing the NAE modem, Philz, and Negalite's latest rom, but for whatever reason, it was so buggy and glitchy I couldn't really use it, which I've never had happen with their work. So I downloaded omnirom, which I'm on, and it's working fine, but now I have no sound whatsoever. I also used RomToolbox Pro to flash TWRP. Any suggestions on how to fix this would be greatly appreciated.
Additional Information
I'm on TWRP 2.6.3.1 because 2.7.0.0+ don't work for me
Flashing the Modem was successful, not sure where it all went wrong.
I also followed Mudavo's guide for updating to NAE modem and firmware while keeping the MF9 bootloader. The only thing I didn't do is flash the MK2 rooted stock ROM before updating to the Negalite.
Any expediency in resolving this matter would be greatly appreciated.
Click to expand...
Click to collapse
NAE modem with MF9 it's not an option for you at this point. Anyway I don't see the reasons to keep a different boot loader then the rom, maybe someone can explain.
Get the full NAE tar (if you have 720T you need NAF) and flash it. Note; once you are in NAE you cannot downgrade.
I thought that was just for the bootloader, but not the modem? (Unless Samsung's found a way to bake KNOX into the modem now)
leaderbuilder said:
If you're truly on the MF9 bootloader then PC Odin the MF9 full .tar and reset your phone.
Click to expand...
Click to collapse
This is the best advice. Always revert back to the same base software as the bootloader. Rooted if you can find it, or unrooted if you just want to get it back to working status and can root it manually later. To emphasize what leaderbuilder said though:
Make sure you know you are on MF9 bootloader before trying to restore it. Otherwise it will fail.
I got a good deal on the Cricket..formerly AiO... i337z model but apparently it is not supported as other versions here..
Is it possible to root, install custom recovery and flash this S4 variant? Should I sell it and get the At&t version?
kinvid said:
I got a good deal on the Cricket..formerly AiO... i337z model but apparently it is not supported as other versions here..
Is it possible to root, install custom recovery and flash this S4 variant? Should I sell it and get the At&t version?
Click to expand...
Click to collapse
Supposedly Safestrap works on it just the same as ours, but I don't know what root methods work. What system version are you on, 4.2 or 4.4?
DeadlySin9 said:
Supposedly Safestrap works on it just the same as ours, but I don't know what root methods work. What system version are you on, 4.2 or 4.4?
Click to expand...
Click to collapse
I can confirm that towel root works on the i337z from Cricket/AIO (now AT&T). However, I was not able to get the Safestrap for the AT&T i337 to work. I tried Safestrap 3.65, 3.71, or 3.72. They all install, but don't seem to activate. I am on Android 4.4.2, build TUUBNE2.
devzero said:
I can confirm that towel root works on the i337z from Cricket/AIO (now AT&T). However, I was not able to get the Safestrap for the AT&T i337 to work. I tried Safestrap 3.65, 3.71, or 3.72. They all install, but don't seem to activate. I am on Android 4.4.2, build TUUBNE2.
Click to expand...
Click to collapse
Did you try using SELinux Mode Changer and then installing? Since you install to the stock slot with 4.4 it will never register as active but as long as it says installed it should work.
DeadlySin9 said:
Did you try using SELinux Mode Changer and then installing? Since you install to the stock slot with 4.4 it will never register as active but as long as it says installed it should work.
Click to expand...
Click to collapse
Obviously, Safestrap won't be "active" if you're in the stock rom. What I meant was that safestrap would say it installed successfully, but wouldn't "activate" on boot, and give me the safestrap splash screen/menu. My previous phone was a Razr Maxx with a locked bootloader, so I'm familiar with how Safestrap works.
Well, I'm happy to report that after changing SELinux to permissive, I was able to get Safestrap working on 4.4.2. Safestrap 3.71 and 3.72 both seem to work. This is the first phone I've had that has had it set to enforcing by default, so it didn't even occur to me to check that. Thanks for the suggestion!
Now on to ROMs.. any recommendations? I've read that only TW ROMs will work on the S4 with Safestrap. My Razr Maxx has official CM11 (AOSP) builds available. What seems to be the issue with the S4 only working with TW ROMs?
devzero said:
Obviously, Safestrap won't be "active" if you're in the stock rom. What I meant was that safestrap would say it installed successfully, but wouldn't "activate" on boot, and give me the safestrap splash screen/menu. My previous phone was a Razr Maxx with a locked bootloader, so I'm familiar with how Safestrap works.
Well, I'm happy to report that after changing SELinux to permissive, I was able to get Safestrap working on 4.4.2. Safestrap 3.71 and 3.72 both seem to work. This is the first phone I've had that has had it set to enforcing by default, so it didn't even occur to me to check that. Thanks for the suggestion!
Now on to ROMs.. any recommendations? I've read that only TW ROMs will work on the S4 with Safestrap. My Razr Maxx has official CM11 (AOSP) builds available. What seems to be the issue with the S4 only working with TW ROMs?
Click to expand...
Click to collapse
The Razr has an AOSP compatible kernel by default since Motorola doesn't change the kernel that much, and kexec has been developed for Razr to allow loading of custom kernels. Neither of those is the case with the S4, as the kernel is modified for Touchwiz and kexec is not functioning yet. There is one Google Edition ROM that has been made to boot with some slight issues you could go with (no USB MTP, no WiFi hotspot, WiFi requires soft reboot, SELinux Mode changer is required to keep installed) but other than that check out our All Things MK2 and NB1 index thread for working 4.4 ROMs.
DeadlySin9 said:
The Razr has an AOSP compatible kernel by default since Motorola doesn't change the kernel that much, and kexec has been developed for Razr to allow loading of custom kernels. Neither of those is the case with the S4, as the kernel is modified for Touchwiz and kexec is not functioning yet. There is one Google Edition ROM that has been made to boot with some slight issues you could go with (no USB MTP, no WiFi hotspot, WiFi requires soft reboot, SELinux Mode changer is required to keep installed) but other than that check out our All Things MK2 and NB1 index thread for working 4.4 ROMs.
Click to expand...
Click to collapse
Ah, makes sense. Thanks for the explanation.
Update on the SS situation: While I've been able to 3.71 and 3.72 installed and seemingly operational on boot, neither seem to actually work in terms of booting from a rom slot. I've tried a few different TW 4.4.2 based roms, various module levels, and none of them seem to work.
With SS 3.71, I see some errors in the SS console about not being able to mount /systemorig, and I am not able to do a backup of the stock system partition, but otherwise it seems to work ok. However, when I try to boot from slot1, all I get is a black screen.
With SS 3.72, there are no /systemorig errors, and I am able to backup all partitions of the stock rom, and I am even able to boot from slot1, but it actually just boots to stock, and my cell radio doesn't work.
I tried simply restoring the stock rom to slot 1 and booting from it, since that should theoretically work, and I still had the same experience as above, so I'm thinking it doesn't matter what rom/modules try, SS 3.71/3.72 just isn't going to work
devzero said:
Ah, makes sense. Thanks for the explanation.
Update on the SS situation: While I've been able to 3.71 and 3.72 installed and seemingly operational on boot, neither seem to actually work in terms of booting from a rom slot. I've tried a few different TW 4.4.2 based roms, various module levels, and none of them seem to work.
With SS 3.71, I see some errors in the SS console about not being able to mount /systemorig, and I am not able to do a backup of the stock system partition, but otherwise it seems to work ok. However, when I try to boot from slot1, all I get is a black screen.
With SS 3.72, there are no /systemorig errors, and I am able to backup all partitions of the stock rom, and I am even able to boot from slot1, but it actually just boots to stock, and my cell radio doesn't work.
I tried simply restoring the stock rom to slot 1 and booting from it, since that should theoretically work, and I still had the same experience as above, so I'm thinking it doesn't matter what rom/modules try, SS 3.71/3.72 just isn't going to work
Click to expand...
Click to collapse
3.71 not being able to mount isn't surprising as it was never made for kitkat and thus had issues mounting system on kitkat (we had to flash the kernel from our 4.3 version to make it work). ROM slots not working with Kitkat is also another known issue, and all flashes have to be straight to stock slot. Since you have a backup, just flash any ROM from the Index thread and you should be fine.
DeadlySin9 said:
3.71 not being able to mount isn't surprising as it was never made for kitkat and thus had issues mounting system on kitkat (we had to flash the kernel from our 4.3 version to make it work). ROM slots not working with Kitkat is also another known issue, and all flashes have to be straight to stock slot. Since you have a backup, just flash any ROM from the Index thread and you should be fine.
Click to expand...
Click to collapse
You mean use SS 3.72 to flash over the stock ROM?
devzero said:
You mean use SS 3.72 to flash over the stock ROM?
Click to expand...
Click to collapse
Yes. That's how normal I337 users have to flash amd it's pretty safe if you use one of the listed ROMs. Just backup, wipe system, cache, and data, and then flash the ROM.
Sent from my SGH-I337 running GPE
DeadlySin9 said:
Yes. That's how normal I337 users have to flash amd it's pretty safe if you use one of the listed ROMs. Just backup, wipe system, cache, and data, and then flash the ROM.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
I installed a few different ROMs in the stock slot, and it seemed to work ok, but I was not able to get WiFi working. I was not able to find a kernel modules pack for NE2, so I'm guessing this is my problem. The closest I was able to find was NC1, and it didn't make any difference. Is there a way I can copy the modules from my stock rom, or somehow extract them from the backup, then create my own NE2 update zip?
I was able to extract the kernel modules from the stock TWRP backup and create a kernel modules update package for the NE2 build. WiFi works great now.
I am attaching the update package here in case anyone else needs the Cricket/AIO NE2 kernel modules. Perhaps a moderator could copy this to the SafeStrap downloads section? (http://forum.xda-developers.com/devdb/project/?id=680#downloads)
DeadlySin9 - Thanks again for your helpful info on this matter!
devzero said:
I was able to extract the kernel modules from the stock TWRP backup and create a kernel modules update package for the NE2 build. WiFi works great now.
I am attaching the update package here in case anyone else needs the Cricket/AIO NE2 kernel modules. Perhaps a moderator could copy this to the SafeStrap downloads section? (http://forum.xda-developers.com/devdb/project/?id=680#downloads)
DeadlySin9 - Thanks again for your helpful info on this matter!
Click to expand...
Click to collapse
Glad you got it working. Happy modding!
Sent from my SGH-I337 running GPE
Has anyone here with AIO/Cricket attempted to run a Cyanogen ROM? I got the SHOstock 8.1 working... Just interested in what else is avail out there. Go here:
http://download.cyanogenmod.org/?device=jfltecri
shakedown said:
Has anyone here with AIO/Cricket attempted to run a Cyanogen ROM? I got the SHOstock 8.1 working... Just interested in what else is avail out there. Go here:
http://download.cyanogenmod.org/?device=jfltecri
Click to expand...
Click to collapse
CM builds won't work unless you have an unlocked bootloader. Please refer to post #6. http://forum.xda-developers.com/showpost.php?p=54492289&postcount=6
devzero said:
CM builds won't work unless you have an unlocked bootloader. Please refer to post #6. http://forum.xda-developers.com/showpost.php?p=54492289&postcount=6
Click to expand...
Click to collapse
Makes sense. Have you run into any issues with shostock 8.1? So it's been a week or so now and the only issue I have is after my leaving my home's wifi the phone appears to not fall back onto the wireless network for data. I'll have full or next to full bars for phone but I've lost the data indicator. If I attempt to open an app When in this state I'll get an error that there is no data connection. A reboot fixes this. It also only appears to happen when the phone has been on wifi for a long time I.e. overnight. Could it be a battery saving feature? Could it be related to missing a couple of calls and getting just the vm icon?
Shakedown
shakedown said:
Makes sense. Have you run into any issues with shostock 8.1? So it's been a week or so now and the only issue I have is after my leaving my home's wifi the phone appears to not fall back onto the wireless network for data. I'll have full or next to full bars for phone but I've lost the data indicator. If I attempt to open an app When in this state I'll get an error that there is no data connection. A reboot fixes this. It also only appears to happen when the phone has been on wifi for a long time I.e. overnight. Could it be a battery saving feature? Could it be related to missing a couple of calls and getting just the vm icon?
Shakedown
Click to expand...
Click to collapse
I haven't seen any wifi issues. By default the cell connection type is hidden when you connect to wifi, but this can be turned on through 3rd party mods such as Wanam Xposed.
The only issue I've seen is the remove button doesn't work when long pressin on an app in the app drawer.
I was able to get Cyanogenmod to work after installing CWM. That or TWRP. System wouldn't boot, but i had the recovery and just installed the unified CM and all was fine. And from there I went crazy with roms. GPE from kryten, Kushan, wicked (which sucked) anything i could.
---------- Post added at 09:45 PM ---------- Previous post was at 09:40 PM ----------
I'm just throwing this out there, do not flash AIO / Cricket's MH1 update. it made everything audio crash. couldn't get the modem to work at all, nothing stuck when i tried to flash a different one