Team Win Recovery Project 3.4.0-3 for Samsung Galaxy Tab A 7.0 - SM-T280 (gtexswifi)
Code:
***Disclaimer***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Always backup your current ROM (and/or keep stock firmware close by) before flashing.
Big thanks to @ashyx and @jedld for the amazing work done for this device.
Installation Instructions
If you don't have a custom recovery:
- Download twrp-3.4.0-3-_mone-gtexswifi.tar
- Reboot your tablet in download mode (power+vol-down+home) and connect it to your pc
- Using ODIN load the downloaded file to the AP slot and press start
- As soon the tablet start to reboot hold vol-up and home (don't let it reboot to system)
- Now you should see TWRP-3.4.0-3
If you already have a custom recovery:
- Download twrp-3.4.0-3-_mone-gtexswifi.img
- Reboot into recovery mode
- Flash the downloaded img in the recovery partition
- Reboot the recovery, now you should see TWRP-3.4.0-3
If you require "root", just download Magisk (v18.1 as of February 2019) and flash it with twrp. You may need to install MagiskManager afterwards. No extra steps required.
Old root instructions:
ROOT Instructions
These methods have been tested on samsung's T280XXU0AQA4 firmware
SuperSU v2.82:
- Download SuperSU-v2.82-201705271822 and T280XXU0AQA4-SuperSU-v2.82-boot.img
- Move the downloaded files to tablet's internal/external sdcard
- Reboot into recovery mode
- Flash SuperSU
- Flash "T280XXU0AQA4-SuperSU-v2.82-boot.img" into boot partition
- Reboot, now you should be rooted
Magisk v12.0:
- Download Magisk-v12.0.zip, T280XXU0AQA4-Magisk-v12.0-boot.img and MagiskManager-v4.3.3.apk
- Move the downloaded files to tablet's internal/external sdcard
- Reboot into recovery mode
- Flash Magisk-v12.0.zip
- Flash "T280XXU0AQA4-Magisk-v12.0-boot.img" into boot partition
- Reboot
- Install MagiskManager-v4.3.3.apk
- Done
- Do not update Magisk and/or MagiskManager
Old methods:
SuperSU v2.79:
- Download SR3-SuperSU-v2.79-SR3-20170114223742.zip and aqa4-gtexswifi-SU279sr3.img
- Move the downloaded files to tablet's internal/external sdcard
- Reboot into recovery mode
- Flash SuperSu
- Flash "aqa4-gtexswifi-SU279sr3.img" into boot partition
- Reboot, now you should be rooted
Magisk v11.6 (currently working only with SuperSU):
- Follow every step to install SuperSU
- Open SuperSU app and make sure you are rooted (let it disable knox is a good idea)
- Download Magisk-v11.6.zip and aqa4-gtexswifi-SU279sr3-Mag116.img
- Move the downloaded files to tablet's internal/external sdcard
- Reboot into recovery mode
- Flash Magisk
- Flash "aqa4-gtexswifi-SU279sr3-Mag116.img" into boot partition
- Reboot, open and update MagiskManager, grant it root permission
- Done
Useful links:
TWRP: https://github.com/omnirom/android_bootable_recovery/
Device Tree: https://github.com/underscoremone/android_device_samsung_gtexswifi
SuperSU: https://forum.xda-developers.com/apps/supersu
Magisk: https://forum.xda-developers.com/apps/magisk
reserved#1
Thank you!
I've been looking for some updated TWRP and Magisk installs for the T280, so this is great. Should this pass SafetyNet checks? On my first attempt, it did not appear to do so, but I'm grabbing a stock image to try again 100% fresh.
Del_Usion said:
I've been looking for some updated TWRP and Magisk installs for the T280, so this is great. Should this pass SafetyNet checks? On my first attempt, it did not appear to do so, but I'm grabbing a stock image to try again 100% fresh.
Click to expand...
Click to collapse
Unfortunately not with Magisk-v11.6... anyway looking at Magisk github topjohnwu is working on fixing bugs for samsung devices.. we probably won't need to use SuperSU with the next version, when it comes up I'll try it out and update the thread.
Happy to see that you released something for or tablet.
I hope that you released also some custom ROM.
Thanks.
Enviado desde mi SM-T280 mediante Tapatalk
I've updated twrp to 3.1.0-1
Nothing major just some little changes in the device tree.. before I was using sc8830 for the board name (chip), but the actual name is SC7730SW and the platform is sc8830. This should be the definitive build until major updates in the twrp source.
Thread updated with Magisk-v12.0.
No need to flash SuperSU with this version.
SafetyNet Passed (see 1st attached picture). :good:
If you reboot and open MagiskManager straight you'll probably get "Not rooted" error (see 2nd attached picture); just close the app, wait a bit, reopen it and everything should be ok.
Can't wait to get my hands on a PC to flash my tablet, appreciate your contributions and hard work!
Having restart problems
I added TWRP, and then successfully flashed supersu and the supersu image to the boot partition because it rebooted just fine after flashing but now when I manually restart the device it stays on the boot screen(the screen with Samsung Galaxy Tab A6 and powered by Android).
Is there an additional step I need to do to ensure that it will boot successfully or am I going to have to reboot into recovery every time now?
UPDATE: I forced a reboot into TWRP and then rebooted the system from there and it booted up just fine. It seems to be when I hold the power button once booted and select restart is when it hangs up.
@_mone just one question. Are you planning/trying to make a custom ROM also for tm-280?
I really hope so. Thanks
Enviado desde mi SM-T280 mediante Tapatalk
vayavalla said:
@_mone just one question. Are you planning/trying to make a custom ROM also for tm-280?
I really hope so. Thanks
Enviado desde mi SM-T280 mediante Tapatalk
Click to expand...
Click to collapse
Yes, I've already started.. but unfortunately I don't have much free time lately so it won't be ready soon.
Recovery updated to TWRP-3.1.1-0
twrp-3.1.1-0-_mone-gtexswifi.tar
twrp-3.1.1-0-_mone-gtexswifi.img
_mone said:
Recovery updated to TWRP-3.1.1-0
twrp-3.1.1-0-_mone-gtexswifi.tar
twrp-3.1.1-0-_mone-gtexswifi.img
Click to expand...
Click to collapse
Great to see some movement here!?
How is it going? Did you have any advance building ROM?
Just curiosity, take your time. Hope you can do it.
vayavalla said:
Great to see some movement here!
How is it going? Did you have any advance building ROM?
Just curiosity, take your time. Hope you can do it.
Click to expand...
Click to collapse
I am able to compile a LineageOS 13.0 build but it doesn't boot for now.. as I said before I don't have much free time lately.. I have more than one project going on but when I'll work again on this-one (custom ROM for the T280) and make some progress I'll let you know.
Device tree and kernel are on my github account.. so everybody is more than welcome to fork, clone, or push changes to it.
CTS profile mismatch on SafetyNet check.
Using Magiskv12 only, no SuperSU, clean install.
Let me know what you need if I can help.
_mone said:
I am able to compile a LineageOS 13.0 build but it doesn't boot for now.. as I said before I don't have much free time lately.. I have more than one project going on but when I'll work again on this-one (custom ROM for the T280) and make some progress I'll let you know.
Device tree and kernel are on my github account.. so everybody is more than welcome to fork, clone, or push changes to it.
Click to expand...
Click to collapse
This is awesome! Can you re-purpose anything from the Tinker ROM?
Hi, I have flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip and aqa4-gtexswifi-SU279sr3.img. Everything seems to be working fine, rooted, etc, except when I reboot or power off, i get stuck on the initial boot screen. It never starts booting. If i go into TWRP recovery and just hit reboot, it boots normally. Anyone have any suggestions of what to the problem is?
sssscary said:
Hi, I have flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip and aqa4-gtexswifi-SU279sr3.img. Everything seems to be working fine, rooted, etc, except when I reboot or power off, i get stuck on the initial boot screen. It never starts booting. If i go into TWRP recovery and just hit reboot, it boots normally. Anyone have any suggestions of what to the problem is?
Click to expand...
Click to collapse
Is your firmware build T280XXU0AQA4?
T280XXU0AQA4, yes that is correct. From sammobile. Thanks for replying.
sssscary said:
Hi, I have flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip and aqa4-gtexswifi-SU279sr3.img. Everything seems to be working fine, rooted, etc, except when I reboot or power off, i get stuck on the initial boot screen. It never starts booting. If i go into TWRP recovery and just hit reboot, it boots normally. Anyone have any suggestions of what to the problem is?
Click to expand...
Click to collapse
I flashed Magisk-v12.0.zip and T280XXU0AQA4-Magisk-v12.0-boot.img and it seemed to fix my problem. I have rebooted at least 8 times, so I think I am good. :good:
Related
Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500. Unfortunately, using loki tool causes a benign "secure boot error message" upon startup.
Here are some scripts that can be flashed in the recovery to convert a loki kernel to a bumped (permissive) kernel. The kernel will remain permissive until a new ROM or kernel is flashed again.
When making a kernel permissive, the following commands will be appended to the kernel boot command line:
Code:
androidboot.selinux=permissive selinux=0
Note: Only apply these scripts one time when setting the kernel to permissive mode or the command line above will be appended twice.
Instructions:
1) Flash ROM
2) Flash one of the scripts below, depending on what you want.
1) Convert a loki kernel to a bumped kernel
v500-loki-kernel-to-bumped-kernel-signed.zip
2) Convert a loki kernel to a bumped permissive kernel (turns off selinux)
v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
3) Convert an already bumped kernel to a permissive bumped kernel (turns off selinux)
v500-bumped-kernel-to-bumped-permissive-kernel-signed.zip
Thanks to @Skin1980 for the bash bump code.
Thanks to @aicjofs for the script base.
This is amazing, thanks for your work.
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
annoyingduck said:
This is really great, we all love what your doing for us - thanks again. I'm gonna take a stab in the dark and guess that its probably a bad idea to use the CM updater due to these having to be flashed along with an update?
Click to expand...
Click to collapse
It's fine to use the cm updater, but you will have to reboot into the recovery twice to apply the patch. Also, if you want your Bluetooth pairings to remain intact, then you want to keep the kernel in permissive mode and never let it boot with selinux enabled (at least until the selinux denials are fixed).
@annoyingduck
You can let cm updater download and verify the update and then hit cancel when it asks to install it. Then manually reboot to recovery and install from the cm updater download directory.
Amazing job @Deltadroid! I applied the first patch, rebooted and the warning message was gone!
Thank you very much for your outstanding work!
[]'s
So... This just removes the warning message when booting?
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
Yes
jesuita said:
So... This just removes the warning message when booting?
Click to expand...
Click to collapse
That is the only visible effect. It provides a cleaner way of mounting the boot.img
Ok thanks
Works fine with last Infected build.
I assume we have to flash this script after each update.
ledabe974 said:
Works fine with last Infected build.
I assume we have to flash this script after each update.
Click to expand...
Click to collapse
Yes, after each rom or kernel you flash.
Yay! thanks to the permissive script, SuperSU works on CM13! =)
nytral said:
Yay! thanks to the permissive script, SuperSU works on CM13! =)
Click to expand...
Click to collapse
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Deltadroid said:
That is good to hear.
The reason systemless supersu does not work with our device is because it breaks the signature on our bumped boot image.
If you choose option #1 on the op after flashing supersu, you should be able to keep selinux in enforcing mode and just rebump the boot image to fix the signature that supersu breaks.
Edit: you will need to dirty flash the rom again to put the device back into enforcing mode.. Then flash supersu and finally the script to bump the boot image over again.
Click to expand...
Click to collapse
Well, that's what I thought and what I did first, but actually latest beta SuperSU (2.68) is not breaking the boot sig for some reason (no bootloader error as with previous builds). Looking at logcat during the stuck boot I noticed some zygote process failing because of selinux and that's when I decided to try to disable it -> success! Now a cleaner way would probably be to give the logs to @Chainfire so he can have a look but given the non-popularity of V500 he probably won't care/not be able to fix it without one. Oh well, at least I have something working although not as secure as it should be. So thank you for this :good:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
glyrakos said:
Thank you for this great job!!! I was stuck on the LG logo with the know loki message... I though that my v500 was bricked for good.
I used the first file after cleaning everything in twrp 3.0.0 (not usb and external) and installing a)6.0 mmb29v, b) su v2.65 and c) your 1st file.
2 questions. 1) whenever I flash and update should I flash it through twrp with the above mentioned order? 2) Should I flash other version (older like 2..8.7.x) and philz zip?
Thank you again for your great job!!!
Click to expand...
Click to collapse
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Deltadroid said:
You did it correctly. Every time you flash SuperSU over again, you will need to flash this script directly after that to bump the kernel over again and fix the boot signature. Any recovery should work, but I recommend using the latest official TWRP.
Click to expand...
Click to collapse
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
glyrakos said:
Sorry, but as a nobbie let me ask you something more. Do you have a link for the latest official TWRP. How to flash it? Through TWRP 3.0.0 that I have now, or through sideload? Also I cannot enter TWRP with the combination of the 3 buttons. I get Factory Reset menu.
Thank you.
Click to expand...
Click to collapse
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Deltadroid said:
The official TWRP for device is here
http://forum.xda-developers.com/showthread.php?p=61363260
You can flash the new recovery image from within TWRP.
When you use the 3 buttons to get to recovery, it asks to factory reset, but it goes to TWRP instead. It is a hack because our recoveries were never actually unlocked. Just say, yes and TWRP will open.
Click to expand...
Click to collapse
Maybe I am not doing something good but when using the 3 button method it goes to factory reset and stays there endless if I do not press something .... but power whipes everything (i've re-setup my v500 for about 15 times already....) ... and volume up/down exits the menu and reboots......
TWRP for C9LTECHN/SM-C9000 Galaxy C9 Pro
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
PLEASE BEFORE YOU FLASH ROMS MAKE A COMPLETE BACKUP OF YOUR SYSTEM INCLUDING EFS SO YOU DO NOT BRICK YOUR MOBILE
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to intall TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock”checkbox/toggle and make sure you Check it or turn it ON.
4) Now Boot your Samsung Android device into Download mode.To Do So Follow the steps below
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not then your device is not connected properly
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Click the Start button on Odin to start Flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up
Your device will automatically reboot when Odin is done flashing. Now You can disconnect your device.
Done!!! TWRP is now installed on your device
NOTE: YOU MAY HAVE TO UNCHECK AUTO REBOOT IN THE OPTIONS TAB IN ODIN
TWRP source code: https://github.com/TeamWin
Source code device tree: https://github.com/travismills82/twrp_android_device_samsung_c9ltechn https://github.com/TeamWin/android_device_samsung_c9ltechn/
TWRP Nougat Download: https://www.androidfilehost.com/?fid=889964283620775437
TWRP Oreo Download: https://www.androidfilehost.com/?fid=1322778262903985796
no-verity-no-encrypt: https://www.androidfilehost.com/?fid=745425885120752506
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Contributors @travis82 @k2wl @deadman96385
I can confirm this works. backup, mount data, restore, otg usb, install.
I am runnung it now
Does this work on a SM-C9000?
Flavio said:
Does this work on a SM-C9000?
Click to expand...
Click to collapse
That's already for C9000. Can't you see the c9ltechn article. That's c9 pro's code
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Flavio said:
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Click to expand...
Click to collapse
You can flash any file still that just an article but you can't mount data anymore or backup data
I can flash files but cannot mount Data. I presume it is still encrypted despite being formatted twice?
Format data and reboot to recovery
ivanox1972 said:
Format data and reboot to recovery
Click to expand...
Click to collapse
So in TWRP format Data and then reboot again in TWRP.
And then flash SuperSU and no_verity?
Ok, I formatted Data twice in TWRP. Mounting Data works.
I flashed SuperSU in TWRP. Mounting Data works.
I flashed no_verity. Mounting Data works.
I rebooted into TWRP. Mounting Data works.
I rebooted into system and then switched off and rebooted into TWRP. Mounting Data does not work.
What am I doing wrong?
Correction:
I have now used this no-verity-no-encrypt_ashyx file:
https://www.androidfilehost.com/?fid=24591000424951049
And now Data stays decrypted!
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
I tested it few days, it works perfect and it is perfectly debloated
Please share Travis. Thank you for your work.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
can you share it please ???
I presume you would have to flash GApps separately with this ROM?
Flavio said:
I presume you would have to flash GApps separately with this ROM?
Click to expand...
Click to collapse
no god no, HK firmware has gapps built in like normal. I'll tweak it up some more and release it today on a separate thread. Right now I'm trying to get kernels to boot-up since they compile fine.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
I am interested, currently I just using the package disabler to disable all bloat samsung app..
do you have flashable s8 systemui for c9pro.. thanks
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
travis82 said:
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
Click to expand...
Click to collapse
Awesome work buddy, ill try to make my own ROM for this device :highfive:
will be pushing f2fs and ntfs support soon too when TWRP becomes official.
Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 6P
osm0sis said:
Guys.. bad news.. my Nexus 5X just got hit with the BLOD.
Good news for everyone is I spent a bit of time tonight to first patch TWRP 3.2.1-0-FBE (File-Based Encryption support) image to be 4core, then made an AnyKernel2 zip which will patch the existing boot and recovery partitions on-device to add all the 4core fixes from @XCnathan32.
Should work over any ROM, any custom kernel, recovery, etc., can be added in queue after ROM, root zip + custom kernel to patch it from TWRP or FlashFire (so good for OTAs), and simplifies the initial process greatly since you can now fastboot boot any 4core recovery.img and then adb sideload my AK3 zip to fix the likely newer recovery you already had on your device.
Click to expand...
Click to collapse
Original thread posts: Nexus 5X, Nexus 6P
Now updated to an AnyKernel3 zip to support the SAR (system-as-root) and 2SI (2 stage init) ROMs that have popped up for Pie and Android 10+!
General Information
If you've found this thread then I'm sure you probably already know what the Bootloop of Death is - separation of the performance (perf) CPU cores - and that the only way to recover from it is to unlock your bootloader and patch to disable the faulty cluster. If you have not enabled unlocking your bootloader yet, the known methods to get it to boot long enough so you can go to System, then Developer Options and toggle "OEM unlocking" are:
super cooling the device in a freezer in a ziplock bag to keep out moisture,
super heating around the camera, and
letting the battery run all the way down before trying to boot.
For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.
Some important notes before going any further:
Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
Freezing at the boot animation suggests ROM/ROM data problem or could also potentially be a BLOD with other components now beginning to separate and that's what people have reported when the 4core mods suddenly stop working with no configuration changes - if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work, sorry but your device is a brick.
If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
I haven't seen anyone say their devices only worked using a "1core" modification who had tried a proper 4core patched setup; 4core makes sense because it's the separate perf cores cluster becoming unsoldered, but if the 4 low power cores cluster also starts to come unsoldered logically not even a single core would work.. I think that's where the "Green Screen Of Death" comes into it.
DemiGod = Green Screen Of Death; unfortunately this (more components separating given more time - maybe the flash memory chip?) is why many call the 4core workaround only temporary.. there's not much that can be done after that from what I've read.
EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.
Android 10 does not appear to support FBE on these devices but the 4core FBE TWRP build can be used to BLOD patch the latest TWRP (see instructions in next post).
On Oreo, I was personally on stock ROM still, FBE enabled, rooted with SuperSU v2.82 SR5 + suhide and the latest Franco Kernel on my 5X. Then I bumped up the min freq on the low perf cores and it's working great - totally fine for general use, just anything creating a bit of heat like games maxing the low power cores for awhile, or charging, will make it pretty painfully laggy and risk further solder deterioration.
Even though SuperSU development is ostensibly dead, I still strongly recommend it on BLOD-affected devices using stock ROM for reasons I'll explain below.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Step-By-Step Installation Instructions
Any quoted commands should be entered without quotes
1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
2) Navigate to https://androidfilehost.com/?w=files&flid=312881 (also mirrored below) and download N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip to your platform-tools folder as well as
2a) twrp-3.2.1-0-fbe-4core-bullhead.img (Nexus 5X), or2b) twrp-3.2.1-0-fbe-4core-angler.img (Nexus 6P)3) Hold Shift + right-click on your platform-tools folder and
3a) Open a command window here (Windows <10), or3b) Open a PowerShell window here, then enter "cmd" at the Windows PowerShell prompt (Windows 10+)4) Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip" into the cmd prompt
8) Reboot and cross your fingers that it works
For information how to seamlessly update to stock and custom ROM OTAs, see the following post
Source Code: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Status: No Longer Updated
Thanks:
- @XCnathan32 for researching and developing the 4core workarounds for both the Nexus 5X and Nexus 6P
- chetgurevitch (GitHub) for the original FBE supporting TWRP builds
- @Aukaminator for the original step-by-step write-up
Update Flashing Instructions
Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3
Always flash the BLOD AK3 zip last!
Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
ROMs:
On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update.
On custom ROMs that do not have built-in Flash After Update (i.e. LineageOS-based), you may add my FlashAfterUpdate addon.d script to /system/addon.d/ and then place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/FlashAfterUpdate/ ensuring the BLOD AK3 is last for the same effect: flashed after every OTA.
On stock ROM rooted with SuperSU (SuperSU v2.82-SR5 recommended) instead of tapping "Reboot & Install" once the OTA is downloaded you should use @Chainfire's excellent FlashFire app to queue the OTA from /data/ota_package/update_s.zip then queue the SuperSU zip, custom kernel and BLOD AK3 zip, ensuring the BLOD AK3 is last. This is how I have mine set up, since this is by far the most seamless. Be sure to disable EverRoot since SuperSU v2.82-SR5 is newer than the SuperSU included in FlashFire.
On stock ROM rooted with Magisk you must uninstall Magisk from within Magisk Manager to restore your stock boot.img, reboot the ROM to restore your stock recovery partition, tap "Reboot & Install" once the OTA is downloaded, then go through the steps above to flash the 4core TWRP and BLOD AK3 zip again. I definitely recommend SuperSU on this device to avoid the hassle of unrooting and/or messing with factory images.
Kernels:
Custom kernels can be flashed from an app like Franco Kernel Manager & Updater, which can be set to flash without reboot for Franco Kernel updates, or "Flash only" can be chosen in the manual flasher. The FK app supports all types of AnyKernel3 zip so the BLOD AK3 zip may then be flashed after the custom kernel zip to repatch the new kernel's ramdisk.
For other kernel managers that don't support AK3 zips, simply reboot to recovery and flash the BLOD AK3 zip from there to repatch before attempting to boot the ROM again. Also see above under "stock ROM rooted with SuperSU", since FlashFire also works perfectly for this use-case, queuing the custom kernel zip and then the BLOD AK3 zip, with FlashFire's EverRoot option disabled since the device is already rooted.
Recoveries:
Download the updated custom recovery .img and, without flashing it, reboot to recovery, use TWRP's flash image feature to flash the new recovery.img, then without rebooting immediately flash the BLOD AK3 zip to patch it. You can then dump/backup the recovery partition if you want it as a recovery.img. Custom recovery updates can also be done from FlashFire, queuing the BLOD AK3 zip afterward, but the "Preserve recovery" feature must be disabled.
If you prefer to stay on stock recovery for some reason, you can still use TWRP to do the above without flashing TWRP to the device by using "fastboot boot twrp-3.2.1-0-fbe-4core-angler.img".
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Changelog
2018-01-15 - Original post in other BLOD threads.
2018-07-21 - Update AK2 Core+Backend files to latest, add searching of all init.*.rc files for problematic cpuset commands which were popularized by Franco Kernel and are now used by multiple custom kernels. (6758 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (1720 downloads)
2020-01-16 - Update AK3 Core+Backend files to latest to fix AVBv1 signing in recovery on Android 10, update boot_signer-dexed.jar. (570 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1412 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1789 downloads)
2021-07-21 - Update AK3 Core+Backend files to latest to support Lineage 18.1 recovery and Android 11 ROMs.
Good luck and enjoy!
Glad to see this exclusive thread... just came here to report that I've been using your fix since Jan this year ( https://forum.xda-developers.com/ne...-6p-bootloop-death-blod-t3640279/post75220708 ) and yeah my phone's still alive and running fine. Kudos to your work... Great job you did there... saving hundreds of bucks... Really appreciated!
Thanks again.
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
SH15 said:
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
Click to expand...
Click to collapse
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
osm0sis said:
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
Click to expand...
Click to collapse
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
SH15 said:
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
Click to expand...
Click to collapse
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
FlameSting said:
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
Click to expand...
Click to collapse
Please read the OP. It works over any ROM, any custom kernel, any recovery.
osm0sis said:
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Click to expand...
Click to collapse
Thank you very much! I flashed the newest factory image for Oreo and then re-flashed the BLOD AK2 zip and it worked. Thank you for your help! :good:
Idk if I'm in the right place.
I recently replaced my battery (2nd time this week, first one was bad) and everything was working fine. Then my phone started randomly rebooting. Googled it and apparently it's one of the first signs of BLOD. Followed this and the phone stopped shutting down randomly. Now the phone only works if plugged into a power source. Idk if I did something wrong or the battery is trash (even though it was working fine all day)
I'd appreciate an guidance [emoji24]
Sent from my [device_name] using XDA-Developers Legacy app
This saved my day! Thanks everyone! Got my 6P booted up again... and it's not even rooted
I want just only to thanks @osm0sis and it's genial solution!
Thanlks i recover my phone and saved a lot of money.
I understand it could be a temporary solution but thanks!!!
gabriele
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
godd said:
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
Click to expand...
Click to collapse
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
I had my phone hang on the google logo a couple times, but rebooting it fixed it. Is this an early sign of this problem? Just replaced battery and so far it seems fine.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
I am in this same boat... RIP N6P, this is my 2nd N6P Google replaced the first one due to the BLOD and now the replacement is dead.
Thanks for all the efforts and help.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
Same as the guy above. Sites down need mirrors or something?
jbjcurly said:
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
Click to expand...
Click to collapse
CavyS said:
Same as the guy above. Sites down need mirrors or something?
Click to expand...
Click to collapse
Mirrored in the OP. Thanks!
Edit: And BasketBuild is also back! :good:
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
>>> *** UPDATED (see 5. ) *** <<<
Installation guide: (pay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
Code:
fastboot boot twrp-3.4.0-0-evert.img
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
!!! 5. Disable HAB verification by flashing this .zip hab_disabler.zip !!! (*)
6. Flash the TWRP installer.zip
7. Install Magisk (optional)
8. Reboot to system and enjoy!
(*) HAB (High Assurance Boot) is a second verification process/service. It checks /system and /oem partition. The hab_disabler.zip will delete/patch the related files. (for further information see "update-binary")
During first boot...
...your device will reboot once. Don't panic, that's quite normal!
...animation after "Hello Moto" will take 2-3 min.
*** tested on PPWS29.116-20-23
WoKoschekk said:
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
Installation guidepay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
5. Flash the TWRP installer.zip
6. Install Magisk (optional)
7. Reboot to system and enjoy!
During first boot your device will reboot once. Don't panic, that's quite normal!
Edit: Tested on build PPWS29.116-20-23
Click to expand...
Click to collapse
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
I tried it on my own. First boot runs fine but the second one ends in a bootloop. I already know whats wrong. Give me a few hours to fix this.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
The problem has been fixed!!
I rebooted several times from system to recovery and vice versa. Magisk and TWRP (installed permanently) work fine. No issues known yet.
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
It works fine fir me. I enabled Magisk Hide to hide some apps but my device doesn't loop after that.
Did you use the updated method?
- Magisk was repacked with new name
- Magisk Hide enabled
- modules installed
- rebooted to recovery and then to system => no looping
- rebooted the device normally => no looping
At this moment I'm using my G6+
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
WoKoschekk said:
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
Click to expand...
Click to collapse
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Dk Gautam said:
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Click to expand...
Click to collapse
Great!! Thanks for your reply!
I'm using neither Lineage nor VoLTE so I don't know if it's supported.
hello OP
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
d_g_m_2000 said:
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
Click to expand...
Click to collapse
Are you trying to boot TWRP?
WoKoschekk said:
Are you trying to boot TWRP?
Click to expand...
Click to collapse
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
ok, ia my pc, i try in another and it boot up... i got ryzen 5 2600 just if anyone else find out what da f*ck is going on... thanks in advance for your comments.
d_g_m_2000 said:
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
Click to expand...
Click to collapse
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
WoKoschekk said:
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
Click to expand...
Click to collapse
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
d_g_m_2000 said:
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
Click to expand...
Click to collapse
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
WoKoschekk said:
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
Click to expand...
Click to collapse
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
d_g_m_2000 said:
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
Click to expand...
Click to collapse
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
WoKoschekk said:
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
Click to expand...
Click to collapse
that's is a real bummer... thank you for your comments!
Hi i install pixel experence rom and im having a problem i canflash anything from my device, storage dont shows corrrct size and, shows binders with aleaty names with nothing inside, and i can't transfer with USB
TWRP 3.5.0 One UI 3.1 for Samsung Galaxy A50 Android 11. How to Root Samsung Galaxy A50 Android 11 with TWRP 3.5.0 + Magisk. The TWRP Recovery support Galaxy A50 One UI 3.1 Android 11 firmware. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The TWRP 3.5.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET ME KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN
Manual Instructions for Flashing and Rooting
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing TWRP as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Install Magisk-v22.0.apk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions - Details
Download
TWRP 3.5.0 A11
Magisk22 app
Thanks to:
@neel0210 for Kernel Source
@Enzoaquino for OrangeFox
Good work
Thanks for twrp
Thank you
Flashing this @ A505GN. Hope it works
The twrp works but the multi disabler didn't work
This is a505gn
I reverted back to 3.4 because I encountered an issue. I'm stuck in bootloop, cannot access twrp nor download mode. Had to remove the back of my phone and unplug the ribbon connecting the battery to the phone just to power it off.
I already flashed the twrp via Odin but when I installed Magick on the phone this came up. Did I done something wrong?
q1pa said:
I already flashed the twrp via Odin but when I installed Magick on the phone this came up. Did I done something wrong?
Click to expand...
Click to collapse
it happens to me sometimes
just rebbot to revocery in twrp
Thank you @redymedan for the recovery. I'm glad to say that
your "how to android" channel is great.
I have a question Please clarify the following.
In this recovery Can we update magisk to latest? (When it released)
Sharath Mane said:
Thank you @redymedan for the recovery. I'm glad to say that
your "how to android" channel is great.
I have a question Please clarify the following.
In this recovery Can we update magisk to latest? (When it released)
Click to expand...
Click to collapse
Yes, you can update it from magisk apps
It worked!
I had to run a patched AP first for magisk to work
Im on a A505G/DS
It worked just fine on my A505FN! Thanks!
Worked perfectly on A505W !
Had to use Multidisabler 3.1 instead.
I have an A505FN and I'm not able to root it with Magisk. If I try to install the linked TWRP_v3.5.0_A505_A11_Magisk.tar with Odin, then I can't reboot into Recovery afterwards - instead the Download-Mode appears again.
With RR-TWRP_v3.4.0_A505_CUBC_OneUI.tar from another Thread, it's possible to start into TWRP after flashing it with Odin. But if I boot into System (LOS 18.1) and start the already preinstalled Magisk, Magisk updates itself and after restart of Magisk I can try to install Magisk and in the first screen "Recovery Mode" is checked. If I click on "Next step", the Option "Recovery Mode" disappears and I can choose a file to patch.
I don't know where I'm wrong.
IngolfN said:
I have an A505FN and I'm not able to root it with Magisk. If I try to install the linked TWRP_v3.5.0_A505_A11_Magisk.tar with Odin, then I can't reboot into Recovery afterwards - instead the Download-Mode appears again.
With RR-TWRP_v3.4.0_A505_CUBC_OneUI.tar from another Thread, it's possible to start into TWRP after flashing it with Odin. But if I boot into System (LOS 18.1) and start the already preinstalled Magisk, Magisk updates itself and after restart of Magisk I can try to install Magisk and in the first screen "Recovery Mode" is checked. If I click on "Next step", the Option "Recovery Mode" disappears and I can choose a file to patch.
I don't know where I'm wrong.
Click to expand...
Click to collapse
Flash stock rom with odin
Reboot. Do not login to google. Check oem grayed out.
Reboot to download mode
Select 3.5.0 twrp as ap. (You should Untick autorestart in options) . Start.
By connecting cable reboot into recovery by using button combo. Do not reboot to system. Do not remove cable.
After entering twrp.
Format data. Next flash multidisabler.
Now select reboot to recovery.
Wait for few minutes, if doesn't boot,force restart by using volume down and power buttons. It will bootup.
You can finish ur setup now.
You can flash other roms . To enter twrp you need to connect cable with pc and use buttons.
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
IngolfN said:
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
Click to expand...
Click to collapse
you will edit your ini.environ.rc
watch it in youtube
IngolfN said:
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
Click to expand...
Click to collapse
Goto twrp and select reboot recovery