Can not flash JB modem and Bootloader - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.mediafire.com/view/ioenxb5nfb2dk/Imagenes pakas#38s4kv125hn3fap
Previously had the intergalactic rom and 0 problems.
But now I can not flash any cr / modem.
Any idea why?

If you have an i747m, don't flash the mjb bootloader as you do not have the att s3. You could brick your phone.

audit13 said:
If you have an i747m, don't flash the mjb bootloader as you do not have the att s3. You could brick your phone.
Click to expand...
Click to collapse
But when I flash a CR my wi-fi and data is not working. (tested in 3 roms)
And afther the first boot my phone dies an never boots again.
I need to iuse ODIN to fix it.

Flashing the wrong bootloader can brick your phone and Odin will not fix a hard bricked phone. If the ROM won't boot, it may not be due to the bootloader. I have a 4.1.2 bootloader and every custom ROM I have tried will work.

Pegajoso said:
But when I flash a CR my wi-fi and data is not working. (tested in 3 roms)
And afther the first boot my phone dies an never boots again.
I need to iuse ODIN to fix it.
Click to expand...
Click to collapse
Looks like you have an hybrid firmware with the (stock) MUMUEMK3 Android 4.2 ROM and a MUMLI1 baseband/modem. The MUMUEMK3 is an official build of the 4.3. I'm not sure about the Mexican variant but I know that, with the US variant like AT&T, the stock 4.3 will not work with older modems and attempting to install an older modem always causes a baseband failure and consequent loss of all cellular functioning. I wouldn't be surprised if this is what you are experiencing and I would suggest you try to flash a 4.3 modem (MUMUEMK) instead. Or you may just look for a complete 4.3 stock image for your variant of the SGS3 and install this via custom recovery. I'd be surprised if this doesn't work.

Mmm actually I'm in the stock firmware.
But I can't find that modem (MUMUEMK)
http://forum.xda-developers.com/showthread.php?t=1831898
The problem here is If i flash a custom rom my phone only boot one time and then dies.
Even If I try to restore my backup (stock firmware) my phone never boot
Yeah I know is hard to belive (Tomorrow I record a video) but this is so confusing

Pegajoso said:
Mmm actually I'm in the stock firmware.
But I can't find that modem (MUMUEMK)
http://forum.xda-developers.com/showthread.php?t=1831898
The problem here is If i flash a custom rom my phone only boot one time and then dies.
Even If I try to restore my backup (stock firmware) my phone never boot
Yeah I know is hard to belive (Tomorrow I record a video) but this is so confusing
Click to expand...
Click to collapse
Looks like most of the emphasis is on the Canadian and US builds. Perhaps we sometimes overlook the Mexican and PR variants of the I747M. I believe, however, you may be able to find the stock image at Sammobile.com. I just checked there now and found this ...
http://www.sammobile.com/firmwares/3/?download=22509
I'll suggest you try to flash the complete stock image. With the 4.3 builds, Samsung appeared to have locked the modem tightly to the bootloader.

Related

[Q] Can a S3 be returned to stock?

Greetings,
I am very new to the sprint S3 and i have only owned it for a few weeks now. I love the phone and its a huge upgrade from what i have been using. I have rooted a couple of phones and have used custom rom's and such but never on this device. I had a lg optimus T that i rooted and flashed.
I am thinking about rooting and flashing this device to cyanogenmod ( and i think the automated installer will work from the looks of it so far anyway ) but i have seen several times over the internet that some features of the phone might not work properly after the flash. Would i be able to return the phone back to stock rom if i flash over to cyanogenmod? Mind you right now i have no way to backup the nand or factory rom.
My phone has been updated to kitkat also if that matters.
TdiGuy said:
Greetings,
I am very new to the sprint S3 and i have only owned it for a few weeks now. I love the phone and its a huge upgrade from what i have been using. I have rooted a couple of phones and have used custom rom's and such but never on this device. I had a lg optimus T that i rooted and flashed.
I am thinking about rooting and flashing this device to cyanogenmod ( and i think the automated installer will work from the looks of it so far anyway ) but i have seen several times over the internet that some features of the phone might not work properly after the flash. Would i be able to return the phone back to stock rom if i flash over to cyanogenmod? Mind you right now i have no way to backup the nand or factory rom.
My phone has been updated to kitkat also if that matters.
Click to expand...
Click to collapse
To go completely back to stock with stock recovery and everything you would use Odin. You say it has been updated to KitKat. I assume you mean stock OTA ND8 so if that is true make sure you DON'T Odin anything lower. You will be able to start over on a shiny new phone if you do because this one will be toast.
Yes, you would just use Odin on a PC to flash the stock ND8 tar file and it would be fresh as a babies bottom. Well, maybe not but it would put everything literally back to how it was when it was brand new.
http://forum.xda-developers.com/showthread.php?t=2738533
It would also wipe your internal storage, so make sure you save pics, videos and downloads off of it (move to the MicroSD card) first.
Just NEVER ever Odin anything older than ND8, or try to flash an older modem than ND8 or you'll brick your phone.
It's a great phone, especially with KitKat! Enjoy and have fun!
P.S. FYI, questions go in the Q&A section.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v2.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

[Q] 4.1.1 vulnerable to Heartbleed, update options?

Both my S3 (SGH-i747M) are still on original 4.1.1 and since they have been working wonderful for me (if it ain't broke, don't fxt it, right?)...plus I don't do much with my phones.
After reading about the Heartbleed Vulnerability in 4.1.1, I'm thinking of updating to 4.1.2 instead of of the latest 4.4.2, but before I do that, can I get confirmation that:
1) from 4.1.2, I can go back to stock 4.1.1 100% for sure using Odin
2) Once updated to 4.3 or 4.4.2, there is NO way to go back to 4.1.1 due to both 4.3 and 4.4.2 have different bootloaders ?
3) if updated to 4.4.2 and since there is no way to downgrade to 4.1.1, the other option would be to use "CyanogenMod" as the last option, correct?
Thanks.
1) Yes, you can go back to stock 4.1.1 from stock 4.1.2 using Odin. I recommend doing this so you can take advantage of the free unlock method.
2) Yes, once updated to stock 4.3 or 4.4 bootloader, you cannot go backwards. Also, you can brick your phone if you attempt to load a 4.4 modem on a 4.3 bootloader.
3) CM ROMs must support your installed bootloader and modem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
audit13 said:
3) CM ROMs must support your installed bootloader and modem.
Click to expand...
Click to collapse
Thanks audit13, you are great!:good:
For the 3) CM ROMs must support your installed bootloader and modem, I have all four Koodo 4.1.1/4.1.2/4.3/4.4.2 (pix attached), are these all OK for CM ROM?
Thanks.
Last time I checked, 4.1.2 bootloader worked fine with CM 10 and I think with CM11. Keep in mind that Cm10 had some issues with some apps and the front facing camera (never had an issue with Skype) as well as Bluetooth being flakey. Read up on it and try it out. You can always revert back to stock if it doesn't work out.
If you are concerned about Heartbleed you should check if 4.1.2 is vulnerable too. Its a pretty old build and i think we were already on 4.3 by the time it became a known vulnerability. I could be mistaken though, but you should check into it if that's a concern.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Matt_7 said:
Thanks audit13, you are great!:good:
For the 3) CM ROMs must support your installed bootloader and modem, I have all four Koodo 4.1.1/4.1.2/4.3/4.4.2 (pix attached), are these all OK for CM ROM?
Thanks.
Click to expand...
Click to collapse
Some of the newer d2lte builds may need the latest bootloader to work. You can determine which bootloaders are supported by downloading the ROM, unzipping the ROM, and open the updater script in Notepad. The first few lines of the script will list the bootloaders that are supported.

[Q] Restore stock recovery without ODIN due to broken usb port

I received the OTA for Lollipop, but I can't install it because I have a custom recovery. I need to install stock recovery, but my USB port is messed up and I can't use ODIN to flash the image. Is there a way to flash stock recovery without using ODIN or the USB port at all? Thanks!
tullman187 said:
I received the OTA for Lollipop, but I can't install it because I have a custom recovery. I need to install stock recovery, but my USB port is messed up and I can't use ODIN to flash the image. Is there a way to flash stock recovery without using ODIN or the USB port at all? Thanks!
Click to expand...
Click to collapse
Unfortunately it's not Lollipop, only a security update (still 4.4.2), I don't believe there is any other way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROMs: Wicked X & Wicked S5 Xperience
bilgerryan said:
Unfortunately it's not Lollipop, only a security update (still 4.4.2), I don't believe there is any other way.
My ROMs: Wicked X & Wicked S5 Xperience
Click to expand...
Click to collapse
Couldnt you use Chainfire's mobile odin to flash stock kernel and recovery, triangle away device status to Official, unroot via supersu app, and accept update, along after the update, follow CNexus's guide to re-root without a PC?
Or does the Knox 0x1 bit still prevent you from updating O_O?
Spark91 said:
Couldnt you use Chainfire's mobile odin to flash stock kernel and recovery, triangle away device status to Official, unroot via supersu app, and accept update, along after the update, follow CNexus's guide to re-root without a PC?
Or does the Knox 0x1 bit still prevent you from updating O_O?
Click to expand...
Click to collapse
Mobile Odin is a bad idea in this instance, high potential to brick you device trying to flash stock that way. I would honestly say spend the $45 and have one of those repair places replace the port
Ah okay, i know it is bad flashing full firmwares through mobile odin. Didnt know itd be bad doing recovery and kernel only.
Spark91 said:
Ah okay, i know it is bad flashing full firmwares through mobile odin. Didnt know itd be bad doing recovery and kernel only.
Click to expand...
Click to collapse
I'm not aware of a way to flash stock recovery without flashing the whole sheebang

Moving back to stock from Cyanogenmod

Hi all, I just dug up my old S3 and need to go back to stock. It has a CM11 nightly on there with the MK3 baseband and CWM recovery (and no Knox loaded!). Needless to say, I've been out of the loop for the past year or so and all of these threads about Odin and the newer updates have my head spinning! I want to go back to stock but also want the ability to re-root and load a different ROM later on. If I use the Odin one click here (http://forum.xda-developers.com/showthread.php?t=2755793), would this cause any problem with re-rooting, recovery, or whatever else? I was burned on my newer Droid MAXX when I updated to a firmware that couldn't be rooted so I don't want that to happen in this case if possible.
TL;DR
If I'm on Cyanogenmod with MK3 (no Knox bootloader), what's the safest way to go back to stock with the ability to re-root later?
Thanks!
dcoaster said:
Hi all, I just dug up my old S3 and need to go back to stock. It has a CM11 nightly on there with the MK3 baseband and CWM recovery (and no Knox loaded!). Needless to say, I've been out of the loop for the past year or so and all of these threads about Odin and the newer updates have my head spinning! I want to go back to stock but also want the ability to re-root and load a different ROM later on. If I use the Odin one click here (http://forum.xda-developers.com/showthread.php?t=2755793), would this cause any problem with re-rooting, recovery, or whatever else? I was burned on my newer Droid MAXX when I updated to a firmware that couldn't be rooted so I don't want that to happen in this case if possible.
TL;DR
If I'm on Cyanogenmod with MK3 (no Knox bootloader), what's the safest way to go back to stock with the ability to re-root later?
Thanks!
Click to expand...
Click to collapse
Yes, that is fine and can be easily rerooted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But if I was to use the one-click, wouldn't that load Knox and that would be permanently disabling any downgrading in the future? If I just flashed the stock 4.3 ROM and installed as normal through CWM, that should keep everything the same (bootloader,modem,etc) correct?
Yes... 4.3 has Knox by the way.
I flashed the 4.3 ROM and haven't had any issues so far. Still managed to avoid installing Knox somehow. Download mode doesn't mention anything about a warranty bit.

Samsung Galaxy S3 GSM Signal Issue

Hello all,
I have an AT&T Samsung S3 with Android 4.3. The problem I'm facing is that my mobile keeps loosing gsm signal and than I have to toggle it into Airplane mode to get it working again. this happens all the time but mostly it happens when I left mobile ideal.
Now here comes the strange part even though I'm not able to make/receive calls/sms, mobile will keep showing me full signal bars no matter what.
This is not a SIM nor signal issue as the same SIM is working fine on other mobiles without any issue
I tried hard reset, cleaned the sim slot but nothing worked.
So yesterday I decided to flash the baseband and unfortunately I flashed it with wrong firmware and after restarting my IMEI was null, but luckily after doing some google I managed to get it back .
Please check the image below for mobile details
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone please help?
Thanks so much in advance!
You could upgrade your bootloader and modem and see if that helps. I don't know if it will or will not. If you are on anything other than stock or stock based ROMs it is a good bet that it will work. If you do try, bear in mind that you can not downgrade back to MJB. Keep the bootloader and modem firmware matched, do not change only the modem.
dawgdoc said:
You could upgrade your bootloader and modem and see if that helps. I don't know if it will or will not. If you are on anything other than stock or stock based ROMs it is a good bet that it will work. If you do try, bear in mind that you can not downgrade back to MJB. Keep the bootloader and modem firmware matched, do not change only the modem.
Click to expand...
Click to collapse
Hi Thank you for your response.
Could you please guide me which bootloader and modem should I use to flash.
I think the one I currently have is the latest one for my mobile
Thanks
The MJB modem and bootloader are from Android 4.3.
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you are on the i747 with Android 4.3, as audit13 said, flash the MJB bootloader and modem. You didn't say what the incorrect firmware was that you attempted to flash. A more cautious way to proceed would be to first check what bootloader your phone reports as being installed. From the Playstore there is the "Phone Info *Samsung*" developed by vndnguyen. If you have Terminal Emulator as an installed app or you have a custom recovery with terminal emulator as an integral part, one such as TWRP, you could run this command:
Code:
getprop ro.bootloader
getprop | grep version.baseband
The second command checks modem (baseband) version.
If you should actually have the i747M you would use different bootloaders and modems than used on the i747.
If, somehow, your bootloader is newer than 4.3 you need to flash the bootloader and modem that matches the installed bootloader.

Categories

Resources