Database Users

[Q] Signal dead when phone is in sleep mode

Hi guys,
I have a problem since the first 4.3 release. When the phone is in sleep mode, the cellular signal dead and i must turn on the airplane mode and turn off it. It's a very fastidious problem, what can i do?
GT-9505 with XViSiON Rom and KT Kernel.
PS: Sorry for my english

anyone?

I have the same problem.
I have even tried different Android 4.3 ROM's to my GT-I9505 where all lost it's GSM signal when i'm setting my phone into sleep mode.
I though for some time that my phone was faulty somewhere here. But to confirm that this was only happening in Android 4.3, i installed FoxHound v2.0 ROM earlier today witch was the latest Android 4.2.2 ROM of that ROM. Here i don't have that problem anylonger.
So what's going on with the Android 4.3 ROM's. Does anyone have any clues?

must be the modem, i had a similar problem back when i was on the S3 and it was related to that
Sent from my GT-I9500 using Tapatalk

happy to know I'm not the only one and happy to know that the problem is only in 4.3. can I flash the 4.2.2 modem on 4.3 rom? or it isn't compatible?
Thanks for reply and sorry for my English

You probably have flashed/installed too good modification
Try to reinstall software, do restore from backup (if you have) or try to google it... No idea why.. I understand it happens for wifi, but not for "mobile signal"

Ok I flashed a MH8 modem and for now it's ok, today and tomorrow i test if it work.

Ok, i have now flashed the XXUEMK8 modem by doing the instructions under here:
Originally Posted by lambstone
Ok it worked.
If anyone else is having issues with the baseband not changing, do this.
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
The only thing i did differently was to use the Odin3 v3.0.9 application instead. You can download this here or here.
You can find all of the modems you need here: http://forum.xda-developers.com/showthread.php?t=2192025
Now the signals isn't dropping anymore :laugh:
So there you have my confirmation on this. So anyone who have the same problem should just do the same by installing the newest modem you find in the link over.

Tom-Helge said:
Ok, i have now flashed the XXUEMK8 modem by doing the instructions under here:
Originally Posted by lambstone
Ok it worked.
If anyone else is having issues with the baseband not changing, do this.
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
The only thing i did differently was to use the Odin3 v3.0.9 application instead. You can download this here or here.
You can find all of the modems you need here: http://forum.xda-developers.com/showthread.php?t=2192025
Now the signals isn't dropping anymore :laugh:
So there you have my confirmation on this. So anyone who have the same problem should just do the same http://forum.xda-developers.com/showthread.php?t=2192025
Click to expand...
Click to collapse
Yes it work, maybe the MK8 modem is fixed for this problem... thanks a lot ^_^
I hope this thread help who have this problem

No Signal after 4.4.2 update

Hey Guys,
Today I updated my i9505 from Cynogen Mod 10.3.1 to the new "[AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1" by Jamal, but I read that you needed to update to the leaked 4.4.2 before flashing so that the modem and bits are upto date before flashing any 4.4.2 ROMs or else you could end up with no wifi after flashing.
So I followed these instructions to flash the leaked 4.4.2:
INSTRUCTIONS
- Extract (unzip) the firmware file
- Download Odin3 v3.09 (From here or here)
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add AP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to AP
- Add BL_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to BL
- Add CP_I9505XXUFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAFNA5_373648_REV06_user_low_ship_MULTI_CERT.tar.md5 to CSC
- Make sure re-partition is NOT ticked
- Click start button, sit back and wait a few minutes.
Which all went well but I couldn't get Wifi after flashing, and (probably not important) but the default language it choose during the setup was Dutch??? Seeing as I couldnt get the wifi to enable I decided to flash Philz Touch Recovery v6 and then put Jamal's "S4 Google Edition - Final-R1.1" by putting it onto the SD card and flashing through Philz recovery.
Flashing went without a problem.... only thing is now I cant get Vodafone (UK) signal 80% of the time, the other 20% I do get signal and can make calls, just seems strange as previously 80% I WOULD get signal!
Did I do something wrong? I had a really bad feeling that flashing the CP, BL and CSC has somehow messed things up......please help!

Same problem, bump.

ColdIce23 said:
Same problem, bump.
Click to expand...
Click to collapse
I just fixed the problem, ColdIce23, check your Baseband Version under Settings > About Device, I bet yours is still set to the original baseband version like mine was...
1) Re-Download the Baseband for the leaked 4.4.2 rom (Here)
2) Open Odin 3.09 and do the following:
Ok it worked.
If anyone else is having issues with the baseband not changing, do this.
Use Odin v3.04
Untick Autoreboot
Flash modem
Reboot once again into Download Mode using (Vol Down plus Home button combi)
Flash Modem once more
Once done,unplug then reboot device manually.
If this doesn't work, try repeating the flash process again while rebooting manually and with auto-reboot option turned off.
Click to expand...
Click to collapse
Now I have FULL SIGNAL! .....so far..... will report back once I have left work but this is a good sign as I had no signal what-so-ever 5 minutes ago!

Flasing a 4.4.2 Modem works well with the Kit Kat based roms. Two to choose from NA1 or NA5, depending on what bootloader your on flash the appropriate modem files.
I've got NA5 on the 4.4.2 GE Rom with Three and no signal issues as of yet.

treesmoker said:
I just fixed the problem, ColdIce23, check your Baseband Version under Settings > About Device, I bet yours is still set to the original baseband version like mine was...
1) Re-Download the Baseband for the leaked 4.4.2 rom (Here)
2) Open Odin 3.09 and do the following:
Now I have FULL SIGNAL! .....so far..... will report back once I have left work but this is a good sign as I had no signal what-so-ever 5 minutes ago!
Click to expand...
Click to collapse
My I9505 baseband version is I9505XXUFNA5. Is not it the updated one?

kamrul.auntu said:
My I9505 baseband version is I9505XXUFNA5. Is not it the updated one?
Click to expand...
Click to collapse
Yes you the latest baseband available.

treesmoker said:
Hey Guys,
Today I updated my i9505 from Cynogen Mod 10.3.1 to the new "[AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1" by Jamal, but I read that you needed to update to the leaked 4.4.2 before flashing so that the modem and bits are upto date before flashing any 4.4.2 ROMs or else you could end up with no wifi after flashing.
/QUOTE]
I think u missunderstood something. For the Kitkat Google Edition u do not have to flash the leak before. Its only for the Samsung Touchwiz Version of Kitkat
tapatalked by an Echoenian
Click to expand...
Click to collapse

nikzDHD said:
Flasing a 4.4.2 Modem works well with the Kit Kat based roms. Two to choose from NA1 or NA5, depending on what bootloader your on flash the appropriate modem files.
I've got NA5 on the 4.4.2 GE Rom with Three and no signal issues as of yet.
Click to expand...
Click to collapse
I flashed the NA5 modem which seems to have failed the first time round, as it didnt actually change the baseband version in settings. Since flashing a second time (when it actual flashed properly) I now have full signal...... but I have another problem now:
When I click the dailer and select a person to call, the screen goes black and I dont see/hear any indication that a call has initiated. I tried with my wife and her phone rings and she can answer the call, but my screen is still black with no sound....
I have tried wiping data / davlik / cache and installing the rom from scratch, but I still get the same issue?
UPDATE:
Right so I just flashed CM11 as a test, and still can't make calls, so obviously not a ROM fault..... does the BL, CP or CSC have anything to do with the making calls procress?

I've got a similar issue.
I've got a M919V running Jamal's 4.3 GPE rom, but after flashing Jamal's 4.4.2 GPE i get no signal. After going into settings and selecting network the signal lasts, but after the screen goes off signal is once again lost.
Is there a procedure to follow that will fix this? This is found when when flashing many 4.4 roms.
-Thanks

Well, I get signal when I'm near a cell tower...
No changes tho. Still same problem.

Hi guys,
I'm wondering if you have resolved your modem problems?
I flashed to Jamal's 4.4.2 version 1.2 and I don't have a signal now.
I flashed the modem to NA5 but styill no signal. Also I can't even check my CSC using *#1234# as "Mobile network not available"
Any suggestions?
Thanks.

Hi Duskin,
For me, I think it's releated to the phone itself as I got a screen replacement. I haven't solved the problem yet because I got to get back to the store where I got my screen replaced.
Sent from my LG-P880 using Tapatalk

[Q] Upgrading to 4.4 modem

I've upgrade my N9005 to 4.4.2, it's still on the 4.3 modem though, so I tried updating using the standalone NA2 modem image via Odin, looks like it flashed ok, boot into the OS, still says baseband is MJ7.
Flashed the entire 2.2GB XEO release of 4.4.2 which has the modem in it, same thing, OS flashes fine, no errors but once in the OS, baseband is still MJ7.
Is there some trick to getting this flashed correctly?

knightnz said:
I've upgrade my N9005 to 4.4.2, it's still on the 4.3 modem though, so I tried updating using the standalone NA2 modem image via Odin, looks like it flashed ok, boot into the OS, still says baseband is MJ7.
Flashed the entire 2.2GB XEO release of 4.4.2 which has the modem in it, same thing, OS flashes fine, no errors but once in the OS, baseband is still MJ7.
Is there some trick to getting this flashed correctly?
Click to expand...
Click to collapse
With modems you have to flash it once, reboot then flash it again once or twice more. Not sure why but that's apparently the correct way.

Hmm, tried Download mode --> Flash, immediately boot back into Download mode --> Flash, boot into OS, reboot into Download mode & flash again. Still no joy. Another couple of reboots & flashes for good measure, no dice.
Can't imagine it'd make a difference, but it there a CWM flashable version of the NA2 modem somewhere? Can't seem to find one anywhere, probably because it's a brick-maker?
Everything seems to work perfectly happily on the older baseband, maybe I should just leave well enough alone. If they've somehow fixed the woeful Compass & GPS performance with the new baseband (is it even related?) then that would interest me greatly however.

knightnz said:
Hmm, tried Download mode --> Flash, immediately boot back into Download mode --> Flash, boot into OS, reboot into Download mode & flash again. Still no joy. Another couple of reboots & flashes for good measure, no dice.
Can't imagine it'd make a difference, but it there a CWM flashable version of the NA2 modem somewhere? Can't seem to find one anywhere, probably because it's a brick-maker?
Everything seems to work perfectly happily on the older baseband, maybe I should just leave well enough alone. If they've somehow fixed the woeful Compass & GPS performance with the new baseband (is it even related?) then that would interest me greatly however.
Click to expand...
Click to collapse
Yup a brickmaker indeed, modems can be a real ballache and can destroy your phone if they mess up, If it works fine I'd suggest leaving it, AFAIK the GPS and Compass issue has not been fixed.

I had another crack at it, still no dice with Odin, but I used TriangleAway to reset the Binary status to "official" (took a couple of tries), then used MobileOdin to flash both modem's (Presumably one is the .img and other the .bin from the .tar.md5 file) and it finally worked!
Interesting that it worked with Mobile but not the desktop client.
Can't tell any actual difference so far of course, but maybe it does something beneficial versus the MJ baseband.

knightnz said:
I had another crack at it, still no dice with Odin, but I used TriangleAway to reset the Binary status to "official" (took a couple of tries), then used MobileOdin to flash both modem's (Presumably one is the .img and other the .bin from the .tar.md5 file) and it finally worked!
Interesting that it worked with Mobile but not the desktop client.
Can't tell any actual difference so far of course, but maybe it does something beneficial versus the MJ baseband.
Click to expand...
Click to collapse
I have got the same issue. I'm on KitKat 4.4.2 and baseband is still MJ7. Phone seems working smoothly.

Does that means you can downgrade to 4.3?

Rosli59564 said:
Does that means you can downgrade to 4.3?
Click to expand...
Click to collapse
The baseband is the modem, not the bootloader. It's the bootloader that gets you "stuck" on 4.4

Recovering from FRP Lock, did I brick my phone?

Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....

Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.

:( How can I recover this i337m in 2019

I have lost the phone that has been working for ages. I am broke atm. Please help I need to use my phone. I was trying to get my radio to work again because I lost data a couple weeks back. So I have spent more time than I even should have for this trying to fix it.
I have run Odin 3.07 with
lineage-15.1-20190210-UNOFFICIAL-jfltexx
lineage-14.1-20190212-nightly-jfltexx-signed
and
open_gapps-arm-7.1-pico-20190209
I have wiped everything and tried 2 different system boards ;
from download mode I have
used I337MVLSGQB1_I337MOYAGQB1_I337MVLSGQB1_HOME.tar
to reload with nothing checked but F. Reset Time.
pulled out the cable then the battery.
went straght to recovery (system was going there already) to do first stage unpack with android and progress bar.
It said BAR and END
I went in back in after restart, and a full wipe.
And after a long wait .. the system very glitchy, slow like something was running in the background (modem ?) if I open the phone app it wont close and calls are silent. then resets over and over..
I have tried custom roms, and flashing latest modem and original ? Whats up ? anyone
PLEAESSEEE help soon .. I am going crazy cuz this is literally my only phone and I need to use it !!!!
Had an old system board and tried to replace it and ended up in the same place with the second board ?!?! what is going on !
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

I know your post was a while ago but you cannot use Odin to flash a custom ROM.
Are you flashing the latest stock ROM from sammobile.com or updato.com?

audit13 said:
I know your post was a while ago but you cannot use Odin to flash a custom ROM.
Are you flashing the latest stock ROM from sammobile.com or updato.com?
Click to expand...
Click to collapse
I ended up using the pixel experience rom. I am sure I have the wrong bootloader and modem for i337m though. It works with data when I reset network settings and re-enable. Data each reboot. For the longest time lineage 9505 ROMs worked until like Feb 5th I saw the data just fall use just fall off. I couldn't get chatr to work anymore. It was a nightmare I went to stock and , pitted the phone and it would only function until I added TWRP and tried a nougat rom or even with latest modem. Wifi was evn a problem. Now I am using like a lollipop bootloader with the green battery charging and modem isn't right. When I flash a different modem and bootloader in Odin and rip the battery and then cableit doesn't even change .
Wtf?

futiless said:
I ended up using the pixel experience rom. I am sure I have the wrong bootloader and modem for i337m though. It works with data when I reset network settings and re-enable. Data each reboot. For the longest time lineage 9505 ROMs worked until like Feb 5th I saw the data just fall use just fall off. I couldn't get chatr to work anymore. It was a nightmare I went to stock and , pitted the phone and it would only function until I added TWRP and tried a nougat rom or even with latest modem. Wifi was evn a problem. Now I am using like a lollipop bootloader with the green battery charging and modem isn't right. When I flash a different modem and bootloader in Odin and rip the battery and then cableit doesn't even change .
Wtf?
Click to expand...
Click to collapse
I'm not sure how you could flash the wrong bootloader unless it was flashed using TWRP or CWM. To confirm, boot into download mode to see the model # listed on the screen.
Are the modem and bootloader matched; i.e. the phone is running a 5.0 bootloader and modem? To easily ensure that both are matched, you can flash the latest stock ROM using Odin.
If the modem version is not changing after being flashed, it is possible that the internal memory is faulty.

audit13 said:
I'm not sure how you could flash the wrong bootloader unless it was flashed using TWRP or CWM. To confirm, boot into download mode to see the model # listed on the screen.
Are the modem and bootloader matched; i.e. the phone is running a 5.0 bootloader and modem? To easily ensure that both are matched, you can flash the latest stock ROM using Odin.
If the modem version is not changing after being flashed, it is possible that the internal memory is faulty.
Click to expand...
Click to collapse
Can you tell me what version the latest boot loader and modem is for Canadian i337m

I haven't had an s4 for a long time but it was running the latest OH1 firmware: https://updato.com/firmware-archive-select-model?record=8D5422F720B911E6949E0CC47A44B7B2