[MODEM][ODIN] Samsung Galaxy S4-mini GT-I9195 (Upd. Oct. 16. - 2017)

cancunia

Senior Member
Dec 21, 2013
77
7
0
Thanks for the hint! There's a chance that the system did boot in between the 2 flashes. If time allows, I'll make another backup tomorrow and try again. As a matter of interest, what's the reason for 2x flashing with no boot in between?
 

IronRoo

Senior Member
Aug 4, 2014
1,342
434
0
Thanks for the hint! There's a chance that the system did boot in between the 2 flashes. If time allows, I'll make another backup tomorrow and try again. As a matter of interest, what's the reason for 2x flashing with no boot in between?
edit: oops I answered the wrong question, first time, that was meant for another post I read earlier!

On some phones the modem files need to flashed twice in a row without booting into system (I forget the actual reason) (turn off automatic reboot)
 
Last edited:

PtosekL

New member
Aug 17, 2017
1
0
0
What is the best modem and baseband for europe? (Czech Republic - Vodafone simcard)
With stable LTE, and not drain battery. What do you suggest?

Actual baseband is I9195XXSCQAI
ROM is LineageOS 14.1
 
Last edited:

IronRoo

Senior Member
Aug 4, 2014
1,342
434
0
What is the best modem and baseband for europe? (Czech Republic - Vodafone simcard)
With stable LTE, and not drain battery. What do you suggest?

Actual baseband is I9195XXSCQAI
ROM is LineageOS 14.1
That's the latest one you have, is it giving you problems?

(I'm still on the last xxu modem CPI1 on Vodafone network in Australia and it's working good with Linage 7.1.2)
 

crypt555

Member
Aug 27, 2013
7
0
0
Save data by flashing

Hello everyone!

I have a S4 Mini that's stuck in a bootloop and I can only enter Odin mode.

I was told I might fix this by flashing the exact same build number/version to the phone because that won't update the bootloader, problem is I can't figure out the exact android version (because it won't start nor can I enter recovery mode). I have another phone of the same model though and that phone has 4.4.2 so I was thinking I could maybe gamble and try flashing that version and hope the bootlooping phone has the same.

Any advice on this or where I might find more information?

I've downloaded modem I9195XXUCPE1 android version 4.4.2 for the task.

Update
The device was successfully flashed with Odin but it did not solve the bootlooping problem. Any suggestions of what I might try next or is this a hardware issue?

Thanks
 
Last edited:

IronRoo

Senior Member
Aug 4, 2014
1,342
434
0
Hello everyone!

I have a S4 Mini that's stuck in a bootloop and I can only enter Odin mode.

I was told I might fix this by flashing the exact same build number/version to the phone because that won't update the bootloader, problem is I can't figure out the exact android version (because it won't start nor can I enter recovery mode). I have another phone of the same model though and that phone has 4.4.2 so I was thinking I could maybe gamble and try flashing that version and hope the bootlooping phone has the same.

Any advice on this or where I might find more information?

I've downloaded modem I9195XXUCPE1 android version 4.4.2 for the task.

Update
The device was successfully flashed with Odin but it did not solve the bootlooping problem. Any suggestions of what I might try next or is this a hardware issue?

Thanks
Not clear from your post if you realise the following. The modems on this thread are just a tiny part of a stock ROM, they will not fix a bootloop as they do not contain the OS, bootloaders etc. You need to use a full stock ROM as originally released by Samsung to fix bootloops/bricks. Custom ROM's like Linage do not change everything on a phone, things like the modem, bootloader etc from stock are not changed. That is why this thread has separate modems collected from some countries/carriers that can be flashed to keep them up to date else they will remain the same as what was on the phone originally. You can download the FULL stock ROM from websites like sammobile etc. I would recommend you do not just download from some random link as these files may have malware added, only get from trusted sources.
 
Last edited:

fankool

Senior Member
Feb 1, 2013
199
38
28
Puglia
Last edited:

redjamesg

Senior Member
May 29, 2012
453
490
0
Copenhagen
thank you. Do you know if there's a changelog?
Another question: I went to sammobile (https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9195/) but I found only older firmware version (nothing with QG code). Where did you find it? You also reported:
Security patch Jul. 01. 2017
what does it mean? I thought it was a peculiarity of a rom, not also of modem. What aspect of security is improved?
The changelog is a bit difficult to find, since the changelog number is regarding the kernel changes, there isn't a specific log for the modem part.

The firmware is obtained from Updato, which is regarded as the database of latest official released firmwares.

The mention of the security patch date, is to notify that it is from the latest available firmware, if there has been some changes to the modem within the security patch, these will be part of the modem provided.
 

cancunia

Senior Member
Dec 21, 2013
77
7
0
Maybe the answer to my questions below are in amongst the earlier replies, if so please point me in the right direction.

I cannot make sense of the naming conventions for the Modems / ROMs.
For Example I9195XXUCOL3
This is an O2 ROM for the UK
https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9195/O2U/

I9195 - OK, that's fairly self explanatory

XXU - Region ? Are these defined anywhere?
C - ? - This letter increments in the O2 ROM list on SAMMOBILE from A-C but does not seem to relate to month or year of release
O - ? - This letter increments from M to O in the ROM list but does not seem to relate to month or year of release
L - ? - This letter changes on each build
3 - Build number?

redjamesg has kindly put a collection of modems on Android File Host, but I'm unsure which ones are for the UK?
https://androidfilehost.com/?w=files&flid=97304

XXS is for ?
XXU is for ? Most if not all of the EU ROMs seem to be XXU so maybe that's it.

Sorry for the possibly daft questions, but don't want to load the wrong modem if I can help it!

Thanks
 

IronRoo

Senior Member
Aug 4, 2014
1,342
434
0
Maybe the answer to my questions below are in amongst the earlier replies, if so please point me in the right direction.

I cannot make sense of the naming conventions for the Modems / ROMs.
For Example I9195XXUCOL3
This is an O2 ROM for the UK
https://www.sammobile.com/firmwares/galaxy-s4-mini/GT-I9195/O2U/

I9195 - OK, that's fairly self explanatory

XXU - Region ? Are these defined anywhere?
C - ? - This letter increments in the O2 ROM list on SAMMOBILE from A-C but does not seem to relate to month or year of release
O - ? - This letter increments from M to O in the ROM list but does not seem to relate to month or year of release
L - ? - This letter changes on each build
3 - Build number?

redjamesg has kindly put a collection of modems on Android File Host, but I'm unsure which ones are for the UK?
https://androidfilehost.com/?w=files&flid=97304

XXS is for ?
XXU is for ? Most if not all of the EU ROMs seem to be XXU so maybe that's it.

Sorry for the possibly daft questions, but don't want to load the wrong modem if I can help it!

Thanks
To two most recent ones in your link do seem to have the dates listed messed up, but if you check the 3rd one the dates & letters match as you would expect. I think you will be safe to assume the last 3 letters of the file name are correct (not the dates typed out) so as long as you are choosing later/higher letters/numbers you will get the latest modem files.

As for the two letters after the XX, I've not seen definitive confirmation what they mean. But people from all regions have been flashing them with no reports of problems, (one user may have had battery drain, but it was not confirmed it was because replacing xxu with an xxs, nobody else reported this ) so long as your phone is an xx (international) version, though personally I've j just used xxu modems as that was what my phone originally had.

(As redyamsg mentions earlier there is a possibility some extra functions may be lost if you use modem from different region, but again nobody has ever reported this on our I9195 phone, that I recall)

Edit: don't forget to make a backup of your modem & csc with TWRP or another app before trying new modem
Edit: O=year L=month
 
Last edited:

cancunia

Senior Member
Dec 21, 2013
77
7
0
Thanks for the reply & clarification regards O&L in my example being dates, after some looking around on other archives yesterday I came to pretty much the same conclusion about the dates. I think the dates on Sammobile probably relate more to when the ROMs are uploaded as opposed to released.
The UK ROMs on the following site, mentioned in one of the earlier posts, match the naming convention for the last 2 alpha chars in the filename:
https://samsung-firmware.org/de/model/GT-I9195/region/EVR/

I flashed the Modem in post #1 yesterday without issues, thanks to redjamesg for extracting them. I still have a reception problem which I thought was related to a Lineage overnight update, but looks to have been a coincidence with a local service outage. At least I have a later modem now!

I borrowed the region codes below from another thread, interestingly the US & Canada are not in here so there are probably a few other gaps too.
Slightly more regions are in this post, but still gaps I think:
https://www.sammobile.com/forum/showthread.php?t=15134

REGION CODES
BD Cyprus, Greece
CP Finland
DBVietnam
DC Thailand
DD India
DT Australia
DX Indonesia, Malaysia, Philippines, Singapore, Vietnam
DZ Malaysia, Singapore
JA South Africa
JC Algeria, Morocco, Nigeria, South Africa, Tunisia
JP Arabic
JR Arabic
JV Algeria, Egypt, Iran, Iraq, Kuwait, Morocco, Nigeria, Oman, Pakistan, Saudi Arabia, South Africa, Syria, Tunisia, Turkey
MT Switzerland
XA Austria, France, Germany, Italy, Netherlands, Switzerland, United Kingdom
XB Denmark, Norway, Sweden
XC Portugal, Spain
XD Croatia, Czech, Hungary, Slovakia
XE Bulgaria, Estonia, Kazakhstan, Latvia, Lithuania, Russia, Ukraine
XF Bulgaria, Croatia, Romania
XW France, Germany, Italy, Netherlands, Portugal, Spain, Turkey, United Kingdom
XX Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom
ZC China, Hong Kong
ZH Hong Kong
ZT Taiwan

Would still be nice to know the meanings of the other letters 'UC' mean from my original example.
The story so far:
I9195XXUCOL3
I9195 = model
XX = Region (Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom)
UC = ????
O = Year (2015)
L = Month (Nov)
1 = Build Number
 
Last edited:

redjamesg

Senior Member
May 29, 2012
453
490
0
Copenhagen
The story so far:
I9195XXUCOL3
I9195 = model
XX = Region (Austria, Belgium, France, Germany, Hungary, Italy, Spain, United Kingdom)
UC = ????
O = Year (2015)
L = Month (Nov)
1 = Build Number
Just to clear a few things, you have it almost sorted out, the U in UC is for Unbranded release, an S here means supplier branded, the C how ever I have never found a reliable explanation to.

Sent from my SM-G930F using XDA Labs
 
  • Like
Reactions: IronRoo

cancunia

Senior Member
Dec 21, 2013
77
7
0
Thanks for the feedback, good to know I'm on the right track. Strangely the example I used is for an O2 UK ROM so not sure what is meant by 'Unbranded'?
 

redjamesg

Senior Member
May 29, 2012
453
490
0
Copenhagen
Thanks for the feedback, good to know I'm on the right track. Strangely the example I used is for an O2 UK ROM so not sure what is meant by 'Unbranded'?
Unbranded means nothing added by vendor, supplier branded usually means extra stuff added like SIM tools, extra settings in SMS handling, additional software merged into system/priv-app (unable to uninstall without root), and customized home screen.

Essentialy when using Unbranded it is the touchwiz provided by Samsung without anything added by the carrier, even tho it might be specifically to certain carrier.

Sent from my SM-G930F using XDA Labs
 
  • Like
Reactions: IronRoo

Oriceles

Member
May 14, 2015
19
4
0
I had the i9195XXSCQAF modem and I'm flashing MJ7 to try a sim unlock, currently having problems with network not working on 3G properly and 4G is not picking up at all... Followed the guide and at first boot my phone turned off... then I waited a while, went to boot again and I got some color points on boot logo which I didn't had before (guess new modem is related?), now I'm stuck at bootloop... currently running LOS 14.1... decided to turn off, went recovery, tried cleaning dalvik, and boot to system but then boot logo screen got messed followed by a blue screen to off. Now I'm doing a factory reset to see if I can boot. I at least can boot to download and recovery with no problem.

Edit: Lineage managed to boot after factory reset but now it's not detecting the sim card and I get baseband uknown :(... gonna try to flash to stock with a firmware that has same baseband as before or google how to fix

Edit: stock rom is okey but still no baseband and still getting a blue screen after the boot logo, I can't turn on wi-fi either. I'm thinking that I should flash the modem of this rom with the method described on OP but I don't know how to create the flashable, I can provide the files by extracting those from the rom I got.

Edit: tried to flash files via heimdall with command "heimdall flash --modem NON-HLOS.bin --RPM rpm.mbn --TZ tz.mbn --verbose --no-reboot" but now I get a ERROR: Failed to send data: "ODIN".

Code:
C:\Users\Alvaro\Documents\android\Heimdall Suite>heimdall flash --modem NON-HLOS
.bin --RPM rpm.mbn --TZ tz.mbn --verbose --no-reboot
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8960"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The param
eter is incorrect.
ERROR: Failed to send data: "ODIN"
Releasing device interface...
Final Edit on my adventure: I decided to flash the stock rom 2 more times, and after that everything reverted to normal, just shame that now I need to go back to LOS 14.1 lmao. I still wish I could know how to flash this without much hassle because I'm pretty sure I will still struggle with signal.
 
Last edited:

redjamesg

Senior Member
May 29, 2012
453
490
0
Copenhagen
I had the i9195XXSCQAF modem and I'm flashing MJ7 to try a sim unlock, currently having problems with network not working on 3G properly and 4G is not picking up at all... Followed the guide and at first boot my phone turned off... then I waited a while, went to boot again and I got some color points on boot logo which I didn't had before (guess new modem is related?), now I'm stuck at bootloop... currently running LOS 14.1... decided to turn off, went recovery, tried cleaning dalvik, and boot to system but then boot logo screen got messed followed by a blue screen to off. Now I'm doing a factory reset to see if I can boot. I at least can boot to download and recovery with no problem.

Edit: Lineage managed to boot after factory reset but now it's not detecting the sim card and I get baseband uknown :(... gonna try to flash to stock with a firmware that has same baseband as before or google how to fix

Edit: stock rom is okey but still no baseband and still getting a blue screen after the boot logo, I can't turn on wi-fi either. I'm thinking that I should flash the modem of this rom with the method described on OP but I don't know how to create the flashable, I can provide the files by extracting those from the rom I got.

Edit: tried to flash files via heimdall with command "heimdall flash --modem NON-HLOS.bin --RPM rpm.mbn --TZ tz.mbn --verbose --no-reboot" but now I get a ERROR: Failed to send data: "ODIN".

Code:
C:\Users\Alvaro\Documents\android\Heimdall Suite>heimdall flash --modem NON-HLOS
.bin --RPM rpm.mbn --TZ tz.mbn --verbose --no-reboot
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
      Manufacturer: "Sasmsung"
           Product: "MSM8960"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 82
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 01
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
libusbx: error [windows_transfer_callback] detected I/O error 87: [87] The param
eter is incorrect.
ERROR: Failed to send data: "ODIN"
Releasing device interface...
Final Edit on my adventure: I decided to flash the stock rom 2 more times, and after that everything reverted to normal, just shame that now I need to go back to LOS 14.1 lmao. I still wish I could know how to flash this without much hassle because I'm pretty sure I will still struggle with signal.
Are you using a functioning USB cable?
Do you have the correct drivers installed?

If you could provide me with the files you are trying to use, then I can create an ODIN flashable .zip file of those.
 
  • Like
Reactions: IronRoo

Oriceles

Member
May 14, 2015
19
4
0
Yep cable is okey, not stock or samsung brand, but I've been using this as my daily driver. Yup both samsung and adb, also used zadig and worked properly. As final edit says, it seems that the problem is my operator, I was able to connect to H+ a while back but it doesn't stay like that for long, I also have all the requirements to be elegible for LTE and I've been unable to get LTE since I got the phone and line, totally weird. I'll wait and visit customer support to see what they can say about it. As for the files, I'll upload them to AFH or Mega in some minutes.

Edit: https://mega.nz/#!WIhzAS5Z!NcU9Vhp7lNlrilKQMKx3bS2b8Nr3LKqs6R8oZNJxoAc
 
Last edited: