Samsung S20FE SM-G780F/DS soft bricked? - Samsung Galaxy S20 FE Questions & Answers

Hello
my sister somehow managed to soft brick the phone.
It started randomly rebooting, then she ask for my help, i started android update (phone is 2yrs old and was never updated). I thought this would solve the problem, my plan B was factory reset.
But just when phone was installing the update it rebooted and never booted again.
I did factory reset (factory mode), didnt help.
Downloaded fresh latest firmware from sammobile, flashed with Odin and still doesnt work. Odin says that everything was OK.
I may or may not download wrong firmware tho, on the invoice for the phone it says SM-G780/DS but i can not find /DS version anywhere?(i suppose this is irrelevant?)
Any help here? Should i root my phone and try flash firmware with TWRP?
***EDIT***
phone rebooted while i was doing system update from Android 11 to Android 12. My guess is that this somehow bricked the phone.

Earlier i downloaded Android 12, Odin successfully installed it but phone didnt work.
Now I tried download Android 12 and i get this error
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 9673 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> up_param.bin
<ID:0/004> ldfw.img
<ID:0/004> FAIL!

I am really lost here.
I searched xda forums/google and if I am not wrong i should somehow unloc OEM before flashing any OS on the phone?.
OEM was never unlocked in develop. options. Is there a way to unlock it with ADB or somehow ?
Tried to flash TWRP but i got error on the phone saying OEM LOCKED

How to fix the missing OEM Unlock button on the Samsung Galaxy S9/S8/Note 8
try to follow this guide so you can see unlocked bootloader if its hidden.
then you can flash without errors hope it helps

you can get new phone if you have warranty

dehumless said:
I searched xda forums/google and if I am not wrong i should somehow unloc OEM before flashing any OS on the phone?.
Click to expand...
Click to collapse
This is incorrect. It's not needed if you're flashing stock fw.
dehumless said:
SM-G780/DS
Click to expand...
Click to collapse
It looks like it's missing a letter before the /DS. What does download mode say your model is?

Related

[Q] I messed up my girlfriend’s GalaxyS ….

Pleaseeee help ….. I am stuck in the downloading mode
Dear experts
I have messed up my girlfriend’s GalaxyS ….
I rooted her phone by following ChainFire’s thread http://forum.xda-developers.com/showthread.php?t=1056334
Followed every step and rooted phone ….Things went smooth…then suddenly phone keep dying in few hours even if its fully charged …. I thought of reapeting the whole process incase I made mistake at any stage
I run the Odin v1.85, selected “CF-Root-XX_OXA_JVO-v3.2-CWM3RFS.tar” file in PDA and click on start…..Suddenly my phone died and Odin said successful 0/ Failed 1
I got in panic mode and start the whole process again…. Since then phone is in Downloading mode.....
Then Magic happen and i got following msg frm Odin
<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> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/004> Added!!
Then as per instruction after phone get rebooted i run superoneclick and click on Root... Its been almost 2 hours and i am having following msg on superoneclick...
Running psneuter....
Pleaseeeeeeeeeeeeeeeeeeeeeeee help me to get it up & running
Waiting for experts to save my relationship
Pleaseeeee help me guys
What to do next?
If you flash cf root kernel you will get root.You don't need superone click.
Try reboot your phone it should work.
Sent from Galaxy on latest nightly with neo kernel
First of all... what was the original firmware?
Second: I hope you have not messed with repartition and bootloader?
yeah, check what version she's running and flash cf-root, since you allready are capable of flashing with Odin you dont need one-click root.
Sent from my GT-I9000 using XDA App
Dear all,
Many Many thanks for your time & reply...
I did reboot at least 3 times... Still having same problem... very strange problem
I have fully charge the phone. Everything is working fine, did my msgs, reply to email, took few pics...upload them....SO far so good, happy happy happyy so put the phone on side & had dinner, picked up phone again and it was off...have to press power button long enough to start the phone... Works fine, shows little drain on battery..put it aside for while and it will be off strangely... Have to restart it by pressing power button on for long enough and it does start, work well and once put it on side for while it goes off .... (My girlfriend is mad at me ;-p ... Dont know how to solve this )
Please help guys ... Here is the required details...
Original-->
Firmware 2.3.3
Kernel 2.6.35.7 I9000xxJV0-CL182937
Build number Gingerbread.XXJVO
Does this info will help you to find the fault?
Really need help...
Many Thanks
Reflash the stock rom again just to be on the safe side.

How to restore stock

My rooted T-mobile Note did not like the OTA update it received today (hung at the samsung logo). I reflashed the rooted UVLG3 firmware image, following the instructions at http://androidlegend.com/how-to-root-t-mobile-galaxy-note-sgh-t879/. This worked, and I'm ignoring the OTA update for now.
I don't need root anymore, i didn't really use it anyways, I would like to get back to stock.
How do i get back to the stock/factory image? From http://forum.xda-developers.com/showthread.php?t=1837907, I see items B (T879-STOCK RECOVERY IMAGE) and D (T879-STOCK BOOT IMAGE). In ODIN, do I need to load one or both of these in one the sections (Bootloader, PDA, Phone, CSC, or UMS) and would i then hit the "Start" button?
Thanks for any help.
Just go to Samfirmware.com and download the tar file for the T879. Put it in the PDA section and start.
Sent from my SAMSUNG-SGH-I717 using xda premium
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<ID:0/004> Added!!
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
How can i rooting the phone if i want to keep stock rom?
Do i have to do same as regular root?
Thank you.
Sent from my SGH-T879 using xda premium
I got it
Sent from my SAMSUNG-SGH-T879 using xda premium
bigape-revamped said:
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<ID:0/004> Added!!
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
Click to expand...
Click to collapse
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Just remember to flash the flash counter zip if u need to send it over to repairs with Samsung cus if they know ur phone is rooted they won't fix it cus rooting a device voids ur warranty... I flashcounter.zip everything I flash a rom... I usually flash that file last...
Sent from my SGH-T879 using xda premium
thanks all I just learn something from this:good:
Problem solved
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
Got it going. Had to jump on a Windows XP 32 bit PC to get the USB drivers to see the phone. Thanks for the help.
Running great on stock.
I have the update on my status bar but I'm wondering what did the update do for u? Can u post a screen shot of ur about phone info? Thnx
Sent from my SGH-T879 using xda premium
I'm curious, can I flash the stock everything of t879 on my at&t note? I have the i717 switched fully to t-mobile with twrp. I want the ota to upgrade from 4.04
Sent from my SGH-T879 using Tapatalk 2
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
I had to flash TWRP temporarily and wipe the phones emmc and flash the stock ROM again above instruction and worked. I guess before doing anything you should wipe/factory reset your phone first before flashing the stock ROM, this I can't test but just based on logical explanation.
My solution for being stuck on the Samsung logo
I know the last post was done a year earlier, but I thought I'd share this information I learned yesterday. After numerous flashing attempts My Note was stuck on the samsung logo.
I had soft bricked my Note by not clearing out the data on my phone. The previous post here gave me a clue and not being really good at this, I wasn't able to install and get TWRP to play nice with my non-working stock rom image. But I was still able to get the the Samsung Recovery and Download modes.
The working solution (borrowed from a post by andersbot on another thread) was:
1. Go to Recovery mode. Do a "clear cache" and next a "wipe data". Then reboot.
2. Go to Download mode and then connect to a XP PC and start up Odin. Be sure to use the latest Samsung USB drivers.
3. Flash with Odin using ther stock firmware downloaded from sammobile.com. Only tick the boxes for f.reset time and autoreboot (Odin default). Click PDA and load the downloaded file renamed with .tar at the end instead of .tar.md 5.
I dont know if this was the easiest way to clear the data on my SGH-T879, but it worked, and my Note started up correctly with the stock rom.

Bricked :(

I can't boot my phone, it says Custom binary blocked by FRP
I can't flash twrp, and whenever I try to flash a stock md5, odin fails
What do I do?
Update- I tried to flash a stock rom from http://forum.xda-developers.com/not...ware-firmware-kernel-modem-recovery-t2902574/
Results were
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Firs of all. How did you brick your phone?
Sent from my SM-N910T using Tapatalk
Did you by chance turned on the Samsung Activation Lock?.This happened to me the first time i tried to install custom rom, i thought the phone had bricked but I was able to get into recovery mode and restart the OS. Try booting into recovery mode and choose restart system If not you will need to flash a stock rom but it needs to be the same version you had.
nano303 said:
Firs of all. How did you brick your phone?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I booted it into recovery and got the Custom Binary Blocked message when I try to boot
glm0025 said:
Did you by chance turned on the Samsung Activation Lock?.This happened to me the first time i tried to install custom rom, i thought the phone had bricked but I was able to get into recovery mode and restart the OS. Try booting into recovery mode and choose restart system If not you will need to flash a stock rom but it needs to be the same version you had.
Click to expand...
Click to collapse
I would, but I can't boot into recovery mode
Fixed it! I flashed about a dozen different files on Odin, finally got a 5.1.1 tar.md5, that's working
aaronfrickinaustin said:
Fixed it! I flashed about a dozen different files on Odin, finally got a 5.1.1 tar.md5, that's working
Click to expand...
Click to collapse
Which one worked?? Please tell me! Stuck in the same situation
This error is due to the Samsung Activation Lock being on before flashing a custom rom, be sure to turn this off in the future before installing another rom. If by chance you forget and get the error just try flashing back the stock version of the rom you currently have and it should come up.

Emergency

i have installed twrp and inside twrp installed the supersu now when i reboot device it is stuck at the samsung galaxy s5 screen HELP!
dexter_17 said:
i have installed twrp and inside twrp installed the supersu now when i reboot device it is stuck at the samsung galaxy s5 screen HELP!
Click to expand...
Click to collapse
Take the battery for 30sec out and reboot again
i have tried that still no luck? have i soft bricked my device i can still boot into twrp
please help
Try to Reflash boot loader in Odin
Otherwise go into download mode and reflash your rom using Odin.
Then twrp
Then SuperSU (not the one in twrp)
how do i reflash bootloader,
all i did was:
boot device into download mode and use odin to install twrp
once inside twrp i clicked supersu install
now the phone remains at SAMSUNG S5 logo
device information:
SSN = g900fgsmh
SM-G900F
6.0.1
anyone? please
hello?
Download a Boot loader: https://www.androidfilehost.com/?w=files&flid=18030
Open Odin select AP and browse for the Bootloader and click install/flash.
i cannot find my one SSN = g900fgsmh any advice>?
dexter_17 said:
i cannot find my one SSN = g900fgsmh any advice>?
Click to expand...
Click to collapse
Download for G900f it should work
SSN = g900fgsmh i cannot find my device in the list
just tried but it still is stuck at samsung galaxy s5
<ID:0/004> Odin engine v(ID:3.1203)..
<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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
this all happened after install twrp can i recover for this nightmare
dexter_17 said:
this all happened after install twrp can i recover for this nightmare
Click to expand...
Click to collapse
Which TWRP version and SuperSU version do you have tried to installed?
And on which firmware you were before?
Twrp version is twrp-3.0.2-2-klte.img (1).tar
supersu version is BETA-SuperSU-v2.44
im not sure what firmware version but android version i had before but i had 6.0.1
dexter_17 said:
Twrp version is twrp-3.0.2-2-klte.img (1).tar
supersu version is BETA-SuperSU-v2.44
im not sure what firmware version but android version i had before but i had 6.0.1
Click to expand...
Click to collapse
Your SuperSU is very old.
Install this TWRP version again : https://dl.twrp.me/klte/twrp-3.0.2-2-klte.img.html
And latest SuperSU : http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
are you here please
it must of started the bootloop after installing twrp, i have tried all the other versions also but still doesnt work.....

Galaxy Tab A 8.0 (2017) updated to Oreo.

Just to let you know guys that the Tab A 8.0 2017 has been updated to Oreo with the September security patch. More info on the attached screenshots.
Finally! And it's even Oreo 8.1. So now it just needs to spread to other varants of the devices, as the base hardware is identical...
AntonyOrtega said:
Just to let you know guys that the Tab A 8.0 2017 has been updated to Oreo with the September security patch. More info on the attached screenshots.
Click to expand...
Click to collapse
Urs is T380 rite. The non sim variant. Hope the update reaches t385 also ... soon.
vsvj said:
Urs is T380 rite. The non sim variant. Hope the update reaches t385 also ... soon.
Click to expand...
Click to collapse
Yes, it's for the Wi-Fi only variant. I think LTE variants will have to wait a little longer because of carriers and the like. And from what I checked, there is no firmware currently available for any of them. Maybe soon
I wonder why there is no custom ROM and ports for tab a 8.0. Am I missing something here...?
So I just bought this tablet last week. Same exact model, 2017 variant and everything. How do I force it to check for updates? Or is there a way to sideload the update? Right now, it tells me under "Software Update" that the latest updates have already been installed. I mean, if I have to be patient, I can do that, too. Does resetting re-download the updates, by any chance? Like I said, it's still relatively new, so setting it back up wouldn't be TOO much of a pain.
And what is your opinion on this? Do I need to root? Right now, the thing seems to run pretty nicely. I'm really only considering rooting it at this point to get rid of the Samsung bloatware.
I have the SM-T580 (2016 - WiFi only) and I keep getting the same message about having the latest updates too!! We must have patience!!
Mikey1969 said:
So I just bought this tablet last week. Same exact model, 2017 variant and everything. How do I force it to check for updates? Or is there a way to sideload the update? Right now, it tells me under "Software Update" that the latest updates have already been installed. I mean, if I have to be patient, I can do that, too. Does resetting re-download the updates, by any chance? Like I said, it's still relatively new, so setting it back up wouldn't be TOO much of a pain.
And what is your opinion on this? Do I need to root? Right now, the thing seems to run pretty nicely. I'm really only considering rooting it at this point to get rid of the Samsung bloatware.
Click to expand...
Click to collapse
Well, in order to do that I just flashed a nougat ROM with a different product code (XAA before, XNZ now) with Odin. And then I got the Oreo update via a notification on the tablet and I just hit the yes button.
I'm good without root, Samsung Experience has all the functionality that I need and then some more, so at least for me there's no need to root my devices. The same for my S9+
AntonyOrtega said:
Well, in order to do that I just flashed a nougat ROM with a different product code (XAA before, XNZ now) with Odin. And then I got the Oreo update via a notification on the tablet and I just hit the yes button.
I'm good without root, Samsung Experience has all the functionality that I need and then some more, so at least for me there's no need to root my devices. The same for my S9+
Click to expand...
Click to collapse
And also you don't need to go through the hassle of setting up the tablet again, just use the CSC HOME in Odin and you're good to go.
OK, one followup.... What's the deal with the OEM Unlock thing? I have Developer Options turned on, I've spoofed the date, checked for updates manually, and rebooted. Also let it just sit, all of the tips I've seen, but no OEM Unlock option. What am I missing? It could just be the kind of puck I normally have, that is not entirely out of the realm of possibility.
Hmm, i tried flashing the newest 8.1 ROM from updato but after entering everything into ODIN and pressing Start, it only took like 5 seconds and then it comes up saying PASS! but when it rebooted, nothing appeared to have changed.. its still on 7.1.1..
Do i have to flash an Australian 7.1.1 then use the upgrade feature on the ROM?
Tablet:
SM-T380 (gta2swifi)
Curren 7.1.1t:
Product Code: XAC
BL: T380DXU1ARB3
PDA: T380DXU1ARB3
CSC: T380XAC1ARB3
8.1 stock ROM:
Product Code: XSA
BL: T380DXU2BRI6
PDA: T380DXU2BRI6
CSC: T380XSA2BRI6
Eclipserazer said:
Hmm, i tried flashing the newest 8.1 ROM from updato but after entering everything into ODIN and pressing Start, it only took like 5 seconds and then it comes up saying PASS! but when it rebooted, nothing appeared to have changed.. its still on 7.1.1..
Do i have to flash an Australian 7.1.1 then use the upgrade feature on the ROM?
Tablet:
SM-T380 (gta2swifi)
Curren 7.1.1t:
Product Code: XAC
BL: T380DXU1ARB3
PDA: T380DXU1ARB3
CSC: T380XAC1ARB3
8.1 stock ROM:
Product Code: XSA
BL: T380DXU2BRI6
PDA: T380DXU2BRI6
CSC: T380XSA2BRI6
Click to expand...
Click to collapse
Do you mind sharing a screenshot of what you're trying to do? And what variant of the ROM are you using? I flashed the New Zealand one.
AntonyOrtega said:
Do you mind sharing a screenshot of what you're trying to do? And what variant of the ROM are you using? I flashed the New Zealand one.
Click to expand...
Click to collapse
I tried flashing the australian 8.1 version using ODIN 3.12.3
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> aboot.mbn.lz4
<ID:0/006> sbl1.mbn.lz4
<ID:0/006> rpm.mbn.lz4
<ID:0/006> tz.mbn.lz4
<ID:0/006> devcfg.mbn.lz4
<ID:0/006> cmnlib.mbn.lz4
<ID:0/006> keymaster.mbn.lz4
<ID:0/006> apdp.mbn.lz4
<ID:0/006> msadp.mbn.lz4
<ID:0/006> NON-HLOS.bin.lz4
<ID:0/006> lksecapp.mbn.lz4
<ID:0/006> sec.dat.lz4
<ID:0/006> boot.img.lz4
<ID:0/006> recovery.img.lz4
<ID:0/006> system.img.ext4.lz4
<ID:0/006> persist.img.ext4.lz4
<ID:0/006> userdata.img.ext4.lz4
<ID:0/006> modem.bin.lz4
<ID:0/006> adspso.bin.lz4
<ID:0/006> cache.img.ext4.lz4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Eclipserazer said:
I tried flashing the australian 8.1 version using ODIN 3.12.3
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> aboot.mbn.lz4
<ID:0/006> sbl1.mbn.lz4
<ID:0/006> rpm.mbn.lz4
<ID:0/006> tz.mbn.lz4
<ID:0/006> devcfg.mbn.lz4
<ID:0/006> cmnlib.mbn.lz4
<ID:0/006> keymaster.mbn.lz4
<ID:0/006> apdp.mbn.lz4
<ID:0/006> msadp.mbn.lz4
<ID:0/006> NON-HLOS.bin.lz4
<ID:0/006> lksecapp.mbn.lz4
<ID:0/006> sec.dat.lz4
<ID:0/006> boot.img.lz4
<ID:0/006> recovery.img.lz4
<ID:0/006> system.img.ext4.lz4
<ID:0/006> persist.img.ext4.lz4
<ID:0/006> userdata.img.ext4.lz4
<ID:0/006> modem.bin.lz4
<ID:0/006> adspso.bin.lz4
<ID:0/006> cache.img.ext4.lz4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Use the latest version of Odin, I have seen other people having problems flashing Oreo ROMs because they are using an old version of Odin. I think is 3.13.1.
AntonyOrtega said:
Use the latest version of Odin, I have seen other people having problems flashing Oreo ROMs because they are using an old version of Odin. I think is 3.13.1.
Click to expand...
Click to collapse
Just as you mentioned the newer ODIN, i found it lol..
Flashed perfectly.. Thankyou
Eclipserazer said:
Just as you mentioned the newer ODIN, i found it lol..
Flashed perfectly.. Thankyou
Click to expand...
Click to collapse
Yeah no problem dude, enjoy!
Location
AntonyOrtega said:
Just to let you know guys that the Tab A 8.0 2017 has been updated to Oreo with the September security patch. More info on the attached screenshots.
Click to expand...
Click to collapse
In which Country do you live?
AntonyOrtega said:
Well, in order to do that I just flashed a nougat ROM with a different product code (XAA before, XNZ now) with Odin. And then I got the Oreo update via a notification on the tablet and I just hit the yes button.
I'm good without root, Samsung Experience has all the functionality that I need and then some more, so at least for me there's no need to root my devices. The same for my S9+
Click to expand...
Click to collapse
How did you flash the Nougat ROM and then update it?
Where there any new features added or any changes to the UI. Did they add Samsung Experience?
Mikey1969 said:
OK, one followup.... What's the deal with the OEM Unlock thing? I have Developer Options turned on, I've spoofed the date, checked for updates manually, and rebooted. Also let it just sit, all of the tips I've seen, but no OEM Unlock option. What am I missing? It could just be the kind of puck I normally have, that is not entirely out of the realm of possibility.
Click to expand...
Click to collapse
you know, I don' know how to answer your question, I am getting ready to try to root one of these myself, I ran into a problem with this tablet and I would like to tell you about it so you know beforehand. I have stock set up right now, and I play alot of games on my tablet, the one thing I have found with this tablet is DLC DOES NOT usually work with it, when you open a game offline it shows as no DLC. I gotta try to figure out how to root this damn thing as the proprietary stuff is VERY severe.
Nice tablet, GREAT portable TV with 400 GB SD Card and all, but the security on the device is Rediculous.
This war of mine will not show as DLC installed even if you purchase it unless your online, same with Project Highrise.
Roller Coaster Tychoon Classic works perfectly though (DLC always shows as present and available).. I don't get it.

Categories

Resources