Database Develop

ODIN Softbrick Fix??

Hello,
I've spent the better part of 2 days trying to figure this out. First, I attempted to use ThePagel's ODIN guide to root without tripping the KNOX counter. That wouldn't work, as I constantly received NAND write start/fail messages. Ultimately, I followed the CF Auto Root guide at tomsguide-dot-com/us/samsung-galaxy-s6-guide,review-2856-3.html. I located my device (SM-G920T), and downloaded the appropriate auto root files which included ODIN 3.10.6. I previously downloaded and attempted to use ODIN 3.10.6 and ODIN 3.10.7. The ODIN version that came with the auto-root program had differences in the ODIN.ini file, but when I followed the instructions it flashed a CACHE.img and RECOVERY.img file, showed a green "PASS" sign, and attempted to reboot.
When my phone automatically attempted to reboot, the top of the GS6 logo screen has red letters stating "Recovery is not SEAndroid Enforcing." When I return to the download/ODIN screen I see the following in formation now:
Product Name: SM-G920T
Current Binary: Custom
System Status: Official
FRP Lock: Off
Secure Download: Enabled
KNOX Warrant Void: 1 (it tripped)
RP SWRev: B:3, K:2, S:2
After this failure, I realized my phone was previously Android 5.1.1, and the CF Auto Root files I used are for 5.0.2. Now I'm attempting to use ODIN to restore a stock 5.0.2 as well as a 5.1.1 build, but keep receiving the NAND Write Start/Fail message. After a NAND failure going to Android 5.0.2, I notice my device has a black and red message reading, "SW Rev. Check Fail. Device: 3, Binary: 1." Attempting to go back to Android 5.1.1 (where I started), the error message states "Device 3, Binary 2."
I've attempted to alter the .tar.md5 file and include ONLY the CACHE.img and RECOVERY.img, but when I do, the MD5 value doesn't match, and I am unable to proceed.
I'll continue to read threads and try to figure out how to fix this, but any help would be appreciated. Thank you.

I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.

**SOLVED**
MBuckley81 said:
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
Click to expand...
Click to collapse
Not sure what exactly changed, but maybe the fact I read this:
forum.xda-developers.com/tmobile-galaxy-s6/help/tried-to-root-5-0-2-5-1-1-guide-t3191903/
I tried doing the same stuff, but it wasn't until I used PeaZip instead of WinRAR or 7Zip. I put the stock 5.1.1 Cache.img and Recovery.img files in my own .tar file (not tar.md5), and was able to use ODIN to push them to the phone. It rebooted, then did the dancing android monkey loading screen. All my other stuff is still on the phone.

MBuckley81 said:
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
Click to expand...
Click to collapse
You don't need to add the .MD5 to the file name..
Stick with .TAR, that will bypass the MD5 Check..

2021_VZW_NOTE4_Tool Too Root+Unlock Bootloaders+Upgrade Or Downgrade_Bootloaders_Works On KK/LL/MM Plus Roms For All 3 Firmwares

This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.​
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK_2021.7z
Instructions
1, You need working adb on your computer. The latest samsung drivers installed. A Sdcard inserted in the phone preferably a 32 gig or less. Must be at least 1 gig. Phone will be wiped! A data connection or wifi is also required.
2. Download and extract the EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK.7z
3. Reboot phone to download mode (pwr+voldwn+home_button). In Odin_Files folder use odin and flash the COMBINATION_VZW_FA44_N910VVRU2APB1.tar.md5 in BL slot in odin
4. Once phone is booted up and connected to computer run 1Install_KingRoot.cmd. This will install kingo root and kingroot app on phone.
5. Once installed make sure phone has data via cell or wifi. Run kingo root to root phone. Phone may kernel panic and reboot just keep trying. Once root is successful move to step 6 if unsuccessful try kingroot if thats succesful click on root permissions in the kingo root app and click on system adb and change prompt to allow. This is not necessary if rooted with kingo app
6. Make sure phone is connected to computer and run1Replace_With_SuperSu.cmd then once this process finishes run 2UnlockBootloader.cmd. This will change CID to Dev edition and then unlock that bootloader. If first time unlocking phone it will change your cid to dev edition then reboot during process. This is fine you will not loose root. Close cmd window wait for phone to reconnect then run again this time it will unlock the bootloaders when done phone will once again power off. Remove sdcard this is very important so I will say again remove SDCard from Phone your phone will not boot with sdcard in until it is reformated! Reboot to download mode you should notice it says DEV Mode.
7. Reboot phone and now you are ready to choose your bootloader you want to be on for this guide we will assume you want to be on latest QL1 Marshmallow bootloader.
8. Make sure phone is connected and run 3UnlockBootloader_MM_QL1.cmd or what ever one you choose. When done Phone will power off and now the bootloader is updated.
9. Now choose the firmware that matches your unlocked bootloader from below
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
10 Reboot phone to download mode and flash above firmware that matches your bootloader version Im using N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar as example. Extract N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar and use provide odin from EMMC_15_VZW_NOTE4_BOOTLOADER_UNLOCK and choose N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 or the one you choose and in odin BL slot uncheck auto reboot and flash. When flash is done make sure to reboot to TWRP recovery which will be installed and wipe data then reboot. You are done!
11. Above firmware running magisk root may til you additional steps are needed and download magisk zip. You can skip this step if you want as it is rooted and magisk apk is installed but if you want I will provide magisk zip used in root if you want to reflash

Upgrade Bootloaders For EMMC 15 VZW DEV Unlocked Phones​
This process requires flashing back all stock firmware in order to upgrade/downgrade bootloaders. So I have made a special rom just for doing this which should make process easy. Its all done with odin and flashire.
Downloads
EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS_2021.7z
N910VVRU1ANJ5_DEV_ROOTED.tar.rar Kit Kat 4.4 Rooted Firmware
N910VVRU2BOG5_DEV_ROOTED_SUPERSU.tar.rar Lollipop 5.0 Rooted Firmware
N910VVRU2BPA1_DEV_ROOTED_MAGISK.tar.rar Lollipop 5.1 Rooted Firmware
N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.rar Marshmallow 6.0 Rooted Firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z Marshmallow 6.0 EFTSU Rooted Latest Firmware!!
Instructions
You must be on EMMC 15 unlocked bootloader if not goto post 1 to unlock bootloader
1. Download the EMMC_15_VZW_NOTE4_BOOTLOADER_UPGRADE_ZIPS.7z and extract this will contain the zips and special firmware for upgrading bootloader. Download above firmware you want to upgrade/downgrade too.
2. You will probably need to wipe data so reboot to TWRP recovery wipe data then reboot to download mode use provide odin in the Odin_Files folder and choose FIRMWARE_FOR_UPGRADE_DOWGRADE_BOOTLOADERS.tar.md5 and flash in BL slot.
3. This will reflash stock firmware and a prerooted special rom with a flashfire preinstalled and minimal files just to boot rom. Your bootloader will be locked for the time being as this is necessary to upgrade bootloaders.
4. When rom is booted choose the zip that matches the firmware you want to install from the FlashFire_Zips folder and place on phone storage.
5. Open flashfire grant root access choose add zip choose the zip you placed on phone click on reboot tab in flashfire and choose reboot to bootloader in will say dev mode this means your unlocked again
6, Now choose above firmware you downloaded extract the tar.md5 file from the rar file and flash in BL slot in odin Uncheck auto reboot when don flashing force reboot to TWRP recovery and wipe data again then reboot phone. You are now Upgraded or downgraded which ever you choose to do.

Mine

This has been needed in our forum for a long time. Fantastic work, thanks!

jrkruse said:
Mine
Click to expand...
Click to collapse
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx

theohtc said:
Hello
I want ask u do you know how to open bootloder for huawei mate 20 pro lya.l09
Thx
Click to expand...
Click to collapse
Maybe ask in the huawei thread.
Sent from some device I modified

How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"

DeeXii said:
How many times does it usually take for kingroot?
UPDATE: Tried many times and eventually it said "Root Failed" "no strategy now"
Click to expand...
Click to collapse
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified

jrkruse said:
I would start over completely. Reflash the Odin files then make sure you have internet access i would use wifi when running kingroot app
Sent from some device I modified
Click to expand...
Click to collapse
Ok I will reflash...
Yes I had internet access, Kingroot does not even function without it.
Thanks for the fast reply!
---------- Post added at 06:15 PM ---------- Previous post was at 05:54 PM ----------
Can't seem to get passed 35%
---------- Post added at 06:41 PM ---------- Previous post was at 06:15 PM ----------
UPDATE:
I used Kingroot desktop version and it rooted the first try.
On to the next step.
---------- Post added at 07:20 PM ---------- Previous post was at 06:41 PM ----------
How long does N910VVRU2CQL1_DEV_ROOTED_MAGISK.tar.md5 take to flash?
It has not errored out at all but it seems to be taking longer than I have ever seen.
It's on tz.mbn.

@jrkruse THANK YOU for putting this into such a simplified method that doesn't require large downloads, multiple command lines, or having to downgrade and re-upgrade just to be able to achieve an initial root, unlock, and TWRP!!! I read through way too many methods that were a MILE long before I happened across this one. The ONLY issue i ran into during this process (should help others), was that I had to insert a newer version (and rename it to match the script) of the KingRoot APK to be able to achieve root on my existing CQL1 firmware. I tried the provided APK many times without success, but a newer version was able to achieve root on CQL1 after only a few attempts/reboots. I downloaded the newer APK (version 5.3.7) from the post provided by @Kingxteam at https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461. If anyone is looking for a simple way to root and unlock CQL1 without having to downgrade first, THIS IS IT!!! Thanks again jrkruse for the automated script, and thank you Kingxteam for the thread and links for a KingRoot APK that works with CQL1!!!

I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.

Jalh said:
I'm getting a bit fustrated by the rooting process. Hopefully someone would be able to help me out.
Once I finished step #3 and boot into the dev and I try to root, it fails. I have tried several times and keep on failing. I took a different route and approach by reinstalling the image and re installing the kingroot and the same. Finally I gave up, and replaced the kingroot apk by its newest release. Eventually I get rooted, but once i try to unlock the boot loader i get the following message "/system/bin/sh: su: not found" .Randomly I was able to successfully run unlookbootloader once, but once the device reboots, i lose root.
Im not sure what to do, to keep root at this point.
Click to expand...
Click to collapse
Did you install the combo firmware because you don’t loose root when on the combo firmware
Sent from some device I modified

Hello all. I'll start by acknowledging that I am a noob with very little experience but can follow technical instructions to achieve desired results when they are described easily for the uninitiated. That said, I too have 2 Verizon note 4s running marshmallow with build numbers ending in CQL1. Following your tutorial, I was able to get one of my phones to step 4 where as described, it kept showing the kernel panic error no less than 10 times. I took the suggestion of another user and was finally able to achieve root with the Kingroot desktop app on my PC. I then clicked on root permissions and changed the prompt to allow. At this point I proceeded to step 6 and after clicking 2UnlockBootloader.cmd, the phone did not reboot as described and the command window returned the following message:
D:\Desktop\EMMC>adb wait-for-device
You May Need To Accept Root Dialog On Phone ...
Files/n4unlock\: 1 file pushed. 1.2 MB/s (23432 bytes in 0.018s)
cd /data/local/tmp/n4unlock
chmod 777 unlock
chown root.root unlock
./unlock
yes
exit
/system/bin/sh: su: not found
Process Complete.
Press any key to continue . . .
No dialog box appeared on my phone and I'm not sure why it says SU not found or what the significance of that missing item is to the process. Am I missing a step? Assuming I have not unlocked the bootloader with step 6, what now? What should I do at this point to achieve the desired result? I do realize that these are older phones and some might care less but making them work now could help my family in a big way. I'd gladly share some of those savings with anyone willing to help troubleshoot... thanks in advance.

Hanging on 1st BL file
Not my first time but seems like im getting hing up during the first flash. how long does it normally take for this 1st BL to flash over
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 636 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
Hung here for about 10min any help would be great thanks!

jrkruse said:
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recovery And Install PreRooted Firmware Of Your Choice!.​
I posted this because the current unlock methods are not easy to do. This should make process easier
If you already have unlocked bootloader and want to change bootloader versions then goto post 2
Click to expand...
Click to collapse
Working perfectly & really much much easier (than the original method which I have done twice so far so I know what I am talking about)!! Thank you

I have to throw in my hat saying that this method didn't work for me either. Like others I got stuck at the rooting stage, I tried numerous times to get root, it didn't work. I then used the upgraded KingRoot, it worked but step 6. 2UnlockBootloader.cmd script wouldn't take, since it seemingly kept losing root. But don't worry, if you've tried this method and are stuck you can still salvage it by going through the manual methods.
Make sure reactivation lock is off if you have the option (I didn't on the firmware that OP installed on the phone), usb debugging is on and adb devices brings up your phone)
----
Flash back to stock
----
I had to flash it to a stock rom using Odin (stick them in AP and make sure re-partition in options isn't checked) Android version 5.1.1, as going through the steps below (which are basically what's in 2UnlockBootloader.cmd) manually still wouldn't take: https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
----
Root and bootloader unlock
----
I used the android version of KingORoot to root
I used this guide (the files used in this walkthrough are the ones largely used in the others below and downloads faster): https://forum.xda-developers.com/no...asy-guide-how-to-root-verizon-galaxy-t3454593
Which has a video here: https://www.youtube.com/watch?v=cfpehEkhfyg
and a text walkthrough with photos (that I like more) from the same guy here: https://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
(Since I largely used this make sure you put "samsung_unlock_n4-fix" in the fastboot folder)
Mine however began to bootloop (I'm unsure why they tell you to reboot to system on step 19 after installing the systemonly firmware but do it anyways I guess. But you had to install the kernel and superuser in twrp as addressed here: https://youtu.be/dhcV93GuHB4?t=1285
After that it booted up to 5.1.1 download rootcheck to root check it.
----
Rooting for Marshmallow
----
After that's done if you want to flash MarshMallow roms, including rooted stock 6.0.1 then you need to further go through the process here, which is basically doing it all over again:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
(Going through this process will kill your wifi connection, the KingORoot PC program didn't work to re-root mine, so you must have a sim card data connection I guess (or reverse tethering if you can get that to work(I had data so I didn't go through that).
then here when you get to the part about flashing a rom:
https://forum.xda-developers.com/no...firmware-safe-upgrade-to-marshmallow-t3402727
(Flashed with Odin (AP) not TWRP)
Anyway, I'm now rooted and bootloader unlocked. It wasn't too hard, once I found the guides it went pretty smoothly. Good luck!

using this method I get a black screen after booting up any aosp rom... logs from booted lineageos17.1:
https://pastebin.com/7yhL7FzM

I rooted 3 910v phones with this method. and am running unofficial Lineage 18.1 roms on all 3 kingroot for pc worked for me.

I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z​

jrkruse said:
I updated root files and method too work on newer computers
Added latest firmware
VZW_N910VVRU2CTI1_ROOTED_FORCE_WIPE.tar.7z​
Click to expand...
Click to collapse
Thank you again for making our life easier, the ones who will appreciate your efforts are the ones who have done it manually ROCK ON!

How to flash magisk_patched.tar to Samsung Galaxy S10+ using Heimdall?

I know the guide to flash that tar file assumes that people use Windows and Odin, but for those of use that use Heimdall in Linux, is there a guide on how to flash magisk_patched.tar to the phone?
I know I can use VMware or VirtualBox, but I really don't like to use Windows anymore so I would be happy if someone could give me a failsafe way to flash in Linux.

I'd like to know that too since the official installation guide unfortunately only refers to Odin.

I ended up flashing the *img within TWRP as boot image. It worked.

geronimoge said:
I ended up flashing the *img within TWRP as boot image. It worked.
Click to expand...
Click to collapse
Can you explain what you mean? I don't have TWRP should I install that first and how?
I'm also stuck on this step, using Heimdall to flash the patched Magisk firmware without instructions

I have the same problem - not sure how to flash a magisk_patched.tar file (to Samsung Galaxy Tab A7 lite) using Heimdall on Linux. However, I cannot use the TWRP method because there isn't one yet for this device.
Heimdall is set up and recognises the device. I downloaded and saved the PIT file. Then in the flash tab on Heimdall I add the PIT file, then I'm not sure which partition to choose to flash the magisk.tar to. I also don't quite understand the magisk install instructions where it says "flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware". Do I have to extract the contents of AP....tar.md5, insert the magisk_patched.tar file and compress it again? Or do I simply select all of the folders from the original firmware package (AP, BL, CO, CSC) and magisk_patched.tar individually and flash them all (in the same way you can queue up zip files to flash via a custom recovery?
Thanks for any help.

tixos said:
Can you explain what you mean? I don't have TWRP should I install that first and how?
I'm also stuck on this step, using Heimdall to flash the patched Magisk firmware without instructions
Click to expand...
Click to collapse
This is how I managed to have a iode OS (lineage based) rom with magistk root using heimdall on a linux machine.
activate usb developer mode.
Download Magisk-v25.2.zip and put it on the phone (internal storage).
unlock the bootloader.
Download twrp recovery image. twrp for s10e, this is for s10e, but you have to use the twrp for s10+
issue: adb reboot bootloader
issue: heimdal flash --RECOVERY {twrp.img} --no-reboot
press power + volume down to reboot and then QUICKLY press power + bigsbi + volume up to boot into recovery. If you are booting in the normal system then you were not quick enough, you have to repeat steps 5, 6, 7.
in twrp install the Magisk-v25.2.zip from the internal storage and select wipe.
reboot in normal system.
rename Magisk-v25.2.zip to Magisk-v25.2.apk and install it.
enjoy the root!!
The pitfalls that I found and do not work.
Take the stock ap.tag image and patch it with the Magisk aplication on the phone and take the *.img and flash them with heimdall.
Install the Magisk-v25.2.zip via adb sideload.
Step 7 is maybe not intuitive enough: on s10e if you flash the twrp recovery and then it boots in the normal system image, the system image will revert the recovery image back to the original so you loose the twrp.
Hope this help some one else.

ETTT said:
This is how I managed to have a iode OS (lineage based) rom with magistk root using heimdall on a linux machine.
activate usb developer mode.
Download Magisk-v25.2.zip and put it on the phone (internal storage).
unlock the bootloader.
Download twrp recovery image. twrp for s10e, this is for s10e, but you have to use the twrp for s10+
issue: adb reboot bootloader
issue: heimdal flash --RECOVERY {twrp.img} --no-reboot
press power + volume down to reboot and then QUICKLY press power + bigsbi + volume up to boot into recovery. If you are booting in the normal system then you were not quick enough, you have to repeat steps 5, 6, 7.
in twrp install the Magisk-v25.2.zip from the internal storage and select wipe.
reboot in normal system.
rename Magisk-v25.2.zip to Magisk-v25.2.apk and install it.
enjoy the root!!
The pitfalls that I found and do not work.
Take the stock ap.tag image and patch it with the Magisk aplication on the phone and take the *.img and flash them with heimdall.
Install the Magisk-v25.2.zip via adb sideload.
Step 7 is maybe not intuitive enough: on s10e if you flash the twrp recovery and then it boots in the normal system image, the system image will revert the recovery image back to the original so you loose the twrp.
Hope this help some one else.
Click to expand...
Click to collapse
Sorry for necro-ing here, but, after following these steps, which I was already familiar with, I noticed that there is, quite literally, no way to follow through with this if, say, a button is not working.
I am trying these steps with a Galaxy S6, you see, and the home button is broken. Were not for that, it'd have taken me less than an hour to flash a custom ROM and Gapps on my relative's phone. However, because the Home button is broken, there is no way to go from download/bootloader mode directly into recovery mode, making it so that the stock firmware always overwrites the recovery partition.
Would you be so kind as to offer any insights into alternative solutions, if they exist?

099349613a5fbd51bd6237f13 said:
Sorry for necro-ing here, but, after following these steps, which I was already familiar with, I noticed that there is, quite literally, no way to follow through with this if, say, a button is not working.
I am trying these steps with a Galaxy S6, you see, and the home button is broken. Were not for that, it'd have taken me less than an hour to flash a custom ROM and Gapps on my relative's phone. However, because the Home button is broken, there is no way to go from download/bootloader mode directly into recovery mode, making it so that the stock firmware always overwrites the recovery partition.
Would you be so kind as to offer any insights into alternative solutions, if they exist?
Click to expand...
Click to collapse
+1
Similar problem here, with a defected "Volume Up" button on SM-T530 tablet.
I followed this tutorial and successfully flashed boot partition with magisk_patched-25200_4042u.img. Hope this helps.
https://www.reddit.com/r/Android/comments/79fzxy

Heimdall just cant read files above 5gb and for the super.img of my galaxy tab a8 is 6.3 gb. any solutions?

Question Magisk for S21 Ultra?

I just received my Galaxy Ultra SM-G998B. Anyone had successfully root your gs21 using magisk? How's the safety net?
Like to hear any feedback before rooting my phone.
Tnx

heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help

Try magisk canary

I tried rooting the regular S21 but without success yet ( https://forum.xda-developers.com/t/...e-links-and-flashing-discussion-here.4220563/ )

Try magisk canary

Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?

Ziomus said:
Same here with S21+
So for now i lost samsung pass and s health :/
Did someone try patch kermnel locally?
Click to expand...
Click to collapse
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?

rodrigofd said:
Can you describe exactly what you did? So we can cross out the options that don't work ....
Can you do that as well @peterkoarl ?
What exact Magisk app version did you use?
Magisk package version?
Did you patch the AP .tar (large file), or just the boot.img inside?
Click to expand...
Click to collapse
thanks for your reply, i updated my OP with all the infos

peterkoarl said:
thanks for your reply, i updated my OP with all the infos
Click to expand...
Click to collapse
Couple things:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed

rodrigofd said:
* are you keeping your data intact between flashes? i.e. no format?
There's a chance that booting a custom boot.img, on a device that already has data created from a stock boot.img, doesn't work (because of the encryption key)... but I can't say for sure, it's an assumption.
Click to expand...
Click to collapse
i used CSC, not HOME_CSC - i thought that would mean that data gets wiped?
i did not manually do anything in regards to formatting. what .. could i do?
rodrigofd said:
* Also, how long are you really waiting on SAMSUNG logo screen, after flashing magisk'ed boot.img?
I recall that the first boot after doing this, can take several minutes, specially if you have many apps installed
Click to expand...
Click to collapse
yeah i remember that as well from older devices; i let it sit for at least 10 minutes on the initial flash to make sure, so im pretty sure its stuck.

i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.

peterkoarl said:
i just tried (again) using latest canary 6fb20b3e (21406) to patch the whole ~7G AP file,
transferred it back via adb pull,
flashed it together with BL+CP+CSC,
to no avail - again stuck at SAMSUNG logo. gonna wait another 15 minutes but.... it seems stuck.
Click to expand...
Click to collapse
Have you tried patching just the raw boot.img file? (Not tar'ed)
You need to uncompress the boot.img.lz4 file first, so you get a boot.img, copy that file to the phone, and select it with Magisk app.
Then get back the patched *.img file into the PC, rename it back to boot img, put it in a TAR, and flash that TAR with Odin.

peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy

peterkoarl said:
heya,
anyone got magisk to work yet?
i'm on AP_G998BXXU1AUAC_CL20701476_QB37730003 and trying to install magisk fails by getting immediately stuck on the SAMSUNG boot logo.
i tried, using MagiskManager-v8.0.7.apk (Magisk v21.4):
- extracting AP_G998BXXU1AUAC_CL20701476_QB37730003_REV01_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
- transferring to device (via mtp), patching in manager,
- transferring back via adb pull because the wiki said so
- using Odin3 v3.14.1_3B_PatcheD i flashed BL+CP+CSC+patched_AP, with autoreset on
-> stuck on samsung logo
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried extracting AP, created a tar from boot.img.lz4, patched it on device, transferred back, flashed *just* the patched boot image as AP in ODIN -> same outcome
then i re-flashed all stock BL+CP+CSC+AP, device booted normally again
then i tried flashing BL+CP+CSC+patched_boot_image, same outcome
then i odin-flashed stock boot tar as AP, device booted normally again
=======
also tried canary magisk; seems like the outcome is always the same. i can reflash stock boot.img and the phone boots fine. i am not sure which canary "version" i had, probably some around 27.01.2021.
thanks for any infos/help
Click to expand...
Click to collapse
Patch the extracted the boot.img first and rename the patched boot to "boot.img" BEFORE (not after) compressing it to tar.
Also ensure to enable OEM unlocking in Developer options before flashing the patched boot tar

thanks for all the replies.
i tried the "boot.img only" approach first; makes no difference. magisk says it patched it fine, renamed it back to boot.img, tar'ed it into boot.img.tar, flashed that via odin without autoreboot. cant even get into recovery after restarting.
EDIT: i WAS able to enter stock recovery now; i realized that since i need to have the pc/usb cable connected to be able to enter download mode, maybe i need the same for recovery - and yes, volup+power while cable is connected does drop me into recovery. however, even after factory reset there, it wont boot.
EDIT2: yes my bootloader is unlocked, oem option in dev is greyed out.
EDIT3: i re-did the boot.img-only approach and made sure that i got into recovery IMMEDIATELY after odin this time; did a factory reset and cache wipe. hit power off. powered the phone back on. stuck on samsung logo. this does not seem to be going anywhere.
i didnt know anything about vbmeta before, starting to google it now.

DaReDeViL said:
Try to get the vbmeta disabled tar file and place it in Odin's userdata along the other files to flash, disable auto reboot and manually reboot your phone while keeping power+volup pressed which will allow you to wipe data. Reboot and enjoy
Click to expand...
Click to collapse
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....

peterkoarl said:
i.. think i tried exactly this now; i used the vbmeta.tar from https://forum.xda-developers.com/t/howto-flash-a-blank-vbmeta.4136509/ (there are 2 files attached there which are exactly the same, not sure whats going on with that)
in odin, i used BL/CP/CSC from orig rom, the FULL (7gb) magisk patched AP, and the vbmeta.tar in USERDATA
powered off manually, rebooted into recovery, and the first time i got a recovery-android-logo and a text "erasing" for like a second or two. then the device rebooted, and got stuck on samsung logo again.....
Click to expand...
Click to collapse
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use

DaReDeViL said:
Try to reboot to recovery again and do a factory reset.
Btw, find attached the vbmeta disabled tar file I use
Click to expand...
Click to collapse
thanks, tried, no difference
looking closer at your img, it seems to hold keys for the SM-G981B (Galaxy S20).
i *guess* i need the same thing for my model - my research into how this is done has unfortunately so far been unfruitful....

some more info; when unpacking stock AP, i get the following files:
24/01/2021 14:22 19.864.283 boot.img.lz4
24/01/2021 14:22 658.262 dtbo.img.lz4
24/01/2021 14:25 1.130 metadata.img.lz4
24/01/2021 14:22 2.769 misc.bin.lz4
24/01/2021 14:22 45.072.126 recovery.img.lz4
24/01/2021 14:25 6.207.213.323 super.img.lz4
24/01/2021 14:25 734.568.963 userdata.img.lz4
24/01/2021 14:25 3.751 vbmeta.img.lz4
24/01/2021 14:25 2.815 vbmeta_system.img.lz4
24/01/2021 14:22 12.136.709 vendor_boot.img.lz4
is it possible that this vendor_boot.img is interfering with magisk?
do i need to touch vbmeta_system somehow?
are any of these "new", as in, magisk cannot handle that stuff (yet)?

Try following this guide for the S20 series as it should be the same theoretically. I'm gonna try it as soon as I get my s21 ultra

I have a SOFT BRICK on my A605FN (a6plte)

So i tried to root my phone and it happend. After i flashed A10 to phone (again) because my system stuck on bootloop after trying to again flash root. I booted to the system. The normal welcome screen appear, instead of complete it, i decided to go to the recovery and wipe phone again. I dont know why i did it, but i did and now the phone is stuck on bootloop. I tried many things but when i try to even flash system again without root, it stucks on logo. One boot takes time about 2,3 minutes, at the end almost black screen appears (almost because its little shining, it looks like LCD black) for 3sec then everything goes again until battery drain out. From this i can normally boot to any custom or stock recovery. It happend like 3weeks ago and phone is still on bootloop. Please help. Im on TWRP 3.2.3-1_ashyx and i cant find any newer for this phone model, there isnt any orangefox recovery too. I dont know what to do, i tried everything i can like ADB, no success, odin, no success, apps that repair system, also no success. I dont know Im a moron or something but if you can help, tell me everything step by step. Im on bootloader 8.
here is the TWRP i use

Download and flash latest stock firmware for your country via Odin:
Download Samsung Galaxy A6+ SM-A605F firmware
Download the latest Samsung firmware for Galaxy A6+ with model code SM-A605F. Check out our free download or super fast premium options.
www.sammobile.com
Then use this TWRP version for easy flashing custom roms or Magisk (root):
[RECOVERY][UNOFFICAL][LINK FIXED] TWRP 3.5.0 for Samsung Galaxy A6+ 2018
Team Win Recovery Project 3.5.0 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...
forum.xda-developers.com
However you don't need TWRP if you need only root. Instructions here:
Installation
The Magic Mask for Android
topjohnwu.github.io

When i flash latest stock rom im still in bootloop, I also have problem with flashing that TWRP because odin just errors with Complete (write) operation Failed. Re-flashing system doesnt work. I tried everything, even re-partition. I cant use ADB, also I cant do TOTAL re-install of system because my TWRP is too old and i cant delete Vendor partition, only from TWRP 3.4.0 or higher i can do that, also that old TWRP is buggy,

MDN2137 said:
When i flash latest stock rom im still in bootloop
Click to expand...
Click to collapse
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?

nqnxev said:
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
Click to expand...
Click to collapse
Im not that stupid . I putted AP fle in AP slot like everything else, i also used CSC not Home CSC.

nqnxev said:
How did you do that? Just putted AP, BL, CP and CSC (not HOME_CSC) in Odin and flashed?
Click to expand...
Click to collapse
Im 100% sure i putted everything in right slot

If you have working properly TWRP at the moment, then just flash newer version TWRP from current TWRP (get IMG file and flash as "Recovery" (choose "Recovery" partition for flashing) and reboot).
MDN2137 said:
and i cant delete Vendor partition
Click to expand...
Click to collapse
Why would you do that? Don't mess with partitions ifself without reason. Just try to update TWRP and then wipe partitions: cache, dalvik, data. You can then try also flashing GSI. Follow instructions from this thread. Maybe it will help.

well... the phone is still stuck on bootloop, but i updated the TWRP thanks to you, but before i had to wipe several partitions to do that, because without that i had error with that SEANDROID bla bla bla, it just means i propably installed wrong recovery or system. I dont know what to do i tried everything i know and Im out of ideas. Please help, this phone is trying to kill me, i want to throw this phone from scycraper and i think this is the best idea.

I think that phone is bricked really hard, like a real brick, but maybe there is still some chance.

The same situation after flashing GSI? Also bootloop?

I dont know how to flash GSI on latest Android10 update

MDN2137 said:
I dont know how to flash GSI on latest Android10 update
Click to expand...
Click to collapse
Instructions here.

Well...... it worked! Thanks.