I have been happily running AICP Lollipop since July 2015 on the MK3 radio. At the time, I read about issues with the "newer" modems and not being able to roll back the firmware to an older modem. I'm interested in trying out the newer Android 6.0 roms, but many of them mention a requirement of the ND8 modem. I haven't had any major reception issues with my current MK3 modem. Are there any issues upgrading the device to one of the newer modem?
I found the L710VPUDNJ2_L710SPRDNJ2_SPR stock file on the forums here. From what I gather, this would upgrade my device to stock along with the more recent NJ2 modem? Do I just wipe my current system (I already have a nandroid backup), and flash this image with Odin? Even with a backup, I have a feeling that I won't be able to go back to my old rom. Should i just go to the older ND8 instead of NJ2 since that is the minimum required for many of the 6.0 ROMs?
Nj2 works fine. That's what I have now. No issues updating. You flash the nj2 .tar in odin. Then you will be able to restore your aicp nandroid.
To root, of course, just odin flash the latest twrp .tar. The newest is twrp 3.0.0-0.
You nandroid should work fine, but I would take this chance to do a clean flash of the rom.
I think 12/27 is the latest aicp lp. They have aicp m now. It works pretty good.
I was running the newest aicp marshmallow for a few, Not quite as smooth as LP. I went back to lollipop for now.
Related
I need some help on how to update my Baseband Version/Modem.
My Current Baseband Version: I747UCDMG2
And i'm running CM11 Android 4.4.2 Kitkat.
sian23 said:
I need some help on how to update my Baseband Version/Modem.
My Current Baseband Version: I747UCDMG2
And i'm running CM11 Android 4.4.2 Kitkat.
Click to expand...
Click to collapse
I believe CM11 will work fine with 4.3 firmware and modems. I would suggest using the MJ2 firmware and MJB modem, at least until you have decided you need even newer than them. An advantage to MJ2 is that it can be downgraded if you ever have need for that. A link to it can be found in the OP of http://forum.xda-developers.com/showthread.php?t=2252932. Another advantage is that it was released prior to the release of KNOX. Not only will this firmware/baseband combo will run CM11, it will run TW based 4.3 roms and many TW based 4.4.2 roms.
If you are wanting to get to the latest firmware and baseband, do not use the MJ2 firmware. Many people would recommend you upgrading sequentially through MJB, NE4, and to NJ1. Links to the MJB firmware can be found in the same post as the MJ2 I linked. Enewman17 has a thread regarding upgrading to NE4 firmware. http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you have an interest in unlocking your phone from your carrier, do it prior to upgrading to MJB and beyond. Once reaching MJB it can only be unlocked by your carrier or by using a paid service.
dawgdoc said:
I believe CM11 will work fine with 4.3 firmware and modems. I would suggest using the MJ2 firmware and MJB modem, at least until you have decided you need even newer than them. An advantage to MJ2 is that it can be downgraded if you ever have need for that. A link to it can be found in the OP of http://forum.xda-developers.com/showthread.php?t=2252932. Another advantage is that it was released prior to the release of KNOX. Not only will this firmware/baseband combo will run CM11, it will run TW based 4.3 roms and many TW based 4.4.2 roms.
If you are wanting to get to the latest firmware and baseband, do not use the MJ2 firmware. Many people would recommend you upgrading sequentially through MJB, NE4, and to NJ1. Links to the MJB firmware can be found in the same post as the MJ2 I linked. Enewman17 has a thread regarding upgrading to NE4 firmware. http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you have an interest in unlocking your phone from your carrier, do it prior to upgrading to MJB and beyond. Once reaching MJB it can only be unlocked by your carrier or by using a paid service.
Click to expand...
Click to collapse
If i was to flash NE4,should i flash MG2 to MJB first and then flash NE4?
And also,do i have to do a factory reset while flashing these files?
sian23 said:
If i was to flash NE4,should i flash MG2 to MJB first and then flash NE4?
And also,do i have to do a factory reset while flashing these files?
Click to expand...
Click to collapse
Yes, I would recommend incremental updating: MG2 > MJB > NE4; as shown in the second thread I linked.
I am only on the 4.3 leaked firmware and official 4.3 baseband, I have not updated to NE4 at this point. But, I was on the 4.1.2 stock rom when I updated to the MJ2/MJB firmware-modem combination. I went back into that rom with no factory reset and no wipes. After a couple of days with no issues I flashed a custom 4.3 rom. I did do the recommended reset and wipes in the flashing process, that was due to the rom, not the firmware and baseband. Also, the link does not suggest resetting or wiping in the upgrade of firmware and modem. If you have any issues after flashing, then I would suggest the factory reset and wipes with possibly even a reflash of your rom.
dawgdoc said:
Yes, I would recommend incremental updating: MG2 > MJB > NE4; as shown in the second thread I linked.
I am only on the 4.3 leaked firmware and official 4.3 baseband, I have not updated to NE4 at this point. But, I was on the 4.1.2 stock rom when I updated to the MJ2/MJB firmware-modem combination. I went back into that rom with no factory reset and no wipes. After a couple of days with no issues I flashed a custom 4.3 rom. I did do the recommended reset and wipes in the flashing process, that was due to the rom, not the firmware and baseband. Also, the link does not suggest resetting or wiping in the upgrade of firmware and modem. If you have any issues after flashing, then I would suggest the factory reset and wipes with possibly even a reflash of your rom.
Click to expand...
Click to collapse
Thanks!Updated it to MJB without Factory Reset.
I'm going to install NE4 when CM12 comes out.
http://forum.xda-developers.com/showthread.php?t=2968854
unofficial, but working they say.
"all I can really do, is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
http://forum.xda-developers.com/showthread.php?t=2968854
unofficial, but working they say.
"all I can really do, is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
And this is the other unofficial CM12 for the d2att
http://forum.xda-developers.com/galaxy-s3-att/orig-development/rom-cm12-d2att-alpha-builds-t2959561
Are those unofficial builds safe?
Like for example i flashed it on my phone,and CM12(official came out).
Can i flash Unofficial CM12 -> Official CM12 without errors?
sian23 said:
Are those unofficial builds safe?
Like for example i flashed it on my phone,and CM12(official came out).
Can i flash Unofficial CM12 -> Official CM12 without errors?
Click to expand...
Click to collapse
i personally have never flashed one of the cm12 unofficial builds. i suggest you read thru the threads and see if people are having issues or not and then decide. i would also definitely make a backup of current setup if did decide to try.
if you did a full wipe between unofficial and official , i would imagine to be most sure way to avoid errors.
imho there is ALWAYS a risk in flashing/rooting/modding,etc.
good luck with whatever you decide.
"all I can really do, is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
i personally have never flashed one of the cm12 unofficial builds. i suggest you read thru the threads and see if people are having issues or not and then decide. i would also definitely make a backup of current setup if did decide to try.
if you did a full wipe between unofficial and official , i would imagine to be most sure way to avoid errors.
imho there is ALWAYS a risk in flashing/rooting/modding,etc.
good luck with whatever you decide.
"all I can really do, is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Mhmm,my decisions made up,and i should wait ti'll they released the official CM12...i think they would release it soon.
But i would make a research about it.
Background: I attempted to update from SlimKat 7.0 stable to 9.0 stable and discovered my apn's were missing and when I try to add them manually it fails to save. I have also found others with this same issue but none have an easy fix. I'm on UCDLK3 firmware, after restoring to previous state using nandroid backup apn's are present. If I try to flash any ROM (even other than Slim) my apn's are missing, even a dirty flash of 7.0 over 7.0. I know I can fix this by flashing stock UCDLK3 and root/twrp/flash slim 9 and everything will likely work fine. I plan to do just that but want to make sure I'm doing things as smart and clean as possible. There is a lot of info out there and I'm finding it hard to sift through old stuff and find the current state of things.
Question: Is there an actual advantage if I upgrade the firmware from UCDLK3 to UCUEMJB while still planning to use SlimKat 9 Stable with BMS kernel and TWRP recovery? Are there any disadvantages? Either way what is the shortest path to get back to stock (either LK3 or MJB) and flash SlimKat?
Thanks
Your APN may not be sticking because your modem and bootloader may be too outdated.
Some of the latest CM11 and AOSP ROMs require a KK bootloader and modem.
And then there are some roms that require at least a 4.3 bootloader and modem, either the MJ2 (leaked) or MJB (official) bootlaoder/modem combos. I have seen mention of these working in some OPs and in the body of other threads. In some of the later TW ROMs you may have to use a custom kernel like kt747 or iBuddler's. I don't know if any kernel other than the stock in SlimKat and AOSP ROMs would be needed with the MJ2/MJB firmware and modem.
I don't know of any advantages other than some of the ROMs require firmware newer than DLK3 to properly boot, receive data, or have a working wifi. As far as disadvantages, KNOX was introduced with the MJB firmware and stock ROMs, once going to MJB or newer firmware you can not make firmware downgrades without a very real risk of hardbricking your phone. Also you will need to insure your baseband and modem versions match. If they do not you risk hardbricking of another variety.
I had not yet realized that the newer AOSP and CM11 required you to go all of the way to NE4, thank Audit.
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
thanks for posting fix. am sure it will help others. audit13 and dawgdoc , thank you for continued help with the awesome Slll. :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
jeff.leonard said:
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
Click to expand...
Click to collapse
When you restored to LK3, what Firmware version were you coming from? I'm looking to go to LK3 from the NJ1. However there seems to be cautionary red flags all over the place due to bootloader changes that were made in 4.3.
The OP was already on LK3 with a custom ROM.
Since you are on NJ1, you cannot downgrade the bootloader.
I haven't upgraded my baseband/modem since I was running S3RX, so I am on NE4 baseband currently. I have been running CM12 for some time now and have no plans on going back to KK.
So I'm wondering what the best way to update to NJ2 would be. Should I download d2att_I747UCUFNJ1_bootloader_modem_4.4.2_12-3-14.zip flash in twrp, reboot then flash d2att_I747UCUFNJ2_bootloader_modem_4.4.2_8-19-2015.zip?
thanks!
miatawnt2b said:
I haven't upgraded my baseband/modem since I was running S3RX, so I am on NE4 baseband currently. I have been running CM12 for some time now and have no plans on going back to KK.
So I'm wondering what the best way to update to NJ2 would be. Should I download d2att_I747UCUFNJ1_bootloader_modem_4.4.2_12-3-14.zip flash in twrp, reboot then flash d2att_I747UCUFNJ2_bootloader_modem_4.4.2_8-19-2015.zip?
thanks!
Click to expand...
Click to collapse
That matches what I did when I updated from MJB -> NE4 -> NJ1. Download enewman's zips that bundle the bootloader and modem together. Flash sequentially, and reboot into your ROM between each bootloader/modem flash.
I haven't updated to NJ2 yet. NJ1 is working fine.
Hey all. I am fairly inexperienced when it comes to rooting, though I have done a few succesfully in the past. I currently have the newest version of TWRP installed on my Samsung I747M. The I747M I have is not from one of the major carriers, but as far as I am aware, the phone is factory network unlocked. Carrier is GCI, in Alaska.
I currently have a 4.4.2 Touchwiz Rom installed and started having problems after I attempted to flash the ROM Dandroid, which is 4.3 (http://forum.xda-developers.com/showthread.php?t=2121506). I had created a backup using TWRP before flashing the ROM and reverted back once I noticed the problem.
The main issue I am experiencing at this time is the Baseband Version, IMEI, and other information related to the modem is showing "Unknown" and features such as wifi will not toggle on.
I had also attempted to flash the most current version of the modem that I was able to find thru Odin. Odin showed the flash as successful. The version I flashed to the phone was I747MUMUEND3: modem_CWM_I747MUMUEND3.zip - 18.80 MB - April 3rd, 2014 (http://forum.xda-developers.com/showthread.php?t=1831898)
At this point, I can still get into recovery, download modem and I am able to boot up the phone and access most all functions. The next step I was going to try was going to be to flash back to stock firmware from sammobile's website (Was using to use the Roger's version of 4.4.2), though I don't want to cause more issues than I can handle or resolve thru software.
Any advice on how to proceed would be greatly appreciated or even just how to get the modem/wifi features functional again would be helpful. I'm just as happy staying on my current ROM at this point if I can get the phone fully functional again.
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
audit13 said:
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
Click to expand...
Click to collapse
Forgot to mention, this is something I did try. I attempted to flash Cyanogen Mod 12.1 (Download: cm-12.1-20151017-NIGHTLY-d2att.zip (286.76 MB) ) and most recent nightly build & the most recent stable release (CM11) (Download: cm-11-20140210-SNAPSHOT-M3-d2att.zip (194.37 MB) ). When flashing these, I transferred the downloaded ZIP file to the internal storage of the phone in the root directory and attempted to run an install from TWRP. Both installs failed.
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: http://www.sammobile.com/firmwares/database/SGH-I747M/
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
audit13 said:
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
Click to expand...
Click to collapse
I'll give that a shot when I get home. Stock firmware was one of my next thoughts. I have it downloading at the measly 15 Kbps offered for free from sammobile so hopefully should be done by the time I get home & update this thread with any progress.
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in TMS3KK thread. The ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
dawgdoc said:
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the "http://forum.xda-developers.com/showthread.php?t=2725192"Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in http://forum.xda-developers.com/showthread.php?t=2725750" TMS3KK thread. The http://forum.xda-developers.com/showthread.php?t=1756776" ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
Click to expand...
Click to collapse
I'm not opposed to any of this. Mostly just trying to slim down this phone to the basics as much as I can and am quite open to any recommendations. Main thing I want to maximize is battery life & simplicity since this is for my wife and those are her major wants in a phone. I figure any kind of ROM that just covers the basics should cover my bases & would prefer one with a darker/black skin to maximize battery life w/ the OLED screen. I am in the process of flashing to the Roger's stock ROM as I type this w/ my fingers crossed.
Just to add, no over clocking or anything of that nature is desired. If I remember correctly I ended up putting the ktoonsez kernel on one of my handsets, either this Galaxy S3 or my Galaxy S5, though I can't recall which since it was so long ago.
Alright! So progress! Wifi, Baseband version, IMEI and all other missing information restored & now works w/ stock rom flash. In process of reflashing TWRP now.
Let us know what happens.
Still all good with TWRP installed. Have not flashed back on a custom ROM yet. After reviewing some of the above recommendations, I am kind of liking the looks & features of TMS3KK (http://forum.xda-developers.com/showthread.php?t=2725750) and feel it would suit my needs.
I factory reset, cleared cache, and cleared Dalvik thru TWRP & then made a back up. Prior to this, I confirmed everything was still working normally w/ phone fully loaded after TWRP was installed.
One of the things mentioned on the installation instructions for that ROM is the following:
---
Do not mix and match 4.3 firmware (bootloaders/modem) with the new 4.4.2 ones. You will hard brick and I warned you. This works the same as any 4.3 or ND8port ROM with 4.3 firmware and it can use the new 4.4.2 ones also.
Link to recovery flashable i747 and i747M 4.4.2 bootloader and modem packages: http://forum.xda-developers.com/gala...hable-t2856914
---
How would I go about confirming my current bootloader/modem versions to make sure they are both 4.4.2 before flashing this ROM? At the link provided, those files/links to the files were removed because they were causing some bricked devices per a note at the top of that thread. Here's a link to the thread I am referencing since the above link looks to be broken. (http://forum.xda-developers.com/gal...mware-ne4-ne6-nf2-recovery-flashable-t2856914)
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
audit13 said:
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
Click to expand...
Click to collapse
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
fodor362 said:
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
Click to expand...
Click to collapse
Glad to hear the phone is running well.
I've heard it said "Happy wife, Happy life."
I have two Sprint L710s; one has baseband L710VPUDOH1 and one has L710VPUDND8. Both are running LOS 14.1. I have a OEM/stock nandroid from the OH1 phone, but not from the ND8. I'm trying to do a OEM Restore on the D8 phone, so that I can run a carrier activation.
When I restore the backup (made with OH1), then the ND8 phone boots into a stock ROM, but the wifi slider will not move to "on", and apps are crashing left and right (sounds like the system can't work with the modem). I'm wondering if I need to backup the bootloader and modem partitions from the phone that made the backup (baseband OH1), and flash them onto the ND8 phone? Or maybe even all partitions (since I'll follow with a twrp wipe anyways)?
specialgreen said:
I have two Sprint L710s; one has baseband L710VPUDOH1 and one has L710VPUDND8. Both are running LOS 14.1. I have a OEM/stock nandroid from the OH1 phone, but not from the ND8. I'm trying to do a OEM Restore on the D8 phone, so that I can run a carrier activation.
When I restore the backup (made with OH1), then the ND8 phone boots into a stock ROM, but the wifi slider will not move to "on", and apps are crashing left and right (sounds like the system can't work with the modem). I'm wondering if I need to backup the bootloader and modem partitions from the phone that made the backup (baseband OH1), and flash them onto the ND8 phone? Or maybe even all partitions (since I'll follow with a twrp wipe anyways)?
Click to expand...
Click to collapse
That's happening because the boot.img doesn't match the system. You cannot update that way. You need to find a complete nd8 stock firmware .tar and flash it with Odin. Or even nj2 (which is the update after nd8).
Those files from the oh1 phone will not work on the nd8 one, too many differences.
madbat99 said:
That's happening because the boot.img doesn't match the system. You cannot update that way. You need to find a complete nd8 stock firmware .tar and flash it with Odin. Or even nj2 (which is the update after nd8).
Those files from the oh1 phone will not work on the nd8 one, too many differences.
Click to expand...
Click to collapse
Thanks, MadBat99. I did not find an Odin ND8 (it looks like most of the ROM sites are paywall now?), but I found an ND8 "one-click installer" from RWilco12, which worked great. I wonder if I can use that later on my OH1 phone (should the need arise); both ND8 and OH1 are after Knox.
specialgreen said:
Thanks, MadBat99. I did not find an Odin ND8 (it looks like most of the ROM sites are paywall now?), but I found an ND8 "one-click installer" from RWilco12, which worked great. I wonder if I can use that later on my OH1 phone (should the need arise); both ND8 and OH1 are after Knox.
Click to expand...
Click to collapse
It won't brick (as you said, after Knox) but the WiFi not turning on may persist. But since it's the whole firmware, it may work fine.