[Guide] - eSim Firmware Flash/ Odin Upgrade/ Flashing and N986U to N986U1 & Vice Versa - Samsung Galaxy Note 20 Ultra Guides, News, & Discu

Instructions are updated to get eSIM​INTRODUCTION - Firstly sorry for posting this as this is common knowledge for many. I still see so many people asking the same questions again and again and i do want to help so decided to write a guide.
If you have Odin Flashing questions please ask here. I have converted a device from U to U1 (just for fun) so i know this works, many other users have confirmed this too.
SECTION1​
Pre-Requisites - PC / Laptop, USB Cable, Phone
Switch on USB Debugging from Developer options. To turn on developer options go to Settings>>About Phone>>Software Information>> Then tap the build number 7 times - Developer options will appear at the bottom of Settings Menu.
HOW TO - N986U to N986U1 and or Flash ATID or Flash Any Odin compatible ROM
1. If you want to flash or update to One UI 3 Beta then Download the ATID Firmware here. (This point is old when people were on Android 10 not relevant now)
1. For changing Carrier locked device to Unlocked Firmware (N986U to N986U1) Download the firmware for U1 from OTA Thread or by using Frija
OR​1. For changing unlocked device to Carrier locked Firmware (N986U1 to N986U) Download the firmware for U from OTA Thread or by using Frija - This is usually being done to get eSIM Capability on your phone
If you are Flashing One UI 3 Stable download the appropriate firmware. (This point is old when people were on Android 10 not relevant now)
There are many resources for downloading firmware, there is a thread in the N20 Ultra forums, there are tools like Frija and SamFW and more, then there are various websites. Where you are downloading from is your outlook just ensure you download Odin compatible ROM.
2. Download Patched Odin here
3. Unpack/Unzip what you downloaded in Step 2 (Odin Compatible ROM) and put in a folder. Lets call the folder "Flash"
4. Run Odin, click on BL, Browse to the "Flash" folder, add BL file from there, Do the same for AP (click on AP, Add AP file, this will take some time), Same for CP (click on CP, Add CP file)
NOTE ATTENTION CAREFUL To get eSIM Capability on your phone if you are on bootloader version 2 please see step 5a and Skip Step 5​5 . Click on CSC, Add the file with the name starting with Home_CSC). If you use Home_CSC your phone will not get formatted and data will remain Intact
USERDATA Stays empty.
​5a. Do the same for CSC (click on CSC, Add the file with the name starting with CSC. This will format your phone and your phone will factory reset. You will lose your data and would need to setup your phone like it was new. USERDATA Stays empty.
6. Now connect USB cable to your laptop (Only laptop and not the phone)>> Turn off your phone >> Press volume up and volume down keep them pressed and plug in the USB type C into your phone.
7. You should be in download mode now, press volume up. In Odin you will see that phone is added.
8. Press start in Odin. Wait for it to finish and let the phone restart (it will happen On its own).
9. Done
SECTION 2​HOW TO - N986U or N986U1 Latest Security Patch or Firmware upgrade / downgrade
1. Download the firmware for Corresponding device - For example if you are on SM-N986U1 then download for U1. If you are N986U locked to TMB, VZW, SPR etc etc download the firmware for U device and your Own CSC from OTA Thread or by using Frija or SamFirm tool.
2. If downloaded using Frija or SamFirm Tool it will be in a compressed folder (ZIP). Extract the firmware files in a folder, lets call it "Flash"
Follow the rest of the steps from Step 4 Above.
SECTION 3​Going from one carrier locked device to another one like from ATT to TMob - Use the same instructions as in SECTION1 - just download the appropriate firmware.
FAQ​Can I get E-Sim with this ?
Yes, I have updated the instructions in this post.
If you are doing this to get E-Sim capability that t-mobile just added here is a post from someone who converted their phone to T-Mobile version (Old Post can be ignored)
WARNING - If for some reason you use ODIN to Flash back to Android 10 after being on Android 11, YOU WILL LOSE YOUR DATA
This is not a guide for Downgrading by whole Android Iteration as in Going from Android X to Android (X-1) or Android (X-2) ____ Versions ​

Reserved

I am having trouble with flashing the firmware onto my device. I am trying to convert my SM-N986U to SM-986U1 but every time I try to flash it I get an error. I have everything downloaded and prepared for it but I keep getting errors.

TuxPenguin98 said:
I am having trouble with flashing the firmware onto my device. I am trying to convert my SM-N986U to SM-986U1 but every time I try to flash it I get an error. I have everything downloaded and prepared for it but I keep getting errors.
Click to expand...
Click to collapse
What are the errors?

TuxPenguin98 said:
I am having trouble with flashing the firmware onto my device. I am trying to convert my SM-N986U to SM-986U1 but every time I try to flash it I get an error. I have everything downloaded and prepared for it but I keep getting errors.
Click to expand...
Click to collapse
airmaxx23 said:
What are the errors?
Click to expand...
Click to collapse
Yes tell us more, what are the errors you are getting?

So I'm kinda nervous. I got a message that ATID didn't like the current build. Said error when booted. Only options were to try again, factory reset, or view logs. I have the sm-n986u1

GDHAMTON7 said:
So I'm kinda nervous. I got a message that ATID didn't like the current build. Said error when booted. Only options were to try again, factory reset, or view logs. I have the sm-n986u1
Click to expand...
Click to collapse
ATID didn't like the current build?? Never heard of that error. Do you have a screenshot. How did you flash? Did you use Odin? You can always try again.. And worst case force reboot your phone..
Sent from my SM-N986U1 using Tapatalk

warriorvibhu said:
ATID didn't like the current build?? Never heard of that error. Do you have a screenshot. How did you flash? Did you use Odin? You can always try again.. And worst case force reboot your phone..
Click to expand...
Click to collapse
Unfortunately I didn't get a screenshot but it said something like there was an error with files or something. Either way I had a back up. I was already on the regular atj5 build on android 10. It is all working now.

GDHAMTON7 said:
Unfortunately I didn't get a screenshot but it said something like there was an error with files or something. Either way I had a back up. I was already on the regular atj5 build on android 10. It is all working now.
Click to expand...
Click to collapse
So you were able to get Beta?
Sent from my SM-N986U1 using Tapatalk

warriorvibhu said:
So you were able to get Beta?
Click to expand...
Click to collapse
I was. The members app works as well. Thank you

Thanks changed from AT&T to XAA. But damn bloatware on phone with ATT firmware is more worst then in europe.

I have been trying to odin my att note 20 ultra to the t-mobile firmware, so far I've only been able to get it to boot like it is the unlocked version, and can't find the reason

c-prodigo said:
I have been trying to odin my att note 20 ultra to the t-mobile firmware, so far I've only been able to get it to boot like it is the unlocked version, and can't find the reason
Click to expand...
Click to collapse
I dont know anyone who has done such a thing but i guess there is a use case for everything. Have you tried flashing unlocked Variant first and then Odin to T-Mobile.

that's exactly what I did, I switched from att to t-mobile, and first I wanted to see how the unlocked version would work, now I want to try the t-mobile firmware, but after downloading the one that says t-mobile and using odin, the phone stays on the unlocked firmware

c-prodigo said:
that's exactly what I did, I switched from att to t-mobile, and first I wanted to see how the unlocked version would work, now I want to try the t-mobile firmware, but after downloading the one that says t-mobile and using odin, the phone stays on the unlocked firmware
Click to expand...
Click to collapse
Which T-Mobile firmware?
If you want carrier stuff you have to change your CSC to TMB and flash U version not U1 version.

rjohnstone said:
Which T-Mobile firmware?
If you want carrier stuff you have to change your CSC to TMB and flash U version not U1 version.
Click to expand...
Click to collapse
Exactly
c-prodigo said:
that's exactly what I did, I switched from att to t-mobile, and first I wanted to see how the unlocked version would work, now I want to try the t-mobile firmware, but after downloading the one that says t-mobile and using odin, the phone stays on the unlocked firmware
Click to expand...
Click to collapse
Hope you downloaded a U firmware and not U1, CSC can be T-mobile on U1 too so make sure you download U firmware and hope you are not confusing CSC with T-Mobile firmware

I am trying to switch from U1 to U VZW brand. I get this error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 9881 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!

mariuszsnit said:
I am trying to switch from U1 to U VZW brand. I get this error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 9881 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Click to expand...
Click to collapse
Are you trying to go from the unlocked 3.1 DUC1 build to VZW firmware? They updated the bootloader from BL1 to BL2 on DUC1 so we are not able to roll back to anything older. The VZW firmware is still on BL1.
If that is the case will have to wait for VZW to release new firmware with BL2 before you can switch. My guess would be it will be included in next months security patch update.

Great guide to people like me that are thinking about dipping their toes in for the first time when it comes to flashing. I do have a question or two though:
What are the advantages of flashing from a U device to the unlocked U1 version? For instance I have the T-mobile U version and I have for the most part uninstalled all the carrier bloatware that came with it and put the ones that I couldn't into deep sleep so my battery life for the most part is unaffected. I also got it unlocked when I first got it since I paid outright for it. I notice most people also like getting updates faster and flashing enables them to do so but I honestly don't mind waiting for the slower OTA ones.
I guess I'm looking for a reason to do this (bored too) and use it as a learning process as well to gain the experience since I've never flashed before. Are there any settings or features in the U1 devices that I can't get from the play store that I can get by flashing? The only feature I truly miss is call recording but I don't think anyone has been able to figure that out yet..

dj24 said:
Great guide to people like me that are thinking about dipping their toes in for the first time when it comes to flashing. I do have a question or two though:
What are the advantages of flashing from a U device to the unlocked U1 version? For instance I have the T-mobile U version and I have for the most part uninstalled all the carrier bloatware that came with it and put the ones that I couldn't into deep sleep so my battery life for the most part is unaffected. I also got it unlocked when I first got it since I paid outright for it. I notice most people also like getting updates faster and flashing enables them to do so but I honestly don't mind waiting for the slower OTA ones.
I guess I'm looking for a reason to do this (bored too) and use it as a learning process as well to gain the experience since I've never flashed before. Are there any settings or features in the U1 devices that I can't get from the play store that I can get by flashing? The only feature I truly miss is call recording but I don't think anyone has been able to figure that out yet..
Click to expand...
Click to collapse
It mostly comes down to bloat and unlocked devices being eligible for beta programs. They used to do beta programs for some carriers but it seems to be happening less.
For the most part there isn't much difference. I've been toying with the idea of switching my unlocked to Verizon firmware to get RCS which Verizon recently activated for several Samsung devices. Was hoping it would come for the unlocked phones but doesn't look like it will. Haven't heard anything about the google/samsung RCS partnership in months.

Related

[Q] Q: Un-rooting / flashing stock Note 3 - HELP

Hello there,
I have looked through the forums and have attempted various different tutorials on how to un-root and flash back to the stock firmware. I am with Rogers Wireless (Canada), and have downloaded Odin and N900W8VLUBMI5_N900W8OYABMI5_RWC which is the rogers firmware for my device. Every time I connect my device to Odin in download mode, select PDA / AP, I get an error log with the following:
Code:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLUBMI5_N900W8OYABMI5_N900W8VLUBMI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone itself, I see:
"SW REV CHECK FAIL: [sb1]Fused 2 > Binary 1"
I cannot seem to flash it, no matter what I do.
Any help is appreciated, I would really like to flash back to the stock firmware and remove root. Thank you.
bustin.droid said:
...
On the phone itself, I see:
"SW REV CHECK FAIL: [sb1]Fused 2 > Binary 1"
I cannot seem to flash it, no matter what I do.
Any help is appreciated, I would really like to flash back to the stock firmware and remove root. Thank you.
Click to expand...
Click to collapse
You are currently on a newer firmware (you can check it in Settings/About or with *#1234# ). You are on a new bootloader and you will not be able to return to an older firmware. Check your knox status - if that is 0x1 you will also never be able to make it back to 0x0. Read around for more info (but generally you should be able to write the latest ROM from your carrier, and that should also remove root).
xclub_101 said:
You are currently on a newer firmware (you can check it in Settings/About or with *#1234# ). You are on a new bootloader and you will not be able to return to an older firmware. Check your knox status - if that is 0x1 you will also never be able to make it back to 0x0. Read around for more info (but generally you should be able to write the latest ROM from your carrier, and that should also remove root).
Click to expand...
Click to collapse
Thank you for the reply,
I see that knox is set to 0x1, doh. Where would I be able to find / download the same / latest firmware for my Rogers Wireless Note 3?
Edit: Found it, thank you. So there will NEVER be a way to trip knox back to 0x0?
bustin.droid said:
Thank you for the reply,
I see that knox is set to 0x1, doh. Should I be able to download the latest firmware from the Rogers website?
Click to expand...
Click to collapse
I don't know about Rogers, but for instance you can look here:
http://www.sammobile.com/firmwares/1/?model=SM-N900W8&pcode=RWC#firmware
There is also another option that might also work - with Kies 3 using Tools -> Emergency firmware recovery - but I believe you might need the latest Kies version and even that one might not work. (I consider that one a little safer only in the fact that if something very bad happens you might get away with free service on it by saying Kies created the problem, while saying that you bricked the phone in Odin will guarantee that service will NOT be covered by warranty).
xclub_101 said:
You are currently on a newer firmware (you can check it in Settings/About or with *#1234# ). You are on a new bootloader and you will not be able to return to an older firmware. Check your knox status - if that is 0x1 you will also never be able to make it back to 0x0. Read around for more info (but generally you should be able to write the latest ROM from your carrier, and that should also remove root).
Click to expand...
Click to collapse
i had the same thing when i flashed the 4.4.2 into hongkong one, same happened and it is stuck,
i cant flash either 4.4.2 not hongkong,
any ideas with thanks.
xclub_101 said:
I don't know about Rogers, but for instance you can look here:
http://www.sammobile.com/firmwares/1/?model=SM-N900W8&pcode=RWC#firmware
There is also another option that might also work - with Kies 3 using Tools -> Emergency firmware recovery - but I believe you might need the latest Kies version and even that one might not work. (I consider that one a little safer only in the fact that if something very bad happens you might get away with free service on it by saying Kies created the problem, while saying that you bricked the phone in Odin will guarantee that service will NOT be covered by warranty).
Click to expand...
Click to collapse
your right, kies does helps, but was wondering can we blame kies for the 0x1 when flashing back to stock if we do a warrenty exchange through the carrier? haha
After I flashed Poland 4.4.2 rom I lost my warranty and Knox now 0×1. ANY ideas how to fix it.
Sent from my SM-N9005 using XDA Premium 4 mobile app

[Q] Rerooting Samsung I337

I apologize if my situation is here somewhere. I have read through so many forums and can't find what I need, plus I am sort of new at this. So here goes.
I rooted my Samsung I337 about 8 months ago for the first time. I can't remember exactly how, but I followed a thread here to do it. It worked perfectly! I then flashed the Golden Eye rom to it through TWRP. I have loved it since then. I did a back up of my original rom on my phone from the start. Well, I decided yesterday to unroot it. I followed the directions from a thread here and it seems to have worked except that when I turn it on, the custom screen is first. However, I have no supersu and when I try to get rooting apps it tells me I need to root my phone. So I assume it worked.
Well, I have used it for a day and now remember why I rooted it in the first place. I want to put it back but can't seem to do that. I downloaded Odin, connected my phone, and when I try and download the file to it, it fails. This is what I get.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The only thing I can see is that I am told the COM port should be yellow and mine is blue. Does that make a difference? What could the issue be? Any help would be awesome!
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
traderkat64 said:
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
Click to expand...
Click to collapse
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
DeadlySin9 said:
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
Click to expand...
Click to collapse
Ok, I won't update!! Thanks!!!!

Bricked Galaxy S5 (G900V) after attempted root, no methods fix so far

Hi all,
I am new to rooting (first attempted root) and working with Android, so I'm not familiar with all the jargon.
Earlier I attempted to root my Galaxy S5 (G900V) using jrkruise's guide (http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370). Following the guide closely, after running root.bat I used Odin as per the instructions at the end of the root.bat program. Odin gave me the notification that it was successful. So as per the instructions I attempted to turn on my phone, however it was stuck at the Samsung Galaxy S5 screen.
I have tried factory reset/format and clearing data cache to no avail. I have also tried putting a stock ROM back on via Odin and was met with this message.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please let me know if you have any other fixes that may be able to fix this type of problem, thanks.
UPDATE: I was able to solve my problem flashing the following ROM: https://www.androidfilehost.com/?fid=24438995911970571. This could be helpful for anyone with similar problems, so I will leave this thread up for anyone having troubles.
I was following the exact same directions and ended up with the same issue. Did you try the root process again and find out where you (and probably I) messed up while following the directions on your given link? Before rooting I purchased SuperSu Me, but never opened it. You seem to be a little ahead of me, but I'm also in your boat. I hope to find out your result.
jd13 said:
Hi all,
I am new to rooting (first attempted root) and working with Android, so I'm not familiar with all the jargon.
Earlier I attempted to root my Galaxy S5 (G900V) using jrkruise's guide (http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370). Following the guide closely, after running root.bat I used Odin as per the instructions at the end of the root.bat program. Odin gave me the notification that it was successful. So as per the instructions I attempted to turn on my phone, however it was stuck at the Samsung Galaxy S5 screen.
I have tried factory reset/format and clearing data cache to no avail. I have also tried putting a stock ROM back on via Odin and was met with this message.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please let me know if you have any other fixes that may be able to fix this type of problem, thanks.
UPDATE: I was able to solve my problem flashing the following ROM: https://www.androidfilehost.com/?fid=24438995911970571. This could be helpful for anyone with similar problems, so I will leave this thread up for anyone having troubles.
Click to expand...
Click to collapse
duece29203 said:
I was following the exact same directions and ended up with the same issue. Did you try the root process again and find out where you (and probably I) messed up while following the directions on your given link? Before rooting I purchased SuperSu Me, but never opened it. You seem to be a little ahead of me, but I'm also in your boat. I hope to find out your result.
Click to expand...
Click to collapse
Nope, I'm not entirely sure where I messed up in the first place. I haven't tried the root process again and intend to wait a while before trying again, I don't want to risk bricking/messing up my phone right now. Next time I think I'll be more careful following the instructions configuring the King Root .apk.
Well I went ahead and gave it a 2nd try and had success! Here are some notes that will help you.
1. Do factory reset so nothing is in the way and start up your cell, copy and past over KingRoot, & install it.
2. At this time also copy over Knox_Removal_SU_BB_INIT.D.zip (The actual whole .zip file) to a folder on your device
3. I "Prepared My Phone For Root" at the bottom of the steps and then went to the top and ran root.bat and then root2.bat. I did get hung up on the "Samsung Galaxy S5" screen again, but I looked at the command prompt screen that opens with root.bat and it was prepared for that situation and had directions for me to follow. I followed those directions and was able to boot up. At this point I went to the Play store, signed in, and installed the SuperSU Me paid app and followed the directions.
4. On Step 6 of the directions, it says to flash OK3, but I noticed the BPB1 file (and saw it was newer when the developer added it) and used it instead as it is newer software.
5. Everything else ran smooth, when you're asked to install the Knox Removal .zip, it's on your device, just find the .zip file itself and open/run it.
Hope this information helps and now I'm off to figure out how I can use the hotspot feature, given I have unlimited data. (That was my entire purpose for rooting)
duece29203 said:
Well I went ahead and gave it a 2nd try and had success! Here are some notes that will help you.
1. Do factory reset so nothing is in the way and start up your cell, copy and past over KingRoot, & install it.
2. At this time also copy over Knox_Removal_SU_BB_INIT.D.zip (The actual whole .zip file) to a folder on your device
3. I "Prepared My Phone For Root" at the bottom of the steps and then went to the top and ran root.bat and then root2.bat. I did get hung up on the "Samsung Galaxy S5" screen again, but I looked at the command prompt screen that opens with root.bat and it was prepared for that situation and had directions for me to follow. I followed those directions and was able to boot up. At this point I went to the Play store, signed in, and installed the SuperSU Me paid app and followed the directions.
4. On Step 6 of the directions, it says to flash OK3, but I noticed the BPB1 file (and saw it was newer when the developer added it) and used it instead as it is newer software.
5. Everything else ran smooth, when you're asked to install the Knox Removal .zip, it's on your device, just find the .zip file itself and open/run it.
Hope this information helps and now I'm off to figure out how I can use the hotspot feature, given I have unlimited data. (That was my entire purpose for rooting)
Click to expand...
Click to collapse
Great, thanks a lot! Haven't tried this yet, but I'm hopeful - will update thread after I try this (probably not any time soon, on vacation and don't want to brick my phone and spend vacation trying to fix it)

N930TUVU2API4_CL9115549_QB10937257_REV00_user_low_ ship_MULTI_CERT

Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Good one bud.... I can't get it last night but I'm glad u did[emoji106]
TwisT3DroiD_N920T
Threads of this nature do not belong in the development section. Please read the sticky titled "Rules for Posting in Development" before posting in there again.
THREAD MOVED
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
PhilPan said:
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
yes, as odin wipes your internal card and firmware..
PhilPan said:
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
just factory reset.....poof root gone!
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
ted77usa said:
Good one bud.... I can't get it last night but I'm glad u did[emoji106]
TwisT3DroiD_N920T
Click to expand...
Click to collapse
Throwing you in the mix as well. Please see my post above.
-BoneZ- said:
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
Throwing you in the mix as well. Please see my post above.
Click to expand...
Click to collapse
@-BoneZ-
U said that u tried to go back to stock from root? Meaning u have pgc firmware and u CAN'T use this PI4 firmware to go back to stock..... when u do that u stuck with newer Bootloader and u not able to root again.... if u need to go back then flash PGC original firmware.
EDIT:
If u already on PI4 then flash all at once.... BL AP CP CSC....
TwisT3DroiD_N920T
-BoneZ- said:
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
Throwing you in the mix as well. Please see my post above.
Click to expand...
Click to collapse
Yes you must flash all parts of this to be on stock PI4 ROM. But remember that you will lose root and not get it back.
You sir are a life saver thank you so much i was stupid didnt read thru forums and tried to root on the latest update...this flashed via odin brought my phone back to life
ted77usa said:
@-BoneZ-
U said that u tried to go back to stock from root? Meaning u have pgc firmware and u CAN'T use this PI4 firmware to go back to stock..... when u do that u stuck with newer Bootloader and u not able to root again.... if u need to go back then flash PGC original firmware.
EDIT:
If u already on PI4 then flash all at once.... BL AP CP CSC....
TwisT3DroiD_N920T
Click to expand...
Click to collapse
galaxyuser88 said:
Yes you must flash all parts of this to be on stock PI4 ROM. But remember that you will lose root and not get it back.
Click to expand...
Click to collapse
Thanks, guys. Those were the answers I was looking for.
Hello I want to say thank you for providing the T-Mobile Firmware Package for restoring the Note 7 to its original state after a Rooting atampt botched up. I also had this problem but now restored the phone with the supplied firmware. Thank you.
I do have one problem though. The firmware supplied has the first update with the annoying Safety Recall statement in that hugh box while plug is inserted, pulled out and turned on. I like to know if you can supply the original firmware that the phone came boxed with or if you have some kind of way of getting rid of that stupid annoying big box message that pops up all the time.
And again thank you so much.
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
mikesx4911 said:
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
Click to expand...
Click to collapse
Have you tried this yet?
★[ROM] [STOCK] N930TUVU1APGC | 6.0.1 |… | T-Mobile Samsung Galaxy Note 7
http://forum.xda-developers.com/tmo...om-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
mikesx4911 said:
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
Click to expand...
Click to collapse
If you can restore it back to stock. This thread may help. It's helping me.
Need help with Package Disabler 6.3 | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/help-package-disabler-6-3-t3494052
So I just tried to do the instructions from the ROM STOCK below however I get stuck on step 5 when I try to flash the "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRM WARE.tar.md5" it FAILS at
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> adspso.bin
<ID:0/003> apdp.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth) <------------------------
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I than did a quick search had someone suggest checking "re-partition" that also failed with the same error. After rebooting the phone it wouldn't boot anymore and was stuck at "an error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software"
So I gave that a go and it tells me that the device is not supported after doing the model and serial number lol.
ConcernedCustomer said:
Have you tried this yet?
★[ROM] [STOCK] N930TUVU1APGC | 6.0.1 |… | T-Mobile Samsung Galaxy Note 7
http://forum.xda-developers.com/tmo...om-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
If you can restore it back to stock. This thread may help. It's helping me.
Need help with Package Disabler 6.3 | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/help-package-disabler-6-3-t3494052
Click to expand...
Click to collapse
mikesx4911 said:
So I just tried to do the instructions from the ROM STOCK below however I get stuck on step 5 when I try to flash the "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRM WARE.tar.md5" it FAILS at
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> adspso.bin
<ID:0/003> apdp.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth) <------------------------
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I than did a quick search had someone suggest checking "re-partition" that also failed with the same error. After rebooting the phone it wouldn't boot anymore and was stuck at "an error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software"
So I gave that a go and it tells me that the device is not supported after doing the model and serial number lol.
Click to expand...
Click to collapse
I was able to stop the 60% update with package disabler, but was also trying to go back to pgc update...getting the same fails as you. 3 Button into recovery and wipe everything then reboot. Should start you fresh to use the phone
Sent from my SM-G935T using XDA-Developers mobile app
ArmyofTracy said:
I was able to stop the 60% update with package disabler, but was also trying to go back to pgc update...getting the same fails as you. 3 Button into recovery and wipe everything then reboot. Should start you fresh to use the phone
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
If only it was that easy. As of now I can't even get into android it fails to boot. I cleared cache and factory reset and still won't boot. I'm sure I will have to flash now for sure from recovery or download mode. I think Samsung is ****n with us somehow to not let us flash.
mikesx4911 said:
If only it was that easy. As of now I can't even get into android it fails to boot. I cleared cache and factory reset and still won't boot. I'm sure I will have to flash now for sure from recovery or download mode. I think Samsung is ****n with us somehow to not let us flash.
Click to expand...
Click to collapse
The same thing happened to me. I re-flashed to the recent firmware I had installed originally (the one with the big ugly safety recall message from September). I flashed everything at once BL, AP, CP and CSC(I used the HOME_CSC_*.tar.md5 named file because I was returning to stock)
This site appears to be an archive for all Android devices. You can find the firmware of your phone using the model going back to launch date.
Download Firmware – Samsung Update
http://updato.com/firmware-archive-select-model
I think you will find this thread useful as well. It contains definitions and explanations on flashing and working with Odin. I just wish there was more information.
Good luck
Galaxy Note 7 All-In-One Information & A… | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/galaxy-note-7-one-information-answers-t3448689
Is there a way too get back to PGC? That was the one before the recall? I've tried flashing it and it fails
Sent from my SM-G935T using XDA-Developers mobile app
ConcernedCustomer said:
The same thing happened to me. I re-flashed to the recent firmware I had installed originally (the one with the big ugly safety recall message from September). I flashed everything at once BL, AP, CP and CSC(I used the HOME_CSC_*.tar.md5 named file because I was returning to stock)
This site appears to be an archive for all Android devices. You can find the firmware of your phone using the model going back to launch date.
Download Firmware – Samsung Update
http://updato.com/firmware-archive-select-model
I think you will find this thread useful as well. It contains definitions and explanations on flashing and working with Odin. I just wish there was more information.
Good luck
Galaxy Note 7 All-In-One Information & A… | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/galaxy-note-7-one-information-answers-t3448689
Click to expand...
Click to collapse
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Failed again... Tried both CSC files

Need help updating galaxy s8 active [email protected]

Im having an issue with my att s8 active, it has not updated since june 26th 2018 and according to att its 4 updates behind and i cant get the pie update. After spending all day on the phone with the useless insurion and samsung support as they either wanted my deductible to replace my phone or send it in and lose it for a few weeks. Is there anyway to update it by odin and firmware, if so is there a link to the last 4 firmwares? I have flashed using odin before on previous galaxies and im comfortable doing it again if its possible. My phone is not unlocked or rooted and I dont need it to be.
My current base band is G892AUCS2BRF2 and im in the us
jd14771 said:
im just going to reply here so if anyone else has this issue its in the right forum.
Have you performed a factory reset yet? dumb question but the easiest to ask.
Click to expand...
Click to collapse
yes I have, I have been thru everything with samsung and att. Now im trying my luck here, I have downloaded firmware G892AUCS2BRF2 and the new pie 9.0 G892AUCU5CSF8 I cannot get odin to install either one. It either hangs and crashes at initialization or gives me a fail
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6082 M
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
jd14771 said:
Alright, next two stupid questions. Is USB debugging enabled?
Are you running odin as an administrator?
Click to expand...
Click to collapse
yes and yes there is no such thing as stupid questions only stupid software problems
jd14771 said:
Have you tried using odin3b instead of the official odin?
Click to expand...
Click to collapse
If you are referring to this https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Yes i have tried both versions he has down there to download.
jd14771 said:
Last thing i can think of at the moment is trying another source for the update files. possibly they are corrupt seeing as they are not available from sammobile, you are relying on people uploaing it themselves, so the chances the update is compromised is pretty good.
Click to expand...
Click to collapse
pulled them from this thread https://forum.xda-developers.com/ga...ctive-stock-odin-t3667204/page18#post79978095
the new pie update only has one link as well as the G892AUCS2BRF2 I dont know where else to get them as its hard to trust any page. I havent been around a while so im out of the loop. I kept my active stock so i wouldnt have to do any of this put it just stopped receiving ota updates june of last year
Edit: weird thing is att advanced tech showed my phone as receiving the update.
jd14771 said:
which one did you download? the one from post #1, or a more recent one posted in the comments?
have you tried this one? (from that thread)
https://drive.google.com/file/d/1bw-cYNY1KoEH4Pa-a9dJRQJW09r_uw93/view
G892AUCU5CSF8
Click to expand...
Click to collapse
Ill be safe and redownload that link and try again
Nope:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 6082 M
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
jd14771 said:
alright. Give this one a go. The file name is still as it was when pulled from the device, so it seems untouched.
https://drive.google.com/uc?id=1v2wrmevn2acw7i6k8dmxaz5uktakj6b9
while that downloads can i get your imei
Click to expand...
Click to collapse
357712081494899
edit: fail on the rj one
jd14771 said:
can you post a screenshot of
settings > about phone > software information
Click to expand...
Click to collapse
https://photos.app.goo.gl/bBoj2GXaRyuXa51J9
jd14771 said:
makes absolutley no sense. no sense at all. What i did was suugest trying to install software with bootloader V3 and V5. it make's no sense that this is not taking the files.
Do you have samsung's usb drivers installed on your computer?
Click to expand...
Click to collapse
yep even reinstalled them, broke out an old laptop going to try that.
edit: THERE IS HOPE currently flashing on the laptop!!
ironcobra said:
yep even reinstalled them, broke out an old laptop going to try that.
edit: THERE IS HOPE currently flashing on the laptop!!
Click to expand...
Click to collapse
edit 2: Successful flash finally, there must be a conflict on my build of windows or my chipset drivers.
jd14771 said:
litterally the last thing icould suggest that i believe has a chance of working is flashing the latest Tmobile rom from sammobile.
use this tool (requires 2 Microsoft add ons, read the post) to download the firmware quick.
with the tool running, enter
Code:
Model: SM-G892U
Region: TMB
AUTO (check this box)
binary nature (check this box)
->select check update
make sure to check "Check CRC32" and "Decrpyt Automatically"
->select "Download"
If that fails, then my best suggestion is to visit a samsung repair center near you and have them update it. i confirmed with samsung chat that they can do it. you should call them to verify they will though and if it incurs a charge.
---------- Post added at 02:53 AM ---------- Previous post was at 02:48 AM ----------
can you post detailed specs of each machine? ive seen a few people with your same issue. would help others diagnose the issue if its computer related.
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/1x7SLSotHVDuGhcbnnRRD6PK7ndcvCUj3?usp=sharing
Mine the ryzen system is the problem pc, thanks for the help though really appreciate it.
jd14771 said:
interesting- the main difference that i can see is that your PC does not have Secure boot enabled, while hers does.
your device encryption support status
Code:
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
i can't list hers because it says elevation required to view, but im willing to bet that might be the problem? idk. if you feel like it, boot into your bios and enable secure boot, and see if it allows you to re-flash the same files you are flashing now when its done. eaither it will be a quick no, or samsung ODIN requires secure boot to work.
Click to expand...
Click to collapse
Ill check into it thanks

Categories

Resources