Downgrading A71 firmware from bootloader(BIT 3) - Samsung Galaxy A71 Questions & Answers

Hi All!
I have tried to downgrade from my A71 without any success. Most probably reason is that my phone has firmware (bit 3). If anyone wondering why downgrading, here's reason: My car has support for only Mirrorlink (no Android auto). Samsung has stopped supporting Mirrorlink June 2020. Resetting factory setting with newer firmware than May 2020 --> Mirrorlink disappears. I know that there is lot of old phones with this support which could be bought second handed but where's the fun of that ?
Is it possible to downgrade firmware from Bit 3 to Bit 1/2?
Is this Bit information saved into phone way that it cannot to be rewritten?
I'm thinking following process:
* Flash NcX 2.5 A71 ROM with TWRP --> Getting TWRP for flashing
* Format/system wipe? Is it needed?
* Using TWRP flashing Bit1 stock rom into phone from memorycard
* One zip file which includes BL, AP, CP, CHC ? Or every file extracted from zip file?
Any comments, ideas are most appreciated!!
BR JHS
HERE's what I have tried now
Here's list of firmwares which are available for my A71 and info how the flashing went.
Device Model CSC Version Bit OS Build date
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU3ATJ2 3 Q(Android 10) 20201020152334 (Now flashed into phone)
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU3ATI8 3 Q(Android 10) 20200930134804 (Odin3 firmware update via downloading works ok)
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU3ATH8 3 Q(Android 10) 20200831142334 (Odin3 firmware update via downloading works ok)
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU2ATG1 2 Q(Android 10) 20200701232104 (Fails..)
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU2ATE8 2 Q(Android 10) 20200519160329 (Fails..)
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU1ATA7 1 Q(Android 10) 20200115142416 (Fails..)
SM-A715F / Galaxy A71 SM-A715F NEE A715FXXU1ATA1 1 Q(Android 10) 20200103192741 (Fails..)
Odin3 fails with following info:
Here's log from Odin:
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 8337 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> abl.elf
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I answer to myself
Is it possible to downgrade firmware from Bit 3 to Bit 1/2?
Is this Bit information saved into phone way that it cannot to be rewritten?
Click to expand...
Click to collapse
Bootloader version (BIT 3) cannot be downgraded, at least i didn't find any information about this. Any news?
TWRP lets you flash older firmware versions because it is ignoring bootloaders version check. There is no guarantee that older version of firmware works ok with newer bootloader. Needs to be tested.
New questions:
What happens if I take BL file from newer firmware and try to flash it with older AP, CP and CSC?

-JHS- said:
I answer to myself
Bootloader version (BIT 3) cannot be downgraded, at least i didn't find any information about this. Any news?
Click to expand...
Click to collapse
From what I know, no. You can't dowgrade bootloader version
-JHS- said:
New questions:
What happens if I take BL file from newer firmware and try to flash it with older AP, CP and CSC?
Click to expand...
Click to collapse
Never tried it

ShaDisNX255 said:
From what I know, no. You can't dowgrade bootloader version
Never tried it
Click to expand...
Click to collapse
What about creating custom "stock" rom? Latest NEE bootloader + rom from e.g. May. This procedure has been successfully used before, don't know if it works today.
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
I have newer created any custom roms but I don't think it does not require nuclear power plant technology experiense So if anyone have, any updated guides for creating Custom ROM -> Please let me know (xda have so many of them, don't know which one to follow).
So working process could be following
* Flash NcX 2.5 A71 ROM with TWRP --> Getting TWRP for flashing
* Flash custom stock rom via twrp
* And yes, I get bloody MirrorLink working in A71
Please comment!

-JHS- said:
What about creating custom "stock" rom? Latest NEE bootloader + rom from e.g. May. This procedure has been successfully used before, don't know if it works today.
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
I have newer created any custom roms but I don't think it does not require nuclear power plant technology experiense So if anyone have, any updated guides for creating Custom ROM -> Please let me know (xda have so many of them, don't know which one to follow).
So working process could be following
* Flash NcX 2.5 A71 ROM with TWRP --> Getting TWRP for flashing
* Flash custom stock rom via twrp
* And yes, I get bloody MirrorLink working in A71
Please comment!
Click to expand...
Click to collapse
Well, in theory it should be possible to leave your bootloader as is and just flash the new ROM with TWRP.
However, 2020 devices get a little more complicated because of what's called a super.img
Long story short, the only way I've tested to be able to work out a ROM would be with SuperR's kitchen
The Windows version is paid for and the Linux version is free, so if you don't want to invest money on the Windows version then use Linux version
The way to do it would be as follows:
-> Extract the firmware you want to make a ROM of with SuperR's kitchen
-> Use "sparse" type on everything
-> Make any changes you want to your ROM once extracted
-> Download the super image plugin
-> Use the kitchen to start building the following images:
->system.img
->vendor.img
->product.img
->odm.img
-> After all those are finally built (with "sparse"), then you can finally run the super.img plugin and start building a super img with those images inside it
-> After it's finally done, you can finally use that super.img and flash it with TWRP
So yes, it is a very tiring process. If this is really important to you and you really want to do this, contact me in Telegram (ShaDisNX255) and I can try to help you out.

Related

[ODIN][TAR] 5.0.0 I9505GUEUDNL3 Full Restore

NL3 is released.
NOTE: This image is *NOT* rooted! If you need root, see here.
WARNING: Stop asking if you can flash this on other phones. You can NOT. It is meant for the I9505G ONLY. This is NOT a "rom". This is a system image for the I9505G. Flashing to any other phone will brick it.
Kernel Source:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-I9505G
OTA zip (must be sideloaded in stock recovery):
http://android.clients.google.com/p...USER_I9505G_XAR_UCNF3_to_UDNL3_Update_FWD.zip
ODIN FULL RECOVER IMAGE (root is NOT built in):
Shamelessly stealing @MJHawaii instructions from this thread (THANK YOU):
http://forum.xda-developers.com/showthread.php?t=2398217
(DISCLAIMER) Please read and follow the instructions carefully. I nor anyone else on this forum is responsible if you brick your phone, lose your job, or life as you know it ends. Make sure you fully Understand what you're doing before you do it. Modifying any phone comes with a risk.
INSTRUCTIONS:
WARNING: Please do not flash this if you're low on battery...go charge your phone!
o) Download the I9505GUEUDxxx_FULL.tar.md5.gz package from below
o) Make sure you have the USB Drivers installed and you have Odin 3.09 from below
o) Put your phone in download mode and connect it to USB:
-Disconnect the phone from USB
-Power OFF your phone
-Hold Volume Down, Home, and Power
-When the "WARNING!!!" screen comes up, release the buttons
-Volume up to enter download mode
-Connect the phone to USB
o) Open Odin
o) Click on AP, then select the I9505GUEUDxxx_FULL.tar.md5.gz package you downloaded
o) Odin will extract the tar md5 file from the gzip archive, and this will take a while...be patient
o) Once the tar md5 is loaded, make sure you have a COM PORT in Odin ( any )
o) Click Start and wait till it finishes flashing...your phone should reboot when it's done
NOTE: If your phone does not boot, then boot into stock recovery and Wipe Data Factory Reset.
DOWNLOADS:
ODIN 3.09
I9505GUEUDNL3_FULL
A GIANT thank you to @MJHawaii for helping me learn this process!!!
Thank you for this. This has been a very much needed update IMO. Your work is always appreciated here. Whether or not the odin image is rooted, it is an easy fix for sure. Once again thank you. And enjoy the fresh Lolli.
I specifically decided not to use a rooted image this time due to the fact that being rooted blew up the ota for me. I wanted a place to start from that was clean. I figure our first 5.x update was a good place to kick out a new, fresh baseline build.
SamuriHL said:
I specifically decided not to use a rooted image this time due to the fact that being rooted blew up the ota for me. I wanted a place to start from that was clean. I figure our first 5.x update was a good place to kick out a new, fresh baseline build.
Click to expand...
Click to collapse
Good choice, in my opinion.
jpculp said:
Good choice, in my opinion.
Click to expand...
Click to collapse
I second (or 3rding) that .
For the first time ever i'm going to use Stock img with no root and happy about that
How to install a firmware i9505G GPE in an international I9505?
opoeta said:
How to install a firmware i9505G GPE in an international I9505?
Click to expand...
Click to collapse
You read the big red warning at the top of the post!
I9505 and I9505G isnt the same device?
Same way as I9505 ROM works in a I9505G, should happen otherwhise (or no?)
I just installed this and so far everything is working great. One small thing is confusing me though. I can't seem to find the settings for the Home button. When I push it nothing happens, unless I hold it down and then I get the app switcher. I feel really dumb right now. Lol
_DrizeX_ said:
I9505 and I9505G isnt the same device?
Same way as I9505 ROM works in a I9505G, should happen otherwhise (or no?)
Click to expand...
Click to collapse
Read the OP
So, isnt a ROM
Im sorry
_DrizeX_ said:
I9505 and I9505G isnt the same device?
Same way as I9505 ROM works in a I9505G, should happen otherwhise (or no?)
Click to expand...
Click to collapse
This is NOT A ROM. Doesn't it SAY that in the OP? Does it not also say that it will brick any device OTHER than an i9505G? They are NOT the same device. They use completely different partition tables. Rom devs take that into account. Since this is not a rom, it will not take that into account.
_DrizeX_ said:
So, isnt a ROM
Im sorry
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2557353
Thanks for this
Attempted to flash the I9505GUEUDNL3_FULL.tar.md5 image and it failed. Here is the Odin message:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I am soft bricked. I can successfully flash a stock recovery and get into recovery but that's it. Odin flashing any full image fails at the same spot.
Any tips or help would be greatly appreciated!
P.S. I can flash a stock recovery but attempting to flash a modem fails at the same spot. Confused.
Best regards,
Derek
What rom are you coming from?
Latest Stock 4.4.4 Rooted (I think NF3 but can't tell since I can't start up )
Just installed this last night on my stock S4 GPE. Working flawlessly and the phone feels a lot snappier than with 4.4.4. Lollipop is such a nice update.
Not exactly a problem, but I notice that the stock Android Messenger (SMS/Text) app is gone and that it's now Hangouts that by default handles texts/SMS. I find no separate stock texting app installed, unlike on my Nexus 6 with Lollipop.
DerekChas said:
Attempted to flash the I9505GUEUDNL3_FULL.tar.md5 image and it failed. Here is the Odin message:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I am soft bricked. I can successfully flash a stock recovery and get into recovery but that's it. Odin flashing any full image fails at the same spot.
Any tips or help would be greatly appreciated!
P.S. I can flash a stock recovery but attempting to flash a modem fails at the same spot. Confused.
Best regards,
Derek
Click to expand...
Click to collapse
Try a different USB cable and./or USB port. See if that makes any difference.
People have been asking about root quite a bit. I put together a new tool for those that aren't sure how to install it on a phone like this.
DOWNLOADS:
GPE Root
https://www.clockworkmod.com/rommanager (Use the i9505 NON touch version for rooting)
http://download.chainfire.eu/supersu
INSTALL:
o) Create a C:\GPE-Root folder
o) Unzip GPE-Root.zip to the C:\GPE-Root folder. NOTE: If you do not follow directions, then do NOT have spaces in the path you choose to use or it WILL fail.
o) Copy the CWM recovery img file to the C:\GPE-Root\recovery folder
o) Copy the SuperSU zip file to the C:\GPE-Root\supersu folder
USAGE:
o) Run the run.bat in the C:\GPE-Root folder
o) Follow instructions
NOTE: If your phone is not detected in ADB sideload mode, install the universal ADB diver in the C:\GPE-Root\ADB_USB folder

Galaxy s6 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 , 3.11 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 )
(whitch version i should use to flash 920F or V or A ? )

Stock Official ATT_ODIN_N960USQU1ARG9 Note9

Stock Official ATT_ODIN_N960USQU1ARG9 Note9
Model: SM-N960U
Model Name: Galaxy Note9
Country: USA
Version: Android Oreo 8.1.0
Security Patch Level: July 1st, 2018
Product Code: ATT
PDA: N960USQU1ARG9
CSC: N960UOYN1ARG9
Download here: AT&T N960USQU1ARG9
MD5: 92461b75fbee75796b979b45e52b0658
Download here: Odin3_v3.13.1_3B_PatcheD
Link up.
Running On My Galaxy S9+ SM-G965U Wicked Venom
Any root info yet for the att note 9,or if the safestrap recovery for the note 8 will work on the note 9
gubbilo144 said:
Any root info yet for the att note 9,or if the safestrap recovery for the note 8 will work on the note 9
Click to expand...
Click to collapse
No information on this and Safestrap will not work on Oreo 8.1
Running On My Galaxy S9+ SM-G965U Wicked Venom
THANK YOU!!! Any special way of flashing it?
Getting this... Any idea why?
<ID:0/012> Added!!
<ID:0/012> Removed!!
<ID:0/013> 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/013> Odin engine v(ID:3.1301)..
<ID:0/013> File analysis..
<ID:0/013> Total Binary size: 135 M
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> FAIL!
<ID:0/013>
<ID:0/013> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
after i download the att odin file, i can't extract the files. it says file is corrupt, i downloaded 4 times, all same.
i have an unlocked 960u1 unlocked usa note 9 variant and want to install ATT stock firmware.
is it possible to do it?
On another thread you posted the TMO firmware. You said that if you don't use the USERDATA file and then Factory Reset then it'll automatically get your Carriers bloatware and features. I'm planning to install this on my USA unlocked note 9 so I can get the ATT HD Voice, Wifi calling, etc. What would be the difference if I use or don't use the USERDATA file from this?
Can we get a re-upload or mirror? The one available is corrupted.
truciet said:
Can we get a re-upload or mirror? The one available is corrupted.
Click to expand...
Click to collapse
Reuploading Again will Let you know when it's up. Thanks For Reporting :good:
truciet said:
Can we get a re-upload or mirror? The one available is corrupted.
Click to expand...
Click to collapse
First Post Link Updated , Please Report back!
firepowr said:
On another thread you posted the TMO firmware. You said that if you don't use the USERDATA file and then Factory Reset then it'll automatically get your Carriers bloatware and features. I'm planning to install this on my USA unlocked note 9 so I can get the ATT HD Voice, Wifi calling, etc. What would be the difference if I use or don't use the USERDATA file from this?
Click to expand...
Click to collapse
I'm wondering same
Venom0642 said:
First Post Link Updated , Please Report back!
Click to expand...
Click to collapse
It works now! Thank you!
truciet said:
It works now! Thank you!
Click to expand...
Click to collapse
Your Welcome, thanks for reporting [emoji106][emoji106]
Running On My Galaxy Note9 SM-N960U Wicked Venom
Does this odin come with your stock wallpapers @Venom0642? I wanna be sure that I have the latest update of Android and some decent looking girls on my phone.
mammothjojo88 said:
Does this odin come with your stock wallpapers @Venom0642? I wanna be sure that I have the latest update of Android and some decent looking girls on my phone.
Click to expand...
Click to collapse
Lol no private property [emoji23][emoji23]??
Running On My Galaxy Note9 SM-N960U Wicked Venom
Downloaded and did not find a home CSC file?
Anyone know if I could flash the AT&T files on the international N960F model? Was hoping to get LTE, wifi calling/HD Voice.
What would my results be if I did flash?
Thank you in advance for any knowledge you could provide me.
guys, i haven't touched an android phone since note 3, 5 years ago.
please correct me if i'm wrong:
i got unlocked n960u1, unlocked usa note 9.
i'm trying to:
1) download odin (i believe it's version 3.3 patched)
2) download and install samsunng usb drivers
3) download ATT stock firmware (from this thread)
4) enable developer options on my phone by tapping baseband version 10 times (already done)
5) phone on download mode by holding vol down + byxby + power
6) connect phone to pc via usb
7) extract att stock firmware zip file. select each file (bl, csc, etc) to odin
8) start with oding after clicking on each individual module from the att stock firmware.
9) voila!
now, question:
is all of this correct?
i believe my phone has a locked bootloader, so would the above steps work? or do i need something like safestrap? (this is what i used to custom rom my note 3 back in the days).
can i flash att firmware into my phone even though the bootloader is locked?
nycalex said:
is all of this correct?
i believe my phone has a locked bootloader, so would the above steps work? or do i need something like safestrap? (this is what i used to custom rom my note 3 back in the days).
can i flash att firmware into my phone even though the bootloader is locked?
Click to expand...
Click to collapse
Yes, to all of your questions. You just need to boot into recovery.

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.

[ROOT][ANDROID11][OFFICIAL][MAGİSK] Magisk 22.0 patched boot.img M51

Magisk 22.0 Patched Boot Image
I'm not responsible for any bricked device.
Installation
1- Just flash it via odin.
2- After 1-3 loops it will boot into recovery. Don't panic just format data from there.
3- Install Magisk-v22.0.apk
4- Open it and click "Okay"
5- Enjoy it.
I'll release in three days twrp and ofox for Android 11. Use this rooted boot image for now.​
Great Work.
Looking forward to your Android 11 TWRP soon.
any progress updates for us, maybe?
Thanks man, awesome work! Looking forward to try your twrp version!
Thanks for the patched image. Root was one of the primary things keeping me on Android 10. Good to know now there's root for Android 11 as well. Will definitely be using this when I upgrade.
Hi everybody. In this moment, I have root for Android 10 version. Does it possible to get smartphone updates (Android 11 included) and keep the current root without problems? Or Should I unroot the device and after that, update in Android 11 version? Thank you.
does this root option breaks the fuse? after which samsung in the event of a guarantee knows that something was done? knox flag?
odin error
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 64 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> vbmeta.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
userprince said:
odin error
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 64 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> vbmeta.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Enable developer options and make sure that oem unlock is on
userprince said:
developer option no longer has oem unlock option.
Click to expand...
Click to collapse
you have to either turn on the access to the net or wait a few hours, I had it in samsung and it appeared after a while
"I'll release in three days twrp and ofox for Android 11. Use this rooted boot image for now." - please do
Hello my friends
1. Can I upgrade the mobile system from (Android 10 UI 2.5) to (Android 11 Oneui 3.1) using 5 files via odin?
2. Is this (patchedRamdisk.tar) a root of (android 11 Oneui 3.1)?
3. Then flash (TWRP-3.5.1_10.0_Beta1) and install (magisk-v22.0.apk).
And if there is a mistake in this, how is it to be done.
M H N said:
Hello my friends
1. Can I upgrade the mobile system from (Android 10 UI 2.5) to (Android 11 Oneui 3.1) using 5 files via odin?
2. Is this (patchedRamdisk.tar) a root of (android 11 Oneui 3.1)?
3. Then flash (TWRP-3.5.1_10.0_Beta1) and install (magisk-v22.0.apk).
And if there is a mistake in this, how is it to be done.
Click to expand...
Click to collapse
Do step 1 and 3. But use beta twrp 3.5 beta 2
LahKeda said:
Do step 1 and 3. But use beta twrp 3.5 beta 2
Click to expand...
Click to collapse
Can you give me the link please
M H N said:
Can you give me the link please
Click to expand...
Click to collapse
Check twrp thread and download the latest build provided in the thread
Is there any bugs ?? Can I uninstall system apps ?
Do we need to unlock bootloader first?
aze89 said:
Great Work.
Looking forward to your Android 11 TWRP soon.
any progress updates for us, maybe?
Click to expand...
Click to collapse
i need to wait for the twrp manifests for a stable build but i can port an unstable beta for you users if you want.
anggabastian said:
Do we need to unlock bootloader first?
Click to expand...
Click to collapse
Yeah
abhi_ki said:
Is there any bugs ?? Can I uninstall system apps ?
Click to expand...
Click to collapse
No its stable u can uninstall system apps but be careful.
M H N said:
Hello my friends
1. Can I upgrade the mobile system from (Android 10 UI 2.5) to (Android 11 Oneui 3.1) using 5 files via odin?
2. Is this (patchedRamdisk.tar) a root of (android 11 Oneui 3.1)?
3. Then flash (TWRP-3.5.1_10.0_Beta1) and install (magisk-v22.0.apk).
And if there is a mistake in this, how is it to be done.
Click to expand...
Click to collapse
yeah its a part of android 11 you can use it

Categories

Resources