[Q] CM 11 M12 - No Service/Data - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Hello,
I OTA updated from CM 10.2 stable to CM 11 M12 snapshot and I installed the gapps separately. Almost everything seems fine except for "No Service" issue. Data connection is not working, but am able to make and receive calls. There is no APN settings and adding one does not gets saved.
I searched xda and few threads state that it is due to old modem. However, this thread in xda says that the bootloader and the modem version has to be match, otherwise installing a modem with mismatching bootloader may hard brick the phone.
According to "Phone info *Samsung*" app my
Bootloader version is : I747UCDMG2
Baseband version is: I747UCDMG2
1. Do I just get the latest Modem ONLY from this thread or do I need to get BOTH bootloader and modem from dstruct2k thread.
2. If I can't solve the issue, can I just flash stable CM 10.2 back with corresponding gapps? Will it cause any such issue, because somewhere in the above thread it was mentioned that dowgrading modem might hard brick the phone too.
Thanks in advance. Any help is really appreciated.

Looks like your bootloader and modem are too old to fully supported your updated ROM.
You will need to update both; however, once updated, you can never downgrade either to be safe.

audit13 said:
Looks like your bootloader and modem are too old to fully supported your updated ROM.
You will need to update both; however, once updated, you can never downgrade either to be safe.
Click to expand...
Click to collapse
Thanks. Is there a order in which both has to be flashed like bootloader first and then modem next? Do I flash both at the same time or flash one first, reboot and then flash the other?
Also, if I don't proceed to flash the new bootloader and modem, can I safely flash CM 10.1 now without bricking the phone?
Thanks again for your reply and help.

spk_xda said:
Thanks. Is there a order in which both has to be flashed like bootloader first and then modem next? Do I flash both at the same time or flash one first, reboot and then flash the other?
Also, if I don't proceed to flash the new bootloader and modem, can I safely flash CM 10.1 now without bricking the phone?
Thanks again for your reply and help.
Click to expand...
Click to collapse
not to buttin in , cause @audit13 knows a heck of alot more than me , but this thread
http://forum.xda-developers.com/showthread.php?t=2808654
has bootloader/modem combo zip. i think mjb and ne4. just flash and it updates both at same time. be sure to read OP first though.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Both should be flashed in tandem.
Yes, you can go back to cm10.2 as cm roms don't flash a bootloader or modem.

mrrocketdog said:
not to buttin in , cause @audit13 knows a heck of alot more than me , but this thread
http://forum.xda-developers.com/showthread.php?t=2808654
has bootloader/modem combo zip. i think mjb and ne4. just flash and it updates both at same time. be sure to read OP first though.
"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
audit13 said:
Both should be flashed in tandem.
Yes, you can go back to cm10.2 as cm roms don't flash a bootloader or modem.
Click to expand...
Click to collapse
Thank you very much to both of you. I followed the thread you mentioned and installed the MJB bootloader/modem combo and I got the data connectivity back. I did not install NE4 though as I dont really need it now I guess. Thanks again.

good to hear you got it fixed. :thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"

Related

[Q] New Bootloader

Hi guys,
I have looked at numerous threads and just can't find exactly what I need or maybe I'm too dumb/too much of a noob to understand what I need, I am on CM10.1 nightlies with CWM and I can no longer flash the nightlies. It gives me assert fail messages. After some digging, I think the problem is that I need to update the bootloader as they no longer support the ICS bootloader (I am assuming I am on ICS bootloader, how would I know?). But then I couldn't find the latest bootloader and how to install it. Is that even the problem? Any help is appreciated or even if you can point me to the right thread, that would be awesome. Thanks for the help.
jlor23 said:
Hi guys,
I have looked at numerous threads and just can't find exactly what I need or maybe I'm too dumb/too much of a noob to understand what I need, I am on CM10.1 nightlies with CWM and I can no longer flash the nightlies. It gives me assert fail messages. After some digging, I think the problem is that I need to update the bootloader as they no longer support the ICS bootloader (I am assuming I am on ICS bootloader, how would I know?). But then I couldn't find the latest bootloader and how to install it. Is that even the problem? Any help is appreciated or even if you can point me to the right thread, that would be awesome. Thanks for the help.
Click to expand...
Click to collapse
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Update your modem/firmware/baseband: I know the most recent build of LiquidSmooth require you to be on baseband MD4. You can get it over on Freeza's thread. The file you're looking for is:
MD4 Firmware:
MD4 Firmware/modem/baseband update
MD5: EEEAFDBE59CF9C5B492B1A591EC92D02
Click to expand...
Click to collapse
All you have to do is wipe cache and dalvik cache and flash this Rom in your recovery. Reboot and now you're on MD4.
Update your Recovery: I normally run the latest and greatest TWRP, but others like the stability of some of the older builds. I'd flash the latest 2.5.0.0 TWRP from Naddict's thread.
Those would be the first three things I'd try.
topherk said:
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Update your modem/firmware/baseband: I know the most recent build of LiquidSmooth require you to be on baseband MD4. You can get it over on Freeza's thread. The file you're looking for is:
All you have to do is wipe cache and dalvik cache and flash this Rom in your recovery. Reboot and now you're on MD4.
Update your Recovery: I normally run the latest and greatest TWRP, but others like the stability of some of the older builds. I'd flash the latest 2.5.0.0 TWRP from Naddict's thread.
Those would be the first three things I'd try.
Click to expand...
Click to collapse
Awesome! Your 2nd suggestion worked! I had tried your other 2 suggestion already with no luck but #2 was what I needed. Thanks so much!
topherk said:
I'm not 100% sure what the problem is, but I'll take you through step-by-step of what I'd do if my phone were giving me this problem.
Double check the md5sums of the CM10.1 Nightly Zip: It doesn't seem like this is the problem, but it's always the first thing I check.
Those would be the first three things I'd try.
Click to expand...
Click to collapse
Yes that most definitely was his problem, the new cm10.1 nightlies require the md4 firmware update because of the bootloader.
Sent from the future via Xparent Green Tapatalk 2

[Q] Questions about the new bootloader

*Question aswered *
Hi, am I the only one to be really confused about this new bootloader thing that we need to flash certains roms? Theres is no guide at all on our T999(v) to explain what
-are the benefits to install this R: Install newer CM and AOSP Roms without random reboots and to actually boot them
-how to install it R: Follow the guide on the link providen in this post below
-what are the risk R: If you dont instal the right bootloader for the right device = brick. But the proccess is the same to flash a ROM
-is there any issues known with this bootloader R: Still waiting
-can we flash old roms that worked on the old bootloader on this one R: YES !
-how do we know if we need the new bootloader before flashing a rom. R: Open a terminal emulator and run those commands : su *enter*
getpro ro.bootloader And check if you have the newest booloader referred to the guide on the link below
As you can see all those questions are not really understood from our T999(v) forum. I've researched on the forum for any information and I've found only this guy that provide MD5 bootloader with a few instructions http://forum.xda-developers.com/showthread.php?t=2282603 but really this is confusing. I do not want to make a fatal mistake and brick my S3 so this is why i'm asking all those questions to you guys. For info I own the SGT-T999v.
kruse1944 said:
Hi, am I the only one to be really confused about this new bootloader thing that we need to flash certains roms? Theres is no guide at all on our T999(v) to explain what
-are the benefits to install this
-how to install it
-what are the risk
-is there any issues known with this bootloader
-can we flash old roms that worked on the old bootloader on this one
-how do we know if we need the new bootloader before flashing a rom.
As you can see all those questions are not really understood from our T999(v) forum. I've researched on the forum for any information and I've found only this guy that provide MD5 bootloader with a few instructions http://forum.xda-developers.com/showthread.php?t=2282603 but really this is confusing. I do not want to make a fatal mistake and brick my S3 so this is why i'm asking all those questions to you guys. For info I own the SGT-T999v.
Click to expand...
Click to collapse
In the thread you linked, there is a T999v link. So you'll want to take that. Do not flash our bootloader on your phone. Must be T999v bootloader.
We don't have access to a changelog. Need to do it to flash newer AOSP ROMs. Why? Because the older ones were causing rebooting issues.
There is no risk as long as you get the bootloader for your device.
You can flash old ROMs.
Aerowinder said:
In the thread you linked, there is a T999v link. So you'll want to take that. Do not flash our bootloader on your phone. Must be T999v bootloader.
We don't have access to a changelog. Need to do it to flash newer AOSP ROMs. Why? Because the older ones were causing rebooting issues.
There is no risk as long as you get the bootloader for your device.
You can flash old ROMs.
Click to expand...
Click to collapse
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Just flash the zip through CWM or TWRP. The guy says in the OP he made the flashable files so you don't have to use a computer for this process.
If you get bad 4g, then just flash the modem you're on. There's a modem sticky thread in the development section.
Bootloader and modem/baseband are not the same thing.
I have the DLJA modem and the MD5 bootloader. I haven't had any issues at all.
Remember, if you have a T999v, only flash modems and bootloaders made for that specific device. It will clearly say in the op when you read it.
Goodluck.
Sent from my SGH-T999 using xda app-developers app
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Bootloader shouldn't cause signal issues. But flashable over recovery is correct.
Sent from my SGH-T999 using xda premium
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Stop talking about MD5. That firmware is not for your phone. I want to be certain you aren't going to flash that. As for battery life, I had to revert to LJC because of battery drain. The AOSP ROMs only require LJA or newer for us. I don't remember your firmware versions.
Safe to use recovery to flash this stuff. You could make an Odin package, but it would be a waste of time.
IXChicharitoXI said:
Just flash the zip through CWM or TWRP. The guy says in the OP he made the flashable files so you don't have to use a computer for this process.
If you get bad 4g, then just flash the modem you're on. There's a modem sticky thread in the development section.
Bootloader and modem/baseband are not the same thing.
I have the DLJA modem and the MD5 bootloader. I haven't had any issues at all.
Remember, if you have a T999v, only flash modems and bootloaders made for that specific device. It will clearly say in the op when you read it.
Goodluck.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Great thank you! So i've looked for my actual bootloader on my S3 with those commands : su getpro ro.bootloader I was surprised, it told me that I already have the T999VVDLL1 bootloader required for newer AOSP CM roms.
All of this is correct.
You also do have the option of flashing the latest firmware for your model device using Odin.
As long as you've upgraded to VLDLL1 via OTA, Kies or Odin you don't need to do anything.
Sent from my SGH-T999L using xda premium

MJ5 bootloader flash problems

Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Im having the same problems. odin is giving no love on updating the bootloader
Kenny_ken said:
Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Click to expand...
Click to collapse
Did you try to flash the kernel as stated in the installation instructions of the rom that your trying to install?
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
TeamFox said:
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
Click to expand...
Click to collapse
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
asin_punk said:
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
Click to expand...
Click to collapse
To clear things up i have already got agni kernel installed via recovery. I just cant update my bootloader via odin.
problem flashing mj5 bootloader and agni kernel too
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
anandsaurabh said:
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
Click to expand...
Click to collapse
Agni kernel is only flashable via recovery not with odin.. Its a zip file.. U can flash it using CWM or Philz Or twrp recoveries
Sent from my GT-N7100 using XDA Premium 4 mobile app
U r right hazin ... That file can be flashed only via recovery... But I m not able to flash it.. It goes into aroma installer, does its work and says done but does not show on settings... I e saved log file too of that process...
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
did you fix the problem ?
apuntigam said:
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
Click to expand...
Click to collapse
having the same thing now...
Davids said:
having the same thing now...
Click to expand...
Click to collapse
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
so the phone is dead ?
apuntigam said:
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
Click to expand...
Click to collapse
noting to do to bring back wifi&BT ?
Davids said:
noting to do to bring back wifi&BT ?
Click to expand...
Click to collapse
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
apuntigam said:
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
Click to expand...
Click to collapse
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Davids said:
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Click to expand...
Click to collapse
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
apuntigam said:
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
Click to expand...
Click to collapse
i have the 7100..
somthing for that device..
Davids said:
i have the 7100..
somthing for that device..
Click to expand...
Click to collapse
Ok, then it's a completely different discussion... not sure why the bootloader would be failing in that case, since it was built for that device. You could try a different Odin? (Assuming of course that your are NOT trying to DOWNGRADE the bootloader... it's well known that you can't downgrade the bootloarder to MJ5 from something more recent).
Otherwise, I'm sure there are equally useful ROMs for the N7100 in the Note 2 Original Development forum.
But, since your device is probably pretty old and almost certainly out of warranty by now, I would seriously consider flashing the latest official Samsung ROM to get the latest bootloader and then flash whatever you want on top of that. Voiding the warranty is irrelevant if you're already out of warranty. But, I have heard that even with the latest bootloader some people still have trouble with wifi and BT. In that case all I can suggest is playing around with different ROMs until you find something that works for you. As I'm not a N7100 user I can't really offer more advice than that, sorry man.
Guys where I can find a REAL WORKING link to download mj5 or higher bootloader??
I tried a lot & most of them are obselete
Maybe downnload the latest stock ROM from sammobile.com and extract the bootloader?
https://www.sammobile.com/firmwares/database/GT-N7105/

[Q] SGH-I747 Update Issues to 4.4.2

I'm trying to help out a friend and update his Galaxy S3 SGH-I747. He originally had cyanogenmod installed but he restored his phone back to stock and flashed a stock recovery back to the phone. When he tries to do an OTA updated it downloads but fails to install? His current android version is 4.1.1 but his baseband is I747UCUFNE4 which if im not mistaken is for android 4.4.2 what would be the easiest way to get his phone updated to the stock 4.4.2 software?
Follow one of enewman17's how to update threads in General.
4.4.2 upgrade stops at 28%
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
Can you be a bit more specific?
Thanks
bmoliver said:
Can you be a bit more specific?
Thanks
Click to expand...
Click to collapse
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
DocHoliday77 said:
Follow one of enewman17's how to update threads in General.
Click to expand...
Click to collapse
BWolf56 said:
The beauty of search: http://forum.xda-developers.com/search.php?searchid=292146343
Two threads from enewman17: UCUEMJB to UCUFNE4 firmware update; How to update SGH-I747 to UCUFNE4_4.4.2
Click to expand...
Click to collapse
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
EDIT: One more thing that I observed is when I am trying flash something in the download mode, I get the error and "sw rev check fail fused 3 binary 0" and it fails
Thanks,
CJ
bmoliver said:
Thanks, I had found the last link (....2789917) by doing a Google search (i.e., searching within the forum was less successful).
Click to expand...
Click to collapse
jchennuri said:
Hey bmoliver and BWolf56,
I am in the same boat as your friend where my baseband (bootloader) version is I747UCUFNE4 but the software version is stuck at 4.1.1. AT&T is identifying a OTA update, downloading but the update is failing.
I tried the method described in http://forum.xda-developers.com/showthread.php?t=2789917. But when I am trying to flash MJB bootloader, it is failing. I read elsewhere in this forum that downgrading from UCU to MJB is not really advisable.
I am stuck in 4.1.1 and my phone is half functional at the moment with the camera, nfc, bluetooth not functional :crying:.
Was your friend able to get this resolved bmoliver?
I tried searching for a I747UCUFNE4 md5 file that I can flash using odin (just a hope that it might work) but could not find.
It would be great if one of you can point me to it.
PS: I am a complete newbie to this entire thing and so far from what I read, my phone is probably soft-bricked and am hoping that someone would guide and help me get out of this.
Thanks,
CJ
Click to expand...
Click to collapse
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
BWolf56 said:
You don't want to downgrade bootloaders, that will brick your phone.
You'll have to flash NE4 with Odin (or a NE4 custom ROM through custom recovery) to get your baseband and software matching.
The thread you linked should work if you follow it to a T. If something doesn't work, let us know and be specific about what happened.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the info BWolf56,
Sorry for asking a trivial question (just getting accustomed to the lingo used here) .
When you say I should follow it to a T, are you just referring to follow all the steps.
I tried two things
1. follow each step, but failed at step 3 since I was trying to downgrade my bootloader.
2. I jumped from step 2 to step 6 and tried to flash 4.4.2OTA.zip in recovery mode but that also failed. I dont remember the exact error I got, I can try it again to give you more details if you think it is safe.
Thanks
Click to expand...
Click to collapse
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
BWolf56 said:
If you jumped to #6, you didn't flash a custom recovery, which you need to flash the OTA.
Click to expand...
Click to collapse
jchennuri said:
I did install TWRP 2.6.3.1 which I am guessing is the custom recovery (as part of step 2) and then I tried to flash the OTA. Am I missing something here?
Click to expand...
Click to collapse
What error did you get when flashing it?
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
BWolf56 said:
What error did you get when flashing it?
Click to expand...
Click to collapse
jchennuri said:
I just tried flashing it again and got the following error.
I loaded the zip into my internal SD and went to recovery mode (twrp gui, Power+Home+Volume Up)
and tried installing the zip
_______________
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Package expects build fingerprint of samsung/d2u (the screen does not allowing me to scroll to the right to look at the complete line after 'd2u')
E: Error executing updater binary in zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Error flashing zip '/data/media/Samsung_SGH-I747_4.4.2_OTA.zip'
Updating partition details...
FAILED
_________________
This is the error I am getting.
Am I missing something? Please let me know if you need any more info
Thanks a ton!!!
Click to expand...
Click to collapse
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
BWolf56 said:
Sounds like you'll have to use Odin to flash Stock.
Your build.prop is most likely borked (or has been changed to something it's not). d2u is not a variant of the S3, nor does it exist.
Click to expand...
Click to collapse
jchennuri said:
Thanks a ton for helping me identify the problem.
I just have to look if a stock file to flash using odin is out there somewhere.
I will post in http://forum.xda-developers.com/showthread.php?t=2789917 to see if enewman17 or someone from the community have a tar or md5 file that I can use.
I will try that and update on how it goes.
Click to expand...
Click to collapse
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
BWolf56 said:
You can grab the stock ROM here: http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Just make sure you grab the right version.
Click to expand...
Click to collapse
jchennuri said:
Thanks for the pointing me there.
I could not find the stock firmware for NE4 though.
They only have MJ2, LK3, LG1, LEM versions, no MJB either.
Click to expand...
Click to collapse
There isn't a NE4 stock for Odin. I just noticed the post hasn't been updated in a while.
I though I could find it on Sammobile.com but they have LK3 as their latest too.
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Thanks Doc!
Hopefully enewman17 can come up with a solution for this.
Just an information which I was not able to completely comprehend but maybe pros like you or Bwolf56 will be able to.
I opened Kies and this is what it says.
Firmware information
This is the latest firmware.
Current firmware version: PDA:LK3 / PHONE:NE4 / CSC:LK3 (ATT)
Any thoughts on how do I get the PDA and CSC updated (not even sure what exactly they are)
Thanks
DocHoliday77 said:
Since you somehow have the 4.4.2 modem, you can not flash anything older than the 4.4.2 firmware. Currently there is nothing that you can flash to fix this. Normally, I would say to flash an older modem, but if Odin is seeing it as already updated to 4.4.2 (SWREV 3), and the only thing you have that is 4.4.2 is the modem, flashing anything older will likely hard brick.
You need either the full stock firmware, which there is not one, Thanks AT&T!, or a recovery flashable firmware for 4.4.2. Enewman17 has this, but it will not work for you because of how the modem is flashed. For some reason, he has it patching the 4.3 modem rather than including the full updated one like with the other partitions. If someone makes the same thing, but with the already updated modem, you could probably flash that. No guarantees though. Running 4.1.1 firmware/bootloaders with a 4.4.2 modem is a scenario which is highly unpredictable, so anything you try to flash might cause more problems, we just don't know.
I've PM'd enewman17 to ask if there was a specific reason he updated the modem the way he did. If there is not an issue doing it like i mentioned someone can try to make a new package like that for you to try.
Click to expand...
Click to collapse
Ok, enewman17 just put this together if you want to try it. This includes the full NE4 stock firmware minus system, kernel, cache and recovery.
So flashing it will preserve your current Rom, kernel and recovery, but will otherwise fully update your base firmware/bootloaders to NE4.
This should be perfectly safe to use, but seeing as it is untested, I cannot make any guarantees that it won't make things worse. (I wouldn't post it if I thought it would, but there is always the possibility)
Flash from custom recovery such as TWRP.
http://www.androidfilehost.com/?fid=23578570567716667
Sent from my SGH-T999 using Tapatalk
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
If you want to fully update your system (rom) to stock NE4, enewman17 has a thread in the development section with stock rooms you can flash via recovery after you update your firmware posted above.
Sent from my SGH-T999 using Tapatalk

[Q&A] AT&T I747 UCUEMJB 4.3 Stock Restore

Q&A for AT&T I747 UCUEMJB 4.3 Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for AT&T I747 UCUEMJB 4.3 Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
help with att galaxy s3
i bricked my galaxy s3 i747 and using enewman17s method here http://forum.xda-developers.com/showthread.php?t=2658486
I downloaded the mk5 file from another one of his posts, and with that download it gives me multiple folders and a boot.img.
Now correct me if I'm wrong, the phone is actually up and running now, but the main problem i have found with it is that the sound is not working at all and videos dont want to play. Do i need the files in those folders and the .img file to make everything work properly? any other information can be provided and all is welcomed thank you.
Can I perform the procedure from 4.0 stock unrooted?
Enviado desde mi GT-N7100 mediante Tapatalk
msedek said:
Can I perform the procedure from 4.0 stock unrooted?
Enviado desde mi GT-N7100 mediante Tapatalk
Click to expand...
Click to collapse
Did you brick you phone while on 4.0? How did you brick it?
No the device is virgin non rooted, new out of the box and unlocked, I want it to be 4.3 unrooted and unlocked
Enviado desde mi GT-N7100 mediante Tapatalk
What is the model? In Canada, the s3 is the i747m. In the USA, the s3 is i747. The i747m bootloader and modem cannot be flashed on a i747.
Stock restore from 4.4.4 Carbon
I'm on Carbon 4.4.4 nightly 20140824-0205. Can I use this to return to stock ?
eric512 said:
I'm on Carbon 4.4.4 nightly 20140824-0205. Can I use this to return to stock ?
Click to expand...
Click to collapse
What bootloader is on your phone? You need to confirm that before proceeding. If you have a 4.4.2 bootloader and you use the 4.3 restore procedure, you could brick your phone.
audit13 said:
What bootloader is on your phone? You need to confirm that before proceeding. If you have a 4.4.2 bootloader and you use the 4.3 restore procedure, you could brick your phone.
Click to expand...
Click to collapse
If I run "getprop ro.bootloader" it says I747UCUEMJB, which is 4..3?
eric512 said:
If I run "getprop ro.bootloader" it says I747UCUEMJB, which is 4..3?
Click to expand...
Click to collapse
Yes, that is 4.3. Make sure you read the instructions very carefully. Flashing is always risky and there is always a chance that you wind up bricking the phone.
audit13 said:
Yes, that is 4.3. Make sure you read the instructions very carefully. Flashing is always risky and there is always a chance that you wind up bricking the phone.
Click to expand...
Click to collapse
Yes, but any more risky than flashing to the Carbon rom I just loaded?
Normally, flashing custom ROMs such as Liquid and Carbon do not flash a modem or bootloader. If something goes wrong, you can boot back into recovery and re-flash or flash a different ROM.
Flashing a stock ROM desktop Odin usually includes a modem and bootloader change. I believe changing the bootloader is the most crucial part to get right.
Hi there, first time poster and I want to thank the OP for the great efforts, write up and support!
I have a rooted ATT SGH-i747 that OTA soft-bricked on the way to 4.4.3 - I was able to get the phone back up and working with the 4.3 .zip and ODIN 3.7 following your thread, and then restored most of my data - but now my phone won't connect to 4G, it's wifi only, and Baseband version is "unknown"
I am assuming I should continue to update to 4.4.2 but I don't want to do further damage...
Any advice on how I can get back on ATT 4G or what my next move should be?
FWIW, I have CWM and TeamEpic-Root-from-Recovery -v5 installed on external SD
dont know if this will help, but maybe a starting point :
http://forum.xda-developers.com/showthread.php?t=2835386
good luck.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
dont know if this will help, but maybe a starting point :
http://forum.xda-developers.com/showthread.php?t=2835386
good luck.
Click to expand...
Click to collapse
Thanks for the quick reply!
Trying to access Mobile Networks my phone keeps telling me to insert the SIM card... and it's in there but it's not recognizing it.
I know the SIM is good cause I can use it in my other phone... now what have I done?
uhhhh.....not sure. hopefully someone more knowledgeable will chyme in. srry
"all i can really do , is stay out of my own way and let the will of heaven be done"
Disregard, im all set. flashed to stock and ota worked to upgrade to kit kat, yay
OCTANEJUNKIE said:
Thanks for the quick reply!
Trying to access Mobile Networks my phone keeps telling me to insert the SIM card... and it's in there but it's not recognizing it.
I know the SIM is good cause I can use it in my other phone... now what have I done?
Click to expand...
Click to collapse
Is the baseband still unknown? If it is, you should determine the bootloader installed on your phone. Sounds like a mismatch between the bootloader and modem.
Thanks bro you just saved my life and my fone's life
thanks a lot bro i was so pissed that i installed the cm 11 and i hated it and when i tried to go back to stock i just coudn't i tried all the methods the odin version it always failed and said that nand write error so i just gave up hope and thought that i would go to the shop in the morning and get the sw changed then at the very last moment i saw your post and i said why not give it a try and i was surprised and equally shocked that it was this simple to flash this rom thanks again bro and stay blessed
Restore i747 from 5.0.1 lollipop to stock rom
i'm in 5.0.1 CM lillipop and i want to restore my i747 to stock rom (4.4.2 KK) i tried to restore in 4.3 but no brick, stuck on AT&T logo ! i tried to return to 5.0.1 and it stuck on CM logo with Circle blue !
HELP
Sorry about my bad english

Categories

Resources