Develop Bugs

Problems downgrading to 4.1.1 firmware

I'm having some trouble flashing 4.1.1 on a 4.1.2 phone. I was linked to this site and grabbed the 4.1.1 firmware from there. I've tried both Odin 3.07 and 3.09 but I get a "complete(write) operation failed" error with both.
What's odd is this device is most assuredly an i747, yet on the phone's screen in Download Mode the Device Name field shows T999 for some reason. Might that have something to do with this failure to flash?
I was able to successfully flash a file earlier that rooted the device, successfully from the looks of it. SuperSU seems to be working fine.
Any ideas on how I can get this flashed so I can unlock the phone for use on Smart Talk?
Edit: After doing a factory reset from recovery I now get this from Odin:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Looks like there is a bootloader mismatch that it's causing the write failure.

audit13 said:
Looks like there is a bootloader mismatch that it's causing the write failure.
Click to expand...
Click to collapse
Audit, could it be that it's got the BL for T999 which is what's causing the errors? However, wouldn't that have been likely to cause a soft brick in the first instance unless the rest of the system is compatible? I guess he could check system information under Settings to see if this really has i747 firmware or someone's previously successfully "changed" it to a T-Mob phone. Not sure that's possible but I was just thinking ... perhaps a previous J-Tag operation especially if it was purchased in the secondary market.

Larry2999 said:
Audit, coup as t be that it's got the BL for T999 which is what's causing the errors? However, wouldn't that have been likely to cause a soft brick in the first instance unless the rest of the system is compatible? I guess he could check system information under Settings to see if this really has i747 firmware or someone's previously successfully "changed" it to a T-Mob phone. Not sure that's possible but I was just thinking ... perhaps a previous J-Tag operation especially if it was purchased in the secondary market.
Click to expand...
Click to collapse
It was purchased as a refurb. Everything under System Setting - About Phone shows up as i747. Completely stuck at this point.
Edit: I just installed an app called Info that shows all relevant build information.
Bootloader version shows as T999UVDMD5
Model is SGH-I747
Build ID I747SEMC1
How can I fix this mismatch?

Headcase_Fargone said:
It was purchased as a refurb. Everything under System Setting - About Phone shows up as i747. Completely stuck at this point.
Edit: I just installed an app called Info that shows all relevant build information.
Bootloader version shows as T999UVDMD5
Model is SGH-I747
Build ID I747SEMC1
How can I fix this mismatch?
Click to expand...
Click to collapse
That would explain it then. Thankfully T999UVDMD5 would appear to be the Bootloader for the T-Mob version running Android 4.1.2 (and not the inflexible 4.3). Have you tried flashing the 4.1.2 bootloader via recovery or, if you are feeling adventurous, the 4.1.1 version? You may find both via the links below ...
(http://www.androidfilehost.com/?fid=23269279319197288)
http://www.androidfilehost.com/?fid=23269279319197287
See also previous thread on updating bootloaders (http://forum.xda-developers.com/showthread.php?t=2321310)

Larry2999 said:
That would explain it then. Thankfully T999UVDMD5 would appear to be the Bootloader for the T-Mob version running Android 4.1.2 (and not the inflexible 4.3). Have you tried flashing the 4.1.2 bootloader via recovery or, if you are feeling adventurous, the 4.1.1 version? You may find both via the links below ...
(http://www.androidfilehost.com/?fid=23269279319197288)
http://www.androidfilehost.com/?fid=23269279319197287
See also previous thread on updating bootloaders (http://forum.xda-developers.com/showthread.php?t=2321310)
Click to expand...
Click to collapse
Tried flashing the first one from stock recovery and got:
Verifying update package...
E:signature verification failed
Installation aborted
I read somewhere that this happens when trying to flash a non-signed file in stock recovery so I installed Clockwork recovery and tried flashing both of those files. They both yield this error:
E:Error in (file path and name)
(Status 7)
Installation aborted.
Tried flashing via TWRP and get:
E:Error executing updater binary in zip (file path and name)
Updating partition details...
Failed

So apparently this phone is already unlocked. Never bought a refurbished phone before so didn't even think to try before unlocking it.
So I guess I don't need to downgrade to 4.1.1 afterall. Where does that leave me? I still have this mismatched bootloader (for the T999 model).
Am I okay to just try flashing a recent ROM like AOKP 4.4?

Headcase_Fargone said:
So apparently this phone is already unlocked. Never bought a refurbished phone before so didn't even think to try before unlocking it.
So I guess I don't need to downgrade to 4.1.1 afterall. Where does that leave me? I still have this mismatched bootloader (for the T999 model).
Am I okay to just try flashing a recent ROM like AOKP 4.4?
Click to expand...
Click to collapse
Looks like we learn all the time. I didn't know you could install a bootloader for one system on another system and still get it to work. Thankfully your phone is unlocked. If the phone is working normally, your best option may be to leave it that way for now although, as we've seen, this could seriously limit firmware upgrade possibilities. It's doubtful whether flashing a custom ROM would help because even custom ROMs don't have their own bootloaders and still have to rely on the manufacturer's bootloader to run. A custom ROM would, therefore, probably leave things the way they are with the bootloader. I'm sure there would be a way to get this done. We just have to research a little bit more.
Maybe, now the phone is unlocked and you probably don't need the lower firmware anymore, you may try updating to 4.3 JB. At this stage, you really have nothing to lose so it may be worth trying.

Hello why you want to downgrad maaaaaaaaad
Sent from my GT-S7500 using xda app-developers app

laith al shishani said:
Hello why you want to downgrad maaaaaaaaad
Sent from my GT-S7500 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to downgrade in order to unlock, but it appears to already be unlocked so that's no longer necessary.
Larry2999 said:
Looks like we learn all the time. I didn't know you could install a bootloader for one system on another system and still get it to work. Thankfully your phone is unlocked. If the phone is working normally, your best option may be to leave it that way for now although, as we've seen, this could seriously limit firmware upgrade possibilities. It's doubtful whether flashing a custom ROM would help because even custom ROMs don't have their own bootloaders and still have to rely on the manufacturer's bootloader to run. A custom ROM would, therefore, probably leave things the way they are with the bootloader. I'm sure there would be a way to get this done. We just have to research a little bit more.
Maybe, now the phone is unlocked and you probably don't need the lower firmware anymore, you may try updating to 4.3 JB. At this stage, you really have nothing to lose so it may be worth trying.
Click to expand...
Click to collapse
So just try flashing AOKP or CM or something via TWRP? Don't the newer ROMs require an updated bootloader?
Edit: Got impatient and tried flashing Cyanogenmod. I used the CM Windows installer to minimize any chances of me screwing up the process. Followed the instructions, installer said installation complete, successfully installed, etc. All it did was do a factory reset. Touchwiz 4.1.2 is still on there.

[Q] Problem with 4.4.2, and with downgrading to 4.2.2

Hi, so after I updated to Kit Kat 4.4.2 on my S4 mini, my phone kept dropping my network (Canada - Bell mobility) randomly usually either ten or twenty minutes after I connect to it but sometimes right away. I've tried taking it in to Bell and I have had the SIM card replaced three times and I've factory reset it numerous times with the problem still occurring. I've been told by a cell phone recovery shop that I could try downgrading back to Jellybean. I've searched for a while and noticed some people have had success with this method -> http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 so I decided to try it out myself. Every time I try to download it onto my phone with Odin I receive an error code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help me with either one of my problems? Any help would be gratefully appreciated.

BoJo963 said:
Hi, so after I updated to Kit Kat 4.4.2 on my S4 mini, my phone kept dropping my network (Canada - Bell mobility) randomly usually either ten or twenty minutes after I connect to it but sometimes right away. I've tried taking it in to Bell and I have had the SIM card replaced three times and I've factory reset it numerous times with the problem still occurring. I've been told by a cell phone recovery shop that I could try downgrading back to Jellybean. I've searched for a while and noticed some people have had success with this method -> http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 so I decided to try it out myself. Every time I try to download it onto my phone with Odin I receive an error code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can somebody please help me with either one of my problems? Any help would be gratefully appreciated.
Click to expand...
Click to collapse
What jelly bean firmware did you try to flash...As I mentioned in the post :: http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 you must use BRAZIL UNBRANDED JELLYBEAN 4.2.2 UBUBNE2
Here is the sammobile link to that firmware page :: http://www.sammobile.com/firmwares/3/?download=30561
Also wipe data, cache and flash the firmware. I downgrade thrice :: from Germany KK, from slovakian KK , Newzealand KK , and Belgium branded KK. Anyway Good luck.

sasank360 said:
What jelly bean firmware did you try to flash...As I mentioned in the post :: http://forum.xda-developers.com/showpost.php?p=53752825&postcount=620 you must use BRAZIL UNBRANDED JELLYBEAN 4.2.2 UBUBNE2
Here is the sammobile link to that firmware page :: http://www.sammobile.com/firmwares/3/?download=30561
Also wipe data, cache and flash the firmware. I downgrade thrice :: from Germany KK, from slovakian KK , Newzealand KK , and Belgium branded KK. Anyway Good luck.
Click to expand...
Click to collapse
I flashed the Brazilian firmware you linked to in your post. Could you please provide links to the firmwares you downgraded to? I'm rather new to this and I have not been able to navigate Sammobile very well. Thank you so much for your time and I apologize for any inconveniences I cause.

BoJo963 said:
I flashed the Brazilian firmware you linked to in your post. Could you please provide links to the firmwares you downgraded to? I'm rather new to this and I have not been able to navigate Sammobile very well. Thank you so much for your time and I apologize for any inconveniences I cause.
Click to expand...
Click to collapse
I do not think you can downgrade further. Brazil UBUBNE2 has same bootloader as kitkat. While older jelly bean firmwares have 1st revision of knox and odin gives fail message when you try to downgrade from UBUBNE2 JB. I tried it only once and it failed, so fearing I might hard brick my phone I never tried that again. I need senior members to confirm what I said.
BTW can you remember the fail message on your phone when odin failed....??
Also I found brazil JB to be very stable and with f4k kernel I had great battery life.

sasank360 said:
I do not think you can downgrade further. Brazil UBUBNE2 has same bootloader as kitkat. While older jelly bean firmwares have 1st revision of knox and odin gives fail message when you try to downgrade from UBUBNE2 JB. I tried it only once and it failed, so fearing I might hard brick my phone I never tried that again. I need senior members to confirm what I said.
Also I found brazil JB to be very stable and with f4k kernel I had great battery life.
Click to expand...
Click to collapse
When I had tried to flash the Brazil UBUBNE2 onto my phone, it gave me the error I posted in the original post. I am only trying to downgrade to it, not past. I re-downloaded the firmware from the link you supplied earlier, and when I tried flashing it onto my phone I received the same error as I posted at the beginning.
Could it be something that I'm doing wrong? I open up Odin, put my phone into download mode, plug my phone into my computer, place the firmware into the AP spot, then I press start, and after a little bit it displays the error. I am using Odin v3.09.

BoJo963 said:
When I had tried to flash the Brazil UBUBNE2 onto my phone, it gave me the error I posted in the original post. I am only trying to downgrade to it, not past. I re-downloaded the firmware from the link you supplied earlier, and when I tried flashing it onto my phone I received the same error as I posted at the beginning.
Could it be something that I'm doing wrong? I open up Odin, put my phone into download mode, plug my phone into my computer, place the firmware into the AP spot, then I press start, and after a little bit it displays the error. I am using Odin v3.09.
Click to expand...
Click to collapse
That is strange. You downloaded the proper firmware from link I gave you and also steps of flashing are correct.
Did you try to remove knox files from firmware??? Or flashed it untouched.
Actually many users did exactly what I did and successfully downgraded. Try one last time after wiping data and cache. Good luck. Also is your device I9195 or any variant of that like I9195L / I9195T. All the above procedure must be done on I9195 international S4 Mini LTE. Good luck.

sasank360 said:
That is strange. You downloaded the proper firmware from link I gave you and also steps of flashing are correct.
Did you try to remove knox files from firmware??? Or flashed it untouched.
Actually many users did exactly what I did and successfully downgraded. Try one last time after wiping data and cache. Good luck. Also is your device I9195 or any variant of that like I9195L / I9195T. All the above procedure must be done on I9195 international S4 Mini LTE. Good luck.
Click to expand...
Click to collapse
I flashed it untouched, I don't know how to remove the knox files. My device's model number is SGH-1257M, so could that be the problem? Am I out of luck for being able to downgrade? If I can't downgrade do you know if there is a way for me to stop losing connection to my cell network, the initial problem I described, that is the reason I want to downgrade my phone.

BoJo963 said:
I flashed it untouched, I don't know how to remove the knox files. My device's model number is SGH-1257M, so could that be the problem? Am I out of luck for being able to downgrade? If I can't downgrade do you know if there is a way for me to stop losing connection to my cell network, the initial problem I described, that is the reason I want to downgrade my phone.
Click to expand...
Click to collapse
THAT IS THE PROBLEM. As you can see the model number of your device is I257M. The firmware you flashed is meant for I9195 international S4 Mini LTE. The phone you have is carrier branded S4 Mini. Not the international one. Do not flash firmwares and ROMs meant for other model numbers. I cannot advise you on SGH-I257M as I have no idea how the kitkat is seeded to that device.
http://www.sammobile.com/firmwares/1/?model=SGH-I257M&pcode=0 --- This is the list of latest firmwares for I257M. Use these firmwares, not I9195 firmwares.

sasank360 said:
THAT IS THE PROBLEM. As you can see the model number of your device is I257M. The firmware you flashed is meant for I9195 international S4 Mini LTE. The phone you have is carrier branded S4 Mini. Not the international one. Do not flash firmwares and ROMs meant for other model numbers. I cannot advise you on SGH-I257M as I have no idea how the kitkat is seeded to that device.
Click to expand...
Click to collapse
Oh, well that is disheartening. Thank you for your time and patience. I really appreciate you trying to help.

BoJo963 said:
Oh, well that is disheartening. Thank you for your time and patience. I really appreciate you trying to help.
Click to expand...
Click to collapse
No mention. It is essential to learn from little mistakes.

[Q] PIT file I9195

Hi everybody !
I have a S4 mini 16gb (GT I9195) locked Verizon. I bought it in hong kong and the problem is that there was already a Custom Rom on it.
I tried to install many ROMs (french and german version) with ODIN to have the menu in french (I'm from Paris). I didn't tried operator one's, only constructor one's and it has always failed.
I tried many ROMs, cables, many version of ODIN and many USB plug but nothing changed it's still stucked on NAND Write fail on the ODIN report.
I think my only option is to flash the PIT and to install a new rom. Many question about it :
Am I right about flashing the PIT ?
Do the PIT have to match with a special ROM when using it with ODIN) or any ROM for S4 mini while match wit a good PIT file?
The biggest problem is that I only found one PIT file corresponding to this phone and it failed. Nothing happened. Is any of you has a PIT file ok ?
Thanks for your help and sorry if my english is not perfect.

What firmware version you have?
I think i9195 is international not carrier specific, then you could flash any firmware as long as you're not downgrading bootloader (Odin will fail downgrading)
Can you post your download screen.

Help!!! please!!!
fburgos said:
What firmware version you have?
I think i9195 is international not carrier specific, then you could flash any firmware as long as you're not downgrading bootloader (Odin will fail downgrading)
Can you post your download screen.
Click to expand...
Click to collapse
Sorry for the late answer, I've been really busy at Work.
I have the 4.2.2.
I tried with many versions of firmware (even the latest downloaded on sammobile but always failed.
I don't know what download screen you want (sorry i'm a total noob).
When I try to flash the PIT Odin fail with this message : "Set PIT file" and the "Fail!". On the Phone i have this message on the download mode screen "Secure check Fail : PIT".
I don't know if it helps.

Samsung S9 plus G965XU (Demo Mode)

Hi i reformatted my Samsung S9 plus G965XU ( DEMO UNIT) with the wrong firmware because i thought it would get rid of the demo version ( i was wrong)
So can anyone here share with me the original firmware that comes with this phone?
Right now im able to get to download mode or recovery mode but recovery mode is locked meaning factory reset settings does not work
Here is the erorr message im getting on the start screen
SS RDX
Subsystem Crashed: MODEM
------------------------------------
DDR Vendor: Samsung
SOC_HW_REVISION: 2.1
Generating summary...
>General info
>DDR info
>DCVS Info
>RPM
>TrustZone
>Hypervisor
>APSS
>Modem
Done!
Click to expand...
Click to collapse

MarkAnthonyMontreal said:
Hi i reformatted my Samsung S9 plus G965XU ( DEMO UNIT) with the wrong firmware because i thought it would get rid of the demo version ( i was wrong)
So can anyone here share with me the original firmware that comes with this phone?
Right now im able to get to download mode or recovery mode but recovery mode is locked meaning factory reset settings does not work
Here is the erorr message im getting on the start screen
Click to expand...
Click to collapse
good luck getting the OG firmware for a demo unit. I have a S7 and S7 edge demo units and theyre finicky. The edge took the g935f firmware just fine and works perfectly. The flat is still being a pain in my as$
id keep trying different firmware revisions on it since its a million to one shot for the demo unit firmware to ever be available

youdoofus said:
good luck getting the OG firmware for a demo unit. I have a S7 and S7 edge demo units and theyre finicky. The edge took the g935f firmware just fine and works perfectly. The flat is still being a pain in my as$
id keep trying different firmware revisions on it since its a million to one shot for the demo unit firmware to ever be available
Click to expand...
Click to collapse
I here yah, so far I was able to reformat it with a SM-G965W but its not getting past the samsung logo as it just keeps going around in a loop

MarkAnthonyMontreal said:
I here yah, so far I was able to reformat it with a SM-G965W but its not getting past the samsung logo as it just keeps going around in a loop
Click to expand...
Click to collapse
Try it again with the exact same stuff but on a different computer and even a different cable, also a fresh download of the firmware. Use the frija tool to download the firmware like literally 4 times faster than from sammobile ditectly

youdoofus said:
Try it again with the exact same stuff but on a different computer and even a different cable, also a fresh download of the firmware. Use the frija tool to download the firmware like literally 4 times faster than from sammobile ditectly
Click to expand...
Click to collapse
Thanks... frija tool yup i came across this tool a few weeks ago. I del;eted the tool because at the time it did not have the Sm-G965XU firmware. For all the troubles that i am having could of been prevented if i had just followed some tutorials on youtube on how to remove the demo screen saver and limitation on 70% charging the phone. I have the receipt still and contacted the cellphone store the same day but because i formatted the phone the warranty for 3 months was void

I was fully aware before purchasing the phone by the store manager whom i know that this particular phone only can be used over wifi for that reason is why i was getting it for only 200.00$ due to the fact that it has no modem or antenna minus a few other things. I just wanted a phone so that when im in bed i can listen to the radio and also because it has a good camera i was planing on taking photos and videos of my cats. Only 5 minutes after arriving at home I was stupid and compulsive reformatted the phone with firmware downloaded from online to my pc with odin and ever since October 1st its been UN-usable

youdoofus said:
The edge took the g935f firmware just fine and works perfectly.
Click to expand...
Click to collapse
do you think the firmware that worked for you could possibly work for me even though mine is 2 generations ahead, i am only guessing because i know with computers you can erase everything on the hard drive and reformat it with Windows, LINUX etc.....

MarkAnthonyMontreal said:
do you think the firmware that worked for you could possibly work for me even though mine is 2 generations ahead, i am only guessing because i know with computers you can erase everything on the hard drive and reformat it with Windows, LINUX etc.....
Click to expand...
Click to collapse
well, there are only 3 versions of the phone. Theres the Exynos, G965U snapdragons and the 9650 snapdragons, so one of the GSI image sets has to work. Unless they did some trickery with the bootloader to make it to where it can only accept a development bootloader or something like that. If thats the case, then youre gonna be on a needle in a haystack chase

youdoofus said:
If thats the case, then youre gonna be on a needle in a haystack chase
Click to expand...
Click to collapse
exactly that

MarkAnthonyMontreal said:
exactly that
Click to expand...
Click to collapse
just to make sure, you did flash the F firmware on it too, right?

Youdoofus said:
just to make sure, you did flash the F firmware on it too, right?
Click to expand...
Click to collapse
yes i did but it not work

S9 plus G965XU LDU and S9 LDU G960XU
Hi,
I have a S9 LDU G960XU
In order to fix this issue you will need to get and flash the original stock LDU modem [all other parts of the rom i believe you can use any firmware that is compatible with G965U or G960U]
I found a website that claims to have this file, I have not tested it so i cannot vouch for it to solve the problem- see link
S9 plus - https://firmware.gem-flash.com/index.php?a=downloads&b=file&id=73412
S9 - https://firmware.gem-flash.com/index.php?a=downloads&b=file&id=73406
the way I removed the demo rom from my S9 was that i flashed a rom i found that does not touch the modem, all other features work including fingerprint, 100% charge, removed all bloatware. basically functions as regular s9 minus the cell capability. Interestingly it "repaired the IMEI" and now my S9 has an IMEI# but it wont recognize any sim cards.
here is the link www.murk.pw/G960XU_CONVERT_TO_G960U_8.0_U1.rar
NOTE: before you lash any rom on LDU you must deactivate the demo app on the device, only after you have deactivated the demo app should you flash this or any rom, otherwise you will get and MDM lock.
The only other way I know how to get the "original modem" from a LDU would be to use easyjtag box to copy the original modem partition on a non-flashed/original rom LDU. and then flash that file on your "problem" LDU, this should fix your issue, as the incorrect modem is triggering the knox or your device.
let us know if this info helped.

yearner said:
Hi,
I have a S9 LDU G960XU
In order to fix this issue you will need to get and flash the original stock LDU modem [all other parts of the rom i believe you can use any firmware that is compatible with G965U or G960U]
I found a website that claims to have this file, I have not tested it so i cannot vouch for it to solve the problem- see link
S9 plus -
S9 -
the way I removed the demo rom from my S9 was that i flashed a rom i found that does not touch the modem, all other features work including fingerprint, 100% charge, removed all bloatware. basically functions as regular s9 minus the cell capability. Interestingly it "repaired the IMEI" and now my S9 has an IMEI# but it wont recognize any sim cards.
here is the link
NOTE: before you lash any rom on LDU you must deactivate the demo app on the device, only after you have deactivated the demo app should you flash this or any rom, otherwise you will get and MDM lock.
The only other way I know how to get the "original modem" from a LDU would be to use easyjtag box to copy the original modem partition on a non-flashed/original rom LDU. and then flash that file on your "problem" LDU, this should fix your issue, as the incorrect modem is triggering the knox or your device.
let us know if this info helped.
Click to expand...
Click to collapse
tried the link for g960XU convert to G960U and it gave me this error in odin:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5045 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> abl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is the rar missing the CP file?
I have the same LDU as you s9 and I flashed the wrong firmware and now just want any firmware to get working device again ( I don't need cellular)

yearner said:
Hi,
I have a S9 LDU G960XU
Click to expand...
Click to collapse
Are you able to send us your complete Samsung S9+ Rom with everything on it because mine got screwed trying to install a different firmware so I really need the original firmware.

70 % charge limit
MarkAnthonyMontreal said:
Thanks... frija tool yup i came across this tool a few weeks ago. I del;eted the tool because at the time it did not have the Sm-G965XU firmware. For all the troubles that i am having could of been prevented if i had just followed some tutorials on youtube on how to remove the demo screen saver and limitation on 70% charging the phone. I have the receipt still and contacted the cellphone store the same day but because i formatted the phone the warranty for 3 months was void
Click to expand...
Click to collapse
Hi just bought a Samsung Tab A 2019 LDU on ebay, every function is fine apart from 70 percent charge limitation, can you please let me know how to remove this. Thanks

[SOLVED] Confused about Odin and SamFirm (also sha256 error).

I want to flash the factory unlocked firmware. As I understand it, this means I need to flash the SM-N975U1 XAA firmware. I'd also like to have the stock VZW firmware in case I want to revert to it, and as I understand it this would be the SM-N975U VZW firmware.
PHONE INFO
- Tmo carrier unlocked, with verizon sim (and therefore verizon bloat apps)
- Software up to date, with Feb 1 patch level
- Build Number QP1A.190711.020.N975USQS2BTA7
- See pics here for more About Phone details
FIRST ISSUE:
- You'll notice if you search SamFirm with Model SM-N975U and Region VZW, it doesn't find anything. It gives this error.
Error: Could not send BinaryInform. Status code 200/666
Could not fetch info for SM-N975U/VZW. Please verify the input or use manual info
Click to expand...
Click to collapse
- Same if you search with Model SM-N975U and Region XAA
- It DOES give results for both regions if you change the model to SM-N975U1. However, the file it downloads for in both cases is absolutely identical from the filename all the way down to the byte size. Filename: SM-N975U1_10_20200118102941_hj8esiossq_fac. And in any case, this doesn't give me a stock firmware to revert back to.
SECOND ISSUE
- When I try to flash the XAA files in Odin I get
<ID:0/006> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
- I understand this is potentially resolvable with a patched Odin, but I'm hesitant to jump right into that given that I'm not totally clear on why Odin isn't finding firmwares and why the ones it DOES find are literally 100% identical despite one being for VZW and one being for XAA.
Any thoughts on where to go from here? Am I doing something wrong? I spent several hours reviewing tens of pages of threads here and in various google searches, and watching a few videos, but nobody's perfect. Thank you guys for any help here!
Updates:
1. With no responses, I tried Frija and it was able to find the SM-N975U VZW firmware and the SM-N975U1 VZW and XAA firmwares.
2. Still, the SM-N975U1 VZW and XAA firmwares are identical, so I just tried to flash the XAA one.
3. I encountered every single complication imaginable:
- Problem: SHA256 error
- Solution: Odin Patched from here, unfortunately it's not the most current version but I crossed my fingers and it didn't brick my device.
- Problem: constant Added!! Removed!! in Odin.
- Solution: try different USB outlet
- Problem: Odin flashing stalls at SetupConnection step
- Solution: Try the official stock USB cable that came with the phone. This is USB-C on both ends, so I'm lucky my computer has the port.
- Problem: The XAA firmware file Frija gave me (again, identical down to the byte to the files produced by SamFirm) is for the Star Wars version.
- Solution: You have to manually set the PDA/CSC/PHONE values in either Frija or SamFirm to get the regular XAA variation. I made an explanation of how to get those values, and as far as I know it's the only one on the internet, here. TLDR, they are as follows:
PDA: N975U1UES2BTA1
CSC: N975U1OYM2BTA1 <-- notice the M instead of Z here (the Star Wars one has a Z)
PHONE: N975U1UES2BTA1

OP updated with resolution.

Find an older version. Flash it and then update through Samsung switch on your PC.

Milly7 said:
Find an older version. Flash it and then update through Samsung switch on your PC.
Click to expand...
Click to collapse
Updating OP with the solution.