Related
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
saywhhaa33 said:
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
Click to expand...
Click to collapse
First of all you have entered wrong model no here note 5 model no should be SM-N920xx
1)Have you enabled Oem unlocking from developers option before flashing twrp and cf-autoroot using odin? If not then you done a mistake!!
2) Have you tried to flash latest stock firmware using odin with latest usb drivers installed on you pc and proper odin flashing guide?(Flash latest 6.0.1 for your device with latest usb drivers installed on pc and connect phone to main usb port using original usb cable) After flashing stock rom if your facing bootloop then you can try reset through stock recovery (Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
3)If you can boot into twrp recovery normally then flash any custom rom suitable for your device i.e. for sm-n920p..Custom roms are pre-rooted so no need to flash cf-autoroot..Flash custom rom, if you successfully boot up the rom( It's difficult to boot custom rom though if you haven't enabled oem unlocking you will face custom binary is blocked by frp protection),then enable oem unlocking from developers option and try flashing stock rom again
4) Next option for you is download Samsung smart switch for pc, install latest usb drivers on your pc, connect your phone to pc in download mode(Press volume down+power+home button simultaneously),in smartswitch select emergency software recovery, it will ask you imei,model no and serial no which you can find either on box or back panel of your phone,smartswitch will detect latest stock firmware for your device, hit update now,give some time until update complete..Your device will be automatically reboot..If even you face bootlopp, then goto stock recovery(Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
**IF SUGGESTION IN SECOND POST HELPS YOU THEN ITS DONE, AVOID NEXT SUGGESTIONS**
Are you sure you can't install cf auto root again to solve it? IF not...
I did a search and got hits for twrp for N910P. Get it loaded, get it wiped and have another shot at success. Next way to get rid of the persistent rooter gone rogue, load up a factory BL + AP. If that doesn't work download another version and try again.
I've enabled OEM unlocking, flashed latest stock AP...BL.. And so on, factory reset in both factory and TWRP. I have also tried flashing CF Auto root again to see if that would fix it also custom ROMs bootloop except for CM13 and Lineage OS- Which is weird because the ROMs are for the SM N920C model and I'm and Sprint model, So I don't understand that. Weird!! Everything recognizes me as SM N920C except when I am in download mode. Also, having no imei or any back ups make its even harder since my computer completely crashed on me because I am unable to use Samsung smart switch due to the wrong model and null imei. So I'm completely stumped with this issue. Not sure if its a corrupted partition or folders not being in the correct folder locations along with wrong permissions, I've literally stressed everything to my knowledge about this and I'm all out of what issues this could be related to
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
chemeleon said:
So I tried to mod my phone (with this, if you're interested https://forum.xda-developers.com/gal...creen-t3759567) but I did something stupid. I thought TWRP was working properly but I'd installed Oreo and didn't wipe data. Well I installed the zip anyway. At the end, an error showed up (could not mount /data or something similar) and my phone will now not boot.
If I try to boot the phone, it just vibrates and stays black. Volume Down + Power + Bixby gets the phone out of this state and the charging screen shows again. I can't boot into TWRP at all. I can boot into download mode but Odin keeps failing when I try to reflash the XEF Oreo firmware (screenshot is in the attachment, it says passed but doesn't attempt to flash the files). I managed to flash TWRP which worked but since I can't boot into it it didn't help. Anthing else I can flash with Odin, or can anybody tell me what's going on / if it's unrecoverable? (I've tried a couple of different versions, they all exhibit the same behaviour)
Click to expand...
Click to collapse
There is a newer version of odin, are you using that? You will need that to flash Oreo. Can get it in the link below. Odin v3.13.1
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Doh! Had it already, was the only one I didn't try. It's flashing now. Many thanks
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Post any bricks below that you have encountered!
I'm interested in how many variations there are, and how common they are.
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Hovo said:
One weird error I'm getting all of a sudden is "Custom binary blocked by FRP Lock" when I tried to reboot my phone. Any ideas?
Click to expand...
Click to collapse
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
TechNash said:
Please describe this issue in further detail. Has this been happening out of nowhere, or did you just try flashing something via Odin/Download mode or TWRP.
Also, before flashing did you enable OEM unlock
This also happens when something flashed via Odin/Download mode is incompatible.
Are you still able to boot into the default system partition? If not safe mode?
Click to expand...
Click to collapse
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
It goes away when u log in to google with the last account that is associated with the phone
Hovo said:
I should have updated my post, I'm not sure what happened but I flashed stock through Odin and the problem went away, after that I was able to flash twrp and root/install other roms.
It's still weird that the problem happened out of nowhere, not sure what triggered it.
Click to expand...
Click to collapse
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
TechNash said:
Probs OTA. It happened to me my first 3 tries. Ended up factory reseting, and installing fresh via Odin, didn't fix it.
I just turned off auto reboot on Odin, and then pulled my battery on my J7. Booted up straight to Recovery from there.
Click to expand...
Click to collapse
It would make sense if it was an OTA update TY
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Nightwinter said:
Hi, I tried to root my phone and I got this error, I don't mind restarting the phone, but isn't there a way for me to backup my data (photos mainly) first?
Click to expand...
Click to collapse
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
TechNash said:
Sorry I didnt respond.
Looks like you didnt flash encryption breaker. Keep this on your SD Card as its a great way to recover from these errors, and you will need it when you flash ROMS.
Just boot in recovery, flash ashix no verity no encrypt, then reboot into system. You shouldnt have this error.
Click to expand...
Click to collapse
Keep what in the SD card? the is no file in your quote.
Nightwinter said:
Keep what in the SD card? the is no file in your quote.
Click to expand...
Click to collapse
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
graevon said:
He's referring to the encryption breaker file ("no-verity-no-encrypt_ashyx.zip") in his first sentence. That is assuming you already had it and should be keeping it on your SD card all the time for flashing ROMs
Click to expand...
Click to collapse
Thanks for explaining that to him.
TechNash said:
Thanks for explaining that to him.
Click to expand...
Click to collapse
how to remove Verification Failed or root in the TWRP file manager without losing data
Mujeeb64 said:
how to remove Verification Failed or root in the TWRP file manager without losing data
Click to expand...
Click to collapse
Flash ashyx-no-verity-no-encrypt.zip in twrp.
Reboot
TechNash said:
In this tutorial I will inform you on three different soft bricks, and how to fix them.
You must be able to boot into TWRP and/or Odin/Download mode!
1.) Verification Failed.
Method #1
This method will work with people whom can't reset their device, due to an unmountable /data partition, and those whom experience this error, who can reset but have valuable items, applications, videos, or photos that they don't want to lose. Must be able to boot into Odin/Download mode. (Volume Down+Home+Power)
The solution is actually pretty simple. Boot into Odin/Download mode. This has to be done correctly, not from TWRP recovery. When the prompt for "Volume Up = Continue" and "Volume Down = Cancel (Restart)" press volume down. You should no longer see verification failed, but instead be sitting on the T-Mobile logo. This is normal, and could take 30 seconds to 10 minutes, depending on the amount of data.
This method works all because of Knox. Knox is what Samsung uses to void your warranty. Companies are not allowed to void a warranty when rooting, installing roms, or recovery, unless they have direct evidence. Knox will trigger this when it isn't sure. It will try forcing you to bring it to Samsung, and they can directly find out why it was caused. This happens when it thinks that you cancelled.
Method #2
This one will require you to lose all your data, but is mainly intended for those whom cannot reset their device. Download the stock firmware from the links below. Open Odin (Jodin3 will not work! It is not fully functioning, do not try it.) and boot device into Download/Odin mode. On your computer, you should see 'Added' in the logs. If this does not show up download the Samsung USB Drivers. Select AP and then select the stock firmware. Now flash it. This can also be done through TWRP
For bootloop and frozen Android/Carrier logo just do Method 2. You usually will keep all your data.
FOR 'VERIFICATION FAILED' YOU CANNOT RESTORE FROM A BACKUP!
FOR BOOTLOOPS AND FROZEN STARTUP SCREEN, YOU CAN!
Downloads:
Samsung USB Drivers
7.1.1 Stock Firmware
Odin3 v3.12.10
Click to expand...
Click to collapse
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
smirk24 said:
I have a samsung j700t ud that had the 7.1.1 update installed from tmobile or samsung and it caused the to remain in a continual reboot loop until the battery of the phone dies. Will the methods above repair the issue?
Stuff I've tried:
1. Wipe cache
2. Called samsung and tmobile
3. Used samfirm to download firmware to use with odin that was successfully done but the reboot loop still remains.
Click to expand...
Click to collapse
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
TechNash said:
Was the update sent out to you, or did you download it from SamMobile?
If the update was sent out to you I'm afraid I cannot help, but if you flashed it from SamMobile use an older version like Marshmallow or Lolipop.
EDIT: Make sure you factory reset device and wipe cache after installing from SamMobile.
Click to expand...
Click to collapse
Id love to but i dont know how to get the marshmallow software and install it to the phone but id like to learn how.
How to recover from Verification Failed without losing data ?Does installing TWRP via Oddin Works and does it able me to transfer my data after installing TWRP ? I dare not try doing it as i have never did it b4
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.