Related
Hi guys,
I was hoping someone could help me out. I have rooted before (long time ago) but I can't seem to find a lot of information on this specific phone (SM-J727S). I have been searching online (and across many dodgy looking websites, thanks No Script!) and this is about all that I have found:
The Galaxy J7 is also known as the Galaxy Wide 2 in South Korea
http://pdadb.net/index.php?m=device&id=11601&c=samsung_sm-j727s_galaxy_wide_2
It was released on May 2017, runs Android 7.0 (Nougat) and uses the Exynos chipset
TWRP has a release for the J700 series but I'm not sure if it would work on the J727S
https://twrp.me/devices/samsunggalaxyj7exynos.html
The source code for the system has been released, but I couldn't find a stock ROM (which made me reluctant to try TWRP)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=j727s
This is the closest I got to a Stock ROM but I don't trust the site, is this site trustworthy? (again, I came across too many dodgy sites to just download anything)
https://stockromupdate.com/2017/07/26/stock-rom-sm-j727s-samsung-galaxy-wide-2/
The KingRoot method currently will not work and is asking me to wait for an update (phone is probably too new to root?)
The closest thing I can find on this forum are these posts (but none reference the J727S model)
https://forum.xda-developers.com/galaxy-j7/development/root-sm-j727p-galaxy-j7-perx-td-lte-t3611202
https://forum.xda-developers.com/galaxy-j7/help/root-sm-j727p-galaxy-j7-perx-galaxy-j7-t3598117
So, I'm hoping someone could point me in the right direction. Thanks in advance
I'd thought I'd mention that the bootloader is unlockable in this phone. I had read elsewhere that other people cannot access the 'OEM Unlock' option on their version of the J7. It isn't the case with this phone
https://forum.xda-developers.com/galaxy-j7/help/galaxy-j7-pop-galaxy-halo-t3647805/page2
I also got a message from Google talking about my accounts being accessed by a 'J7 Pop'. I guess the Galaxy Wide 2 is also known as the J7 Pop?
So, I'm still on the track of rooting this device. I'm just gonna update any relevant stuff here.
The closest TWRP that I can find is for the 2016 version of this phone, it has the same Exynos chipset.
I'm thinking of trying this, but are there any problems with flashing the wrong version of TWRP? (Will I brick the phone? Or will it just error-out on recovery and boot normally?)
https://twrp.me/devices/samsunggalaxyj72016exynos.html
I also found (what I believe to be) the Stock ROM for this type of phone, you have to sign up to the site in order to download it. It is specific to SK Telecom (Korean telecommunications provider)
https://www.sammobile.com/firmwares/samsung-galaxy/SM-J727S/SKC/download/J727SKSU1AQD6/172065/
If someone can advise about going forward with the similar TWRP version I'd appreciate it. Cheers!
EDIT: Kinda answered my own question, from the TWRP download page https://dl.twrp.me/j7xelte/
Downloading an image for a different device, no matter how similar, usually does not work.
Click to expand...
Click to collapse
Any way to request an TWRP version?
I am Korean, and it's very hard It's angry me............................
XDDDD I'm from South Korea too and the J727S is customized with the Knox Enrollment Service that blocks the wifi and cellular data AND apk installization. (trying to uninstall it )
I found this: https://www.androidinfotech.com/2018/02/root-samsung-galaxy-wide-2-sm-j727s-nougat.html
anyone habe twrp for this model ????
Hi.. I've this model also.. tried to downgrade..but it can't..always failed
My friend was installing the twrp to root a J7 metal.
Now the cell phone does not restart, and I do not know what the **** it did KKkkkkkkkkkk
It wants to remove the twrp without formatting the device.
If installing the original rom by Odin using home_csc does it return to normal without formatting?
Restore
CPI Justiceiro said:
My friend was installing the twrp to root a J7 metal.
Now the cell phone does not restart, and I do not know what the **** it did KKkkkkkkkkkk
It wants to remove the twrp without formatting the device.
If installing the original rom by Odin using home_csc does it return to normal without formatting?
Click to expand...
Click to collapse
If you have the firmware file the phone was on at the time he tried to Root it just flash the files using Odin an you should be good !
peter couniaz said:
If you have the firmware file the phone was on at the time he tried to Root it just flash the files using Odin an you should be good !
Click to expand...
Click to collapse
This is will make a clear data???
He canoot loose the data from the phone..
Home CSC file !
CPI Justiceiro said:
This is will make a clear data???
He canoot loose the data from the phone..
Click to expand...
Click to collapse
If he flashes the Home CSC file it may restore data but he may have to start from scratch ! Sorry an good luck !
P.S did he have it backed to Google if so Google will give the option to restore when you sign in !
Very hard to find twrp or cwm foe this model..also the combination file..and upgreded to android 9..
So I just got my new ATT samsung J7 2018 and after searching i have not found a root or bootloader unlock method for the devices. Is there any work being on this device ? Could some one maybe point me in the right direction to get root on this device ?
ramious2012 said:
So I just got my new ATT samsung J7 2018 and after searching i have not found a root or bootloader unlock method for the devices. Is there any work being on this device ? Could some one maybe point me in the right direction to get root on this device ?
Click to expand...
Click to collapse
I have been searching for this for 1week now...and its all cause in " Dev Option " the ( OEM is Hidden ). Atleast im stuck in this part with this phone cause the rest i know with Odin.
I just got this phone a few days ago and I'm already looking for a root as well. I found one post on a root for this phone, but I kinda doubt it's legit. If you search 'Samsung galaxy SM-J737A root' on google, it should be the first search results. I'm keeping an eye on these forums for now.
ramious2012 said:
So I just got my new ATT samsung J7 2018 and after searching i have not found a root or bootloader unlock method for the devices. Is there any work being on this device ? Could some one maybe point me in the right direction to get root on this device ?
Click to expand...
Click to collapse
I have serach it just like that before and try afew of this Tricks but still wont show me the OEM option in Dev. That one with setting the date to 10 to 7 days before wont work cause i dont have that " Manual Software Update " option. I aint working atm so im like full searching away.:laugh:
anybody had any luck with this?
bigTINY779 said:
anybody had any luck with this?
Click to expand...
Click to collapse
Still of this moment No luck. Saw today with a so called Box Z3x something that works good ( the hack version that dosent use the actuall box ) but this Devi e Model Version wont showup.....
If you see KG STATUS: checking or if it's not there after the wait time then you shouldn't need to use the OEM unlock option
Original recovery post for the J7 2017
https://forum.xda-developers.com/ga...fm-g-gm-x-samsung-galaxy-j7-pro-t3835629/amp/
https://mega.nz/file/fFFSxALD#1nOVnhF0k6vojg19bK60YCSugHH4LPULdmhYx-wHhP0 here is the J7 2017 recovery that should work since the 2018 model is the exact same but minor screen differences (I do not take credit for this recovery I'm just supplying the link)
It should flash without issues as the bootloader should already be unlocked
TheExploitedOne said:
If you see KG STATUS: checking or if it's not there after the wait time then you shouldn't need to use the OEM unlock option
Original recovery post for the J7 2017
https://forum.xda-developers.com/ga...fm-g-gm-x-samsung-galaxy-j7-pro-t3835629/amp/
https://mega.nz/file/fFFSxALD#1nOVnhF0k6vojg19bK60YCSugHH4LPULdmhYx-wHhP0 here is the J7 2017 recovery that should work since the 2018 model is the exact same but minor screen differences (I do not take credit for this recovery I'm just supplying the link)
It should flash without issues as the bootloader should already be unlocked
Click to expand...
Click to collapse
The file in that link doesn't work anymore. Do you have another one by any chance?
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
kpwnApps said:
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
Click to expand...
Click to collapse
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
cooltt said:
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
Click to expand...
Click to collapse
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
snaksalot said:
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
Click to expand...
Click to collapse
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
cooltt said:
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
Click to expand...
Click to collapse
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
snaksalot said:
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
Click to expand...
Click to collapse
Hmmm so it may be that loophole is now closed, what you need to think about is if you deffo need root? Or is it just nice to have. I'm sure a dev will get round it soon.
snaksalot said:
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
Click to expand...
Click to collapse
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
kpwnApps said:
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
Click to expand...
Click to collapse
Okay I was completely unaware of TWRP being an option or the possibility of Magisk with a locked bootloader, now to clarify I'm running the latest unbranded US Region firmware for the US T-Mobile version of the Qualcomm Galaxy S7 "(TMB) G930UUEU9CSA3" that being said I have a few questions about how to specifically to proceed if you don't mind helping me?
First is the version of Odin available from the post provided above inst the modified version I've been required to use for all my previous flashing "Odin3_v3.13.1_3B_PatcheD" should I use this one or the version provided in the post above "Odin3_v3.13.1"?
My next question is that all the different versions and variants of TWRP available for my device the Galaxy S7 and the S7 Edge are either for Exynos Canada/International or Korea or the Chinese Qualcomm variant of each. Should I download and use the TWRP for the Chinese Qualcomm S7?
The sammobile link in the original post for "Android 8.0 Oreo Stock Rom" provides me with a list of the latest and up to date international versions of firmware for the Galaxy S7 Edge "SM-G935FD" I'm assuming I should just use the stock firmware image for my device "SM-G930U" instead?
The link for the no-verity-opt-encrypt-6.0 is dead but I don't think its needed because of something someone said in the original post about this method failing after latest security update "the one I'm on" https://forum.xda-developers.com/showpost.php?p=78115895&postcount=18 he said he solved it easily with information and another flash able zip from this post https://forum.xda-developers.com/showpost.php?p=77000849&postcount=47 and the zip from here https://forum.xda-developers.com/showpost.php?p=76564735&postcount=37
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
snaksalot said:
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
Click to expand...
Click to collapse
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
I'd be interested to know how this turned out if the device with V9 bootloader could be rooted with temp TWRP method.
Can i actually flash magisk on my 930u?
Is there any way to root my g930t ?
I'm on v9 bootloader, and i don't care about knox tripping.
Did developpers really failed to break the security of this little old device ? Or no one worked it ?
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Toolmighty said:
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Click to expand...
Click to collapse
Yes same hardware
cooltt said:
Yes same hardware
Click to expand...
Click to collapse
Can't get twrp to flash. Tried w rom as is, tried factory reset tried reinstall w/o auto reboot. All get same error
what about jruze root?
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
nm it uses flashfire
Toolmighty said:
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
Click to expand...
Click to collapse
Yes by using 1st and #1623 post number it can be rooted easily. I already have done that on both G930P and G930U.
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Softwarehttps://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
spawnlives said:
Samsung firmwares can not be downgraded. This is due to your bootloader version number. The bootloader version is the 5th number from the right of the firmware being downloaded. You can also check in setting - about phone - software info - baseband version ( 5th number from right). You can also tell bootloader number in download (Odin) mode with a line saying AP SWREV B:? : K? : S?. The B is your bootloader number.
Combination firmware works on the same principle in regards to bootloader numbers.
You can only flash the same or higher bootloaders version numbers.
Custom roms will work as long as the bootloader version number is the same ( or higher ) than what is on you phone.
Click to expand...
Click to collapse
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
RE: spawnlives. Many thanks for clearing that up, I now understand. Like many other people I have been trying to mix and match BL files from different OS variants to try and trick the device into accepting the main Nougat AP file via Odin, but nothing works.
These NEW combination files suggest that it is possible to downgrade the BOOTLOADER files on certain devices. However I downloaded all that was available for my device and tried the lot and found the only ROM that would flash correctly and properly was the latest one with the Binary 4 Bootloader. The rest would not register in Odin due to MD5 binary error messages.
In download mode my device AP SWREV B:4 K:2 S:2. ( So I have binary 4 which was released in January 2019, I believe). and this must have been updated when I updated to OS 9 Pie , using all the AP, CSC , BL and CP files.
So as you say, the answer is either , look for a Nougat 7.1 rom with a BL file that has a BINARY 4 code. Or buy another device that has the original Nougat 7.1 installed, which is silly really. :laugh:
Thanks :good:[/
The best you can do is roll back to Oreo. A new phone running nougat would be the best choice. I don't use custom roms but they all seem to keep up to the latest version. I have not seen one that ( latest version ) that is nougat favoured.
Click to expand...
Click to collapse
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
spawnlives said:
tsam19 said:
RE:spawnlives
Yes having researched the total list of softwares for the SM-T395 device, it seems the BL was updated to 4 on the 2nd roll out of Oreo 8.1. And having checked ALL stock Nougat variants, there was never any release of 7.1 with a bootloader binary 4!
I presume the BL Binary version is the 5 character from the right on the picture. (underlined red) :good:
It would make sense for Samsung to give the end user a choice what software they want, by keeping the BL version the same or giving a choice of BL selections to allow upgrade or downgrade.
Anyway, I rolled back to Oreo 8.1 with the binary 4 BL. And unfortunately there aren't many CUSTOM roms , nor a working TWRP for the Samsung Galaxy Active Tab2.
Thanks again :good:
Click to expand...
Click to collapse
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
spawnlives said:
tsam19 said:
spawnlives said:
Yes the bootloader is 5th from the right.
I don't own a tab2. If no work twrp can be found and you want to at least have root try using magisk and used the patch root method.
Also to avoid possible upgrade turn off automatic updates in setting - software update as well as in developer option - auto update system.
Click to expand...
Click to collapse
Have rooted the device no problem with magisk and patching the original boot img file. Then flashing patched boot img via odin. Causing device verification to need to reformat the device, resulting in correct root.
Once a device , this device is rooted, no official updates can be installed anyway. When you try to uodate software, a pop up shows as the device recognises the software has been modified.
As for TWRP there ISN'T any version of TWRP available for the Samsung Galaxy Active Tab2 (SM-T395). I have even emailed the makers , developers of TWRP why there isn't one in their device inventory list on their webpage.
So no TWRP, and NO custom roms either for this model.
My concern , was all about finding a valid , safe way to downgrade back to original Nougat 7.1. And until someone can produce a working image with a BL with binary 4. Then there's only one optiin and that is to buy another untampered device with Nougat 7.1 out of the box and leave it un updated. :good:
Thanks for replying.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
tsam19 said:
Hello all
Been a member here for some time now and have a perplexing issue.
I upgraded a Samsung Device SM T395 to OS Pie 9 and decided I didn't like it. (There are no other posts with help on this matter)
I kept the STOCK roms Nougat 7.1 and Oreo 8 and want to put Nougat 7.1 back on my device , but is proving difficult using ODIN 13.3.1 or any other version of Odin. The result is FAIL, that's using a combination of AP, CSC, CP and BL.
I managed to get Oreo 8 back on it, but want Nougat 7.1 original installed instead.
Can anyone tell me can ADB Fastboot be used to Flash a Stock Rom back on a Samsung Device or is Odin the only method?
I know there are other similar programs like QFIL and Qualcomm that I have used for the Mi Max brand devices.
The device was rooted with Nougat 7.1 originally and I have USB debug set and FRP / OEM lock off also. So there's no problem there.
The last resort (stupidly expensive idea :crying is for me to buy another exact device that has Nougat 7 installed when boxed up!
I don't see how upgrading to Pie 9 and then wanting to go back to the original factory installed rom is a big problem, can anyone explain?
Would a CUSTOM Nougat 7.1 rom work if installed via TWRP ?
I have also come across this COMBINATION Software https://samsungcombinationfile.com/samsung-sm-t395 that is supposed to allow the downgrading of Android software, but hasn't worked as I had been lead to believe.
https://combinationfirmware.com/combination-samsung-galaxy-tab-active/
Thanks for reading :good:
Click to expand...
Click to collapse
To answer your question of how is downgrading such a big problem, it is due to security reasons, to keep your device as secure as possible with the newest available software and the latest security updates.
Sent from my SM-S767VL using Tapatalk
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Good news! so you've manged to root Android 12? if so, what steps did you take?
beanbean50 said:
Good news! so you've manged to root Android 12? if so, what steps did you take?
Click to expand...
Click to collapse
Android 12? No, I'm on 11.
TarikVaineTree said:
Android 12? No, I'm on 11.
Click to expand...
Click to collapse
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
First of all: I'm no Dev...just someone who likes to play lego. From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk. I've read a good startup here. Hopefully this makes this...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
VerdandiAmine said:
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
Click to expand...
Click to collapse
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
beanbean50 said:
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
Click to expand...
Click to collapse
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
TarikVaineTree said:
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
Click to expand...
Click to collapse
I've finally managed to root Android 12 after weeks of trying.. Yippee..!
TarikVaineTree said:
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
Click to expand...
Click to collapse
Using phone info my correct CSC is VAU. The software I used to get firmware is Frija and I deployed it with Odin.
So flash the magisk patched boot.img file to AP via Odin as well as flash the firmware BL file to BL? Okay I will try this with VAU firmware and report back with what happens.