I just upgraded to Pie on my SM-T380 and am now running into an issue after trying to re-root the tab.
I had previously rooted the tab using TWRP and Magisk and didn't have any problems except that I could not update Magisk since every time I went to TWRP I could not mount data, etc. I did an upgrade from Oreo to Pie today and it appeared to work without problems. I then tried re-rooting following the instructions here SM-T380 Rooting Guide but now only get an error screen when booting up (Security Error...) stating that "Only official released binaries are allowed." I can't boot into recovery and I've tried to reflash TWRP and get a FAIL in Odin every time.
I've tried to find the stock images to just reflash everything through Odin but am unsure which is the right image file (https://www.sammobile.com/samsung/galaxy-tab-a-2017/firmware/#SM-T380, I'm in the US). Can someone point me in the right direction?
Appreciate any help!
I found firmware for my T280 at this website https://samfrew.com/
Related
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
Hard to help if you do not write in detail. Such as phone type, links you have used, etc etc
Hipp0123 said:
Hello everyone, I went to root my phone today, I used a Youtube tutorial with the exact links/downloads given. Followed the steps but my device is having trouble rebooting, it is just stuck on the Samsung logo flashing and I'm not too sure what to do. Also when it boots up I get the error message in the top left of my screen saying "Recovery Is Not Seandroid Enforcing", hopefully that helps.
Thanks.
Click to expand...
Click to collapse
You need to flash SuperSU manually.
1. Flash TWRP
2. Format data
3. Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip
http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
You simply brick your phone. You need to know that there is not Chainfire-AUTO-Root for Nougat, so you need first flash Stock FIRMWARE from Sammobile, then flash TWRP and flash SuperSU
Or you can flash many of 100 roms with prerooted supersu and busybox.
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
seppdep said:
Hi there,
After upgrading my S7 Edge G935F to stock version xxu1dqd7 (with latest May 2017 upgrades) I had to install TWRP (twrp-3.1.1-0-hero2lte.img) again.
Unfortunately this change will NOT recognise my pattern lock now! I had to re-install the stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) using the HOME_CSC file to hold my data.
This re-installation brought me back to the game, but without TWRP and hope for root, but the pattern pin (the same) is now working...
Update 1
Installing TWRP (twrp-3.1.1-0-hero2lte.img) over the new stock image (DBT-G935FXXU1DQEF-20170523093738 with ODIN) without having the pattern lock enabled feature during start will result in stuck on
the samsung title.
Update 2
I had to repeat the step above (stock firmware), so stay now without root.
Will check later with other stock versions
>It seems you didn't format the data partition or dm-verity was not installed. Happened to me, won't boot if >anything is altered like when installing a custom recovery.
Yes, I did it with and without dm-verity, All 3 options,
TWRP (ok, but pattern lock will not recognized)
TWRP + supersu (2.82) (stuck on the samsung logo)
TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo)
Yes, I didn'T format the data partition. Didn't want to lose my data ( Never had a problem to upgrade stock roms on my old S4 and root after).
Before the stock upgrade, I run with the Jan 2017 patch level (I bought this 2 days ago) and was able to root with the above method.
Today I wanted to jump the the latest stock version but run in trouble then.
Update 3
Downgrading to Stockrom from 2017-Jan-30 Germany 7 G935FXXU1DQB3 G935FDBT1DQA8 is not an option (anymore), The system boot up but with lot of errors and it's unresponsable and not usable.
Upgade then to the April patch status (2017-Apr-17 Germany 7 G935FXXU1DQD7 G935FDBT1DQD1) brought me back to operational,
but TWRP + supersu (2.82) + dm-verity (stuck on the samsung logo).
Will try it now with the Februar patch version
Downgrade to the Feb patch status (2017-Feb-23 Germany 7 G935FXXU1DQBX G935FOXJ1DQB2) had the same resut like the Jan version - not usable.
I'll give up now and install the April version without TWRP.
I need root to restore my apps AND data with Titanium Pro.
Click to expand...
Click to collapse
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
doclorenzo said:
With the TWRP + supersu root method, no matter what 7.0 stock ROM you use, you will not succeed before you disable boot pin and format data. You can restore data after rooting.
So start with the latest stock ROM that is working 100% for you, flash twrp, format data, flash supersu, and it should work. You have to format data because root and stock rom currently does not work with encryption.
Or even simpler, use the new cf autoroot, however it seems you still have to format data.
I had high hopes that the new cf autoroot nougat binary would work with encryption, but alas it seems it doesnt, at least I had the same wrong pin code at boot issue as with twrp. I havent had time to test it, nor to format data and root, so I am currently not rooted.
Click to expand...
Click to collapse
Thank you doclorenzo.
I had success with the latest stock version (xxu1dqd7) and your recomendation to format data in TWRP.
In short: Boot in Download mode, Install TWRP via Odin, Boot into TWRP - format data, supersu (2.82) + dm-verity
and then restore all data. Unfortunately it requires lot of time (at least 4 hrs to restore the apps + more for fine tuning)
Thank you and hope to have a better way with the next stock update and TWRP
I really try to do stuff on my own without having to make other people repeat themselves a million times but this process is just so complicated and confusing that it's giving me a headache.
My goal: Be able to boot up LineageOS 16.
Code:
httpsforum.xda-developers.comnote-4snapdragon-devrom-lineageos-16-0-t3900807
It says it requires MM firmware and TWRP 3.2 or higher.
I have the retail 900V Note 4.
So far I have managed to downgrade to 5.1.1 and unlock the bootloader. (It says MODE: Developer)
From there I was able to install TWRP 3.0.2.
But now what?
Right now I have a phone that won't boot because there is no OS on it.
1. I can't get Odin to flash any other TWRP besides the 3.0.2 version. Odin just freezes halfway through and never completes. I'm assuming this might be because I'm not on an unlocked MM build yet. Currently still on LP.
2. I'm unsure how to get root back once I upgrade to a MM build. (I only have access to WiFi atm and this guide says it will disable it.)
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
Any help is greatly appreciated.
I'm no expert so some of the things I'll suggest may not work.
As a first thought have you tried installing Lineage from TWRP 3.0.2
I'd suggest
1. downloading the OEM MM ROM from Sammobile and install that first so at least you have an OS to start with.
2. after setting it up install the official TWRP App update to the latest version of TWRP
3. ensure SuperSU is on the internal drive although I've not had problems installing it from a MicroSD and install it from TWRP Recovery. You should now have a rooted phone on the latest version of TWRP
4. put the Lineage ROM on the internal drive although again I've not had problems installing from a MicroSD (although it does take longer) and after 'Wiping' the system (it should tell you what steps are required from the Lineage guidance) install it.
5. After setup you will probably have to install SuperSU again or Magisk assuming there's no trace of SuperSU left on the system.
Hopefully someone will jump in and comment if I've missed something obvious or got it all wrong. Although I've rooted all 3 of my SM-N910Fs and SM-N910C at least once and installed various ROMs I don't consider myself particularly knowledgable. So far I've not bricked any of my phones or Tablets.
I really appreciate the reply.
Currently I am trying to flash 5.1.1 stock onto the phone and Odin just freezes about 25% into system.img.ext4
I have tried a dozen times.
I believe what makes my phone so difficult to flash is the stock bootloader is locked.
I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage
I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).
Hi, I wanted to finally root my phone so I followed the Magisk guide but it's prereq. is to install TWRP first and apparently the official S8 firmware which my phone has (Android 9)
triggers 'auto recovery restore system' every time the phone resets effectively making it imposible to enter TWRP mode 'cos it replaces it with stock recovery mode
So the TWRP guide says I can fix this by deleting a certain system file which, you guessed right, requires root...so I'm stuck in a loop
Any ideas how to deal with one or the other? Is using an older root method like SuperSU the only way since flashing an older or custom OS requires TWRP again
Just wanna root my S8 G950F
Shaped65 said:
Hi, I wanted to finally root my phone so I followed the Magisk guide but it's prereq. is to install TWRP first and apparently the official S8 firmware which my phone has (Android 9)
triggers 'auto recovery restore system' every time the phone resets effectively making it imposible to enter TWRP mode 'cos it replaces it with stock recovery mode
So the TWRP guide says I can fix this by deleting a certain system file which, you guessed right, requires root...so I'm stuck in a loop
Any ideas how to deal with one or the other? Is using an older root method like SuperSU the only way since flashing an older or custom OS requires TWRP again
Just wanna root my S8 G950F
Click to expand...
Click to collapse
Sounds like you haven't install twrp correctly.
What guide are you using and how have you actually tried to install twrp.
If using magisk there are two ways of installing, one with twrp one without twrp.
Hi,
Disclaimer:
First post here, sorry if opening a thread here instead of replying to, e.g.
https://forum.xda-developers.com/t/rom-official-gts4lv-gts4lvwifi-13-lineageos-20.4536203/
is not correct. I've read the forum rules, and searched for similiar issues with that device, but at a glance did not find something alike.
Appologies in advance if I did a mistake or overlooked something, I'll try to learn and do better next time.
Device: Samsung Galaxy Tab S5e LTE, SM-T725, gts4lv
Bootloader: unlocked
Aim: magisk rooted twrp in recovery, lineage20
Following these instructions, I'm able to root the latest stock rom with magisk, flash that via odin, and get a magisk-patched twrp recovery:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
https://twrp.me/samsung/samsunggalaxytabs5elte.html
(Details:
Get the current stock via frija, extract AP, patch via magisk on device, adb pull to host, flash stock with odin (magisk'ed AP,BL,CP,CSC).
Reboot device into stock, finish magisk app install. Reboot once. Device rooted. Installed TWRP app, granted root permissions to it, download twrp for device, patched image with magisk, flashed that to recovery via twrp app.
Sucessfully tested twrp, looks good.)
Trouble begins when I install lineage via twrp adb sideload, following
https://wiki.lineageos.org/devices/gts4lv/install#installing-lineageos-from-recovery
with the difference using twrp instead of lineage recovery.
Coming from the magisk-in-twrp-recovery rooted stock, I did a factory reset (wipe cache/dalvik cache/data), and twrp adb sideloaded the latest lineage20 for that device.
Console command outputs look good, no obvious errors. After the initial reboot, I got a recovery boot loop.
Going back to square one, reverting to magisk rooted stock using odin.
Then, I also tried sideloading lineage19, same result.
For the record: I initally started the lineage installation also flashing NikGApps or MindTheGApps (arm64), and the fdroid priviliged extension afterwards, but got the boot loop there.
I wiped system/data/cache/dalvik, went back to magisk-in-twrp-recovery rooted stock as described above and then tried with just lineage, but still a bootloop.
Do I maybe have to once again flash the AP with the VBMeta.tar via odin prior to moving from the rooted stock to lineage?
I am a bit hesitant to do so, because
https://topjohnwu.github.io/Magisk/install.html#important-notes says
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
Not sure if the VBMeta step is only required to initally unlock the device.
I am thankful for any advice how to narrow down the issue.
Best regards
I tried to install lineage+twrp+magisk/root at the same time without great result as well.
I was able to install lineage and twrp, but when I was there it was impossible for me to "activate" Magisk
So I switched back to custom rom + twrp + magisk/root. All good, but that's not what I was searching for.
I installed Lineage from Odin, then flashed twrp. https://wiki.lineageos.org/devices/gts4lv/install.
Try this guide, if you'll have success please let me know how you did it.
See my post here https://forum.xda-developers.com/t/rom-13-official-crdroid-9-4.4541563/post-88458655
Issue is with patching twrp with magisk it seems. Use either stock Lineage recovery or follow instructions I posted.