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!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?
That's the latest one you have, is it giving you problems?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
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.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
Country / Region Romania (Orange)
PDA I9195XXUCQG1
Product Code ORO
Security patch Jul. 01. 2017
thank you. Do you know if there's a changelog?
- Latest Modem: I9195XXUCQG1
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.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. 2017what does it mean? I thought it was a peculiarity of a rom, not also of modem. What aspect of security is improved?
Thank you.[...]
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.
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.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
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.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
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.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'?
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...
Are you using a functioning USB cable?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".
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.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...