U to U1 Firmware Flash Fails - Samsung Galaxy Note 10+ Questions & Answers

I have a Note 10+ 975U. It was orignally though Sprint, then T-Mob, and now unlocked so I wanted to flash the U1 firmware in odin, but it fails. To my knowledge, the U and U1 firmware should be interchangeable? Is this due to the bootloader lock?
Odin says:
<ID:0/005> FAIL! SHA256 is invalid

use patched Odin
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com

Related

[Q] Please help!! M919UVUAMBF baseband?

I tried rooting my phone on 4.2.2 but ended up bricking without having a nandroid backup. So i downloaded stock UVUAMDB tar from k0nane thread and it flashed without any issues through odin. However, my baseband version now is UVUAMBF and my build number is UVUAMDB. Is this normal? I also can't connect to wifi and every other rom i flash fails on ODIN. I can flash any recovery but can't flash any other rom except the MDB tar file. Also tried downloading the UVUAMDL and flashed it but still failed on ODIN. Can someone please help with this? I have been trying to fix for 2 days now. Please help!!
What is your model number?
serio22 said:
What is your model number?
Click to expand...
Click to collapse
It is SGH-M919. Thanks for responding. Hope my phone is not totally useless now.
Can you link to the firmware you flashed? That build and baseband isn't even for the M919.. Have you tried flashing latest NB4 firmware?
serio22 said:
Can you link to the firmware you flashed? That build and baseband isn't even for the M919.. Have you tried flashing latest NB4 firmware?
Click to expand...
Click to collapse
I flashed the stock tar from this thread:
http://forum.xda-developers.com/showthread.php?t=2258628
I have attached a screenshot of the about device section of my phone.
hyperenigma said:
I flashed the stock tar from this thread:
http://forum.xda-developers.com/showthread.php?t=2258628
I have attached a screenshot of the about device section of my phone.
Click to expand...
Click to collapse
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
The Sickness said:
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
Click to expand...
Click to collapse
Alright. Thanks very much. I'm downloading right now and I'll post back regarding the outcome.
The Sickness said:
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
Click to expand...
Click to collapse
So i tried installing the official MDL 4.2.2 via odin but failed. I got this;
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl2.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any reason why? Thanks once again
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
In download mode, it says,
ODIN MODE
PRODUCT NAME: SGH-M919
CUSTOM BINARY DOWNLOAD: YES
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
That's all it says. Recovery and everything else flashes in ODIN except modems and roms. Also in custom recovery using TWRP, it says error can't mount system. Don't know what's wrong. Plug into kies and says that's the latest firmware. Trying to update ota but can't because of my flash counter I think.
serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
Also, something weird happened in that I tried rooting using CF ROOT and I succeeded but when I click superuser, it says KNOX is enabled and that it will disable it. Am I supposed to have KNOX on 4.2.2? These all makes no sense to me.
serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
Please help. I don't even know what else to do right now. Can I flash a kernel or pit file or something. Just bought this 3 days ago.
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
serio22 said:
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
Click to expand...
Click to collapse
I downloaded the CF root file for the tmobile s4. I'll try your suggestions above and get back to you. Thanks.
serio22 said:
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
Click to expand...
Click to collapse
I just tried everything you suggested above and stil no luck. Switched USB ports, switched computers and switched USB cables. Guess I am stuck with this.
hyperenigma said:
I just tried everything you suggested above and stil no luck. Switched USB ports, switched computers and switched USB cables. Guess I am stuck with this.
Click to expand...
Click to collapse
Is all that you want root or do you intend on flashing custom ROM?
serio22 said:
Is all that you want root or do you intend on flashing custom ROM?
Click to expand...
Click to collapse
I just want a ROM that could work with my Samsung gear since it doesn't work on 4.2.2.
hyperenigma said:
I just want a ROM that could work with my Samsung gear since it doesn't work on 4.2.2.
Click to expand...
Click to collapse
Ok and you say you can't flash ROMs with any recovery correct? And they are latest? If so then only thing I can suggest is to see if you can flash 4.4.2 with Odin, search for fenny's NB4 firmware and flash that, after that you can flash recovery and hopefully be able to flash ROMs without issue.. Just remember that it will trip Knox counter once you flash recovery
Im extremely curious where that baseband came from. Cause MDB was the firmware that shipped with the m919 on release. And according to your last 2 Letters of your baseband you have a modem from a firmware that came before MDB that was never shipped with the m919 but the rest MDB. I mean MBF isnt even on Samsungs open source site for ANY m919 variant. So that means MBF wasnt even released to the public or someone like me would of emailed for release of the source like I just did for GNG8.
You said you got it 3 days ago right? Did it come from a Samsung or Tmobile employee or something?
Anyways. Your getting the notification about knox cause theres a few knox files on 4.2.2 just basically not doing anything and SuperSu is detecting them. Your odin is failing on the bootloader (SBL/Samsung Boot Loader) Just for curiosity purposes can you download android terminal emulator and type getprop ro.bootloader and press enter post what version it says?
Since odin is failing, Id try Heimdall.
ShinySide said:
Im extremely curious where that baseband came from. Cause MDB was the firmware that shipped with the m919 on release. And according to your last 2 Letters of your baseband you have a modem from a firmware that came before MDB that was never shipped with the m919 but the rest MDB. I mean MBF isnt even on Samsungs open source site for ANY m919 variant. So that means MBF wasnt even released to the public or someone like me would of emailed for release of the source like I just did for GNG8.
You said you got it 3 days ago right? Did it come from a Samsung or Tmobile employee or something?
Anyways. Your getting the notification about knox cause theres a few knox files on 4.2.2 just basically not doing anything and SuperSu is detecting them. Your odin is failing on the bootloader (SBL/Samsung Boot Loader) Just for curiosity purposes can you download android terminal emulator and type getprop ro.bootloader and press enter post what version it says?
Since odin is failing, Id try Heimdall.
Click to expand...
Click to collapse
I bought it from a guy brand new. The phone was working perfectly fine when I purchased and there was no issues at all. I tried to flash a custom rom with 4.4.2 on the phone after rooting and everything just got messed up. Didn't check the baseband version then so I am not 100 percent sure about that as well. When I downloaded terminal emulator and did as you suggested, I got
M919UVUAMBF
I tried heimdall but don't know where to get the firmware package for the m919. Please any assistance will be very much appreciated at this point. Thank you very much

Note 2 - Latest firmware XXUFNG4 - MJ5 Bootloader no knox - Can not flash via Odin

My Note 2
- Latest Firmware XXUFNG4 4.4.2, old bootloader MJ5 (no knox)
- Can not flash any .tar, .md5 (CWM, TWRP, CFAutoRoot...), odin 3.04 and 3.09 always says no pit file, and failed. So that I can not root
- It used to work well with older firmware 4.3 and 4.4.2, but now it fails
I am trying to root with Kingo... But is there any better solution to this?
I reflashed new firmware via odin, and it has been OK and rooted already. Thanks all.

Need PIT for S6 Edge

Hello
Previously I had flashed my phone to UK ROM. I would like to back to TH (Thailand) ROM but always failed on hidden.img
If my understanding is correct. I should have to right PIT file with suitable with this rom "G925FXXU3DPBK"
Anybody who had the PIT file please shared me.
Thanks in advanced.
Wrong forum, you don't need the pit file, you need the correct firmware for your region or just remove the hidden.img from the firmware.
An alternative is to flash the firmware with TWRP V3.

How to install new stock .tar file? ODIN 3.12 says "Download BL + AP + CP + HOME_CSC

How to install new stock .tar file? ODIN 3.12 says "Download BL + AP + CP + HOME_CSC
I did download G935PVPS4APK1_SPT4APK1_SPR_Sprint_USA_6.0.1 which does contain files that start with AP_, BL_, CP_, CSC_SPT, HOME_CSC_SPT.
These match with the ODIN sections which I was previously advised never to flash.
What are each of these? Should I actually flash them? Should I flash them in a certain order? I always get fail when I try to install (may need to run as admin).
hammerchucker said:
I did download G935PVPS4APK1_SPT4APK1_SPR_Sprint_USA_6.0.1 which does contain files that start with AP_, BL_, CP_, CSC_SPT, HOME_CSC_SPT.
These match with the ODIN sections which I was previously advised never to flash.
What are each of these? Should I actually flash them? Should I flash them in a certain order? I always get fail when I try to install (may need to run as admin).
Click to expand...
Click to collapse
If your download is zipped, extract the tar.md5 file and load in AP slot.
You've downloaded a S7 Edge file but posted in Note 4 forum. Check your model number and make sure you're flashing the right stock tar. Note 4 has stock tar thread in general forum for Note 4.
Even the Sprint S7E uses a full stock tar.md5 file to flash in AP slot per Sammobile. The dialogue you're seeing in the newer Odin is used for other purposes like recovering phone. Maybe other models use that or it's another option for flashing native csc on international phone but Sprint phones would normally use the full tar.md5 in AP slot.
Sent from my SM-N920P using Tapatalk
samep said:
If your download is zipped, extract the tar.md5 file and load in AP slot.
You've downloaded a S7 Edge file but posted in Note 4 forum. Check your model number and make sure you're flashing the right stock tar. Note 4 has stock tar thread in general forum for Note 4.
Even the Sprint S7E uses a full stock tar.md5 file to flash in AP slot per Sammobile. The dialogue you're seeing in the newer Odin is used for other purposes like recovering phone. Maybe other models use that or it's another option for flashing native csc on international phone but Sprint phones would normally use the full tar.md5 in AP slot.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks for the response and catch that this is S7 ROM. It never flashed (failed in ODIN) and I ended up d/l the Sprint N4 PK1 which led to a successful Note 7 install.

trouble flashing from U firmware to U1 firmware

i saw the U1 firmware could be flashed over the U firmware on the S9 on some threads. i mainly want to switch to the U1 firmware cause i saw it has android 10 on it while the U firmwares dont yet. My S9 is running up-to-date firmware of G960USQS7CSK5. ive tried using odin, odin patched 3B, and odin modded by raymond all version 3.13.1. For the U1 firmwares ive tried DTA5 (android 10) and CSK2 (android pie) to flash over the U firmware thats currently running on my phone. when i use any of the odins besides the raymonds modded one. i get a fail error right after "setup connection". then for the raymond modded version ive tried twice now and first time i got a fail for "Auth write" and second time i got a fail after "initialization" but no reason why it fails. ive looked all over threads and the tips seem to be scrambled all over the forums about it but i cant seem to get a clear answer. any ideas how i can get this to go through? its becoming frustrating
Bump
Are you using the CSC or the HOME_CSC file? I tried flashing the U1 DTA5 firmware earlier today using the HOME_CSC file and got errors, but using the CSC file worked fine.
Hai Karate said:
Are you using the CSC or the HOME_CSC file? I tried flashing the U1 DTA5 firmware earlier today using the HOME_CSC file and got errors, but using the CSC file worked fine.
Click to expand...
Click to collapse
i tried both. got same result
UPDATE: swapped USB ports and everythings working now. thread can now be closed. thanks

Categories

Resources