Install Canadian Firmware (SM-J320W8) in AT&T Variant (SM-J320A) - Samsung Galaxy J3 (2016) Questions & Answers

I Have a J3 SM-J320A and I want to install the Canada Firmware SM-J320W8. If I try to flash the ROM with ODIN appears a bootloader error on the phone and fails to flash sboot.bin.
Is there a way for install the firmware or make .tar file without the bootloader?
I made a .tar file just with system.img file and another file without sboot.bin for try to flash it with odin but when I press start ODIN closes by itself.
Both models have the same chipset and supports the same frequency networks.

Related

[possible fix] Broken camera after flashing MJ4 modem

Hey guys
After flashing MJ4 modem from official XXUDMJ6 my camera was not able to record any videos anymore.
Gave me an error and force closed a few seconds after pressing on the record button. Also happened with every other camera app.
Found a possible fix that worked for me, you might want to give it a try if you have the same issues.
What to do:
- Flash official untouched XXUDMJ6 firmware with Odin
- Reboot to download mode
- Flash XXUBMJ1 modem (get it here) via Odin 3.09
- Untick "Auto Reboot" and Flash as CP
- After flashing process is finished reboot in download mode again with 3 button combination and flash modem again (you may need to restart Odin and untick Auto Reboot)
- After flashing is done reboot smartphone
- Smartphone will start but will not ask for PIN and will have no connection, also system process will force close
- Reboot to download mode and reflash the whole untouched XXUDMJ6 firmware again
- Reboot, camera should be working now
I flashed Omega v 3.0 after this and camera still works.
Flashing non-hlos from stock mj6 should be a good solution also
Flashing NON-HLOS.bin and modem.bin wasn't enough in my case. Even adding hidden.img.ext4 and multiple factory resets didn't solve the problem and camera and WLAN kept broken.
The only solution was to include boot.img and recovery.img from the unmodified Samsung tar-file.
Create a tar.md5 including the following files:
NON-HLOS.bin
boot.img
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4
modem.bin
recovery.img
system.img.ext4 <- created by Universal RDLV
DO NOT INCLUDE THE .MDB FILES!!! DO NOT INCLUDE UNMODIFIED system.img.ex4!!!
Use Odin from the RDLV-Bundle to flash that tar.md5 file and you will be fine. I'm on OXAUDMJ6 now with Knox-Flag 0x0 and working root, camera and WLAN.
Additionally I changed my region from XEF (France) to BTU (UK) with "Galaxy CSC Changer" (PlayStore) to match the region of the CSC file - but that step should be optional.
Using the wrong CSC doesn't change the Knox-Flag - I had to do it to change from XEF to BTU, because they are not in the same multi.csc file.

[Q] Problems with updating bootloader / modem

edit:
I finally managed now to flash DBT NB4 with PIT..
Hello guys,
I have some problems with my N9005.
First problem:
I tried to update my bootloader, also modem witn Odin 3.09
BL: NA6
Modem: NA2
Tried to update bootloader to ND5, also tried modem to NC2. I used key combo to get into download mode.
Auto Reboot and F Reset Time ticked, nothing else. Tried one by one, first BL with BL tab, modem with CP tab
Nothing changed after reboot... still NA6 and NA2
I also used mobile odin, skips modem cuz of write protection. This also is readable in download mode.
Second problem:
After every reboot (normal, recovery, etc.) the time is reset, you have to config manually or let it grab frome time-servers.
Annoying...
Can anyone help me?
Can anyone help me?
I tried to flash N9005XXUENB7_N9005DBTENB2_N9005XXUENB1_HOME.tar.md5 with PDA tab now, with hidden.img it stopped with FAIL (size)
So I used the pit file for DBT and tried again, still FAIL! (Size)
Note 3 now starts only to download mode with firmware upgrade error warning...
edit:
I finally managed now to flash DBT NB4 with PIT..
Sometimes pit file is needed for certain firmware.
http://forum.xda-developers.com/showthread.php?t=2643109
When updating bootloader and modem, u have to shutdown phone completely before the 3 combos. And do it one by one at the correct tab.
Sent from somewhere under the sky, at the corner of this rounded earth.

how to make pit BL AP CP CSC files from a rooted G900V which is at 4.4.2

So, I have 2 phones - both are g900v.
one is at 4.4.2 rooted and another one is at 5, non-rooted and I can't root it, and can't downgrade as at fails at [aboot] fused 2 > Binary 1
or with some other error - basically, failing cuz odin is touching on the bootloader piece of it
So, as I understand, rooting at this point would require flashing separately AP CP CSC and Pit
1. how do I produce them?
2. which button/option in odin each file corresponds?
3. would it work better with sdk and push via cmd?
4. any way to extract these files from a stock tar file ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 ? I extracted files from it, but they don't look like AP CP CSC and Pit - at least don't start with AP CP CSC and Pit, as someone reported they should.
thanks.

Fully Updated Sprint G930P bootlooping after Odin flash - SW REV CHECK FAIL Error

I got this S7, wanted to flash 930U firmware to use T-Mobile but a failed flash has me in a boot loop. I fully updated before trying to flash, so it is I assume on the newest bootloader, etc.
I have attempted the newest firmware files that I can find (G930AUCS4BQL1) but am still getting the SW REV CHECK FAIL through Odin.
Are there files available that will fix this, do I just need to wait for them to come out, or have I bricked this thing?
Thanks for any help and have a great day!
Update:
- Using PrinceComsy Odin results in: FAIL! (Auth)
- USB Debugging is OFF and I am unable to boot to change that
- I am leaving the BL file blank in ODIN
perhaps you should try using offcial odin when flashing official images.
try version 3.12.3. whatever you do, don't use the princecomsy version unless for flashing engboot

[SOLVED] Custom binary blocked by frp forgot OEM - back to stock firmware but how?

Hi,
I have my moms SM-A310F
..fool me I forgot to enable OEM before installing TWRP and flashing the latest LineageOS
After a reboot it shows "Custom binary blocked by FRP lock"
After some research I came to the conclusion that only flashing back to the Samsung firmware could save me.
I'm going to use Odin.
My problem is that the firmware provided by samMobile and samfrew both only provide .img and .bin files.
I found out how to convert them over here: [Script][Tool] how to create a tar.md5 file from img For Odin
But which ones do I need to convert? And where do I need to flash tem to in Odin?
I got:
boot.img
cache.img
cm.bin
hidden.img
modem.bin
recovery.img
sboot.bin
system.img
Odin gives me the options to flash:
BL
AP
CP
CSC
USERDATA
I know that I can ignore USERDATA. But what about the others?
Do in need to flash all the files above? And which file goes where?
Thanks a lot, my mom (and I) will be very thankful for your help.. ;-)
just realised that unzipping the .zip file (firmware) on a Mac caused the issue. If I unzip on Windows i get a tar.md5 that I can flash on AP
on Mac unziping gives me a folder with all the mentioned files.
I have a big problem. Please help. I unknowingly disabled developer mode and when I reboot it says "Custom binary blocked by FRP. (boot.img)" or "Custom binary blocked by FRP. (recovery.img)" in recovery. The worst thing is that Odin mode does not recognize the device. I have also installed the latest samsung drivers. But it is useless. My device is J2 Prime or G532F. Please help me...

Categories

Resources