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!
Related
I just bought my Epic 4G a few days ago and quickly discovered the existence of rooting and custom ROMS. Needless to say I took the plunge the other day.
I attempted to install the Epic Experience Froyo yesterday but it doesn't seem to load up properly.
Seemed simple enough. I boot into clockwork, I cleared data/factory cache, cache partition, and davnik cache three times each. I installed the ROM from my SD card, install says it's successful, so I hit the reboot.
After this I expect my new rom to load up but all that happens is the samsung logo comes up for about a minute, phone reboots again and goes into the factory Android system recovery utility.
Any ideas? Please help, my phone is inoperable at the moment.
-Dennis
Sounds like kernel. Dl a costume kernel and flash it thru cwm.
Sent from my SPH-D700 using Tapatalk
I'll have to apologize ahead of time because I'm completely new to rooting.
Which kernel should I use (a link to one with instructions would be helpful), and how do I get it on my SD card if it isn't booting up? (my pc doesn't have an SD card reader)
Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209
So, flash Odin/DK17 and then flash Epic Experience over this?
Ya also did you first do the one click root method to make sure you are definitely rooted? If you press. Volume down + camera button + power when booting and the letters are blue you are NOT rooted. If they are green then you are rooted. Sometimes when you install a rom it might take away your root so you might try doing it in the order of this:
1. Flash back to stock 2.1
2. Do theone click root method
3. Flash DK17 modem through odin
4. Install Epic Exprience
hgvidal said:
Did you first use odin to install the DK17 modem and kernel through odin? That might be the step youmissed because if you just flashed straight from stock 2.1 to epic experience you need the updated froyo modem and kernel. Check here if you're still confused.
http://forum.xda-developers.com/showthread.php?t=853209
Click to expand...
Click to collapse
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?
idontwanttostudy said:
I went straight from 2.1 to 2.2 firmware without using odin or anything of the sort. Will I notice a difference? If so what difference will it make and can I just install DK17 modem and kernel or do I have to revert back to 2.1 first?
Click to expand...
Click to collapse
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.
hgvidal said:
Hm that is interesting. When i first made the mistake of going from to a 2.2 rom without upgrading the modem my cell & data service wouldn't work. It kept looping on and off and would not stick. Maybe it depends what rom you went to as maybe some require the modem as mandatory and others do not? I am not sure. But if its working for you, you should just be able to flash the DK17 through odin without going back to 2.1.
Click to expand...
Click to collapse
I just did it today with the newest froyo version out by chance would it come with them? If not where can i get them? I cant seem to find the modem to dl
How can i tell by looking in my phone if i have it or not?
idontwanttostudy said:
How can i tell by looking in my phone if i have it or not?
Click to expand...
Click to collapse
Go to settings -> about phone and then check where it says "Baseband version" it should say DK17 in there. If it doesnt follow these instructions to download the files you need. It has step by step directions
http://www.nomie.mobi/how-to-install-dk17-modem-samsung-epic/
I assume this is the rom you flashed:
http://forum.xda-developers.com/showthread.php?t=856715
In the first post it has a link to the instructions to properly flash the rom. You can use those instructions to flash the modem and see if it fixes your problem. You might be better off just flashing everything again. It would mean downloading odin and the files to your pc and flashing them to your phone from your pc. The simplest way to do this is follow this thread
http://forum.xda-developers.com/showthread.php?t=853209
Follow the instructions carefully and when your done you have the new modem, the froyo rom, clockwork recovery, and be rooted.
I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?
idontwanttostudy said:
I was at the site earlier but when i click the dl link it takes me to some wordpress and tells me registration is currently not allowed then asks for a username and password
@Raylusk can i do this method even if i am running the 2.2 firmware? Or would i have to revert back to the original is so how do i do it?
Click to expand...
Click to collapse
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App
raylusk said:
You can do it running 2.2. This will wipe your phone and install the new system.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ok I finally have it all worked out thanks a lot!
hgvidal said:
1. Flash back to stock 2.1 [through odin]
3. Flash DK17 modem through odin
4. Install Epic Exprience
Click to expand...
Click to collapse
I actually skipped step 2 and everything went fine for me. My laptop was being an asshole and not seeing the phone, so the 1 click root script simply wasn't working.. but then I realized that the DK17 flash via Odin that I got form the epic experience thread included clockworkmod and was pre-rooted and everything so I saw that step as unnecessary.
I recently flashed Task 650 AOKP 4.3 and I'm having a problem with it hanging on the Samsung logo screen nearly every time I reboot. I did a clean install and wiped everything except internal storage when I flashed it. I'm running TWRP 2.6.3.1 and I have the MDL baseband. What do you guys think the problem might be?
acts4:12 said:
I recently flashed Task 650 AOKP 4.3 and I'm having a problem with it hanging on the Samsung logo screen nearly every time I reboot. I did a clean install and wiped everything except internal storage when I flashed it. I'm running TWRP 2.6.3.1 and I have the MDL baseband. What do you guys think the problem might be?
Click to expand...
Click to collapse
Make sure the download is full, and make sure you have the right kernel for it and that you used loki if it's not auto-loki
DeadlySin9 said:
Make sure the download is full, and make sure you have the right kernel for it and that you used loki if it's not auto-loki
Click to expand...
Click to collapse
I checked the md5 before I flashed it and it was fine. I also just used the kernel that came with the Rom package. There was no need to loki because the Rom was already auto-loki'd.
I reverted my recovery back to 2.5.0.2 to see if that fixes the problem. I'll keep you posted if the issue continues with the older recovery version.
acts4 said:
I'll keep you posted if the issue continues with the older recovery version.
Click to expand...
Click to collapse
Thanks!
We'll keep waiting for your reply...
...over in the Q&A subforum where you should be posting questions & help needed threads.
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.
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
I've recently flashed NAE modem via Odin 3.09, also flashed Philz latest recovery. I was doing this so i could flash Rawintellects Stock(ish) ROM.... which seemed so badass. Really wish i could have got it working. Anyway, on to the problem.
Firmware flash went fine, Philz reovery went fine, ROM flash went fine. Now... I BELIEVE (can't remember) that i was coming from a MDL firmware, not sure though. After ROM flash, things were glitchy. No wifi (fixed after following suggestions in his thread. No 3g... fixed after a clean wipe 3X's and fresh ROM flash. And NO SOUND... never fixed. I spent half a day trying to get it right, never could.
So I decided to try another ROM, next was Negalites WondROM. Seemed cool, but had all the same issues. Exact same. Locking up, swipe screen locking up. System crashes, random reboots. NO SOUND. Figured, WTF.... tried another ROM same issues. At this point I thought maybe all these ROMS had the same kernal and that was the issue, so i flashed dif kernals compitable and recommended for dif ROMS. ALL SAME ISSUES. From here I figured it was the NAE modem the phone didn't like for whatever reason.
So now I'm stuck. I want to start over, want to flash MDL modem again, want to put the ROM i had back on here (I believe it was BluKuban or something). I am fairly certain there is now ay to take this phone back to the store and have them repair it, they will surely find something that will void the warranty even though im also fairly certain there is no warranty left on the phone. This phone is a business phone on our business account (one of 6 phones) and we've had buisiness with this sprint location for over a decade so i amy be able to persuade a repair.
Need help guys =(
Fixed
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
ograyray said:
Battery below 40 percent made this phone do some wonky things, after being fully charged this morning, i was able to use download mode and flash stock modem and revert all changes and get factory image. Lost root, recovery, and roms. But everything is back to normal.
Got the info i needed to do this from this guys thread, the only other thread that i found with the same symptoms and issues as me: http://forum.xda-developers.com/showthread.php?t=2662491
WOOHOOO!!:good::good:
Click to expand...
Click to collapse
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
tensux said:
NAE wont work on my phone with any ROM, same issues. MF9 works just fine so I don't bother. You could have just ODIN'ed the modem only rather than losing everything.
Click to expand...
Click to collapse
Thanks, at that point I was happy to get anything to work, nothing lost really, just maybe 4 or 5 roms, a few GAPS packages, dealing with realizing I flashed a 4.4.3 image though.... And reading through everything looks like there is no root method available for 4.4.3 yet.... BUT HEY, got the phone functional and usable.
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
tensux said:
You can still root your phone...nothing you have done is final
Sent from my SPH-L720 using XDA
Click to expand...
Click to collapse
I like two things. 1. Phone works 2. 4.4.3 is fast and battery life is awesome so far. I do hate the bloatware and bright ass yellow splash screen on boot. But i believe i can stick with this until root for 4.4.3 is out.
Gonna miss my ROMs till then. Unless you can find root method for 4.4. It's out for S5 but not S4. I'd be shocked if i was wrong.
You should read up a bit... No reason you can't be rooted on 4.4.3
Sent from my SPH-L720 using XDA