Related
Hi.
I got a note 2 and would like to have an odin image with the official state as I bought it before I start tinkering with it (root, flashing rom, etc) so I can restore it if I need to claim warranty service.
The issue is: The firmware is of the austrian mobile operator 3 (www.drei.at) and I did not find an official firmware for it!
Can someone point me to it if it exists (did not find it on http://www.sammobile.com/firmware)?
Else: Is it possible to create an "official" system dump of it that works with odin? So if I restore from that created firmware it restores to the state I bought it without anything changed (no custom firmware counter increased, etc).?
I know there are some guides on how to create odin dumps, but they are rather complicated and I am unclear if I restore from one of those if it counts it as official (does it need to be signed for that and anyone not from samsung even do that?) and does not increase it.
Can you help me?
http://forum.xda-developers.com/showthread.php?t=1951091
You can root your phone and do whatever you want, and whenever you want. You can simply return to official warranty version by following steps in first reply of the link i attached.
Thanks
I don't think you get want I mean:
I know how rooting and flashing and odin works, i've done it lots of times. And i've also returned phones to stock.
Until now however I always had unlocked devices with completely official samsung firmwares, but now I have an oparator specific firmware: that of 3 austria.
I did not find an image for this firmware, so I cannot flash back the correct stock image because I did not find that specific image provided anywhere.
So my question:
- Where do I get the firmware JRO03C.N7100XXALIJ for 3 austria? Is it even available?
- If not: can I create it myself?
On http://www.sammobile.com/firmware the only option sensible that gives me results is the latest 10...
Is there a way to view all firmwares for a device (i.e.: n7100) to make sure mine is not among them?
this site is much better. you won't find that firmware exactly but you find other updates for your specific region!
http://samsung-updates.com/device/?id=GT-N7100
Hi guys.
I've got a China-bought Galaxy Tab S (T705C). The current ROM doesn't allow Google Services. Hence, no Gmail, no Google Play store on my Tab.
Can anyone throw me a bone here?
Where do I begin with installing European firmware for the Tab?
1. Do I need to root the device?
2. Do I have to install Cyanogenmod / some other firware loader?
3. Will LTE firmware work on this model? (It's 4G)
Thanks
For reference, would this ROM be correct for the 8.4" Tab ?
http://forum.xda-developers.com/galaxy-tab-s/development/firmware-galaxy-tab-8-4-lte-t2837428
Galaxy Tab S 8.4 (LTE) SelambA ROM NH1 V1.2.1 20140921
emfields said:
Hi guys.
I've got a China-bought Galaxy Tab S (T705C). The current ROM doesn't allow Google Services. Hence, no Gmail, no Google Play store on my Tab.
Can anyone throw me a bone here?
Where do I begin with installing European firmware for the Tab?
1. Do I need to root the device?
2. Do I have to install Cyanogenmod / some other firware loader?
3. Will LTE firmware work on this model? (It's 4G)
Thanks
Click to expand...
Click to collapse
1)yes. http://androidxda.com/root-samsung-galaxy-tab-s-8-4-sm-t705c
2) you need a recovery ( TWRP) to install Rom zip file.
3) If the HW is the same I would assume yes. Does support main LTE frequencies
4) yes, Selamba Rom is correct
:good: Dude, you're my hero.
I'll give it a try.
emfields said:
:good: Dude, you're my hero.
I'll give it a try.
Click to expand...
Click to collapse
I have the exact same problem, very curious if you are able to solve the issue and how.
Partial progress - Update 11/26
dqs23 said:
I have the exact same problem, very curious if you are able to solve the issue and how.
Click to expand...
Click to collapse
dqs23: If it will be of help to you - here's where I've gotten so far:
My understanding, to this point, is:
1. I need to install a European ROM to use Google services, and Google Play store on the Tab S.
2. I think that the SM-T705C is the same as the T705, just from China. So, I assume that this ROM (French-based) should work:
3. I'll need a tool such as Odin or Heimdall to install a Root program.
Recommended in the above link is this one: CF-Autoroot
4. Upon flashing CF-Autoroot, I'll then be able to install a ROM manager such as TWRP, from whence I can backup and install the custom ROM.
Where I'm currently hung:
I'm using an Ubuntu 14.04 machine, which can't run Odin.
I don't have a Windows machine, or access to one conveniently.
There's a Java based version called JOdin, which I've used, but it hangs at "Cannot extract PIT file."
Using Heimdall alone, I have the same problem - Cannot retrieve PIT file. (Which I presume is necessary to proceed with flashing the Root package. So, it's apparently an Ubuntu/Heimdall issue, perhaps with this particular device.
I understand it's possible to get PIT files from other means, but I'm a bit out of my depth, and don't want to f*$# things up. So, at this point, I'll probably wait and try to get a Windows machine going, and test from there.
Please kindly add any additional information you find here to this thread.
Thanks for the update emfield.
As this is the first time I'm doing a root everything is very new to me. Luckily I have an expert nearby to consult with on the basics.
What I've done so far is rooted the tablet with cf-autoroot but after installed gapps manager I was unable to download the proper gapps (4.4.1-2) as it gave me download unsuccessful error every time.
I guess what I'm looking for is some kind of confirmation from others how they were able to flash it to a EU rom and the steps they followed.
emfields said:
Hi guys.
I've got a China-bought Galaxy Tab S (T705C). The current ROM doesn't allow Google Services. Hence, no Gmail, no Google Play store on my Tab.
Can anyone throw me a bone here?
Where do I begin with installing European firmware for the Tab?
1. Do I need to root the device?
2. Do I have to install Cyanogenmod / some other firware loader?
3. Will LTE firmware work on this model? (It's 4G)
Thanks
Click to expand...
Click to collapse
That will not likely happen as China locks everything down, as that product is actually manufactured in China, it will be fully compliant with whatever regulations exist for those products. I got around some of it by extracting the Chinese Odin image and the HongKong image, then I took the Hong Kong Cache.img and placed it in the new Chinese image.
Doing that allowed me to change the csc to whatever country I wanted, in this case Hong Kong, I was then able to get my news and other things in English.
Use 7Zip to create your new tar image, since it is not signed by Samsung you will trip the Knox flag, you will need to root your phone in order to flash GAPPS. The key parts of the firmware are blocked by the Chinese bootloader so rooting is absolutely required.
lorinkundert said:
That will not likely happen as China locks everything down, as that product is actually manufactured in China, it will be fully compliant with whatever regulations exist for those products.
Click to expand...
Click to collapse
Hey Lorin, please let me go back a step with your response:
1) By "That will not likely happen", do you mean it's not possible to root and install a different ROM?
I've found a European-based ROM, based off the stock Samsung 4.4 firmware, which is for the SM-T705. (It's here.)
Are you saying that's not possible / not going to work?
lorinkundert said:
I got around some of it by extracting the Chinese Odin image and the HongKong image, then I took the Hong Kong Cache.img and placed it in the new Chinese image.
Click to expand...
Click to collapse
2. Sounds interesting. Can you clarify slightly about the "Odin image"? Is that an image of the firmware? (Same thing as a stock ROM?) And where did you get a HK Rom?
Thanks!
emfields said:
Hey Lorin, please let me go back a step with your response:
1) By "That will not likely happen", do you mean it's not possible to root and install a different ROM?
I've found a European-based ROM, based off the stock Samsung 4.4 firmware, which is for the SM-T705. (It's here.)
Are you saying that's not possible / not going to work?
2. Sounds interesting. Can you clarify slightly about the "Odin image"? Is that an image of the firmware? (Same thing as a stock ROM?) And where did you get a HK Rom?
Thanks!
Click to expand...
Click to collapse
Sammobile.com has all the ROMs, I just downloaded the Chinese and Hong Kong Versions and replaced cache.img in the Chinese ROM with the HK version, that should work using a cache.img from Europe. Odin will work with a tar image without the md5 extension. If using Window, 7Zip will create a tar file
If you attempt to flash any other ROM on a Chinese ROM ex. T705C, T805C Odin will fail and knox will be tripped, you can flash a custom ROM but you will lose the radio, no LTE, 3G or 2G
105
lorinkundert said:
Sammobile.com has all the ROMs, I just downloaded the Chinese and Hong Kong Versions and replaced cache.img in the Chinese ROM with the HK version, that should work using a cache.img from Europe. Odin will work with a tar image without the md5 extension. If using Window, 7Zip will create a tar file
If you attempt to flash any other ROM on a Chinese ROM ex. T705C, T805C Odin will fail and knox will be tripped, you can flash a custom ROM but you will lose the radio, no LTE, 3G or 2G
Click to expand...
Click to collapse
I see.
Were you able to download a PIT file for the T705C? Linux user here, using Heimdall. On Mac and Linux, we're unable to extract a PIT file from these devices.
2. Regarding "Odin will fail on flashing a non-chinese ROM" - So, supposing I am able to root and install TWRP or CWM Rom Manager, even then, flashing a mostly-stock ROM based on the European stock T705, it's definitively going to lose 3G/LTE ?
Thanks
Status update:
Got device rooted ( used Odin 3.07 in Virtualbox)
Got Busybox installed
Got TWRP Backup *app* installed - not yet been able to install backup Recovery menu.
Where I'm currently at:
Trying to get TWRP recovery working, to make a backup of my current stock ROM.
Problem: Rebooting into recovery menu does NOT yield any menu options for backup/recovery. It seems to be the stock Android 4.4 recovery menu: NO ability to create a backup. (That I can find.)
Anybody got some idea what to do here?
emfields said:
I see.
Were you able to download a PIT file for the T705C? Linux user here, using Heimdall. On Mac and Linux, we're unable to extract a PIT file from these devices.
2. Regarding "Odin will fail on flashing a non-chinese ROM" - So, supposing I am able to root and install TWRP or CWM Rom Manager, even then, flashing a mostly-stock ROM based on the European stock T705, it's definitively going to lose 3G/LTE ?
Thanks
Click to expand...
Click to collapse
Even changing the kernel broke LTE and 3G on mine
Succes!
Thank you very much for the post! I had the same problem.
Before using the ROM you indicated in your post: (pibach's one)
1.I used Odin to root my device.
2.I downloaded the tar file of the TWRP (for this device )
3.Installed the TWRP using Odin
4.Copied the ROM onto device(I didn't use a SD card)
5.I downloaded ROM manager app
and installed it onto the device and used it to reboot in recovery mode(using Reboot into Recovery)
6. In the recovery mode I went to Install and found the zip with the ROM and installed it without any problems
When the system started I was unhappy because there were the same Icons from the Chinese software . But when I opened the menu Play Store was there :good::fingers-crossed:
lorinkundert said:
That will not likely happen as China locks everything down, as that product is actually manufactured in China, it will be fully compliant with whatever regulations exist for those products. I got around some of it by extracting the Chinese Odin image and the HongKong image, then I took the Hong Kong Cache.img and placed it in the new Chinese image.
Doing that allowed me to change the csc to whatever country I wanted, in this case Hong Kong, I was then able to get my news and other things in English.
Use 7Zip to create your new tar image, since it is not signed by Samsung you will trip the Knox flag, you will need to root your phone in order to flash GAPPS. The key parts of the firmware are blocked by the Chinese bootloader so rooting is absolutely required.
Click to expand...
Click to collapse
OK so hopefully nobody had already read my post but none of this was necessary for me as I am still living in China (therefore there's no need to worry about messing up the radio). All that was necessary was to download the "App Search" application that is popular here in China and then search for "Google Play" Store which was still in the mainland China database. In order to set up the account the rest of the way, I used my VPN to connect to the Google network and voila!
The reason it seems tricky at first is because the government blocks a lot of services that are not China-based from reaching China and it also blocks China-based services from going leaving China. So a VPN is an absolute must for using Google...but to find Google apps is a piece of cake.
But if you intend to take the tablet outside of Asia then rooting is most likely still necessary if you want to use LTE/3G.
New to Android
I am in the USA. USA Tablets do not have LTE phones as the carriers want you to buy expensive data packages.
the way around this is to buy the SM-T705C which has the correct transceiver radio in it.
I am savvy when it comes to any windows problem. Recently replaced old X7001 Windows phone with a SM-T705C. S V4.4.2 Kit kat till learning Android
Carrier AT&T 4G LTE
Specs for my own phone
Model: Samsung SM-T705C
Android Version: 4.4.2 (KIit Kat)
Baseband Version: T705CZCU1AOC1
Kernal Version: 3.4.39-4367879
[email protected]#1
Wed March 4 13 40:11 KST 2015
Build Number KOT49H. T705CZCU1AOC1
Se FOR Android Status: Enforcing
SEPF_SM-T705C_4.4.2_0042
WED March 04 13:56:37 2015
Hardware Version MP 0.300
I have read this thread and it seems the best place I have found so far concerning rooting a SM-T705C international version.
I have to date gotten the SM-T705C to mostly speak English. I still get the weather in Chinese and have a few Chinese icons.
I have activated the developers options (Easter Egg)
Downloaded and installed in Win 7
Several android Emulators
Kies3
Downloaded Only: CF Auto root, Odin, Owners manuals in Chinese. Specifications for LTE version
Current Problems:
1. I can not get any Windows 7 or Win 8.1 machine to recognize the SM-T705C at all using the stock USB cable. , Need Help. I need to be able to access & transfer files.
2. Screen shuts off even when connected to USB cable. All I can do is control the delay. Very annoying
My goal is to unlock and then root the phone so that I can dual boot the original OS and any other Android OS.
Some terms I am unfamiliar with:
What is:
TWRP ?
Gapps Manager
Cyanogenmod
What is a Knox Flag ? I understand what it does but Is it hardware or software ?
Please help
MRGCAV @ gmail.com
lol
lorinkundert said:
Sammobile.com has all the ROMs, I just downloaded the Chinese and Hong Kong Versions and replaced cache.img in the Chinese ROM with the HK version, that should work using a cache.img from Europe. Odin will work with a tar image without the md5 extension. If using Window, 7Zip will create a tar file
If you attempt to flash any other ROM on a Chinese ROM ex. T705C, T805C Odin will fail and knox will be tripped, you can flash a custom ROM but you will lose the radio, no LTE, 3G or 2G
Click to expand...
Click to collapse
i need the t805C chinese stock rom to fix my 'baseband unknown' and no 4g/LTe/signal issue.
please??
Doesn't the Hong Kong firmware work on the Chinese version?
Hi
I have the same problem, i want to change to european rom, but can´t, nobody succes?
Thanks
** STOP & DO NOT **
Pass Go (... or collect 200 dollars ...)
Attempt this without reading the first page entirely at least
Attempt this without knowledge of how to recover from softbrick status
Flash any non official Firmware if you're banking on a warranty claim later {It may or may not work}
Post in this thread, any super negativity, disbelief, or naysaying.
Blame any Project/Thread contributor(s) for what YOU did, when YOU flashed your device. Please, no one forced you to press start in ODIN.
Preface
*****
[FOR THE LATEST UPDATE: GO TO POST #185 for the next steps towards rev 4/5 bootloaders.]
https://forum.xda-developers.com/showpost.php?p=79764173&postcount=185
Bootloader v3 and v4 devices currently on MM or Nougat can use the Factory Binary for their particular bootloader version in order to install a 5.1.1 based ROM that can have an untethered full root. To downgrade back to 5.1.1 use the combination firmware available for your bootloader revision. From there you CAN root 5.1.1 un-tethered.
** I do believe using the Binary 5 Combination Firmware, you can still root using the method for the v4 Bootloader, if you don't mind downgrading back to 5.1.1 and being on the combination firmware.
** I still haven't got a root method for fully rooting 6.0.1, or rooting 7.0 at all. These root methods will have your device ending up on a 5.1.1 build of Android.
For rooting Bootloader v4, please see @droidvoider 's Post #110, Post #110
Since there have been many threads scattered throughout the N920A forums about how to root 6.0.1/5.1.1, and how to downgrade the AT&T Galaxy Note 5 MM Builds back to LL builds, I've decided to collect up all the information I've had time to gather. This thread pertains to downgrading marshmallow builds to lollipop builds, and it covers gaining a tethered root system. What I am also going to cover is what I've discovered about the Factory Binary Firmware for this device. This includes what I call the Eng Modem & Eng Sboot, and how the PB2 Eng Kernel can be used with all three of the above.
Throughout all of my testing on the device, I have never once tripped my KNOX counter. The warranty remained valid on the device and it has been persistently rooted.
@TechNyne66 has outlined {proven} instructions for attaining a Tethered Root. I know there are already a few threads circulating the forum here about Root Status & Progress of the Note 5, and I hate just adding one more to the mix, but this isn't meant to be a general discussion thread.
I spent a lot of time reading over the last two years about the Exynos7420 SoC and I am always trying to learn more than high level google searches can give to me. There are a lot of hardware level topics involved I need more information on, hopefully the devs on XDA with this kind of knowledge would contact me. Because google does not always have the answers we search for when it comes to mobile hardware. It is in the minds of the devs here, and not always posted publicly. Not everyone in the world who wants the abilities granted by root access, is ready/able to deal with the potential hazards and security risks to their Device & Personal Lives. But they never will be ready, if we cannot study what those risks are in the first place.
Just remember, there is a reason things like SuperSu exist in the first place. Without a method to manage access to root privelages by installed apps, you'd be using an Open Source Universal Remote that knows everything about you, its surrounding environment, and knows how to manipulate said data. Given the nature of the Exynos7420's 64bit Architecture, all known variants of the SM-G920, SM-G925, and SM-N920 should theoretically be able to run or boot any code we could ever write for a computing device. We have the build-tools. It's just a matter of using a specific version of a particular tool depending on the timing & current context. Ideally.
My Device Results
*****
The firmware that was initially installed on my particular AT&T Note 5 when I first got it, was the August 1st 2016 build "UCS3BPH4". I have the Full ODIN Package, as well as the OTA.zip that upgrades PE6 to PH4. I also have the OTA.zip for upgrading PB2 to PE5.
I really need, if anyone has some, any unreleased official OTA updates for adb instead of just all ODIN files. I'd also like some advice on how examine how the bootloader loads a kernel, and what it looks for when it does. The update chain of OTAs to the PE5 build would be great. The N920A is odd in the sense that AT&T released two different update paths for their devices. Some devices ended up on the left path, and some on the right path.
When I flashed the Unlocked PH4 Modem, my device became carrier unlocked and opened the APN Editor. I consider it an Eng Modem.
When I flashed the Eng PH1 Sboot.bin from the Factory Binary and the Eng PB2 Kernel, I became able to Flash+Root a Lollipop Build that would stick on rebooting. Using a device with a Version 3 Bootloader. If there are other ways to downgrade to lollipop from marshmallow without using the Eng Sboot, please tell me.
I'm not trying to say at this point that the 3APH1 Firmware is actually a real eng binary like they found for the S8. But the system image on the firmware does have some interesting tidbits I haven't seen in any other Factory Binary I've messed with. It's more than normal.
If you cannot find any of the items I'm referring to in the links below. PM Me.
*****
What I understand about 3BPH4
Included Files in Full ODIN Package:
AP_N920AUCS3BPH4_CL7563702_QB10603229_REV00_user_low_ship.tar.md5
BL_N920AUCS3BPH4_CL7563702_QB10603229_REV00_user_low_ship.tar.md5
CP_N920AUCS3BPH4_CL7563702_QB10603229_REV00_user_low_ship.tar.md5
CSC_ATT_N920AATT3BPH4_CL7563702_QB10603229_REV00_user_low_ship.tar.md5
NOBLELTE_USA_ATT.pit
If I remember reading correctly, ODIN FW whose CSC file does not include a 'hidden.img' in their Cache.img are technically Unbranded ROMs. If this is still true today, then this firmware minus CSC is actually unbranded but uses the AT&T multi-cert CSC. Unless I didn't look hard enough, I did not find a hidden.img when I used CacheRipper to unpack the Cache.img -- I don't remember what post I read this in, I read many threads all the time, I can't confirm at this moment this assumption still holds in modern builds or this device series. Still testing other theories.
I'm not sure about other N920a's, but I have a multi-CSC cert on the device, meaning it should be able to accept any firmware compatible within the same series. At least that's how I remember it being. Same goes for my VZW S5 & S6 Edge. -- I don't know how common Multi-CSC certs are still. I honestly can't remember NOT having a Multi-CSC on any of the Samsung Devices I've owned. Mine all have them. I just have some intuitive feeling the Multi-CSC is basically a requirement for Unlocking.
I have successfully downgraded the AP file many times to earlier builds by flashing the AP by itself. I have successfully done a full cold boot after downgrading the PH4 AP file to PB2, OJ1, and OGG. I successfully flashed the PE6 AP file as well.
I have successfully downgraded the CSC file many times when downgrading the AP file as well. I cannot remember at this moment if I had success downgrading the CSC by flashing only the earlier FW CSC file. The One time I can remember, I flashed only the '.PIT' file included with PH4 & the CSC file of the earlier FW. I do know that I've downgraded the AP file and not the CSC with no errors. I have NOT yet tried to downgrade the CSC file by itself to an earlier version than the Installed AP. -- It remains to be tested in more detail how the AP File and PIT File affect the flashing of a different CSC.
The PH build series is the first publicly available FW for the N920A to use a Level 3 Bootloader Binary. I notice this change from Binary 2 to Binary 3 on most devices going from 5.1.1/6.0 to 6.0.1 Builds on Samsung Devices. With the Exception of Verizon, who has been using a Level 4 Bootloader Binary for quite some time, most Carriers are just now getting around to Level 3 Binaries in their Firmware. Leading many people to believe it is completely locked to a level 3 and can never boot anything designed for an earlier binary. -- While I have so far not been able to test a method for fully downgrading all parts of the BL File from Binary 3 to Revision 1 or 2, a Revision 3 bootloader can still boot a Binary 2 ROM. Although I'm told it is possible to fully downgrade all parts of the PH4 bootloader to an earlier version, but have not successfully done so.
I have successfully downgraded the 3BPH4 sboot.bin included within the BL File of the Full ODIN Package. I did it by packaging the earlier sboot.bin into a tar by itself and flashing in the BL slot of ODIN (3.10.6). Anytime I try to flash a full revision 2 bootloader it quite expectedly fails the flash at param.bin. It trips the alarm in Download Mode by stating the error Binary 2 Device 3. In my successes here, Download Mode still showed Official Device Status, Valid KNOX Bit/Warranty Status, Passing DM-Verity Verification. In all my flashes thus far I've never tripped KNOX. Once, the device status changed from Official to Custom, but KNOX was still showing valid. It wouldn't boot due to an error about invalid kernel length, but everything was valid status under the hood. -- The two downgrades I'm referring to, are the downgrades from
N920AUCS3BPH4 sboot -> N920AUCU3APH1 engsboot
Using the Bootloader from the Factory Binary, we can downgrade from Android 6.0.1 to 5.1.1. I also have the N920C_XXU3API1_ENGSBOOT, but ODIN wouldn't even start to flash it before failing. I don't have the param.bin or cm.bin for either of the ENGSBOOT files. If they even exist publicly or privately.
N920AUCS3BPH4 sboot -> N920AUCU2APB2 sboot
Like I mentioned above, I downgraded the sboot from a binary 3 to a binary 2, by flashing only the sboot.bin and not trying to downgrade the param.bin or cm.bin. But I think having the stock PH4 param.bin & cm.bin could be what is leading to a couple roadblocks. While the flash to PB2 sboot went off without a hitch, and did successfully do a full boot, it only lasted for about 20 minutes. When more tests caused it to stick in a bootloop to prevent itself from tripping the KNOX warranty bit due to invalid kernel length causing failed boot. This is also the only time in all my tests that my Device changed from Official to Custom status. Reflashing the Full PH4 package returned everything back to Stock. I also flashed Systemless Root (Which worked btw! But Verity Caught it, hence why the session lasted only 20 minutes or so) during this test session which could have also done it potentially.
My Best experience flashing most of the files I've tried successfully, came from using ODIN v3.10.6, and it does not seem to be a standard ODIN. Instead of just Odin3.exe & Odin3.ini, these are the files that came bundled inside the Odin zip:
Odin Downloader Release Notes.xlsx
Odin3 v3.10.6.exe
Odin3.ini
S1PlugIn.bundle_141117.zip
SS_DL.dll
But it seems like this version of ODIN has some kind of FTP mode within it for grabbing something I have no idea at this moment. So insights from someone smarter than me would be nice. I think FTP mode was enabled by connecting the Device to odin, while in RNDIS USB Mode. If not, I know that connecting to ODIN in that connection mode did something odd in one of the ODIN versions I have. ALSO, what are all the modded versions running around supposed to be used for exactly? And how were they modded? Often times they fail to flash simple things this v3.10.6 flashes successfully without blinking.[/color]
*** *** ***
Rooting/Downgrading Files Involved
I.Note5 Online Repo - https://drive.google.com/folderview?id=0B4PoJYLnmv1BNzY2OXB3QlFfcVk
** This is the folder where I'm keeping all files referenced here + other N920A related material.
II. Binary 3 Lollipop Bootloader (N920AUCU3APH1 sboot.bin, FRP eng Bootloader) - https://drive.google.com/folderview?id=0B4PoJYLnmv1BQ19qeVFUd2cxaWM
** This sboot can be flashed overtop of the Stock PH4 sboot.bin and IT WILL NOT trip KNOX. This is the only "binary 3" bootloader for our device I've found that will boot 5.1.1 based ROM's or Kernels. Using this bootloader, you can flash 5.1.1 based ODIN AP Firmware Files (ROMS) & continue to have Official Device status for Warranty/KNOX Purposes.
III. 2APB2 Lollipop Eng Kernel - https://drive.google.com/folderview?id=0B4PoJYLnmv1BQVBfQUdYeE5IR1U
** This is a 5.1.1 based, rooted kernel. As far as I know this is a leaked Engineering Kernel from the 2APB2 build. Flashing this Kernel and the PH1 eng sboot, overtop of Stock PH4, gives access to an ADB Root Shell during the bootloop/failure. Flashing this kernel overtop of a stock LL based Kernel allows a bootable rooted system.
IV. Metalcated g920a 5.1.1 Root v4 -
** This is Metalcated's Root Method for the Galaxy S6. This zip is used for the Root-Install & Root-Boot script files. The Root-Install command should be ran once the PB2 Kernel has been flashed and successfully rebooted the first time. Afterwards, the Root-Boot command should be ran during the device's next boot process, to continue using the PB2 Kernel & maintain a bootable system.
*** *** ***
6.0.1 Downgrading Instructions (tested using full Stock PH4 FW)
1.) Enable Developer Options
2.) Enable OEM Unlock
3.) Enable USB Debugging (For a safe bet I make sure to "always remember the device" by saving the RSA Key)
4.) Power Off then Boot into Download Mode
5.) Flash the Binary 3 Lollipop Bootloader using the "BL" slot in ODIN. (Listed Above)
6.) Once Bootlogo Appears, reboot into download mode by holding, VOL Down + HOME + POWER
7.) Now Flash the AP File of the Lollipop FW you want to install. (The OGG ROM, has no DM-Verity in Recovery Mode)
8.) Boot into Recovery Mode
9.) Wipe Data/Factory Reset
10.) Reboot
*** *** ***
5.1.1 Tethered Root Instructions (tested on PB2 & OJ1 ODIN AP FW/ROM's)
1.) Enable Developer Options
2.) Enable OEM Unlock
3.) Enable USB Debugging (For a safe bet I make sure to "always remember the device" by saving the RSA Key)
4.) Power Off then Boot into Download Mode
5.) Flash the PB2 eng Kernel (Listed Above)
6.) Once Booted, recheck steps 1-3, then run the "root-Install" script (.cmd for Windows, .sh for Linux) from Metalcated's zip archive.
7.) During Device Boot Up, make sure the device the connected to your PC, and run the "root-Boot" script from Metalcated's zip archive. And the device should finish booting successfully with the PB2 eng Kernel still intact.z
removed outdated information about Note 5 source codes.. Please see links by Delgoth for updated info
** too many words on someone elses thread **
I think the main problem for you is that you are on a binary 4. I have not tested any of this using a device that starts on binary 4.
But thank you for this, and I will go over these a little later today. I do already have the MM sources for the N920A/V/C and am working on that this week.
Flashing the PB2 flashed a LL rooted kernel, thats why on a device with MM installed it will hang. But during that hang plug it into the pc and open ADB
See if you have root shell.
Just wondering if anyone got anywhere with this. I know nothing about what you guys are talking about but I have N920AUCS4CPL1 and was wondering if anyone figured out a root for it
We have another thread up in the General Android Q&A Forum. I currently have adb shell with eng kernel running Lollipop U1AOGG AP running the U3APH1 eng bootloader.
I also have Busybox support, and can make persistent changes to the /system & /data directories
Droidvoider has also created a type of custom odin/heimdall flashing application used during runtime.
This is big stuff!!!
https://forum.xda-developers.com/android/help/injecting-root-setting-selinux-stages-t3573036/page2
in binray 3 not working, tested
What do you mean when you say it did not work for binary 3? Which FW build did you test? And how did you use ODIN when you flashed?
What tests of yours failed specifically? Because I've successfully downgraded to Lollipop from both the PHA & PH4 builds. I haven't actually tried PJ1. But with the corrupt bootloader issue people have mentioned. It would depend on if you upgraded to a Binary 4 sboot or not.
Sent from my Galaxy Note5 using XDA Labs
Does this thread only apply to the at&t note 5?
shawtypanda said:
Does this thread only apply to the at&t note 5?
Click to expand...
Click to collapse
Yes! This isn't going to work on Verizon.
Actually it could potentially work for Verizon.
If you substitute the Verizon Combination Firmware for the AT&T and apply the same principles accordingly.
So you're saying that there could be a root for the verizon version of this phone?
shawtypanda said:
So you're saying that there could be a root for the verizon version of this phone?
Click to expand...
Click to collapse
I need a Verizon tester for my stuff. Your security patch level can not exceed October, 2016. Please check in Settings|Device|About what your security patch level is. If your patch level is 2017, it is not likely I will be attempting to gain root. Unless there are reports of issues such as battery drain, or if enough people complain about not being able to switch carriers again. freddierice connected the dots with his tools which I have altered to be mine.
Greyhat Root Project - Root Console is a tool which executes commands from a text file, not a root shell
trident is freddierice's tool exactly being converted for the Note 5 (yes verizon also) It is a root shell so to speak, but I'm still working on sepolicy injection (read no context hack yet, limited by context)
Greyhat Root Project -- Root Console
Build a cmd_list.txt to issue commands as root. It also replaces screencap with dirtycow so you can use dirtycow with the two contexts. root + system_server or install_recovery. From install_recovery I am able to switch to init context, maybe a couple others, this feature is being finalized today. But ultimately until I finish trident we don't have reload init, can't reload policy
trident Note 5 version
This is still being converted it does work but the INIT_OFFSET needs to be worked out still, then it should reload init which will reload sepolicy correctly.
edit
The binaries for Greyhat Root Project -- Root Console are specific to each build of Android. You can certainly try the Android 6 or Android 5 toolbox / applypatch on your device but if it fails I need to compile a version specifically for your build. Please PM me with build number, obtain as follows
1. Plug in your device and ensure you can connect to adb shell
2. adb shell getprop ro.build.id
(if you're in the shell already leave off the adb shell) getprop ro.build.id
3. PM me that number, should look like MMB29K
I'm on the latest ota update so I'm assuming I don't qualify but if there's a way for me to downgrade or something so I can test this then I will. But how's the progress? I'm curious
What's this funny stuff about us being able to root our EQC6 (Did we have this update? I don't remember) firmware lol ?? I'm not sure this is even close to the truth, I can already see the bricks happening to mislead ppl. Check it out and tell me (us) what we really wanna hear or give us the sad but real truth
http://www.teamandroid.com/2017/05/...d-70-att-galaxy-note-5-n920a-nougat-firmware/
If someone need I can test verizon version if it ever will be..
I'm on 5.1.1. Was waiting for root, but now thinking of upgrading to nougat. Would be a good idea if waiting for root, or should just stick with 5.1.1
Aurey24 said:
What's this funny stuff about us being able to root our EQC6 (Did we have this update? I don't remember) firmware lol ?? I'm not sure this is even close to the truth, I can already see the bricks happening to mislead ppl. Check it out and tell me (us) what we really wanna hear or give us the sad but real truth
http://www.teamandroid.com/2017/05/...d-70-att-galaxy-note-5-n920a-nougat-firmware/
Click to expand...
Click to collapse
Yeah that looks to be an auto generated page.
I think we're almost done. Basic Shell root is achieved. I had SuperSU half installee before I reflashed. On MM builds.
But on the Note 5 and S6 edge it is coming quickly. Ive just been too busy the last two weeks to check out the signatures.
just recently got my hands on a Note 5 but didn't realise that the N920A was near impossible to root. I was just about to update this phone to the stock nougat but then found this thread today and it looks promising.
Currently running the PB2 firmware. If this root ends up being successful, will it only allow for a permanent root on 5.1.1 or 6.0.1? Or will you be able to flash a ROM like Nougat Nemesis and everything will be okay? Understandable that time will only tell. I'm currently using the Nemesis Nougat on my s6 Edge as my daily driver but would much rather use the Note 5 with Nemesis as my daily driver.
I can see why people love the Note. It truly is a great phone.
is this still a thing?
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Frank-95 said:
Hello.
I've just discovered that I can't switch my phone on because it says "custom recovery block by frp lock". I know there are numerous threads on this forum and other websites describing this problem and ways to solve it, included mantaining data.
Every method requires the download of the same version firmware you had installed on your phone. The problem is that I cannot really remember if I kept my Galaxy A3 2016 to 5.1 or I upgraded it to 6.0. Obviously I cannot check it by phone since I cannot even boot, nor via adb since it isn't able to recognise the phone in the download mode.
So firstly: is there a way to retrieve the firware code, or at least, the android version of my phone? Can adb recognise the phone in downlaod mode?
Secondly. According to this link in xda, that user was able to solve the problem using some kind of firmware image (QB1), which seems to be an upgrade. Is that method valid for other samsung phones? For my A3, should I follow the same steps with the correct firmware version?
Thanks in advance
Click to expand...
Click to collapse
1.install KIES
2.press tools
3.press frimware upgrade and installation
4.device id is your device model and serial number can be found under battery
5. allow kies to download and install the image
Video link for more help : https://www.youtube.com/watch?v=LqoX7wNhotk
good luck
Edit: please remember to enable OEM unlock in developer options next time
Kies cannot link to the device in the downlaod mode unfortunetely
Frank-95 said:
Kies cannot link to the device in the downlaod mode unfortunetely
Click to expand...
Click to collapse
try using smartswitch and see if it detects it
-are drivers installed
-does the pc recognize the phone ?
So, I had already tried with Smartswitch, but it says device not supported and does not link at all.
Moreover yes, the computer could read the phone before the frp lock, and even now, odin can detect it in download mode.
Kies just loads for some minutes and then says "unable to link to the device"
EDIT: no sorry kies raises "the device does not respond"
ok we need to flash using odin , i assume you can't access recovery but if you tried and it worked, look at the top of the screen it must show a code like
<your A3 model> followed by <your country> followed by <frimware date>
If you couldnt, we can use an updated version for your model , please provide us with the model if u can.
I can only acces to odin mode. Via that, I have the following text:
Product name is: SM-A310F
Current binary: Custom (it was rooted)
System status: Custom
FRP LOCK: ON
Secure Download: Enabled
Knox Warranty Void: 1
RP SWREV: B:2 K:0 S:0
I am sure that the phone had Vodafone pre-installed applications, and looking at mrcrab.net there exist these possible stock firmware:
Android 5
Android 5
Android 6
Android 6
I only fear that if I mistaken the version I will obtain a wipe of my data, which are not vital but are important to me
Actually there is no way to avoid the reset as we don't know anything about the PDA version, install the drivers type in google "USB Samsung drivers"
It must show developer.Samsung.com/....
I'm on phone so I can't provide it as a link, install the drivers and try again, else we will get the latest version
I already have samsung usb drivers, and odin can succesfully detect the phone in download mode; Kies cannot, though
Anyway, if you open one of the links I posted, isn't the PDA shown in the line:
OS Version : A310FXXU1AOLE (chosen one as example)
In that website there is every stock firmware by model, android version, and mobile operator. I know two out of three, and those 4 links are the 4 possible choices regarding android version. If I picked the right one, would I avoid the data reset, wouldn't I?
EDIT: What, if I did how it is explained here with the latest version? I mean download android 6 last upgrade, extract it, rename .tar.md5 in .tar and flah it with odin? Would it be any risk of loosing data?
Hello,
.MD5 lets odin checksum the rom loaded to it to make sure it's not corrupted, however if you are sure of two main things:
that the frimware you are flashing isn't a downgrade as downgrading flashs a old bootloader which gets you in some kind of troubles possibly a brick, to avoid that, grab the latest version
and the second thing you must make sure of is that the file isn't anyway corrupted.
if you think it's all ok, then you can proceed as of i tried it once and it saved a device.
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Frank-95 said:
Okay, I'm sure now that my android version was 6.0.1 because I read that 5.1 didn't have single app permissions manager, and I definetely remember that I had it.
According to this page, I have three possible choices.
1) I think the right version is the oldest one. In case I mistaked, would I risk a brick even if the major version is the same?
2) Also, if I mistaked, do I risk a data loss even though the major version is the same?
Thank you (we're almost there)
Click to expand...
Click to collapse
The build number must be the same regarding the android version, so to keep the files it must be the same as the one in the phone, else a wipe will be performed.
The problem is that you want your data, that maybe lost if we don't have the exact same build.
Just grab the latest marshmallow or nougat -, but the data would be lost then.
Do a hard reset in case something went wrong.
I was able to unlock the phone a mantain the data! Thanks
I have a special problem with an old Samsung Galaxy A3 2016 SM-A310F (Android 7.0 Nougat)
on which the correct combined file cannot be obtained
I have tried perhaps all FRP removal options without success
A310FXXS5CSH3
EDIT: it is possible, and worked just fine for me
- - - - - - - - - - - - - - - - -
Hi guys.
recently got a used s9, did all the updates (for security updates) and didnt even look, just kept updating and find myself on android P.
I've played around with it and found it less intuitive and pretty lacking in some regards. (and may possibly have some issues relating to the OS too; battery and phone)
software updates says:
Code:
current version: G960FXXXXU2CRLO / G960FOXXM2CRLO / G960FXXXU2CRLI
Security patch level: 1 January 2019
SM-G960F, Phone status: Official, baseband version G960FXXU2CRLI, Kernel version: 4.9.59-15076275, build verison: ppr1.180610.011.G960FXXU2CRLO
I'm wondering if it's possible to flash back to official Android O, while retaining untripped KNOX. (having KNOX in a usable/official status)
I've read online that it should be possible to do, but talk of using the "OEM unlocking" option has me weary.
I dont want to blindy follow a guide to find i've broken KNOX or have a brick.
some of you guys are pretty cluey. so i thought it be a good first place to ask.
cheers
Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
PoochyXXX
PoochyX said:
Once you pass a certain bootloader baseband you can't downgrade.... So odds are your stuck on Pie
Click to expand...
Click to collapse
Hmm, thats what I'm afraid of.
The downgrade guide i mentioned was here:
https://techbeasts.com/downgrade-ga...xy_S9S9_Plus_to_Android_Oreo_from_Android_Pie
not sure how legit it is though.
I havent read anything on XDA on the forums here, hence my new topic.
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
Ohhh
PoochyXXX
*Detection* said:
Yes you can downgrade, just flash with ODIN as normal using CSC and not HOME_CSC
The bootloader thing is true but you can check here which version you have vs which version you want to flash
G960FXXU2CRLI <<< Version 2
Boot the phone into Download mode, look for (BL:1 or BL:2 or BL:3)
As long as you are not trying to flash a lower version BL you will be fine
Click to expand...
Click to collapse
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
AP_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship_meta.tar.md5
MD5: 4ECA2C5657506ADE7B9D3B1721B0F958
SHA1: 14063F2CF282E37C2C7D59D80FFF404C400D306D
BL_G960FXXS2BRJ6_CL14479316_QB20373867_REV01_user_low_ship.tar.md5
MD5: 9529200BCE0C339B04152AC27DE34F5E
SHA1: 1821D68544490355042E7BF1589F2284FEF76324
CP_G960FXXU2BRJ1_CP10881699_CL14479316_QB19997556_REV01_user_low_ship.tar.md5
MD5: 8E07784192BCAF0454AB079ECBBD150D
SHA1: E7EFC1ED9E35C7B1F235792FAF46AFCAA945FF38
CSC_OMC_OXM_G960FOXM2BRJ3_CL14479316_QB20051937_REV01_user_low_ship.tar.md5
MD5: 17932E611CB0DF71C7B91BA84186843C
SHA1: 6BEE275DCC778124CB1EBF88EFA087538D9DCBE3
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.
tim455 said:
I booted into download mode and read and reread the stuff there. Doesnt seem to mention "BL" anywhere unfortunately.
but it has "U2" in a lot of different places, so I'm guessing its BL2.
The previous 3 or 4 have the "U2" version string, but the direct previous firmware has "S2" instead, and also the firmware that is suggested to use. Any hint as to what that means or if it makes any difference?
Second; I'd just like to triple-confirm I wont break KNOX (I'm pretty sure it wont, so I should be fine, but better to check now and make a fool of myself, than be sorry later)
Third;
I couldnt find/get the files off of the recommended sammobile ( https://www.sammobile.com/firmwares/galaxy-s9/SM-G960F/XSA/download/G960FXXS2BRJ6/245612/ ) as apparently they are not hosting the files right now, instead googled and found another source, but I'd like to be sure they are correct and aren't fake, so to speak. or wont compromise the integrity of the phone.
I've had a little google but the MD5 and SHA1 hashes dont really lead to anything in particular.
just googling the name of the files returns that they are also named similarly to the Slovenian firmware.
last;
according to http://doc.samsungmobile.com/SM-G960F/XSA/doc.html which appears to be the release notes for this specific version of the S9, build number G960FXXS2BRJ6 was indeed the previous version
any further insight from anyone would be appreciated.
many thanks.
Click to expand...
Click to collapse
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October
*Detection* said:
No you won't trip KNOX unless you flash something custom
It is in Download mode but says B rather than BL (First set of dark red text)
Files will be fine, no reason for anyone to "fake" a random firmware, and you cannot flash modded firmwares through Odin
DL it again from here if you are unsure
https://samfrew.com/model/SM-G960F/
G960FXXS2BRK3 is the November update Oreo, BRJ6 was from October
Click to expand...
Click to collapse
Thanks for all the helpful information.
Downloading again now just to check hash comparison.
AP SWAEV: B:2 K:2 S:2 -- looks good.
I'll reply back in a few hours with my results.
Many thanks.
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
To understand that you are downloading the BRJ6 firmware ?
Thx.
tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
:good:
dinamo1975 said:
To understand that you are downloading the BRJ6 firmware ?
Thx.
Click to expand...
Click to collapse
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
*Detection* said:
Good to hear, for future reference, you usually don't need to install any separate drivers, they are installed automatically by Windows when you first connect your phone to the PC USB
Click to expand...
Click to collapse
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.
tim455 said:
You are correct. The last OREO update was BRJ6.
The full name for my device is: G960FXXS2BRJ6
It wasnt being picked up at first, and I couldn't get it recognised in ODIN. one of my tutorials mentioned the SAMSUNG drivers, and once I had installed them it was picked up instantly.
But I agree with you, it should have been fine.
Click to expand...
Click to collapse
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin
*Detection* said:
You don't have to flash the firmware for your region if there is a later one for another region, for example BTU (United Kingdom) has a newer Oreo build as I mentioned above
Flash using HOME_CSC to keep data and csc as they are
Another advantage of doing this is you cannot receive OTA updates when CSC and firmware region do not match, so you would not get update notifications and would be forever on that Oreo firmware
The day you want Pie again, flash the correct region with Odin
Click to expand...
Click to collapse
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)
tim455 said:
Are there any disadvantages to flashing a cross region CSC? (other than maybe having to flash any newer updates manually)
Click to expand...
Click to collapse
Not really, I am running DBT firmware with XEU CSC just because the DBT firmware updated first, once XEU releases the same update I`ll flash back, and so on
tim455 said:
many thanks to @*Detection*
I found the latest version of ODIN around....
followed that guide I linked previously (without OEM unlock, as its not needed)
Installed the SAMSUNG usb drivers
Flashed the last OREO AP, BL, CP, and CSC
everything worked just fine.
running now great.
Thus ends my journey,
I hope Pie improves in the future.
Click to expand...
Click to collapse
What was the bootloader version of the Android 8 vs the version you had on Pie? Did you downgrade the bootloader as well?
can the same method be used to go down from 10 to 9? i have snapdragon 960w