Related
Hi everyone,
I am looking for a solution to recover my Samsung Galaxy S7 (SM-G930FD) from a bootloop, without TWRP. I have read through many posts to find a solution, but not have worked for me. Please read the full details before offering a solution.
- I rooted my phone, successfully, using CF Auto Root (via Odin). It was working fine for several days
- I installed Hide My Root from the Google Play Store, which did not work
- I installed XposedInstaller_3.0-alpha4.apk
- I installed TWRP Manager from the Google Play Store
- I installed BusyBox from the Google Play Store
- I downloaded xposed*.zip (xposed-v86-sdk23-arm64.zip) and xposed-uninstaller*.zip (xposed-uninstaller-20150831-arm64.zip)
- I installed TWRP. I did a lot at once, so some steps are a little fuzzy right now.
- I booted into recovery mode (TWRP) and completed a backup for the data, to the SD card.
- In recovery mode, I then selected BOTH zip files for install. Once that completed, the phone restarted and stuck at the Samsung logo.
- I booted into download mode and tried CF Auto Root again, with no success.
- I booted into recovery mode, but TWRP does not seem to appear. It goes to the default Android Recovery with the following options:
> Reboot system now (did not help)
> Reboot to bootloader (did not help)
> Apply update from ADB ("Update from external storage is disabled")
> Apply update from SD card ("Update from external storage is disabled")
> Wipe data/factory reset (did not help)
> Wipe cache partition (did not help)
> Mount /system (did not appear to do anything)
> View recovery logs (lists various logs)
> Power off (turns off phone)
Specifications:
- Samsung Galaxy S7 (SM-G930FD)
- Dual Sim
- International
- Exynos 8890 Octa-Core
- Android 6.0 (Marshmallow)
If you need any additional information that will help you determine a solution, I will attempt to provide to you what I can. I am only looking for possible solutions from the point in which I am at now, not what I did wrong or the correct way to go about doing it. It's a little too late for that now, isn't it?
Thank-you in advanced,
Brandon
SOLUTION
A friend of mine suggested using Smart Switch, which failed, but I was able to come up with a solution from that. Here are the steps I took to bring my phone back to life.
1) Download Samsung Smart Switch and run it
2) From the top right, select "MORE," followed by "Emergency software recovery and initialization
3) Fill in the required information, including the model number and serial number of your device, followed by the OK button
4) Attempt to complete the process vis Smart Switch first
Note: Keep your phone in a cool place, since the screen does stay on the entire time.
If this fails AFTER the download completed (it did for me):
5) Locate the files that were downloaded. On Windows this will be on your system drive under "Users\*user*\AppData\Local\Temp\tmp****", where tmp**** contains random characters. The easiest way to find the name is to sort by date created or modified and look for a large file with a similar name. Now locate the folder starting with the same name. Within this folder there should be 5 files. Copy them all to an alternate location. You will only need the AP file, but you may wish to use the others.
6) Disconnect the phone from your computer
7) Uninstall Smart Switch, Kies, and the Samsung Drivers (if installed)
8) Download the latest version of Odin
9) Restart your computer and reboot the phone into Download mode (Vol Down + Power + Home) => Vol Up on prompt
10) Reinstall Samsung Drivers
11) Run Odin and click the AP button and locate the file you saved, starting with "AP_"
12) Plug in your phone, click Start, and wait for the process to complete.
I hope this helps anyone else looking for a solution, as I have not found this anywhere else online. :good:
UPDATE OF JULY, 13th 2019 : IMPORTANT INFO : This guide is no longer updated. The recent update of June 2019 broke compatibility with my Bootloader Ver. 2 I was using which worked fine from the first Nougat release to the first Pie update (included). As I'm still daily running Android Nougat (7.0), I can't risk to upgrade to BL Ver. 5 and find myself locked under Pie. And the main risk is that I can't know if BL v5 is breaking modem compatibility or not and if it does it means that I'll lose all wireless connectivity under Nougat. So, as I can't risk my device (which is my daily) I have no choice other than dropping the support of this device. I apologize.
SAMSUNG Galaxy Note Fan Edition
Exynos 8890 - International Ver. [SM-N935F/DS]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current Status :
(Pie 9.0) - POST 06/21/2019 Update - Unknown
(Pie 9.0) - PRE 06/21/2019 Update - Rootable
(Oreo 8.0) - Rootable
(Nougat 7.0) - Rootable
Latest Ver. of TWRP: v3.3.1-0
Latest Ver. of Android: Pie (Android 9.0)
1 - ▼ DISCLAIMER ▼
- I DECLINE TOTAL RESPONSIBILITY IF YOU DAMAGE OR BRICK YOUR PHONE WHILE TRYING THIS METHOD ! YOU'RE DOING IT AT YOUR OWN RISKS !
- THIS METHOD IS ONLY VALID FOR THE GALAXY NOTE FAN EDITION (EXYNOS Ver.) SM-N935F/DS VERSION ! IT'S NOT SUITABLE FOR THE KOREAN VARIANTS !
- FLASHING ANY CUSTOM BINARY WILL IRREMEDIABLY VOID YOUR WARRANTY AND KNOX COUNTER WILL BE TRIGGERED (0x1).
- MAKE SURE THAT YOUR DEVICE HAS AT LEAST 70% BATTERY BEFORE ATTEMPTING ANY STEPS !
- ALL THE DATA ON THE INTERNAL STORAGE WILL BE DELETED ! BACKUP ALL YOUR FILES IN A SAFE PLACE BEFORE PROCEEDING !
2 - ▼ Important Infos ▼
To avoid making any mistakes, I HIGHLY recommend you to READ CAREFULLY the WHOLE guide BEFORE attempting anything! Prevention is better than cure remember
The Galaxy Note FE (like many other Samsung devices) use dm-verity and data partition encryption.
► Android 9.0 (Pie) - UPDATE OF THE 06/21/2019 (Bootloader V5) :
The Note FE (International Ver.) Android Pie update of (June 2019) support is unknown.
As I can't try if my patch works, (see above), I can't test if the latest update is rootable or not.
However, the problem is probably similiar to the first Pie release of March 2019, the fix is also probably the same
but due to changes to the kernel or boot routines, the old fix dosen't work anymore.
If you're under an older Pie release (typically with a v4 BL or less) or even under an other Android version, you can still follow this guide.
► About RMM State :
The Note FE (International Ver.) is shipped with a component called "RMM".
This component is able to prevent the end-user from flashing any custom binary on the device while it's active.
You can check if your RMM is enabled or disabled by putting your device in Download Mode :
- If the line "RMM State: Prenormal" is present, then RMM is enabled and you won't be able to flash any custom binary.
- If it's absent, then it has already been disabled which means that you'll be able to flash any custom binary.
This component suddenly disable itself after 7 days of continuous uptime since the device has been last powered on.
You can check your device actual uptime by going into : "Settings" > "About phone" > "Status" > "Uptime"
Or use CPU-Z : "System" tab and "System Uptime". (CPU-Z displays the uptime in days rather than hours.)
Once 7 days are elapsed, it will be desactivated BUT! If you format the data partition for example, which's required to disable data encryption for rooting, it will be back!
Even worse, if you reboot once you've setup your phone, you'll get blocked with a message when you'll powering it on saying ("custom binary has been block due to remaining installment balance") and you'll have to reflash stock to get your device working again...
To avoid that, once the /data partition has been wiped, you'll need to apply the RMM fix (prerequisites section, see below) which prevents the device from re-self-locking itself after rebooting, once the initial setup has been completed.
Everytime you install a new official firmware, RMM might be active again.
It is triggered by an hidden system app called "Rlc" which acts on the bootloader lock.
If your Rlc app is still present, the best thing to do is to simply delete it ASAP to prevent any unpredictable action on your bootloader. (system/priv-app/Rlc)
For custom ROMs, normally they're safe. But still, check if the dev has already deleted Rlc, otherwise you'll have to do it by yourself.
3 - ▼ Prerequisites ▼
1 - A SAMSUNG Galaxy Note FE [SM-N935F/DS]
2 - The Samsung USB Drivers (If not already installed, => [HERE] <= )
3 - Download the lastest Odin (v3.13.1) => [HERE] <=
4 - Download TWRP for the Galaxy Note7 [SM-N930F] (v3.2.1-0.img.tar) => [HERE] <=
5 - For Android Nougat (7.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Click to expand...
Click to collapse
5 - For Android Oreo (8.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Download the /data partition fix (for Android Oreo) [HERE]
Click to expand...
Click to collapse
5 - For Android Pie (9.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Download the Kernel Patch (for Android Pie) [HERE]
Click to expand...
Click to collapse
6 - A PC and a USB-C Cable
7 - A brain, a pair of eyeballs and some fingers (Yeah, that could help... especially the first one..)
4 - ▼ Flashing TWRP 3.2.1-0 on the Galaxy Note FE ▼
If Your RMM is locked you will have to wait 7 days (or 168 hours) while maintaining your device up and running. (NEVER REBOOT DURING THIS TIME ! IT WILL RESET THE RMM TIME COUNTER!)
=> For more info and/or if you don't understand what I'm talking about, please refer to section 2 of this page and read it all.
Once RMM is desactivated (or already desactivated), you can proceed to the next steps :
Make sure to enable "USB Debugging" and "OEM Unlock" in the Dev Options.
Connect your phone to your PC and drag and drop the Magisk package and the RMM fix at the root of your microSD card.
Now, depending on the Android version you're running, drag and drop the additional fix that you've downloaded earlier at the root of your mSD card too. (Only if you're on Oreo or Pie)
Once it's done, backup everything valuable and power off your device.
Enter the Download Mode by pressing simultaneously the "Home" + "Vol. Down" + "Power" buttons for 5 sec. Read the warning message and just answer "Continue".
Launch Odin and select TWRP 3.2.1-0 archive by clicking on the "AP" button.
Go to the "Options" tab and untick "Auto-reboot"
Connect your phone which is in DL Mode to your PC.
/IMPORTANT!\ Make sure Odin is seeing your device properly.
(Once connected, you should see the box under the "ID:COM" tab displaying "0:[COM*]" in blue, meaning your phone has been detected successfully. If not, Install the Samsung USB Drivers, link available in the prerequisites section.)
Flash TWRP.
Wait while Odin in flashing the recovery. /AVOID TOUCHING ANYTHING DURING FLASH PROCESS\
When Odin shows "PASS", take your device in hands, disconnect the USB-C cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the DL mode disappears.
When at the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to enter TWRP recovery.
You should see TWRP logo just after the Note FE splash-screen.
Click to expand...
Click to collapse
Now TWRP is successfully installed. But we're not done yet ! We still have to deal with the data encryption and disable dm-verity in order to boot properly.
5 - ▼ [9.0] Rooting the Galaxy Note FE under Android Pie ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed.
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and Install the RMM fix package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the kernel patch for Android Pie.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the Magisk package, the root solution.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
6 - ▼ [8.0] Rooting the Galaxy Note FE under Android Oreo ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed.
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and install Magisk package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the RMM fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the /data partition fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
7 - ▼ [7.0] Rooting the Galaxy Note FE under Android Nougat ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed !
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and install Magisk package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the RMM fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
8 - ▼ Disable SecurityLogAgent pop-up & Samsung Anti-Malware ▼
Samsung provides an anti-malware on their phones and the Note FE is one of them. The system will detect that Magisk has been installed and a service called "SecurityLogAgent" will regularly
pop-up in your notification bar to invite you to launch the Device Maintenance app and reboot the device using an orange button to "eliminate" the threat. => DO NOT REBOOT USING THIS BUTTON ! <=
You'll end up soft-brick your phone. And this, won't disappear on it's own.
Here's how to disable and definitively hide that anti-malware crap from the Device Management app :
Download the lastest version of MiXplorer => HERE <= (Or any file manager of your choice. MiXplorer is lightweight, nice to use, free and made on XDA.)
Access the root partition in the left panel and go into the "/system/csc" folder
Open the file "others.xml" with the text editor.
Add the following line at the end :
Code:
[I]<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>[/I]
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
The Samsung Anti Malware is now disabled as well as the annoying pop-up.You're good to go, enjoy!
9 - ▼ Fix Samsung Health ▼
For whatever reasons, Samsung locks-up Samsung Health once Knox has been triggered.. But go figure why, there's only a simple thing to do to re-enable the app and be able to use it again easily.
You can either use a file manager or the app "BuildProp Editor".
Download the lastest version of MiXplorer => HERE <= (Or any file manager of your choice. MiXplorer is lightweight, nice to use, free and made on XDA.)
Access the root partition in the left panel and go into the "/system" folder
Open the file "build.prop" with the text editor.
Simply change the line
Code:
ro.config.tima=[COLOR="Red"][B]1[/B][/COLOR]
to
Code:
ro.config.tima=[COLOR="SeaGreen"][B]0[/B][/COLOR]
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
Samsung Health is now working again. :good:
10 - ▼ Troubleshooting ▼
You have a problem with your Note FE ? Take a look at those answers before posting :
Q: I try to flash TWRP with Odin but a message pops up on my device and says "custom binary has been block due to remaining installment balance". What's happening ?
A: RMM. This message is more likely to appear if you still have RMM enabled. Boot your phone, keep it powered on and running and never reboots during 7 days and it should disappear.
Q: I've flashed TWRP with success, formatted data and stuff but I see the message "custom binary has been block due to remaining installment balance" at boot and I can't boot ! What's happening ?
A: RMM again ! Once data has been formatted and Android first reinstalled, RMM lock is back! Same thing can happen if you did not install the RMM fix with TWRP. To unbrick it, you have 2 options : 1 - Flash stock BUT with HOME_CSC. (It will keep the RMM elasped time, but you'll have to keep in mind since how much time has elapsed already.) or 2 - Reflash stock and follow the entire procedure again and the waiting again. The first one might work, if not, then try the 2nd one.
Q: I've managed to install TWRP, root and get my phone up and running but I've clicked on the orange "Reboot" in the Anti-Malware tab in the Device Management app.
Now my phone bootloops (or) shows the message "custom binary has been block due to remaining installment balance" and I'm stuck with it.
A: You've got trapped into Samsung Anti-Malware crap. This utility can't delete Magisk. Any solutions ? Restore one of your previous TWRP backup but if you have none, the only solution is to re-flash stock, repeat the entire procedure, disable SecurityEventLog service to get rid of those annoying security pop-ups AND stay away from the anti-malware utility !
11 - ▼ Extras ▼
Thanks. If there is any mistakes or errors, please feel free to report them to me, I'll correct them
Credits goes to :
Magisk (@topjohnwu & @phhusson, @Chainfire, @nkk71, @osm0sis, @Captain_Throwback, @Didgeridoohan, @jenslody, @digitalhigh, @DVDandroid)
TWRP Recovery (@TeamTWRP)
The RMM Fix (@BlackMesa123)
The /data partition Fix (@dr.ketan & @RicePlay33)
Odin Soft (@anycallmongolia)
MiXplorer File Manager (@HootanParsa)
How to keep the elasped time (@societyragdoll)
SAMSUNG... (@Samsung) (duh)
Author : RicePlay33
Thanks ! I'll give it a try.
Do you think we can use all the flashable mods and custom roms from S7/S7 edge?
Well the answers are : Maybe and No.
Some mods that you can apply with TWRP may work, some not.
Concerning custom ROMs it's totally no. ROMs are designed for specific hardware and phone models. Unless someone creates a custom ROM for the Note FE, it's not possible.
RicePlay33 said:
Some mods that you can apply with TWRP may work, some not.
Concerning custom ROMs it's totally no. ROMs are designed for specific hardware and phone models. Unless someone creates a custom ROM for the Note FE, it's not possible.
Click to expand...
Click to collapse
Yes you can use custom roms from the Note 7 or Note FE of Korea [emoji12]
Envoyé de mon SM-N935F en utilisant Tapatalk
benyou54 said:
Yes you can use custom roms from the Note 7 or Note FE of Korea [emoji12]
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
I wouldn't try it lol. At your own risks
@RicePlay33 just out of curiosity, what mods have you tried ?
Paninno12 said:
@RicePlay33 just out of curiosity, what mods have you tried ?
Click to expand...
Click to collapse
I've only tried the Dual Speaker mod for the S7 edge as it was my previous device, but it only works partially on the FE actually. Whenever I make a phone call for the first time just after rebooting, the microphone works fine but then if I try any more times after, the microphone stops working without any reasons :/ Quite a weird problem.. Like I said, some mods may work, some not.
any mod you want to try i suggest take it from s8/s8+ version. anyway since you guys has root your device... try to update some of the old apps in system. got a better one out there.
I've tried the Dual Speaker for the Note 8 (Magisk mod) but it simply didn't work. That would be awesome if the dev of this mod for the S7/ S7 edge version could release a NFE one (@zubi182)
Does anyone know if Secure Folder can be somehow enabled? I managed to do it on my rooted S7 Edge , but with dark lord rom and some sort of kernel. I'm guessing this isn't possible on this rooted stock rom?
Anyone know where i can get an international note fe?dont want dual SIM version
Secure Folder can be fooled with a modified kernel yeah. To my knowledge too, it's not possible with the stock one.
please help me remove knox on samsung s7 nN935F. picture in attach. thanks all
Hi ! Was able to reboot and edit some lines (using root explorer) in build.prop ro.securestorage to false and ro.config.tima to 0. Problem is.. the securestorage even at false value i still cant view the saved wifi passwords. So i tried changing the permission to 777 thats when i had the red custom binary blocked and rmm prenormal. Flashed to stock rom last night. Not sure how but i tried flashing only with csc_home but red warning is still there. But with ap it worked. Didnt flash bl, cp etc. Am i doing this right? So now i have to wait again. Can i use supersu instead of magisk? the root is not giving me full privelege in this androdumpper app (on the saved password section ). Thank you for your awesome post RicePlay33.
@donart81 I've searched a bit and I've found this => http://phuongpn.com/how-to-decrypting-wifi-password-on-samsung-galaxy-phone-solved/ Did you done the rest of the operation ?
Also, changing the value of "ro.securestorage to false" maybe triggers the RMM lockdown as it seems related to the security of the device. (Encrypting WiFi passwords)
The message was still there because you've ONLY flashed "HOME_CSC", it was specified to flash stock (so including everything BL/AP/CP etc) but for the CSC, choosing the HOME_CSC one. It will flash stock 99% like usual but the HOME_CSC will keep the time elapsed of RMM, reducing the time needed to re-root it again.
You should have tried to disable RMM Maybe it wouldn't have bricked itself.
oh so that's how you flash hehe. i'm such a noob.
yup i think i have done the rest of the operation. I've successfully rebooted after changing the value of the build.prop (ro.securestorage + ro.config.tima) to see if it was not reverted back to original. device was working. it was only when i changed its permission checked it all suddenly it bricked my phone hehe.
next time i'll try to change the value of the "Support Rmm" in the experiment section and report back if it worked
thank you for your informative reply.
There has been some development about a possible RMM State Fix Over here.
Did anyone try it?
I'm just waiting for the 7 days to pass, and this wait itself is killing me!
Yeah I saw that. I was thinking to talk about it but I didn't had the time recently.
I'll update the main post, although I may need someone to try it first and report me what is going on on his device to be able to document it as clear as possible and also to see if it works without any problems.
Don't worry, 7 days and you'll be free like a bird is
hello i installed twrp on the device and made root and then waited 7 days and 7 days is completed. When the device is off and the device is open, the device has failed.
My fault : custom binary blocked due to remaining installment balance
Please melp me mate
what should I do ?
RicePlay33 said:
Yeah I saw that. I was thinking to talk about it but I didn't had the time recently.
I'll update the main post, although I may need someone to try it first and report me what is going on on his device to be able to document it as clear as possible and also to see if it works without any problems.
Don't worry, 7 days and you'll be free like a bird is
Click to expand...
Click to collapse
I will do it as soon as I'm released from the jail.!
However, "This being free is temporary" I guess as it seems like after a new firmware update from Samsung, This will be a routine process.
mest47 said:
hello i installed twrp on the device and made root and then waited 7 days and 7 days is completed. When the device is off and the device is open, the device has failed.
My fault : custom binary blocked due to remaining installment balance
Please melp me mate
what should I do ?
Click to expand...
Click to collapse
Hi, Im not really qualified to answer your query, But from What I have learned -
You need to flash a Stock Rom,
Do the 7 Day wait until the RMM State is disappeared,
Then Follow the steps in the OP, and Flash the RMM State fix immediately to prevent getting locked again.
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?
I've recently purchased Galaxy S5 SM-G900T, Marshmallow, not rooted. Would like to flash Lineageos 17.1. Here is my plan and list of questions. I would be greatly appreciate your comments and suggestions.
1. Flash TWRP version 3.1.0-1 *.tar.md5 file (Use Odin 3.12.3 or 3.11.1?).
2. Make Nandroid backup of the Android phone and save it on SD card. Partitions: System, System.img, Data/user data (excl. storage?), Boot, Vendor, Vendor.img, Cache, Recovery, EFS, Persist, Logo.
3. Copy LOS 17.1 (zip), Magisk 18.1, Magisk uninstaller and Magisk manager.apk (latest stable 7.5.1) to microSD.
4. Reboot in TWRP (deny to install TWRP app) and make clean install of LOS 17.1:
Wipe> Adv. wipe> System, Data, Cache, Dalvik.
Flash LOS 17.1 (zip), Kernel. Install Magisk 18.1, Magisk manager.apk
5. Reboot from TWRP to the System.
6. Root with Magisk, install BusyBox and Substratum modules.
Android 6.0.1 (Marshmallow) probably was installed OTA. Should I first downgrade to the Lollipop or even KitKat or it is OK to go with Marshmallow? Or may be it is better to make a factory reset?
It is not clear for me if Bootloader is unlocked in my Galaxy SM-G900T from T-mobile (see attached pic). If it is locked can I still flash TWRP with Odin?
Are the versions of the Odin, TWRP, Magisk I've listed before OK and safe to flash on Samsung galaxy S5 SM-G900T?
Lineage OS flashing: Is it enough just to wipe System/Data/Cache or I must to Format it? Should I also wipe/format internal storage?
should I install kernel along with LOS or I can do that later?
Kltetmo, Qualcomm Snapdragon 801, Qualcomm MSM8974PRO-AC
ARMv7 Processor rev 1
Bootloader G900TUVU1GQC2
Build MMB29M.G900TUVU1GQC2
Not rooted
OK, you should know that you are wanting to jump to the most Beta builds for the S5!
(Meaning, you might find that some things don't work, or may be a bit buggy on your phone) Now, if you agree to that, then ... (Only IMHO....)
First, if I was in your shoes (...just purchased a used Galaxy S5 SM-G900T) I would actual get the most up to date Stock Rom (Android 6.0.1 for you phone, ( can be found here on XDA, as well as Sammobile could really take a lot of time to download there)) Reason- So you know that you are 100% safe at Stock with all the
Seems that your on the right path, just missing some minor, changes. i just might do it a little different.. could just be me though...
1- Get Stock Rom for your phone
2 - Get Recovery- well TWRP 3.1.0-1 can work, the 3.3.1 seems to have issues to Android 10 Roms
3 - Odin 3.10 seems to work well (IMHO) but can use 3.12 or 3.11
4 - Yes, put the 17.1 image on your Micro SD Card...like in your Lineage Folder, also put any other files you may need or want IN the Micro SD card (i.e. latest Magisk 20.4 and Magisk Manager 7.5.1 9at time of writing)
5 - Flash the latest Stock Rom, (have the Reboot box checked-so it Reboots when done flashing) unplug the phone
6 - Flash your recovery (when doing so, make sure that you do not have the Reboot checked, so you can boot into recovery after powering off the phone, when done flashing, Boot to Recovery
7- True, when in Recovery, DON'T install their darn App! But also, go into settings, and set up Your Recovery... then all should be fine from this point
8 - Make your Backup (Check every box in the list, can even change the Name if you want) It will put it in the TWRP Folder in Internal Storage
9 - Clean up Stock, Wipe System, Data, Cache and Dalvik Cache. (I would format system to ext4 as well as Data Just to make sure nothing is there from Stock) (check out Clean Flashing for the S5)
10 - Flash your 17.1 image, (it will ask to wipe cache and dalvik cache after flashing, DO SO) then in your case flash your Kernel, wipe, flash Magisk, wipe, flash Magisk Manager, wipe
11 - Boot to system after flashing the Rom and all the goodies. Relax... it will take several minutes to boot.
Just a reminder, Make sure that you have charged battery! Don't want any issues with power
hopefully you can see the minor changes I made from your steps 1 - 6 ! Just my 2 cents, but like I said you seem to be on right track.
Now, another good idea that I do, is, I actually Copy my TWRP folder in the Internal SD card to my External Micro SD Card ( So I don't lose my back ups, in case of an issue with the phone)
Hope this helps you out
Update: March 24 2022: This ROM has been retired and a new one based on LOS 19.1 (and TWRP based on Android 11) have taken its place. New thread here: https://forum.xda-developers.com/t/...4-2020-lineageos-19-1-and-twrp-3-6-1.4421365/
---
Update 9:46am EST July 15 2021: new builds of TWRP and LineageOS with TWRP touch fixed and LOS w/ space for Gapps is now live.
WARNING: USE AT YOUR OWN RISK.
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the steps to follow:
Update your device to the latest stock ROM (as of this writing) either using the built-in system updater or via Odin. You want the build that ends with "3BUF3".
Unlock device bootloader using instructions from other threads. This will wipe your device.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Boot device back into download mode and flash TWRP via Odin in the "AP" slot. If you boot up into the stock ROM rather than booting directly back into download mode then go through the initial setup process of the stock ROM and enable developer tools and ensure OEM Unlocking is still enabled (VaultKeeper can possibly undo OEM Unlocking if you get to the ROM but don't go into Developer Tools and view OEM Unlocking is enabled, so make sure to do this).
Boot device into TWRP (recovery mode) and format (not wipe) your data partition. Then reboot back into TWRP.
Push LineageOS (super.new.ext4.img) to device. Ideally push it to an SD card formatted with ExFat or EXT2/3/4 (FAT/FAT16/FAT32/VFAT won't work due to file-size limitations).
Install LineageOS image to "Super" partition. Make sure to select "Install from Image" in order to show .img files in the install selector screen.
(Optional) Push NikGapps Omni to your device and install the zip. Make sure you include a "nikgapps.config" file in your "/tmp" folder that is configured to install to "system" rather than "product" or "default".
Reboot to system. You should now be in LOS with Gapps.
(Optional, but recommended): Install Magisk via TWRP
(Optional, but recommended): Run fix script to fix brightness slider not working and to make Magisk work. If you didn't install Magisk but only want the brightness fix, just enter "n" when prompted in the script. To run the script:
NOTE: Script has .txt file extension to allow hosting on AFH. Remove that so it's just .sh to match the instructions below.
Download and push to device when booted into TWRP
adb push sm-t500_fixes.sh /tmp
Enter an adb shell
adb shell
Change directories and set permissions
cd /tmp
chmod +x /tmp/sm-t500_fixes.sh
Run script
/tmp/sm-t500_fixes.sh
Tips:
If you are not seeing all of your storage space in the OS on the internal flash, boot to TWRP and format data.
Flash TWRP via "AP" slot and flash VBMeta_Disabler via "Userdata" slot in Odin.
Flash LineageOS as an Image, not as a Zip.
For Gapps, use the latest NikGapps for ARM64 and Android 11/R.
For Gapps, make sure you install to the System partition and not Product. To do this you need to slightly modify a nikgapps.config file. Instructions on that can be found on the NikGapps site.
Downloads:
LineageOS 18.1 20210615 Beta 2: https://www.androidfilehost.com/?fid=14943124697586369438
TWRP 3.5.2 Beta 3: https://www.androidfilehost.com/?fid=14943124697586369439
vbmeta_disabled_R: https://www.androidfilehost.com/?fid=14943124697586369440
Fixes for brightness and Magisk (sm-t500_fixes.sh): https://www.androidfilehost.com/?fid=14943124697586369521
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
Brightness controls don't work: Fixed via "sm-t500_fixes.sh script.
TWRP touch screen doesn't work (use USB keyboard or adb). Should be fixed with TWRP Beta 3.
TWRP formatting external SD card may hardbrick device. Do not do this! Fixed with TWRP Beta 2.
Source (device tree for TWRP from my Github): https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Source (kernel sources from Samsung): https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
agreenbhm said:
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the rough steps to follow:
Unlock device bootloader using instructions from other threads.
Patch stock ROM (AP) using Magisk, then flash rooted ROM. Will likely need to wipe device after this.
Boot into rooted ROM and ensure "OEM Unlocking" is still enabled in "Developer Tools".
Boot back into download mode and flash "vbmeta_disabled_R.tar" to disable verified boot.
Boot device back into rooted stock ROM to ensure things are still functional (may require a device wipe at this step).
Boot device into download mode and use ODIN to flash TWRP recovery.tar file via "AP" slot.
Boot device into TWRP to verify functionality (hold Vol-Up + Power during boot).
Access TWRP via adb using "adb shell" or with USB mouse (touch functionality currently not working).
Format data partition on device.
Via ADB shell: twrp format data
Via USB mouse: Wipe -> Advanced -> Format Data
Boot device into download mode.
Via ADB shell: twrp reboot download
Via USB mouse: Reboot -> Download
Flash LineageOS tar file via ODIN using the "AP" slot.
If device boots into TWRP after flashing LineageOS, use USB mouse to select: Reboot -> System
Device should boot and stall for ~1m at the Samsung logo screen with red text below, then should go blank and then display LineageOS boot image.
Downloads:
LineageOS 18.1 20210615 with TWRP 3.5.2: https://mega.nz/file/vMVglThZ#TepIHvdEypezq3z4S_4Lln7FRFVfC7CUjVGq3ByFb6U
TWRP 3.5.2: https://mega.nz/file/GYU1yCCQ#JsthI8BYNtfB08Pzt1eeXta2Lb1zCkUI185Zm88dEW4
vbmeta_disabled_R: https://mega.nz/file/iMFx3CQI#8cP4mPoRaQNwDATqt0vKD8wxqRWSTz1EL79U0fNpW8M
Click to expand...
Click to collapse
Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.
awesome. Will try after work. Also I think you posted in the wrong section.
Which slot to flash the vbmeta?
wizzdome said:
Which slot to flash the vbmeta?
Click to expand...
Click to collapse
AP
Thanks,
After flashing the vbmeta it booted into recovery automatically after what looked like a bootloop in progress, so I wiped with factory reset and then it rebooted fine. (still not sure exactly what the vbmeta does I was hoping it would make it so i didnt get that stupid pop up asking me to hit power button to continue booting due to it having the patched os) anyhow booted fine and twrp installed as you stated without touch screen but mouse with otg works fine. (great job so far) On to LOS... I think I should have checked oem lock before flashing LOS as when I installed I get stuck at boot screen that says oem lock is on... must have been from my factory reset... (facepalm)
Nope... Still sticking on boot with the following showing on the screen...
RPMB fuse not set
RPMB Provisioned
Current BInary: Custom (0x30f)
FRP Lock : OFF
OEM Lock : ON (U) {this was off verified before flash}
KG Status : Checking
Waranty Void : 0x1 (0xE02)
Quallcomm Secureboot : Enable
RP SWREV : B3 (1,1,1,3,1,1) k3 s3
secure download : enable
grdm status : normal (d0000501)
did : 041ce2d22dba
this is displayed in the corner on the bootscreen and looks like it belongs on the download screen, anyhow booting into twrp from this point works however factory reset fails with unable to mount key(something and key(something else) i figure i will let it sit a while as I know sometimes it just takes first boot a while to go through however it doesnt seem to be the problem. Have you had a positive install of the LOS? I am wondering if I had maybe gotten a bad copy of the file. When i go to install I get a pass in odin so not quite sure where to go from here other than back to the factory image any help to get this going would be great... I took on this task cause i needed someting to take my mind off the severely crappy week I have had... so looking forward to anything you can share here...
Actually, userdata is the slot I always use. It might work in both though.
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Nevermind what I said here.
jayzarry84 said:
Anyone get this to work? I just flashed the TWRP part but have not been able to get into TWRP
Click to expand...
Click to collapse
Get adb access in the OS and then run "adb reboot recovery"
agreenbhm said:
Get adb access in the OS and then run "adb reboot recovery"
Click to expand...
Click to collapse
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
You may need to get an otg cable for a USB mouse and choose "reboot system" from the gui. Alternatively, look at the /dev/block/by-name/misc partition and try blanking that out with dd. That has worked sometimes.
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
agreenbhm said:
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
Click to expand...
Click to collapse
Not working. I'll wait for my otg cable to come in
jayzarry84 said:
Not working. I'll wait for my otg cable to come in
Click to expand...
Click to collapse
I was able to use adb to run the TWRP Format Data command and it rebooted the tablet and now LOS has booted up. I think I'm good!
Looking forward to see how this develops
Rom is fast and snappy. Brightness control does not work. I haven’t played too much because of work but that’s what I’ve found so far
Can a mod move this to the rom release section?
agreenbhm said:
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Click to expand...
Click to collapse
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
lewmur said:
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
Click to expand...
Click to collapse
I will look into that, but I'm not optimistic it will work. This device does not separately present the system partition, rather it uses a super partition which contains system, vendor, product, and odm. TWRP only shows me the super partition for working with. I was able to resize the system partition by expanding the Lineage image and file system on my pc to match the original stock system partition, then rebuilt the super image with the other partitions it needs.