Hi folks,
my trusty S3 (SM-T825) got broke unexpectedly. It showed "100% battery" in the morning but was unresponsive. A forced shutdown did reboot the device up to the logo-screen - from where it rebooted again. So obviously it's stuck in a boot loop.
Unfortunately, it does not enter "recovery" either (home) (up) (power). However, it DOES enter "ODIN mode" (home) (down) (power). There it shows me that FRP Lock and OEM lock both are still active. This is no wonder as it caught me unprepared. FRP lock wouldn't be a problem, as I'm the owner of the account and can supply credentials once it boots up again.
Everywhere it is STRONGLY advised to turn off OEM lock before flashing anything to not make it even worse. This renders the device essentially dead, right?
The device is still as original as it can be.
Any chance I can revive it or does that more look like a mainboard problem?
I already have ODIN and I even have an actual 4-part "Original ROM" for my region (Samfw.com_SM-T825_ATO_T825XXU3CTD1_fac.zip), but maybe TWRP and Lineage would be the better options.
Before I just go and make things worse, I'd like to ask for a qualified advice ;-)
smallfreak said:
...... There it shows me that FRP Lock and OEM lock both are still active. This is no wonder as it caught me unprepared. FRP lock wouldn't be a problem, as I'm the owner of the account and can supply credentials once it boots up again.
Everywhere it is STRONGLY advised to turn off OEM lock before flashing anything to not make it even worse. This renders the device essentially dead, right?
Click to expand...
Click to collapse
Afaik you should be able to flash stock with OEM lock active BUT idk if FRP will block flashing process.
If that happens it's imo afterwards in the same state as before so at least it won't worsen it.
Gonna loose all your data anyhow.
Got Smartswitch? This might help as well.
smallfreak said:
....... I already have ODIN and I even have an actual 4-part "Original ROM" for my region (Samfw.com_SM-T825_ATO_T825XXU3CTD1_fac.zip), but maybe TWRP and Lineage would be the better options.
Click to expand...
Click to collapse
You can't replace recovery without OEM unlock.
smallfreak said:
Before I just go and make things worse, I'd like to ask for a qualified advice ;-)
Click to expand...
Click to collapse
Dunno if I'm qualified enough
Next turn ...
I tried flashing TWRP into the AP slot with SamFW FRP-Tool (ODIN). This worked so far but got me a note on the tablet "custom recovery blocked due to FRP lock".
Checking boot on the tablet - as before. Boot loop.
Next turn ...
Code:
Select file AP_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Select file CP_T825XXU3CTA1_CP14962504_CL17011592_QB28791445_REV00_user_low_ship_MULTI_CERT.tar.md5
Select file CSC_ATO_T825ATO3CTD1_CL18361310_QB30233690_REV00_user_low_ship_MULTI_CERT.tar.md5
Reading... OK
Detect mode: Download mode
Model : SM-T825
Bit : 4
Unique number : CBJ100915EAF124
Storage : 32
Vendor : SAMSUNG
Disk : BJNB4R
Firmware : https://samfw.com/firmware/SM-T825/
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Flash failed
Flash time: 00:47
Reading... FAIL
unchecking CP and CSC, leaving only AP.
Code:
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Flash failed
Flash time: 10:00
Reading... FAIL
Reboot tablet in download-mode, next turn: Try BL + AP:
Code:
Select file BL_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT.tar.md5
Reading... OK
Detect mode: Download mode
Model : SM-T825
Bit : 4
Unique number : CBJ100915EAF124
Storage : 32
Vendor : SAMSUNG
Disk : BJNB4R
Firmware : https://samfw.com/firmware/SM-T825/
Analyze files...
Flashing with SAMSUNG Mobile USB Modem (COM5)
Checking file BL_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT.tar.md5
Checking file AP_T825XXU3CTD1_CL17011592_QB30231355_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
Flashing (1/20) emmc_appsboot.mbn.lz4 OK
Flashing (2/20) lksecapp.mbn.lz4 OK
Flashing (3/20) xbl.elf.lz4Flash failed
Flash time: 01:26
Tablet moans about
SW REV CHECK FAIL : [lksecapp] Fused -1 > Binary 0
Click to expand...
Click to collapse
So maybe the firmware revision is different to the currently installed one? The latest file is from 2020 and since I did the usual OTA updates, this should be the version installed. But even if not, it sould not matter to upload a newer one, right?
Anything I can check?
So then obviously "Game Over"
Another piece of expensive waste that otherwise could have served well for years to come. Yes I know, selling something just once is an inferior business model to repeatedly draining my account for the same service.
Related
Dear Esteemed XDA members,
I have spent literally days of testing and researching to try and unbrick my phone. Friends and family have seen my obsession with trying to fix this, some even offering to buy me a new phone!!!! But this ain't about money - this is about having control of my damn device!!! I'm usually pretty good with trying to solve this kind of stuff, but this time I'm truly stumped (and desperate, and obsessed!). I have come to the conclusion that it's directly related to ARM Trusted Firmware. Here are the details of my "journey" to date... please read it, and if you know how to fix it, please share!!! then I can get my life back!!!! Before I go any further, I am certain that my problem was initially triggered by doing an official update on a rooted phone. So to avoid experiencing the same problem I'm about to describe, it's best to unroot and relock your device before loading new official firmware.
I have a Huawei Honor 4x (Che2-UL00, with Kirin 620 chipset) with an unlocked bootloader. Recently, I tried to manually upgrade from Kitkat (emui3.0) to Lollipop (emui3.1), using the official update.app from huawei's website (image was good - I checked the hash). To load the update.app, I used the official huawei recovery. The progress bar went to roughly 90% and then hung. Upon restarting my phone, it went into rescue mode with the following error: Func NO : 15 (bl31 image) Error NO : 1 (security verify failed).
Interestingly, I looked closely at the fastboot.img files for kitkat Vs lollipop (I got the image files by using HuaweiUpdateExtractor). I noticed that only the lollipop fastboot image contains this error message text. Also, bl31 is related to ARM trusted firmware, for more info search for BL31 (Secure Monitor) on google, or see bl31_main.c in the Trusted Firmware source code. So it seems that the lollipop image is using the full ARM trusted firmware, an extra layer of security which is preventing the (unlocked) bootloader from allowing me to load into recovery. I think this is the core problem, and I think there is a way to solve it but I just don't have a deep enough understanding to get there. Below I'll explain each step I went though and provide some additional diagnostic info:
1. First step was to access recovery mode (Vol UP + power). This failed and resulted in same bl31 error message.
2. Second step was to try and update again using the three-button force update (Vol Up + Vol Down + Power). It vibrates once after a few seconds, and freezes with the logo screen with the red light flashing. As an experiment, I tried this without the SDCARD and noticed it vibrated almost instantly, which suggests that it does try to load something from the SDCARD when inserted. I didn't get any further in this mode.
3. Final step I tried was to load into fastboot (Vol Down + Power). This worked and I got into a special "Rescue&Fastboot" mode. First thing I tried was to manually downgrade to kitkat by flashing the kitkat images using the fastboot flash command. The images boot.img, system.img, recovery.img flashed successfully. cust.img simply failed. I desperately wanted to flash the kitkat fastboot.img which doesn't contain the trusted firmware bl31 image stuff, but fastboot replied: FAILED (remote: Command not allowed). In fact, many of the fastboot commands fail with this same error message, even though there is the "PHONE unlocked" writing in red on my phone screen. With the limited command set available (even fastboot oem device-info is not allowed!), here is the diagnostic info I was able to get:
a) fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1452356543
I think this change from RISK to SAFE is the core of my problem. the change_time is from several days ago when I attempted to update. I think it reflects the trusted firmware state (I'm guessing here, as I can't find documentation for these commands).
b) fastboot oem backdoor info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
I think that FB LockState: LOCKED means that fastboot is locked (guessing again, can't find documentation!), which explains why many of the commands fail.
c) fastboot oem check-image
(bootloader) secure image verify successfully
I think this checks the recovery image, because when I flash a different recovery, this signature check fails
d) fastboot getvar rescue_phoneinfo
rescue_phoneinfo: Che2-UL00 V100R001CHNC00B365
This appears to be the ROM version at the time of purchase.
e) fastboot oem get-build-number
(bootloader): Che2-UL00 V100R001CHNC00B384
This actually corresponds to the build number of kitkat I was using just before the failed upgrade to lollipop.
f) fastboot oem relock mycode
FAILED (remote: root type not allowed).
I tried this just to see if it wold relock. I'm not sure what the error means, but I do not that this command failed with signature verify fail if i change the recovery image.
Here are the questions I want to ask:
1. Can I force the device to flash a new image? I can't get into recovery or have full access to fastboot commands due to the trusted firmware stuff. And as I mentioned earlier the three button trick fails with a freeze at the logo screen. It appears that I need to do this using a means other than fastboot. The only interface I have is Android Sooner ADB Interface. adb devices renders nothing. Only fastboot finds a device.
2. Can I somehow make the "security verify check" pass so that I don't get that bl31 error? I'm not sure exactly which images this bl31 thing is trying to verify! Perhaps some combination of images from the new lollipop stuff I tried to flash and the kitkat build I had running previously?
3. Can somehow disable all this Trusted Firmware stuff??
4. Any other suggestions???
This is driving me to the brink on insanity!!! Gotta figure it out!! Thanks for reading and trying to help!
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
prezident36 said:
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
Click to expand...
Click to collapse
I still find it hard to believe this problem absolutely cannot be solved. However, I took it to a Huawei service center and they weren't able to unbrick it either. They had to replace the mainboard, which seems like a complete waste. Cost around $50, so not the end of the world but still annoying.
Anyway, screw this whole "trusted firmware" rubbish. I'm the owner of the device, yet I'm not "trusted".
hello, i have exactly the same problem!
---------- Post added at 10:58 PM ---------- Previous post was at 10:41 PM ----------
Where do i get the replacement mainboard from?
Me too, upgrading kitkat to lollipop. Now facing that rescue error.
My Honor 4X is unlock bootloader and root before upgrading lollipop,
Hello, I was recently given a Tab S3 (Verizon) by a friend, and it was FRP locked. When asked, the friend said that she had no Idea which account might have been on it, and none that she tried worked, so I was stuck. So far I have tried a lot, and most recently, I have been trying to use Odin to flash a Combo file that I found for this model, but it fails to flash, and the tablet states:
Code:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 0
A couple of questions:
1) What does this mean?
2) Is this because it is FRP locked?
3) If it is, am I SOL?
4) If not, am I SOL anyway with the FRP lock?
I have had some experience with android modding, so I'm not a total noob, but don't take that for granted, I may have missed something very stupid/obvious.
The current firmware is: Oreo/T827VVRS2BRJ1
The combo firmware is: Oreo (I think)/T827VVRU0AQB9
Odin reports FRP Lock is on
Well, I managed to get firmware to flash by getting the same version that is on the tablet currently, but the flashing did not help, because FRP lock is still on. I even went as far as to get a partition table file and completely nuke the nand, which was probably a stupid idea, but nevertheless, even that didn't work to remove the FRP lock. Any ideas?
Thanks, SciFI101
P.S. Also note that the firmware that flashed was not a combo file, I have no idea what the difference is, do I need a combo file to remove FRP?
Flash combination firmware and then remove the google account and delete the Google account on device administration. Flash back original firmware all done.
Which combo firmware should I flash? Any that I have tried have failed with the SW REV CHECK FAIL error.
Also, the stock recovery seems to be shagged, after the blue "Installing updates"/"No Command" screen, the screen goes almost entirely dark, but it is still the same blue screen with Andy in the middle. It still boots into the OS and download mode otherwise. flashing BL and/or AP doesn't seem to fix it
Hi i searching hours for hours but don't get the firmware on this phone I have Odin, switch... From Samsung the newest firmware 5 pieces, adb, pipfile, actually drivers different cables and so one the biggest brob is developing mode is not acktiv I got this handy from my download junky grandma I don't know what crashed the phone a fouled try of flashing, a virus no idea sorry my English isn't so good at writing it on my own x.x but I understand 95% last 5% goggle helps the 2 pictures the first one is all time there power+vol. Combo only restart Handy back to same error invalid magic if I try to go in the recovery mode it only get the second picture and stuck on it. Power off key press alone does nothing
1 picture bootload fail, invalid magic
2 picture Odin mode, download speed fast, current binary Samsung official,
KG State broken,
FAP lock off
OEM lock on
Secure download enabled
Sales code Cid Aid /DBT EUX
Warrenty Void 0(0x000)
AP SWREV B7 K7 S7
Did 200.........
CARRIER ID EUX
CHIP ID and CHIP ID SJtag same value
Hope someone can help me out thx for coop mode ^^
Try to download the original phone firmware from samfw
marcmax01 said:
Hi i searching hours for hours but don't get the firmware on this phone I have Odin, switch... From Samsung the newest firmware 5 pieces, adb, pipfile, actually drivers different cables and so one the biggest brob is developing mode is not acktiv I got this handy from my download junky grandma I don't know what crashed the phone a fouled try of flashing, a virus no idea sorry my English isn't so good at writing it on my own x.x but I understand 95% last 5% goggle helps the 2 pictures the first one is all time there power+vol. Combo only restart Handy back to same error invalid magic if I try to go in the recovery mode it only get the second picture and stuck on it. Power off key press alone does nothing
1 picture bootload fail, invalid magic
2 picture Odin mode, download speed fast, current binary Samsung official,
KG State broken,
FAP lock off
OEM lock on
Secure download enabled
Sales code Cid Aid /DBT EUX
Warrenty Void 0(0x000)
AP SWREV B7 K7 S7
Did 200.........
CARRIER ID EUX
CHIP ID and CHIP ID SJtag same value
Hope someone can help me out thx for coop mode ^^
Click to expand...
Click to collapse
having the same issue and i dont know what caused it, did you get it fixed ?
helo sir
plz help me
I think the phone is dead :/
I don't think you can revive it...
I have tried different firmware (original and updated - two each) different usb cables and different usb ports.
I have factory reset and cleared cache numerous times, but every time the tablet only boots to the screen "Samsung Galaxy Powered by Android" and goes no further. I can boot to Recovery, Fastboot mode and Download, but not to System. The firmware is correct - downloaded with Frija.
Please , Can anyone help.
Checks Odin, let's see Pic after your attached file each slot also see Odin options.
tom.android said:
Checks Odin, let's see Pic after your attached file each slot also see Odin options.
Click to expand...
Click to collapse
Can show download mode Pic.
tom.android said:
Can show download mode Pic.
Click to expand...
Click to collapse
Can't read, pleases tell me oem lock , kg status , secure download
Oh. I saw your kg status is broken , it is not unlocked completely.
Your Tab is india government ? Not commercial Samsung.
You must change kg status from broken to checking. There are your community here. Pleases consult india group.
tom.android said:
Oh. I saw your kg status is broken , it is not unlocked completely.
Your Tab is india government ? Not commercial Samsung.
You must change kg status from broken to checking. There are your community here. Pleases consult india group.
Click to expand...
Click to collapse
I am in South Africa not India. It is a genuine Samsung Tablet. I bought it here. Thank-you very much for your help. I will search for a solution tomorrow.
jorjee said:
I am in South Africa not India. It is a genuine Samsung Tablet. I bought it here. Thank-you very much for your help. I will search for a solution tomorrow.
Click to expand...
Click to collapse
Oh sorry for my first introducing .
TRY
To begin with, install the stock firmware onto your Samsung device via Odin [Flash Samsung Stock Firmware via Odin].
Once flashing is complete, boot up the device and skip all the setup.
Then go to Settings > General Management > Date and Time.
Turn off Automatic Automatic date and time. Now manually set the date back to 10-15 days (7 days is the waiting time, we are keeping a few days in the buffer).
After this, go to Settings > Biometrics and Security > Other Security settings and turn off Find My Device.
At this point in time, make sure that you aren’t connected to any network. To be on the safer side, consider enabling the Airplane Mode.
Now go to Developer Options and enable OEM Unlock, If it’s already enabled or greyed out, then the bootloader is unlocked.
You may now boot the device to the Download Mode and verify that the KG has indeed been bypassed. To verify the same, you may see KG STATE as Checking, FRP LOCK: Off, and OEM LOCK: ON(U).
tom.android said:
Oh sorry for my first introducing .
TRY
To begin with, install the stock firmware onto your Samsung device via Odin [Flash Samsung Stock Firmware via Odin].
Once flashing is complete, boot up the device and skip all the setup.
Then go to Settings > General Management > Date and Time.
Turn off Automatic Automatic date and time. Now manually set the date back to 10-15 days (7 days is the waiting time, we are keeping a few days in the buffer).
After this, go to Settings > Biometrics and Security > Other Security settings and turn off Find My Device.
At this point in time, make sure that you aren’t connected to any network. To be on the safer side, consider enabling the Airplane Mode.
Now go to Developer Options and enable OEM Unlock, If it’s already enabled or greyed out, then the bootloader is unlocked.
You may now boot the device to the Download Mode and verify that the KG has indeed been bypassed. To verify the same, you may see KG STATE as Checking, FRP LOCK: Off, and OEM LOCK: ON(U).
View attachment 5686517
View attachment 5686525
Click to expand...
Click to collapse
I cannot boot the tablet.
jorjee said:
I cannot boot the tablet.
Click to expand...
Click to collapse
Can see oem lock status in developer option?
Look at here https://forum.xda-developers.com/t/...e-by-rooting-can-work-on-a03s-phones.4380053/
tom.android said:
Can see oem lock status in developer option?
Click to expand...
Click to collapse
OEM LOCK: OFF (U)
as your bootloader is unlocked already, just install TWRP and flash multidisabler
https://forum.xda-developers.com/t/4467157
Did ODIN flash passed or stuck during this entire process?
Did you try it without patched ODIN version?
Also did you check binary version...
jorjee said:
I have tried different firmware (original and updated - two each) ...
Click to expand...
Click to collapse
Keshav4 said:
Did ODIN flash passed or stuck during this entire process?
Did you try it without patched ODIN version?
Also did you check binary version...
Click to expand...
Click to collapse
Have you flashed update or FW using ODIN successfully?
Not, now I'll make sure nothing breaks it to a permanent damage
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.