[This isn't a request for help, I managed to muddle my way through it, but the info needed seems to be scattered and disjointed, so I thought I'd post it here for others.]
Started with a AT&T Galaxy S III phone running a beta version of CM10 (which could never get OTAs). Wanted to get to a stable or more recent version of CM. This phone is referred to as a SGH-i747 or d2att.
Trial and error:
1st Attempt - Flashed TWRP 3.0.2, flashed CM12.1 release, phone boots gets to starting applications and then dies (poweroff).
2nd Attempt - Flashed CM10.3.1 -> fails to flash ro.bootloader does not match expected values
3rd Attempt - Flashed CM10.1 -> fails to flash ro.bootloader does not match expected values
4th Attempt - Flashed CM10.0 -> Works
So, what's going on?
ro.bootloader is the baseband (cellular radio firmware). My phone had "I747UCDLK3", CM10.1 and require Jellybean compatible radio baseband... CM10.1 advise are trying to tell you that your baseband is too old (ro.bootloader is a misleading name for your baseband). In Android you can see your baseband under "About Phone" in settings, or by opening a terminal and typing "getprop ro.bootloader". In TWRP, you can open the terminal and type "getprop ro.bootloader" to get the value.
Fixing it:
I tried lots of different flashes until I found one that uses JOdin3 to flash the radio. The links for JOdin3 are all long dead, but someone mirrored the JAR files here: http://3of5.com/builds.casual-dev.com/files/JOdin3/. In any case, this got CM to see my baseband as I747UCALEM, however TWRP still saw my baseband as I747UCDLK3. This update was enough to get CM10.3.1 running with cellular signal (did not test calling).
Next thing was applying CM12.1, which flashed and started this time, however "Sim card is missing" was reported. CM12.1 + require still newer baseband firmware to work. I was able to find a list of baseband/radio firmwares here: http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772, the link there (https://www.androidfilehost.com/?w=files&flid=10522) allows you to download flashable packages. I flashed the I747UCUEMJB baseband/radio firmware and then reflashed CM13.0 nightly and Open GApps using TWRP so I could give the phone to my father.
With I747UCUEMJB, CM13 boots and recognizes the sim card. Once we are no longer roaming we'll test to see if further baseband firmware updates are necessary.
Related
What about us Canadian? Im on the most recent baseband VLDDL1 and it won't flash
Rephrase.
Some people are getting ramdom reboots in CM10.1 since they switched to kernel 3.4. Yesterday, +Steve Kondik suggested to update the firmware (RPM, TZ, etc) in this G+ thread to correct the random reboots issue.
https://plus.google.com/104293897496940858109/posts/S8gAfP8NKQT"]https://plus.google.com/104293897496940858109/posts/S8gAfP8NKQT
The way to update the Trusted Zone as well as the Resource and Power Management is to odin the latest stock firmware and then getting back to CM. To make sure people don't get random reboots, the latest nightly now checks the baseband version and fails it it's too old. The problem is it checks only for TMO basebands numbers and not canadian basebands numbers, so we cannot flash CM 10.1 nightlies anymore.
Thanks! Download the newest nightly and edit the updater script to remove the bootloader assert, or add your own to it.
After I flashed CM11 SNAPSHOT M5 on my Brazilian Optimus G E977 model (firmware version E97710d), I faced several crashes with "Subsystem crash" BSOD, with Demigod Handler issue or something like that . Several reboots later, the crashes stopped, however the mobile network was not working. Checked IMEI on status menu it was reported as null. I have a backup of EFS partition performed by FreeGee.
I tried all the tools available that I've found
1-flash a zip package containing the the 3 backed up .img files in CWM Recovery mode;
2-downloaded cwm-lgog_e977-brazil_10b-modem.zip from the EFS and MODEM backup/restore tutorial and flashed the modem zip package (replacing the modem.img with the one from my phone extracted with adb) ;
3-flashing stock firmware;
But still null IMEI and no network signal. Is there anything else I can try? Maybe if I get a specific file from another E977 model?
ksio89 said:
After I flashed CM11 SNAPSHOT M5 on my Brazilian Optimus G E977 model (firmware version E97710d), I faced several crashes with "Subsystem crash" BSOD, with Demigod Handler issue or something like that . Several reboots later, the crashes stopped, however the mobile network was not working. Checked IMEI on status menu it was reported as null. I have a backup of EFS partition performed by FreeGee.
I tried all the tools available that I've found
1-flash a zip package containing the the 3 backed up .img files in CWM Recovery mode;
2-downloaded cwm-lgog_e977-brazil_10b-modem.zip from the EFS and MODEM backup/restore tutorial and flashed the modem zip package (replacing the modem.img with the one from my phone extracted with adb) ;
3-flashing stock firmware;
But still null IMEI and no network signal. Is there anything else I can try? Maybe if I get a specific file from another E977 model?
Click to expand...
Click to collapse
my friend can u us any custom rom ?? if u have external modem error (subsystem crash error ) say me i have one idea
Yeah, I flashed stock firmware and performed a factory reset, it was clean. Then I proceed to root, install FreeGee, BusyBox and then CWM 6.0.4.7 and then flashed the CM11 M5 ROM, has been stable for a while, then it crashed. This is the report:
"DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)"
BTW, I performed a backup of EFS partition 3 img files with FreeGee.
I had to flash stock firmware once more due to crashing, it's completely unstable with CM11 M5, I'll flash CM11 M4 which was perfectly fine and see if it becomes stable.
EDIT: still crashing with CM11 M4, the latest CM ROM really screwed my phone.
EDIT 2: sent my phone to local repair service and the main board was replaced, with a new IMEI. It seems there was indeed a hardware issue. I had a SIM card which I had it adapted into microSIM format but it wasn't recognized by my OG. After the motherboard replacement, it's being recognized now. I have backed up EFS partitions and modem packages following the tutorials on Q&A. But I'm enjoying stock ROM, it has some nice features which I didn't find in CM11, I'll stick with it for a while. I don't believe there will be any more issues regarding CM11 though.
ksio89 said:
Yeah, I flashed stock firmware and performed a factory reset, it was clean. Then I proceed to root, install FreeGee, BusyBox and then CWM 6.0.4.7 and then flashed the CM11 M5 ROM, has been stable for a while, then it crashed. This is the report:
"DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)"
BTW, I performed a backup of EFS partition 3 img files with FreeGee.
I had to flash stock firmware once more due to crashing, it's completely unstable with CM11 M5, I'll flash CM11 M4 which was perfectly fine and see if it becomes stable.
EDIT: still crashing with CM11 M4, the latest CM ROM really screwed my phone.
EDIT 2: sent my phone to local repair service and the main board was replaced, with a new IMEI. It seems there was indeed a hardware issue. I had a SIM card which I had it adapted into microSIM format but it wasn't recognized by my OG. After the motherboard replacement, it's being recognized now. I have backed up EFS partitions and modem packages following the tutorials on Q&A. But I'm enjoying stock ROM, it has some nice features which I didn't find in CM11, I'll stick with it for a while. I don't believe there will be any more issues regarding CM11 though.
Click to expand...
Click to collapse
my friend .hey u here ? u have external moder error now ?
i have one answer this
No, mate, no errors after the mobo replacement. One of these days I installed CM11 M6 and there were no crashes or errors related to modem. As I said, it was a hardware issue, from what I read, the most probable cause was a not complete functional power state, which caused the tension to drop excessiely, crashing the OS, corrupting the EFS/modem software and wiping the phone IMEI.
I recently started using my AT&T Galaxy S3 again and wanted to make sure that everything was up-to-date on it. I did a clean install of everything and cleared my cache and dalvik first beforehand. I updated the following:
CyanogenMod to 11-20141112-SNAPSHOT-M12-d2lte
GApps to kk-20140606
Baseband Version to I747UCUEMJB
Now, seemingly randomly, all audio on my device will stop working; from Apollo, to YouTube, to system sounds and ringtones. Rebooting the phone solves this issue temporarily. However, when I plug my headphones in, that seems to be the catalyst for the issue. Once I have them seated into the jack, all sound then stops and will not resume, even if I remove them, until I reboot. Stranger still, is that if I am playing music and THEN plug in my headphones, it will continue to work as normal.
I had a stable nandroid backup of CM10 that I had been running for the longest time that I reverted to, but the problem persisted.
Somehow, it seems to be related to when I updated the baseband version. I originally flashed CM and GApps cleanly only to find I had no data connection. After some digging, it seemed that newer versions of CM were no compatible with the baseband I was using which is when I proceeded to get the latest one and flash it. All of these strange issues with audio started happening after that. I tried flashing a couple of older baseband versions, but that did not alleviate the problem.
Anybody have any suggestions? I am tearing my hair out trying to get to the bottom of this
NinjaBurg3r said:
...I updated the following:
CyanogenMod to 11-20141112-SNAPSHOT-M12-d2lte
GApps to kk-20140606
Baseband Version to I747UCUEMJB
....
Somehow, it seems to be related to when I updated the baseband version....
After some digging, it seemed that newer versions of CM were no compatible with the baseband I was using which is when I proceeded to get the latest one and flash it. All of these strange issues with audio started happening after that. I tried flashing a couple of older baseband versions, but that did not alleviate the problem.
Anybody have any suggestions? I am tearing my hair out trying to get to the bottom of this
Click to expand...
Click to collapse
What baseband (modem) and bootloader do you have on your phone? You say that you upgraded to MJB, but then later say that you flashed the latest baseband, which is NJ1 for the i747. Were you flashing only basebands or both bootloader and basebands?
What you should do next depends on the current bootloader and modem, and if they are the same version.
Once this device reaches the MJB bootloader you can no longer downgrade the bootloader with risking bricking the device. Once you reach either of the 4.4.2 bootloader and modem pairs you risk bricking the phone if the versions are not the same.
Check before going any further. Either use the Phone Info -- Samsung app from the Playstore, by vndnguyen. Or use terminal emulator commands. There is the chance that some of the flashing did not take and your phone is not at the version of either bootloader or baseband that you think it is.
Code:
getprop ro.bootloader
getprop | grep version.baseband
I had this same sound problem on multiple CM11 based KitKat ROMs. I don't recall whether it got fixed on KitKat or not; I've since switched to lollipop ROMs and haven't seen this problem since. You might try flashing a more recent CM11 nightly to see if the audio thing has been fixed. You'll find the most recent builds under d2att since the d2's have been de-unified.
If you choose to give lollipop a try you will probably need to get your firmware up to NE4 or NJ1. Early on some people were running lollipop on MJB, but I don't believe that is still the case.
I started with unlocking bootloader using minimal ABD and fastboot. Once done my device went into bootloop.Then I download the stock frimware from sony's software called xperifirm which said that it is 15.5.A.1.5 but was 15.5.A.0.18.And wanted me to update using my laptop. tried doing that to but every time a error 12 came up.then i found someone's thread with .ftf file for 15.5.A.1.5 that to generic_IN. flashed it and then booted into it,got network working.then updated to CM13 and still it says sim card not detected.then flashed the same ftf file checked for software update and this is what i got:
Settings>about phone>bulid number:15.5.A.1.5
Update center>system::15.5.A.1.5 Ready to download 104.4MB
still downloaded it and tried to install.but,while installition when phone goes into recvery mode the screen stared blinking and the installition failed .then flashed cwm recovery and tried again but this is what comes up:
CWM-based Recovery v6.0.4.9
E:invalid command argument
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
Install Untrusted Package?
THIS CAN NOT BE UNDONE
- Yes - Install untrusted zip
E:Can't open /cache/recovery/fota/update_package(bad)
Installation aborted.
Rebooting. . .
Note:bold text is recovery log
pls someone help me out I want cm 13 with network working (only one sim working is ok for me but two will be better)
just the same problem
Hi,
I came here looking for a solution to this same problem. I have a C2004, and I have to admit I didn't really know what I was doing, but at this point I'm sure I've followed the right steps at least once. I only followed the official wiki.
I
- unlocked the bootloader
- flashed CM13
- booted, no GApps
- installed GApps (phone unusable due to popups)
- Re-flashed CM13 and GApps before first boot, phone works beautifully but I did all my tests without the SIM, when I rebooted to insert the SIM I noticed the phone was not detecting it. Eventually I found a post detailing what the problem was: CM13 required a previous Android 4.3, but my phone was on an older version.
So I downloaded the radio firmware and the image of the stock Sony OS on 4.3:
- wiped all data
- flashed radio firmware
- restored OS backup with CWM
- booted: SIM card is detected, no idea whether dual sim works because I'm not interested on it, GPS doesn't work
- wiped all data
- flashed CM13 again, still no network.
I repeated the above process several times, always get a working stock OS (except for GPS) but never got CM13 to connect to the mobile network. So, right now I'm stuck on that Sony OS, because it even detects an OS upgrade but can't install it because CWM doesn't know how to handle the upgrade package.
I'd like to know if it is possible to get a copy of the original recovery partition, so that official upgrade can be installed.
Or, better, to get CM13 working, somehow it seems my issue is not common because everything I find on the web points to the same above steps...
After installing CM13 , Did u flash the dual sim patch?
Steps :
First install a custom recovery,
then wipe/format everything
install cm13,dual sim patch and gapps(if u need) in one go because after that your recovery will be replaced by the cyanogenmod recovery and you will have to reinstall another recovery.
I don't know where, but I read that was not needed anymore, and that idea was fixed in my head. Maybe I mixed comments about the dual patch with comments about the radio patch, I can't recall at this point.
Anyway, patching that additional zip fixed the network access for me. Let's just see if its get fixed for the OP as well
Thanks!
You need to flash a patch for enabling dual sim, without it you will get no network ... This is because the official cyanogenmod gives no support for the xperia m dual and so an extra patch has to be flashed before you can really access the sim card's network! hope this helps ! so go on flash the cm13 and then the patch and share the results!!
I recently installed cm14.1 on a Rogers d2can phone and I got unknown baseband and sim card stopped working. I tried flashing different modems which made the situation worse as now even old cm11 roms show unknown baseband.
Can someone please tell me where I can download modem zip file that works for Rogers and for cm14.1?
I recommend flashing the latest KK stock ROM from sammobile.com which will restore your phone back to stock and ensure the bootloader and modem/baseband are matched. After flashing stock and confirming that the imei is correct, then flash twrp, cm14.1, and gapps.
I was downloading from sammobile.com very slow and the download was interrupted in the middle. I will try again later.
Is there a better site to download firmware from?
So I downloaded it and flashed using odin. Flashing took a while but it passed. The phone got stuck on bootloop though.
So I booted to stock recovery and performed a factory reset. Booted again. Now it works!
I'm going to stay on Touchwiz 4.4.2 for a while.
Glad you got it working.
I would not call "staying on Touchwiz 4.4.2", "working" more like opening yourself to a long list of known exploits.
Others are having the same issue (cyanogenmod is dead so I removed the link, hope LineageOS fixes the issue some day.)
Using the last good CM-13 build is probably the best for now.
sim not provision ed MM#2...... easiest fix ....please n thanks;;;;
We'll need more information in order to help solve the sim problem like model #, ROM, etc.