hi
I am on B1 modem and and want to flash c2 modem. I have the tar file (contains modem.bin and non-hlos.bin). i have tried both odin and mobile odin.. the flash does not give any errors but the modem does not change. any help will be highly appreciated.
thanks
xinfinityoO said:
hi
I am on B1 modem and and want to flash c2 modem. I have the tar file (contains modem.bin and non-hlos.bin). i have tried both odin and mobile odin.. the flash does not give any errors but the modem does not change. any help will be highly appreciated.
thanks
Click to expand...
Click to collapse
Did you do some research? Put it on Phone not Pda. Shut down your phone completely and leave about 3sec, then flash the modem and see how it goes.
I am having NO luck flashing the NE2 modem on my G900i, i have tried with Odin V3 and mobile odin.
Odin: I have tried a .tar file and a .bin file, the tar failed but the bin passed but did not take. I even did the flash, pull the battery and flash again trick.
Mobile Odin:
Modem #1 = modem.bin
Modem #2 = Non-Hlos.bin
It booted into recovery but i got the message "Memory Protection in place" on both modems so it wouldn't flash them, then the phone rebooted.
Can anyone help please.
It doesn't work with m/o I try ed it a number of times with no success
Sent from my SM-G900F using XDA Premium 4 mobile app
Hi,
I have a SM-N900K/hltektt (one of the Korean variants of the Note 3), currently with NAC bootloader and baseband versions. I'm running an AOSP-based ROM with TWRP as the recovery.
The latest firmware for this device reportedly fixes an issue us Korean users using AOSP-based ROMs are having with LTE. The firmware version is N900KKKUFNG5_N900KKTTFNG5_N900KKKUFNF3, and I believe this means it has NG5 bootloader and NF3 basebands.
I've downloaded the full ROM tar file, but I'm looking to flash just the bootloader and baseband. I've never done this before, so I wanted to see if this is even possible.
What I have in the tar are:
NON-HLSO.bin
aboot.mbn
boot.img
recovery.img
rpm.mbn
sbl1.mbn
sdi.mbn
system.img.ext4
tz.mbn
Which parts would I flash with Odin, and can I use Mobile Odin for this?
If this seems too risky, I can always flash the whole stock ROM and then restore my own stuff from nandroid, but I wanted to see if there's an easier way to just update the bootloader and baseband.
im not sure about the bootloader
but for the baseband, u can flash the modem.bin and NON-HLSO.bin and it will works! :good:
flashing bootloader is not necessary. If you have any KK BL it's OK
I have old BL et new modem
After a firmware flash in ODIN, is the baseband supposed to be updated? The firmware file does contain the modem.bin and non-hlos.bin, but after booting into the ROM and checking About, the baseband remained the same. I know there's different changes in the new baseband so I'm not sure why it didn't flash. I tried flashing the firmware twice, the same thing. Everything works fine, just that the baseband isn't updated.
Would I have to extract the bin files and repackage them into a .tar.md5 file and flash it in ODIN with CP ticked? Seems like a 2 step process when the entire firmware should've been flashed with AP ticked.
Try to do unchecking "Auto Reboot" and reboot manually.
Hello,
I am on Cyanogenmod 13. and I have outdated Modem and Bootloader. which effect my network signal
I have downloaded the latest stock firmware which is for my specific device .
from reading all over XDA this is what i understand is the procedure:
1. getting the right stock rom <- done
2. extracting the required files <- my main question
3. create 2 tar packages for Modem and for Bootloader
4. creating MD5 checksum of both file.
5. flashing using ODIN while placing modem file to CR slot and Bootloader to BL slot. (flashing it twice before boot as it might be reset)
now i know how to do all this steps but my problem is to understand which files are required to Modem tar and Bootloader tar.
the available flash-able files made by the community are not consistent. for example some of the modem tar file people made contain modem.bin and NON-HLOS.bin while others only modem.bin.
this are the files in the original stock rom:
aboot.mbn
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
which of them i need to place in the Bootloader tar (BL) and which in the Modem tar (CP)?
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
allidea said:
I've also searched around hoping to find answer to this question
Click to expand...
Click to collapse
Which one? About Odin's slot? Use AP slot for everything.
bbsc said:
Which one? About Odin's slot? Use AP slot for everything.
Click to expand...
Click to collapse
I'd like to know which files to extract from stock FW. I don't want to end up in boot loop or something worse.
From what I've seen my stock ROM has following files as shown on 1st attachment and most custom modem + bootloader tarballs have files (below files are from PhoeniX ROM v13.6) as shown on 2nd attachment.
There is one particular file named sdi.mbn which can be found in custom modem+bootloader tarballs and which is not present in stock rom.
Ok, I don't know if it's correct or no, but I used for bootloader/modem/kernel update on SM-G900V such a file as shown on the picture.
The original (HOME) .tar.md5 was renamed to .tar.
The next files from it were deleted:
- cache.img.ext4;
- system.img.ext4.
Pit-file was added.
The resulting file was flashed via Odin's AP slot.
Result:
- bootloader, recovery, kernel and modem updated;
- Binary: Official; System: Official;
- all data on /data remain untouched.
allidea said:
I've also searched around hoping to find answer to this question. I've also compared a lot of bootloader & modem tarballs and each was different. If you found a solution please post it here. Otherwise the safest way is to flash stock firmware and then reflash it with desired custom one ...
Click to expand...
Click to collapse
All described here: https://jdrch.wordpress.com/2017/01...ions-without-breaking-custom-rom-or-recovery/
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
allidea said:
Thanks to both of you. @Hawaiihemd - As I already mentioned I am bothered by mysterious file named sdi.mbn which is not present in stock ROM (also mentioned by others who asked around about it too) but everyone mentioned it should be there ... funny ...
Click to expand...
Click to collapse
Are you still trying to figure this out??
bobbylo said:
Are you still trying to figure this out??
Click to expand...
Click to collapse
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
allidea said:
Nope. I don't know if I figured it out, but I've extracted all files from stock ROM as shown on second attachment in Post #4 above except sdi.mbn, created a .tar and flashed via ODIN ... Everything is working fine and new modem is displayed in device info.
Click to expand...
Click to collapse
ok,so you created a .tar?Not a .tar.md5? why did'nt you need the sdi.mbn?
bobbylo said:
ok,so you created a .tar?Not a .tar.md5?
Click to expand...
Click to collapse
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
For the bootloader select BL and browse to your bootloader file.
For the modem select CP and browse to your modem file.
Click to expand...
Click to collapse
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
why did'nt you need the sdi.mbn?
Click to expand...
Click to collapse
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
allidea said:
No just .tar as ODIN will accept it as well. I'm no expert but my guess .md5 is just a hash to verify .tar.
I used a tool named Odin Tar Converter v1.0 I think I found it on xda somewhere, but you can use any compression tool which is able to make .tar archives ie. 7-Zip.
Afterwards I just followed instructions for flashing bootloader and modem from PhoenixROM so I added .tar archive I've created to AP (newer ODIN) / PDA (older ODIN) and flashed it.
I've came across following instructions:
But since I created .tar regarding PhoenixROM bootloader and modem .tar structure it made more sense to follow PhoenixROM instructions.
Maybe I needed it, but no matter how many stock ROMs I got my hands on none of them had this file. According to this article it seems sdi.mbn contains contains transmission band info although I don't think author himself was clear what it actually is used for. Anyway I decided to try and flash modem without it.
Click to expand...
Click to collapse
Ok,was just wondering...I have an xda page where i created bootloaders and modems for the S5 G900T t-mobile.I use a program called cygwin64 to create the .tar.md5 files.It involves some command line input..Maybe yours is easier....Anyway,don't think i'll need to make any more,as i think there done with updates for the G900T,and maybe all the S5's