Database Develop

[Q] Imposible to install CWM in GT7000 4.1.2

Hi all,
I am getting mad after several hours trying to just install CWM in the GT-7000.
I root it using the farmaroot and it was smooth.
after I tried the easy way of rom manager... and it didnt work.
I even download myself the Philz CMW 6
http://forum.xda-developers.com/showthread.php?t=1901191
philz_touch_6.07.9-n7000.tar.md5
I start the phone volume down - power-home , click volume up to enter into the downloading mode
run Odin 3.09 getting after install the samsung drivers... I get COM9 (light blue?)
I select the md5 file with the AP and click start and this is the output
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
really I dont know what else to try on...any idea??
thanks in advance.
jose

jacortijo said:
Hi all,
I am getting mad after several hours trying to just install CWM in the GT-7000.
I root it using the farmaroot and it was smooth.
after I tried the easy way of rom manager... and it didnt work.
I even download myself the Philz CMW 6
http://forum.xda-developers.com/showthread.php?t=1901191
philz_touch_6.07.9-n7000.tar.md5
I start the phone volume down - power-home , click volume up to enter into the downloading mode
run Odin 3.09 getting after install the samsung drivers... I get COM9 (light blue?)
I select the md5 file with the AP and click start and this is the output
really I dont know what else to try on...any idea??
thanks in advance.
jose
Click to expand...
Click to collapse
You can try to flash philz kernel from here http://forum.xda-developers.com/showthread.php?t=1901191
This time try .zip file and flash from stock recovery
Sent from my GT-N7000 using Tapatalk

Where did you select the file in Odin? What's AP?

treacherous_hawk said:
You can try to flash philz kernel from here http://forum.xda-developers.com/showthread.php?t=1901191
This time try .zip file and flash from stock recovery
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
I finally managed to install using an old Odin version 1.84 a whole custom ROM with the cwm included. Then I could boot into recovery and install the cyanogenmod custom ROM that I wanted.
Thanks a lot anyway,

Hi jacortijo plus help me out how you did that because I'm feeling same to install kitkat rom in my note 1n7000 plus help me out I have rooted my phone nd I'm using jellybean rom
I want to install philztouchrecovery to install kitkat rom but I'm not able to do that so old help me out

Tried to root 5.0.2 with 5.1.1 guide - softbricked it [SOLVED]

Hello!
Ok, I'll admit I didn't read closely enough in my haste to root my new phone, and now it's softbricked. My phone was brand new and still on the 5.0.2 firmware, and I tried to follow the guide at link here on XDA before updating to 5.1.1. After flashing the sboot.bin, it rebooted, but stuck at the Samsung logo screen with some green text at the top of the screen:
ASV TBL VER = 15
ASV TBL VER2 = 1285
ASV big:10 LITTLE:10 630:11 MIF:10 INT:10 CAM_DISP:10 (I think that's right, it's very tiny!)
I've been stuck there ever since! I can get into download mode, but that's it.
I'm not sure what to do now. I've tried reflashing the sboot.bin file, and I've tried flashing the 5.1.1 stock (COF8) ROM (which fails!)
Am I correct in thinking that the sboot.bin file will only boot 5.1.1 roms? If so, how do I get the ROM flashed if ODIN won't do it?
Any help will be greatly appreciated!

I've been thinking about this problem, and I've come up with two options. Either flash back to the original boot loader, kernel, etc. Or somehow get a stock 5.1 ROM to flash.
Any thoughts?
Sent from my (old) SGH-M919 using XDA Free mobile app

More info...
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.

SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
.
Click to expand...
Click to collapse
You are a lifesaver. More specifically a $579 saver.

Lovetoflyguy said:
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
Click to expand...
Click to collapse
Scratch that. I used PeaZip instead of WinRar or 7Zip. I didn't name it tar.md5, flashed and it's booting up now. We'll see if it works.
How did you get the new tarball file you made to pass the MD5 check? I can't get past that check when I make a new .tar file or tar.md5.

Lovetoflyguy said:
SOLVED!
So for anyone else who finds yourself in this foolish situation, here is what worked *for me*.
The problem:
The newer sboot.bin wouldn't allow an older Android version to boot, and I couldn't Odin the newer COF6 or COF8 firmware.
The solution:
I downloaded and unzipped (technically un-tarred) the *STOCK COF8* firmware from Samsung (sammobile.com)
-To do that rename the file by removing the ".md5" extension. Yes Windows, we really do want to change the extension.
-If you don't have a program that recognizes the ".tar" extension, download PeaZip and install it - it's open source & awesome!
-Re-tar all of the files there *EXCEPT* for the sboot.bin.
-Boot into recovery as before, and open Odin - you should be a pro at this by now!
-Click the AP button and select the re-tarred stock firmware, and flash.
-Odin fails after a few files, but this is ok.
-Reboot and you should get a "failed update" error instead of the Samsung logo.
-Now Odin the *STOCK COF6* firmware
-Watch and thank God as it succeeds,and reboots ...normally
-Be patient, it still needs to update Android.
-Decide just how badly you need ROOT.....
Click to expand...
Click to collapse
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode

vegeta_badman said:
i did everything you said but after (-Re-tar all of the files there *EXCEPT* for the sboot.bin.) step the new file was not recognized by odin.....any help???
IMP!!!! did you mean to flash odin from download mode or recovery mode because i've never heard of flashing odin from recovery mode
Click to expand...
Click to collapse
Always!!!! flash Odin files in Download mode.

i did everything as u said it...But i can not flash the STOCK (COF6) in odin it fails..plz help:crying:

Lovetoflyguy said:
When I try to flash a 5.1 stock rom, I get the following output from Odin:
<ID:0/004> Added!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Successfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialization..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!
<ID:0/004>
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
FYI, the text in my download screen says:
ODIN MODE
PRODUCT NAME: SM-G920T
CURRENT BINARY: Custom
SYSTEM STATUS: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:2 S:2
Does anyone know if T-mobile or Samsung could/would fix this, assuming I can't get it going in the next day or two?
thx.
Click to expand...
Click to collapse
how did you flash the firmware back to stock because i cant enter download mode:crying:

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.....

System Software not authorized by AT&T

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )

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.