Related
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
not work
says: SECURE CHECK FAIL : (BOOTLOADER)
also for me....not work....
Gracias !
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Hi Sir,
Also just went through with that dreaded 'Only official released binaries are allowed to be flashed' while trying to install TWRP 3.2.1-0 and root via magisk v16. My G950FD was just a few days old though bought this in used condition. Its currently on v8 Oreo. After flashing this with the stock rom https://forum.xda-developers.com/galaxy-s8/development/rom-galaxy-s8-t3749171 the phone sprang back to life its the 2nd day and still OEM unlock option has not showed up and am quite impatient already wanting to have TWRP and root. After flashing your Nougat bootloader, will I follow this same procedure again? https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
Thanks
So what to do, i wait seven days on my S8. OEM unlock appears, but the phone stays in prenormal mode?
Worked perfectly for me and I also have a G950FD. Thanks a lot man !!!
Wow thanks a lot! This worked great, I was about 3 days into the wait after I made a mistake when flashing..
Really wanted Notorious kernel so I can use Dex, all solved now.
THanks!
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Thank you! I have been fighting with this for what seems like forever and thought I was screwed but this helped! :good:
se puede usar ese metodo para s8+ con oreo ?
I got same problem 'Only official released binaries are allowed to be flashed' and i tried to flash stock rom but it gives fail. Also it says sw rev check fail 2 binary 1 on download mod. how ca i solve this?
The10y said:
I got same problem 'Only official released binaries are allowed to be flashed' and i tried to flash stock rom but it gives fail. Also it says sw rev check fail 2 binary 1 on download mod. how ca i solve this?
Click to expand...
Click to collapse
Just odwnload one firmware bit 2
maurote said:
Just odwnload one firmware bit 2
Click to expand...
Click to collapse
Could you please elaborate? I don't understand. I'm having the same issue.
Try this:
1)- change phone date manually back 8 days
2) go to software update and check for update. You should receive errors messages sometime. Don't worry. Just ignore it.
3)- restart phone immediately after checking software update and go to Developer Options and you should see OEM Unlock appear back. You may need to try checking software update few times to get it work.
Additional information:
https://forum.xda-developers.com/showpost.php?p=76746640&postcount=12
help please I had the same problem, try flashing the attached boot manager but I get error in odin
please twrp for CRGB not work
doesn't work, fail in both normal odin n the special odin.
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Hello,
Could you please tell us if that gonna work for S8 G950FD Oreo 8.0.0 AUG 2018 G950FXXU3CRGH?
I used RMM-State_Bypass_Mesa which is set vaultkeeper.feature parameter to 0 and remove /system/priv-app/Rlc" and maybe more!!
Because it's song good until the test reboot where the system is still stucked with this message.
Many thanks
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
I just get "SECURE CHECK FAIL : (BOOTLOADER)"
milaniov said:
I just get "SECURE CHECK FAIL : (BOOTLOADER)"
Click to expand...
Click to collapse
At a guess without more info I would say you are trying to downgrade your firmware
Hey Guys,
I just bought the s8 yesterday and realised I did not have the OEM unlock and tried flashing the rom from the guide posted here but it didn't flash via odin because downgrading is not possible. I found the date trick on xda's portal and that worked for me and I flashed TWRP by odin.
I allowed system modifications and wiped all data and install no-verity-opt as well as magisk for root. Phone booted up fine and everything was working, I wanted to go to twrp to just check if it was working and it returned with Only official released binaries are allowed to be flashed and well the phone is soft bricked. I was wondering is there any other way other than restoring stock firmware via odin to fix this?
OEM lock shows off in download mode still, I am waiting for the sammobile firmware (5 more hours lol) to download and just wanted to know this time around, is there a fix that I am missing or a step that I missed out so that I could reboot and twrp stays as well as the phone doesn't get soft bricked as this is my daily driver
ItsmYarD said:
Hey Guys,
I just bought the s8 yesterday and realised I did not have the OEM unlock and tried flashing the rom from the guide posted here but it didn't flash via odin because downgrading is not possible. I found the date trick on xda's portal and that worked for me and I flashed TWRP by odin.
I allowed system modifications and wiped all data and install no-verity-opt as well as magisk for root. Phone booted up fine and everything was working, I wanted to go to twrp to just check if it was working and it returned with Only official released binaries are allowed to be flashed and well the phone is soft bricked. I was wondering is there any other way other than restoring stock firmware via odin to fix this?
OEM lock shows off in download mode still, I am waiting for the sammobile firmware (5 more hours lol) to download and just wanted to know this time around, is there a fix that I am missing or a step that I missed out so that I could reboot and twrp stays as well as the phone doesn't get soft bricked as this is my daily driver
Click to expand...
Click to collapse
Install rmm by pass after root before reboot. This will keep oem unlocked.
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Kriranda said:
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Click to expand...
Click to collapse
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
xlucian said:
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
Click to expand...
Click to collapse
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Are you using the dm-verity thing?
rodrigodornas said:
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Click to expand...
Click to collapse
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
xlucian said:
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
Click to expand...
Click to collapse
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
rodrigodornas said:
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
Click to expand...
Click to collapse
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
xlucian said:
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
Click to expand...
Click to collapse
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
rodrigodornas said:
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
Click to expand...
Click to collapse
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
xlucian said:
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
Click to expand...
Click to collapse
but about downgrade.. what is my barrieir?
can just downgrade to same bootloader or i can downgrade to others versions?
thanks!!
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
trexander said:
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
Click to expand...
Click to collapse
Depends, will have to check in download mode, if kg state and/or rmm state is prenormal then you will have to wait.
Om my s8 if i flash firmware i can modify my phone as soon as i connect to the imternet.
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337
xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.