So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:
I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!
I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!
Yep
Ok
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.
Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.
Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
PLAY911 said:
Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
Click to expand...
Click to collapse
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
syked said:
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
Click to expand...
Click to collapse
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
[email protected] said:
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
Click to expand...
Click to collapse
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
syked said:
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
Click to expand...
Click to collapse
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
[email protected] said:
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
Click to expand...
Click to collapse
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
syked said:
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
Click to expand...
Click to collapse
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
[email protected] said:
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
Click to expand...
Click to collapse
G'day mate.
That's strange. I have never seen Optus sport display pop up ads. I've just watched over 15 mins of an UEFA Champions league game on my un rooted Android tablet using the Optus sport app and there were no ads.
Are you sure there's no other apps running in the background that could be generating the pop up ads but thinking it's Optus sport.
Agreed. It is an awesome box
For me it was just easier to Chromecast from my phone or tablet when using the Optus sport app because I couldn't be bothered continuously loading into recovery to have magisk hide work and I don't see the point to leave my box on just for that reason.
As it stands my box is default rooted and I'm using ALVATECHs rom which I find works great.
I'll post some steps later to help you and others loading magisk though.
Magisk in Recovery mode
Before anything always back up your box. If you use TWRP then create a whole back up which makes it easier to restore and if don't use TWRP then maybe you should.
To get Magisk working on the GT-King follow these steps.
Magisk will be installed into the recovery partition so if you flash the image to recovery, you will loose TWRP or default recovery but you could use an SD card to load into TWRP or default recovery and similarly you can use the patched recovery image from Magisk to and load that from SD card when required. I have not worked out how you can load Magisk recovery partition but also load TWRP when required. Technically this is possible because it's a patched recovery image with TWRP. There might be some sort of key sequence that will allow this but have not played enough with it to work it out. If you leave your box on all the time it should be fine because you can boot into "magisk recovery" once and then leave it on.
1) You need a recovery image.
a)If you have root already (such as default root), you can use this command in a terminal app which will covert the recovery file from the system to recovery.img and we will save it on the internal storage (home level).
Code:
dd if=/dev/block/revovery of=/mnt/sdcard/recovery.img
b) if you don't have root because you tried flashing Magisk through TWRP or have manually unrooted then or if you can't be bothered using terminal, you can use my recovery.img here recovery image and save this to a location of your choice2) Download and install Magisk Manager APK from here
3) In Magisk manager main screen click advanced options tick Recovery mode
4) Now next to Magisk Click install then selection the option where you have to select the image
5) Select the image file from either step 1a) or 1b)
6) Give it a few moments and Magisk manager will create a patched recovery img to the same location as the original recovery img
7) Now you need to unroot your device if it's not already by trying to flash Magisk in TWRP. I use impactor universal unroot for this which can be sourced from the play store or other means and follow the instructions in the app. After you restart, the device is no longer rooted but we will need use the magisk patched recovery which will give you root
Now here is where you decide what to do next....
i)Do you boot into existing TWRP recovery via depressing the reset pinhole whilst plugging in the power and then permanently flashing the new patched recovery image or
ii)Do you copy that patched recovery image to a SD Card, renaming it to recovery.img and booting off that temporarily via depressing the reset pinhole whilst plugging in the power
Either way, once you boot into that "magisk recovery" it is now installed and works a treat and have root access but you can hide root per app via Magisk hide
The systemless-host module can be installed via the module manager if you use Hosts file to block ads (I use energized host file for this). I think the path for this after it's installed is /data/adb/modules/hosts
Really appreciate effort and detailed info mate . Will try that later tonight and will let you know. Cheers
Sent from my SM-G950F using Tapatalk
I flashed the magisk_patched/stock-recovery.img with twrp.app and worked!
Many thanks to Syked for this detailed info how to get Magisk working.
Maybe somebody could confirm this is working on the new 2022 GT king ii with the Amlogic a311D2 CPU.
Magisk is a must for me so I'm not buying until this is possible.
Hello guys, decide to mount this tutorial because I still see a lot of people with doubts, yes we already have how to root our device
I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
A tutorials too complex for some users, teaching you how to create your own Magisk modified Img boot, but I like simplicity, so if you don't want to break your head too much, here's a tip, use a successfully modified img boot , what you need is to install the rom stock that was used to create the modified boot first.
let's go to the tutorial, warning that the files posted here are not my own, and if it doesn't work, check if you're not commenting on any flaws, don't try to memorize the tutorial, follow it step by step. come on!:dedos cruzados:
1 - first follow these steps to unlock the bootloader:
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.
Now let's go to the next step, reinstall an outdated system, I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
2 - installing the stock ROM that we will use:
download this rom: https://samfrew.com/ru/download/Gal..._Wi-Fi-__/rue3/KOO/T290KSU3BUE1/T290KOO3BUE2/
OBS: a little detail about this firmware, it is made in arm32, which apparently makes it "lighter", but also has a more acidic use of RAM memory. This was the last software I installed on tab A, and I can say that the use has become better with it, but if you want to stay in the stock rom, even custom gsi didn't get such a good performance. It's worth testing, but be aware of the risks, I'm not responsible for errors.
Updating: use a modified version of Odin, to do the installations, be careful with downgrades, I managed, I was in the most current version of March, and I managed anyway using this modified Odin, but do it at your own risk, download the most current version here:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
And install via Odin, if you need more details just a Google, there are already millions of tutorials for that lol
when you get here you should already be aware that you have lost all your data, but it is necessary that the OEM option is enabled in the options, so in the CSC session use Home CSC, so that you leave the data saved, and do not lose the initial settings : )
once with successful installation, we will now install the file modified by magisk
3 - magisk Installation:
Intall TWRP: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
just follow our friend's tutorial, with a little observation, after starting the process in odin, be sure to hold the volume up button + turn on, to be redirected to the TWRP.
follow the standard steps to install magisk, if it doesn't work, you will have to manually modify the system boot.img along with magisk maneger.
if case of problem:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
I haven't had the tablet in my hands for a few months, so unfortunately I can't help more than that, as I said this was the last system I used, just because GSI are not very functional and are not always light, sometimes they crash more and it has more annoying bugs to fix that discourage daily use. my tip is, stay in stock Koo, excuses for those who can't, the most I can do now is guide them.
As a gift for you, I will teach you how to use Xposed :3
remembering, I did several tests that several times I faced bootlooops but in the end it worked for me, so notice, do it at your own risk.
5 - How to install end use EDexposed with Magisk
these versions were the ones that worked without problems in this rom
Install Riru - (Riru core) V21.0
Install Riru - Edxposed v 0.4.6.1(4510) YAHFA
Reboot, after reboot, install Edxposed Manager
and you can be happy
I thank you all for your help, and remembering that this was just a compilation of tips, to facilitate everyone, take due care to avoid problems, and don't forget to thank: 3 ?
Has anyone attempted this yet?
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
EngineeNerd said:
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
Click to expand...
Click to collapse
is the topic dead
EngineeNerd said:
is the topic dead
Click to expand...
Click to collapse
Hi friend, sorry but there are more current ways of routing, even already working on a TWRP, but now you can do the following, try using the same Firmware in the same version of the bootloader, otherwise there will always be an error, the file compressed this modified to work with Odin, I tested it myself on my T290, but I cannot guarantee its effectiveness if I try to use it in another version, I do not recommend doing this even.
I had trouble unlocking the bootloader until I did this:
After enabling OEM unlocking and turning the device off, plug in the USB cable. Hold both Vol + and Vol - at the same time, then unplug and replug the USB cable. The bootloader unlock screen should come up.
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
does this work if you're on a11?
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking o
Click to expand...
Click to collapse
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
Click to expand...
Click to collapse
what are you specifically asking? the TWRP here is very functional, but custom roms are not very stable for this tablet, some GSI behave well, but it's still better to stock debloated
WillisD said:
isso funciona se você estiver em a11?
Click to expand...
Click to collapse
I do not think so
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
MythoAegis said:
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
Click to expand...
Click to collapse
yes, you can go back to previous versions, but it gets harder when you upgrade bootloader version.
In order not to crash the downgrade, you need to look for the latest Android version you want, from your region you are in now.
An example:
I'm on the latest version ZTO - Brazil - Android 11
to get back to Android 10 I need to download the latest ZTO version with Android 9, of course you can try between different regions, but it will be a little more complicated.
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
themace51 said:
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
Click to expand...
Click to collapse
You mentioned it's on Android 11, didn't you?!
well, I don't have Tab A with me anymore, but the suggestion I give you is to try to go back to Android 10, then install TWRP, and then try to install magisk, I can give you the last firmware I installed,
currently he is with my brother.
The firmware is Koreano, as I said, it is 32bits, and super functional.
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки - 4PDA
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки
4pda.to
take a look here, search for the firmware I told you about, very good by the way
Hey
I am on T290XXU3BUC1 and i do not understand the language on the link you post
I tried your tutorial , but i am getting
sw rev check fail [aboot] Fused 3 > binary 3
hello, about that, but lately I don't have much time, but I'll update it today if I can, you probably got this error because this firmware is old.on 4pda there is a newer version with root, remembering that currently you can root through twrp, I'm going to port my last attempts here, but I notice that I don't have the tablet in my hands. use translation tools, the site is in Russian
I updated the guide as I could, any doubts I'm still here, but I can only guide, it's no longer possible to test.
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
themace51 said:
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
Click to expand...
Click to collapse
have you tried to put the firmware I mentioned? this tutorial probably won't work on android 11 one ui 3.1, i say this because the TWRP is a bit old, so as long as it's on the updated firmware it's really hard to do anything.
if you don't want the specific KOO Firmware, you can get the latest firmware version for your region which is on android 10.
After months of deliberation I finally decided to root my Note 9. It was the first time I've ever tried rooting and it seems to have gone horribly wrong. To root the phone, I followed the guide in the video titled 'How to Root Galaxy Note 9! [EASIEST METHOD]' on youtube which has an instruction link in the description. As a new user here, the forum doesn't allow me to post links yet, so please just type the title on youtube and it'll come up as the first result.
What I did was:
- unlocking bootloader
- Flash AP file with TWRP version 3.4.0
- Wipe data
- Since I was worried about using a software from an unknown source, I then flashed the official magisk v20.4 instead of the 'N9-S9_root_for_oem_issue_devices_v3' file recommended in the video.
After doing so, the note 9 restarted and showed the error message "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.". I allowed the phone to reset.
Following this, the phone restarted and showed exactly the same message of 'verification failed' and no amount of going through the rebooting process resolved the issue. I googled the issue and was advised to flash the phone with Odin by going into download mode. I then tried to go into download mode, but the phone will simply not go into it and tries to restart the normal way. I also tried to connect to my laptop to see if I can flash with odin but the phone was not recognised at all by the computer.
I then tried to reboot using the twrp key combo and this worked. I then decided to try flashing with the 'N9-S9_root_for_oem_issue_devices_v3' file in the tutorial. Yet, this led to the same issue as with the official magisk file.
Looking at some rooting tutorials, I see that some of them recommend flashing CSC, AP, BL and CP instead of just the AP in the tutorial I followed. I then thought that perhaps the issue is I need to install a ROM on the device. I therefore tried to load the lineage 17.1 ROM in the micro SD card and installed it (top left option on twrp 'install') as well as the magisk and disable_dm_verify_forceencrypt zip files.
In hindsight, this was a stupid move from me - I did so I was in full panic mode at that point and desperate for a solution.
After doing so, the phone rebooted and showed a booting animation of a single blue curved line stuck with a circle rolling from right to left on it.
I left it for a while, hoping that it meant the new ROM was booting. 30 min later it was still stuck on the animation!
I then tried to reboot the phone. Pressing power button did nothing. I then tried different combinations and eventually power + volume up + bixby allowed it to restart in TWRP mode.
As of now, the phone is still in TWRP mode. The phone is still not recognised by my laptop and will not enter download mode if I press volume down + bixby when restarting.
I am fully aware that I've screwed up the rooting process and feel awful about it. It was the first time I've ever tried rooting and I really hope it is only a 'soft brick' and that my phone can be saved. I would really appreciate if anyone here could advise what I can do to complete the root process correctly from here?
Many thanks,
Sam
Is there a "download" or "bootloader" option when you press the reboot button in TWRP? My Note9 is on stock, so I'm not 100% certain myself. However if there is, that should take you to Samsung's download screen. This way you can send yourself back to stock if you give up on rooting your device.
BTW, I do recommend following a note9 rooting guide on XDA (it's not too hard to find) over a youtube video, since YouTube videos can often be out of date or a little sketchy.