Develop Bugs

undetected sim, Unknown baseband, Rogers, d2can, cm14.1

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.

Upgrade broke the GPS

Hi all, I have a note 2 shg-i317 that was originally on Bell in Canada. It was unlocked and the aws mod done to it, I use freedom mobile, aka T-mobile in the states.
I was running a Rom for the past 3 years Slimfast 4.4 and liked it. I had tried Nugat on another phone, thought I would try the [ROM][7.1.2][OFFICIAL] LineageOS for N7105
I did the upgrade, broke the root, could not get a few things working, so I decided to restore the Slimfast backup I had just made (complete including modem etc) and everything works except the GPS.
GPS for me is huge, I use it a lot. I cannot lock on to 1 satellite now. Before i was able to lock onto a minimum of 16 in about 30-45 seconds, if outside.
I really dont care if I can get to 7.1 at the moment. I need my GPS back - any troublshooting for getting GPS to work on this phone?
James

I would try to flash the original stock for your phone and country from sammobile. com
Gps should work normaly then. If not your hardware is broken. If it works you can always flash your data back from your Slimfast rom.
Verstuurd vanaf mijn SM-N910C met Tapatalk

Crap, I am posting here, because I did it again. Again not sure how. I tried to run Reserection, and I guess that messed up the GPS.
To put the original stock rom on.. I have to do that through ODIN? I dont remember how I fixed this last year.. Sorry.
Hope somone can help I need the GPS.
James
ps. Used odin 3.09 to flash the original rom... still no GPS

You flashed the latest 4.4.2 room?

audit13 said:
You flashed the latest 4.4.2 room?
Click to expand...
Click to collapse
The Rom that I flashed to try and restore the GPS was I317MVLUDNF1_I317MOYADNF1_BMC (mine was an originally BELL phone)
But that did not repair the GPS from me flashing resurection.. I THINK did it. I flashed an android 6 and an android 7 rom. (Mokee) but tried to go back to my Slimfast.. and the GPS was now broken.
Basically what I did a year ago.. somehow I fixed it then.. but cannot remember at all how I did it.
James

The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.

audit13 said:
The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.
Click to expand...
Click to collapse
Do you mean boot up the rom.. run the reset in the rom? or flash.. - load TWRP back in.. WIPE.. then FLASH again with odin?
Thanks for helping btw.
James

I have backups (complete all partitions) of my rom.. Slimfast 4.4 from 2-3 days ago.. when I tried this. SO.. if I can get the Factory rom to restore the GPS.. how can I restore the backup.. I saw somewhere that the EFS partition could be left out and that might help? dont restore the modem? how??
James

I meant flash with Odin, boot into stock recovery, factory reset, flash again with Odin, boot into stock recovery, factory reset, and boot into the stock ROM.

Nope, still no GPS lock.. I have the flashing circle (always had) and it will not lock.. I read about where people go into a service mode and rebuild the NV? .. I assume this is something that Mokee or Reserection did.. not sure how.
Any other ideas?
James

what about using Odin or TWRP to put different modems in? does the modem effect the GPS?
tried this.. does not seem to. grrrrr wish I knew how I fixed this.
James

I assume there are no loose wires. Does it get a lock when using wifi? Not sure what else to suggest.
Not sure about rebuilding NV.

No.. I broke it with playing with custom roms.. Liniage was last year.. I did not try that this year.. but tried both android 6 reserection and android 7 Mokee.. and I am pretty sure they messed it up.. I am also pretty sure there was something I did .. easy like load an old STOCK rom and it fixed it.. I was then able to put my slimfast 4.4 back over it and it was fine. Unfortunatly .. not enough people still using this device.. I will have to have patience I guess.
James

So I have tried differenct stock roms, but I think the issue is ODIN will not restore code from a rom image that is HARDWARE based. I wanted to use Samsung smartswitch but they disabled the part of it that allowed you to factory reset the phone, this seemed to work for several people. Many have also reported entering a code and going into a service mode.. there you can do to a menu that will rebuild hardware modules back to default. But I have not been able to get into that mode because it seems to be a touchwiz only option, and I cannot find a factory rom that is touchwiz based for this model.
What needs to be done is a true FACTORY ROM image.. that would revert all software and hardware back to original, but I cannot seem to find that anywhere.
James

The only factory roms that I know of come from places like sammobile.com and they are all based on TouchWiz which is Samsung's launcher.

So guess what? put Ressurection back on.. and the GPS is back.
I cannot get it to work in any KitKat based rom.. but now anything Marshmellow up.. works.. HMMMMMM
James

sim card not working oreo/noughat

hi i have had the pleasure of using the developer oreo img and enjoyed it,but decided to reflash stock noughat img
until the official oreo comes out.heres where my issue started,after a successful flash and start up,my sim no
longer shows as inserted,i even tried a restore of my noughat back up.the only way my sim will work nowis with the
oreo stock img reflashed..anyone else have this isssue

Are you sure you flashed all the files included in the Nougat fastboot package zip? There must be an image called 'modem' and anoter 'dsp' which should take care of that.
Try reflashing the Nougat image once again.

I will try again

Having the same exact issue
Flashing the MR3 factory image results in no SIM card, same with fkashing MR1 @TheCrazyLex
EDIT: reflashed again the next day and it's now working....ugh annoying

Had exactly the same issue. Although on initial boot back to Nougat, everything worked fine.
It was only after a restart or two the SIM was then undetected.
I'm flashing stock Nougat again just now, hopefully that resolves it for me too.
EDIT. Ok I've now tried flashing multiple images, they all flash successfully and boot successfully, but none of them are detecting a SIM card.... any ideas anyone?
EDITS AGAIN: It would appear now working after flashing Oreo again, then back to Nougat. Very odd....
I want to lock the bootloader again, which is how I ended up in this mess, so I'm now flashing latest Global ROM again, rebooting and then attempting to lock the bootloader again.
I shall update with results.

any update in the same boat

I'm still having same issues,I'm just using Oreo which is working really well.only downfall I noticed is tethering doesn't seem to be working on it

Are you running the right image as Razer and Three have their own build so wanted to point this out as ThreeUK may not work right with the Razer build. i Remeber them saying something about making sure you use the right build

UPDATE - if anyone is having this issue.
--Take the Oreo preview and flash_all.bat via bootloader
--Let it boot and get in to Android just so you can enable debugging via dev options
--reboot to bootloader and flash_all.bat with the latest Three or Global image
--Again let it boot and enable debugging again
--Now reboot to bootloader, and do BOTH the following in fastboot:
---- fastboot flashing lock_critical
---- let it reboot and go back to bootloader again and perform the next lock
---- fastboot flashing lock
Once finally back in, only then did I have a locked bootloader + working SIM card.
Hope this helps someone.

Locking the bootloader doesn't fix things lol. I was on Oreo yesterday and flashed back to nougat and had signal and relocked the bootloader then 10 minutes later .y phone rebooted and lost sim. Only was to get it back was flashing Oreo then booting then flashing nougat mr1 and got my sim back. Then I locked bootloader and took the ota and now I'm back to normal and can take otas again

This is such a weird issue. like for instance I went back to MR1 from Oreo and had signal but when I picked the bootloader and ota to MR3 it was gone.then just unlocked bootloader flashed MR3 still nothing. So went back to Oreo and it worked and then flashed MR1 again and randomly worked even after the ota to MR3
So absolutely random.

hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too

SIM card issue
Hey @parky169, @Roxas598, @linuxct, @kickassdave, @joemossjr
Thanks for posting about this issue that you saw about the SIM not being detected. Our engineers would like to learn more about this and EXACTLY what happened. Can you please PM me with the details:
What carrier you guys are on?
What was the previous build you were on before you flashed the Oreo developer build?
Can you please walk me through EXACTLY what happened that caused the SIM to go undetected
Were any APNs changed prior/after?
Were any changes made to the files or phone (rooted, custom ROM, etc.) prior to flashing the O build?
How did you resolve this situation? Is this repeatable?
Thanks again for testing the developer build! Please PM me if you run into any more issues!
Best,
Khanger

parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Same issue as the rest. I wonder if this will work with the Oreo OTA modem img, I'm gonna give it a shot. I will report back
EDIT: Well there is probably no reason it shouldn't have worked I would assume the modem images are identical in 8.1 Dev and 8.1 OTA, but it does work by putting the 8.1 MR0 OTA modem img in the 7.1 MR3 and flashing. Honestly i ws too lazy and didn't want to wait for the Dev image to download and I already had a copy of the 8.1 OTA ON MY pc.

Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!

​
Jonlines94 said:
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Click to expand...
Click to collapse
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?

NoXXX said:
​I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
Click to expand...
Click to collapse
Any update on this? I am in the same boat after standard OTA update. Can not save apns either. (at&t)

Thanks!!!
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Thanks for finding a fix. I was worried my phone was jacked up. I was having the same issue. I wanted to downgrade from Oreo since there is an issue with HDMI not having audio. I got signal now whoooo

XT1789-04 Restore Baseband

I am trying to revive my old z2 force t-mo edition. It basically crashed after an OTA and lost baseband and IMEI and i threw in in a drawer for months.
I tried flashing newest firmware-nothing, i tried unlocking bootloader and flashing second new firmware-nothing. The device does turn on--just no data, no wifi etc. I'm not too familiar with blankflashing, is this something i can even do with a device that turns on? Will that even work? Moto assistant says they are "unable to verify a match" when i pick repair device and select XT1789-04. Does anyone else have anything else to try? I have not rooted, have not installed pie firmware or anything. Long story short, im now in need of a working phone so i just want to get this working again!

Same boat as you! Have tried everything on here. What's a blank flash?

Have u tried this?https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
I was in your situation and this fixed everything (in my case 27.1.5 didn't work, 27.1.7 worked)
Just remember to do a factory reset in stock recovery, after flashing. Without it, I had bootlops

Dany XP said:
Have u tried this?https://forum.xda-developers.com/z2...m-tmo-z2-force-27-1-5-flashall-march-t3917070
I was in your situation and this fixed everything (in my case 27.1.5 didn't work, 27.1.7 worked)
Just remember to do a factory reset in stock recovery, after flashing. Without it, I had bootlops
Click to expand...
Click to collapse
Had the same issue with baseband unknown/no wifi/no LTE, the 27.1.7 flashall fixed it for me

Empty IMEI

Hi
Hoping someone here might be able to help as somehow I’ve messed up my IMEI.
I flashed alexndr stock rom over my stock rom with the force XEU option enabled as my default CSC is H3G. Everything worked fine but was failing safety net so decided to flash back to my stock rom with odin but now my IMEI is empty.
I have the EFS backup that Alexandra rom installer created but flashing this doesn’t seem to solve the problem and what’s strange is if I flash alexndr rom back onto my phone my IMEI comes back and everything works normally but with the stock rom its blank.
Anyone know how to fix it?
Thanks

andrewtjb said:
Hi
Hoping someone here might be able to help as somehow I’ve messed up my IMEI.
I flashed alexndr stock rom over my stock rom with the force XEU option enabled as my default CSC is H3G. Everything worked fine but was failing safety net so decided to flash back to my stock rom with odin but now my IMEI is empty.
I have the EFS backup that Alexandra rom installer created but flashing this doesn’t seem to solve the problem and what’s strange is if I flash alexndr rom back onto my phone my IMEI comes back and everything works normally but with the stock rom its blank.
Anyone know how to fix it?
Thanks
Click to expand...
Click to collapse
In the past is was mismatched baseband. But I've never had the issue so I dont know for sure

TheMadScientist said:
In the past is was mismatched baseband. But I've never had the issue so I dont know for sure
Click to expand...
Click to collapse
Thanks
I managed to solve it was definitely a baseband issue. It looks like when I flashed the alexandr rom it updated the baseband to DTD7 where as my my carrier firmware I was trying to flash back to was still DTC5.
I've flashed DTD7 firmware now and everything's back to working normally.