Related
I got the little pop up that there was an update so I installed it and it said the phone was going to boot in 6 seconds or whatever, after that the phone booted into CWM and it said it failed install. Now every time I check for an update it says there's no update right now. Am I the only one with this problem? How do I fix it? Is it because I'm rooted? I'm on the stock rom by the way.
jordan23945bulls said:
I got the little pop up that there was an update so I installed it and it said the phone was going to boot in 6 seconds or whatever, after that the phone booted into CWM and it said it failed install. Now every time I check for an update it says there's no update right now. Am I the only one with this problem? How do I fix it? Is it because I'm rooted? I'm on the stock rom by the way.
Click to expand...
Click to collapse
Yes, it is because you are rooted. Download the stock rooted DeOdex one done by freeza. Good stuff.
Sent from my SPH-L710 using xda premium
Naddict said:
Yes, it is because you are rooted. Download the stock rooted DeOdex one done by freeza. Good stuff.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I need to flash the Lg8 firmware and Other parts? Or does it not work if I don't? I have never flashed anything using Odin, could I get steps? Thanks. Also what if I want to flash another rom? Do I need to flash the lg8 firmware and other parts again?
jordan23945bulls said:
I need to flash the Lg8 firmware and Other parts? Or does it not work if I don't? I have never flashed anything using Odin, could I get steps? Thanks. Also what if I want to flash another rom? Do I need to flash the lg8 firmware and other parts again?
Click to expand...
Click to collapse
see here http://forum.xda-developers.com/showthread.php?t=1743923
you don't need to flash the modem if you don't want to. Although I think (opinion only, and they vary between user) LG8 is a very good modem right now.
Once you flash modem, you will keep it until you revert or flash a newer modem or a rom specifically tells you it also provides it.
Naddict said:
see here http://forum.xda-developers.com/showthread.php?t=1743923
you don't need to flash the modem if you don't want to. Although I think (opinion only, and they vary between user) LG8 is a very good modem right now.
Once you flash modem, you will keep it until you revert or flash a newer modem or a rom specifically tells you it also provides it.
Click to expand...
Click to collapse
Alright, so I don't need to flash the moden or the other parts if I'm flashing an lg8 rom.
Naddict said:
Yes, it is because you are rooted. Download the stock rooted DeOdex one done by freeza. Good stuff.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So flash the DeOdex version via CWR.
Then flash the Modem.zip via CWR.
Then use Odin and flash "Other Parts" .tar file and that's it?
Will there be any differentiation between going this route versus unrooting -> OTA update -> re-rooting?
The way I flash I got the legit update and flash with custom recovery and before the reboot flash the team win root file and ur done then reboot and ur done u have the hole update and firmware and radio and rooted and u keep your custom recovery
Sent from my SPH-L710 using xda premium
Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
rener78 said:
Am I the only one with videotron that is getting the error when trying to flash any of the new MD5 rom. Did a FW and tried all of the new rom's and no matter which one I install I'm getting the error process.android.phone FC. Even went back to stock and nothing is working
Thanks
Click to expand...
Click to collapse
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Misterjunky said:
Perhaps this T999 4.1.2 firmware update was not meant for your videotron phone.
It looks like you will need to get a hold of the stock Odin flash rom for your phone
and Odin flash it before you can do anything else.
Here is the link for the Odin Flash stock Videotron firmware for your phone in case you want
to flash it and start over again: http://www.androidfilehost.com/?fid=9390225151984927270
Click to expand...
Click to collapse
I did that and I still got the error :s
re: fc
rener78 said:
I did that and I still got the error :s
Click to expand...
Click to collapse
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Thanks alot but I give up I've tried what you told me and I still get the error. I guess it's just not ready as you said...Thanks alot again
Misterjunky said:
Try this:
Go into CWM or TWRP recovery and "Fix Permissions" then reboot.
If you still have the problem go into CWM or TWRP again and do a
factory reset/wipe cache/wipe dalvik cache but do not wipe system.
After doing that fix permissions again and reboot the phone.
Click to expand...
Click to collapse
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Are you just trying to flash the firmware? If so is there any you can flash so that its back to normal and working? You mentioned the error happened when trying to use the vtron fw is why I ask.
If you can get it working, flash jovys stock rom instead of the firmware. I dont see why this wont work if your up and running beforehand.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried to flash Jovy's stock MD5 rom and got the FC error, so I decided to go back to rooted stock and then flashing back Jovy's and other MD5 rom and still getting the FC. Will now try Jamieson rom and see from there again. Will post the results.
EDIT Still a no go under Infamous as well. Freaking mad
Thanks
Thats odd. It should work. Let me know how the other goes. Im out until a little later tonight so may not reply for a bit. Good luck!
Sent from my SGH-T999 using xda premium
I'm with Videotron I did get that error, try an original AOSP or CM ROM... Sometimes other ROMS implements T-Mobile features that our SIM i'snt compatible like the Mobile HotSpot App. And dont forget to fully wipe and factory reset it after !
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Do you happen to have mobile odin pro? If so, try flashing the root66 firmware that way. Deselect the modem and flash.
Be prepared with a backup and with odin and your stock firmware though, just in case.
The more I think about it, the more I wonder if its a kernel issue. Youre still using your vtron 4.1.1 kernel with tmobiles 4.1.2 system. Before trying the fw, try flashing the kernel that comes with md5. If you cant find it ill post it up in a while.
I dont know how likely this is the prob, but may be worth trying...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks again I have tried with a 4.1.2 kernel and it's still not working, I couldn't find anywhere the kernel coming with MD5. Looked in [Baseband] ALL T999(V) Modems! w/ MAP and Data Tweaks! and couldn't find it aswell.
Cause I used multi-carrier rom 4.1.2 before, Sprint, AT&T, Verizon but for some reason this one is giving a hell of a time.
Even tried an AT&T port of this T-mobile update and it wasn't working
Thanks alot again I really appreciate it
Well there's an update. None of the MD5 rom is working for me I always get the error. But 4.1.2 ports from other carriers are working. Really strange. So I guess I just need to wait for the official update.
**Edit** Well stockorama is actually working.. Weird
Is there anyone with a videotron sgs3 running an MD5 rom?? Cause I can't, only stockorama 2 other than that I cannot..
Well I give up... I have finally done something that I can not fix. I can normally google and find my own answers and I never have to ask anyone but this time is different.
I have the I317 Note 2, Everything was fine, I was running a stock rom earlier this week and the phone started acting funny. So I though screw it, Ill just go back to stock. So i downloaded.KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar and used Odin to flash the stock firmware. I DID do a full wipe before I went back to stock. It worked fine for 2 days. It kept wanting to download an update. So it did. When it restarted from the update that the phone downloaded it got stuck on the Samsung screen.
I thought no big deal, I will just reflash the stock firmware and start again... FAIL same thing happened. It wont get past the Samsung screen even after leaving it on that screen for a hour. So then I tried to get into recovery... it wont let me.Then I reinstalled the stock rom and waited for boot, then I flashed CWM and tried to get in to recovery that way. No luck.
I feel like I need to do a wipe and start all over but I cant figure out how to do a full wipe without recovery. There has got to be something easy that I am missing but I cant figure it out. I will keep on searching with hope that someone tells me what I am doing wrong or what to do.
THANKS
If its still able to go into download mode and odin recognizes the device your good just be patient and download the correct firmware.
Sent from my SAMSUNG-SGH-I317 using xda premium
There are some issues with the OTA update from LJ2 to MH3, which it appears you still have sitting on your phone. You can try booting recovery and clearing cache - that should get rid of the OTA file.
The thread below has some information on how to update from LJ2 up through MH3 and then MK6. It's intended for those who already have the MK6 bootloader - if you don't already have that or want that, you'll want to stop at MH3 and consider your options.
http://forum.xda-developers.com/showthread.php?t=2618447
Do you know did I use the correct firmware? I have had to run Odin a couple of times before but its a no go this time... I can not get into recovery. Even if I run Odin now with TWRP and restart it still wont let me into recovery... Can I use Odin to to a full wipe?
Were you on 4.3 previously? Via OTA?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
yes I did upgrade to 4.3 when it came available then I went to a custom rom. Then full wiped and downloaded what I thought was a stock rom and here I am.
Are you saying I need to download the 4.3 stock firmware and that is my issue. What i downloaded was from September 2013
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Trust in Odin it never fails.
Sent from my SAMSUNG-SGH-I317 using xda premium
Zen Arcade said:
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
WOW that worked!! I just got my phone into Recovery for the first time in over 24hrs now! I did a full wipe and now I am going to try and reinstall the factory rom that I have. Unless you tell me something different...
Thank you very much, I dont understand it but so happy to have a different screen!
Which factory rom? Where are you ultimately looking to get to?
100% back up and running! Thank you again
Zen Arcade said:
Which factory rom? Where are you ultimately looking to get to?
Click to expand...
Click to collapse
One that would work.... LOL I really dont have a preference other then I did not care for 4.3 I ended up with 4.1.1 and I couldn't be more happy. If they ever get 4.4 I would try that.
Its funny 4yrs ago I had the Sprint Evo. I changed roms more often then I changed shirts it seamed. I never had the issues or anything like what I ran into yesterday. I was so careless just trying every rom that was released. Because of that I will always remember the EVO as my favorite phone.
Those were simpler times...
I assume you want root and know how to get it.
Since you have the mk6 bootloader you will need to avoid odin flashing any packages that contain bootloaders in the future. See my mk6 thread for details.
If you want to get to 4.1.2 there are rooted cwm packages for ma4, mc3, and mh3 available. Wherever you end up, I recommend freezing the AT&T Software Update apk from within Titanium Backup or equivalent to ensure that you don't get a forced ota update at some point in the future.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Hi xda, I hope your Friday is going well.
EDIT: My calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody? I don't even hear a dial tone if I am the one dialing out, the call still goes through though.
Everything below was my original post which has been resolved, didn't want to start a new thread though.
-----------------------------------------------------------------------------------------
TL;DR: My T-Mobile Samsung Galaxy S 4 (SGH-M919) is unable to boot stock rom, and I am unable to enter recovery. I get seandroid messages trying to do either. Fortunately, the phone can enter download mode. What do I need to do or flash to get this phone booting again? Thank you in advance for taking the time to read and help out.
Below is the long story with details:
1. The phone was given to me running stock Android/TouchWiz. Unfortunately, I do not know what version but I assume it was whatever was the latest version as of late April.
2. I rooted the phone using Odin and CF Auto Root.
3. I created a backup of this newly rooted stock rom.
4. I flashed Cyanogenmod 11
5. After a while I discovered that I could answer calls but I could not hear nor be heard during the call.
6. I restored to the stock rom using the backup I made in step 3.
7. The calling issue continued, so I figured I would just unroot and go back to like-new factory settings. This way I could take the phone in to be repaired or whatever.
8. Following this thread: http://forum.xda-developers.com/showthread.php?t=2336392, I attempted to flash k0nane's UVUAMDL Official Tar
9. Odin got stuck connecting to my device, I believe it was because I did not run Odin as admin. I pulled the battery and repeated this step while running Odin as admin.
10. The flash was successful, however during the phone's first boot it got stuck on the T-Mobile splash screen for about 30 minutes or so. I pulled the battery again.
11. Anytime I put the battery back in the phone, it will attempt to boot and hang at the T-Mobile screen, I believe this is a boot loop?
Looking online, people suggest going into recovery and wiping but I cannot enter recovery. I just get the seandroid not enforcing messages. I'm very hesitant to keep looking through the forums and trying things because I feel like I'm on the edge of bricking the phone if I haven't already.
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ok so I flashed the wrong rom then. I hate to ask but where could I find a 4.4.2 stock rom? I just found a rom I believe will work but the file is titled "M919UVUFNB4_M919TMBFNB4_TMB" not sure if this is 4.4.2 or newer?
You download the stock 4.4.2 ROM from sammobile:
http://www.sammobile.com/firmwares/
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
You download the stock 4.4.2 ROM from sammobile:
[link removed]
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
THVRSDAY said:
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
Click to expand...
Click to collapse
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
PanchoPlanet said:
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
Click to expand...
Click to collapse
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
THVRSDAY said:
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
Click to expand...
Click to collapse
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
THVRSDAY said:
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
Click to expand...
Click to collapse
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
THVRSDAY said:
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
Click to expand...
Click to collapse
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
New term for CM, "complicated maneuver" ,.
Reflashing firmware may do it. Can't hurt either.
Pp.
Sent from my SGH-M919 using XDA Premium 4 mobile app
THVRSDAY said:
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
Click to expand...
Click to collapse
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Sent from my SGH-M919 using Tapatalk
serio22 said:
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Click to expand...
Click to collapse
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
THVRSDAY said:
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
Click to expand...
Click to collapse
No it will not work, this is device specific afaik.. Like I said earlier, I recommend you call T-Mobile for a replacement
Sent from my SGH-M919 using Tapatalk
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Skipjacks said:
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Click to expand...
Click to collapse
I have restored the phone to full stock and have been using it that way since I started this thread. Everything is just like fresh from the factory (except for the knox counter being tripped obviously). Calls still didn't work. An IMEI number still shows up the phone's settings. Using WiFi calling hasn't been that bad at all, but I'm screwed in the case of a real emergency with this thing.
Hi All,
I just recently returned to my trusty T999 Galaxy S3 and was wondering what modem I should update to? I just flashed CM11 and everything appears to be working properly except it says 3G in the status bar and not H+ (even though I'm in an HSPA/LTE area).
Currently I am on modem T999UVDLJA, which I believe is a 4.1.1 modem. Should I update to a 4.3 modem?(if so which one?) or stick with the 4.1.1 modem? I've read that once you update to a 4.3 modem you can't go back to 4.1 modems? Is that true?
All recommendations are welcome.
Thanks!
Once on 4.3 firmware you cannot use older modems. If on pre 4.3 firmware you can try the 4.3 one and go back if needed.
First, though, start a large download using mobile data. Go to settings, about device, status, network type. This will tell you your true connection type.
If hspa is not working, its much more likely to be a tower issue than a problem with the modem. Still, it doesnt hurt to try the other modems though!
LJA is very old, you need to update it so you can get H+ try the latest modem
DocHoliday77 said:
Once on 4.3 firmware you cannot use older modems. If on pre 4.3 firmware you can try the 4.3 one and go back if needed.
First, though, start a large download using mobile data. Go to settings, about device, status, network type. This will tell you your true connection type.
If hspa is not working, its much more likely to be a tower issue than a problem with the modem. Still, it doesnt hurt to try the other modems though!
Click to expand...
Click to collapse
Hi Doc,
You are correct, once i start doing a "large download" the data changes to H+ up top, so HSPA is working. Now with regards to pre 4.3 modems not working, I am running CM11 which is 4.4.4 and am running the old UVDLJA modem. In theory is this not supposed to work?
What modems are everyone using right now with the 4.4 ROMS?
Doesn't matter what rom you are on. Its the base firmware. If you have updated to 4.3 firmware, you must use the same or newer modem as the firmware build.
If running non touchwiz kk, as I understand it you can do so on older firmware. To run a touchwiz kk rom though, you must be on 4.3 firmware and thus a 4.3 modem.
You are using a non touchwiz rom, so as long as you are not updated to the 4.3 firmware, you can run the LJA modem without issue. Once you update to 4.3, you will have to use the 4.3 modem.
DocHoliday77 said:
Doesn't matter what rom you are on. Its the base firmware. If you have updated to 4.3 firmware, you must use the same or newer modem as the firmware build.
If running non touchwiz kk, as I understand it you can do so on older firmware. To run a touchwiz kk rom though, you must be on 4.3 firmware and thus a 4.3 modem.
You are using a non touchwiz rom, so as long as you are not updated to the 4.3 firmware, you can run the LJA modem without issue. Once you update to 4.3, you will have to use the 4.3 modem.
Click to expand...
Click to collapse
Ok, thanks for the clarification. How do I find out what my base firmware is then?
torpy said:
Hi Doc,
You are correct, once i start doing a "large download" the data changes to H+ up top, so HSPA is working. Now with regards to pre 4.3 modems not working, I am running CM11 which is 4.4.4 and am running the old UVDLJA modem. In theory is this not supposed to work?
Click to expand...
Click to collapse
I remember there were certain modem versions that wouldn't work with hspa, must have been ICS then..
torpy said:
Ok, thanks for the clarification. How do I find out what my base firmware is then?
Click to expand...
Click to collapse
Use phone info from the play store under firmware it will give you all the info
Sent from my SGH-M919 using Tapatalk
Is it safe to update to a 4.3 modem? Will it "brick" my phone and/or lock it with KNOX?
Which 4.3 modem should i update to?
torpy said:
Is it safe to update to a 4.3 modem? Will it "brick" my phone and/or lock it with KNOX?
Which 4.3 modem should i update to?
Click to expand...
Click to collapse
If you want to update to a 4.3 modem just flash the latest, and it won't brick or give you Knox
Sent from my SGH-M919 using Tapatalk
Im sure the app serio22 mentioned will work fine, but I always tell people to do this as ive learned you cant always trust what an app or gui tells you!
In terminal emulator, enter this:
getprop ro.bootloader
What it returns is your base firmware build.
DocHoliday77 said:
Im sure the app serio22 mentioned will work fine, but I always tell people to do this as ive learned you cant always trust what an app or gui tells you!
In terminal emulator, enter this:
getprop ro.bootloader
What it returns is your base firmware build.
Click to expand...
Click to collapse
That's what I use to tell people as well but they were always confused on how to use it and read the info so I just started mentioning that app instead.. I'm not sure if it works on CM come to think of it. What I like about it is that it gives you tons of info, even how many times you've plugged into the headset jack, and charger! Lol
Sent from my SGH-M919 using Tapatalk
Well I'm on a 4.4.4 rom with very old modem from ever since and I'm getting h+ tho never had any problems really
Sent from my GT-I9505 using XDA Premium 4 mobile app
dorian2kx said:
Well I'm on a 4.4.4 rom with very old modem from ever since and I'm getting h+ tho never had any problems really
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might be a touchwiz thing, never used aosp/cm much
Sent from my SGH-M919 using Tapatalk