Cannot flash a magisk boot onto tab s6 lite. Already flashed Lineage and recovery. - Samsung Galaxy Tab S6 Lite Questions & Answers

I would like to root my Tab S6 lite WiFi using Magisk.
I already installed Lineage 18.1 and its recovery, since TWRP is no more for this tablet.
I then copied boot.img from lineage zip to the tablet and created a magisk boot.
This I then wanted to flash using fastboot flash boot file.
Fastboot devices reports the tablet in fastboot mode.
But I cannot get the fastboot to flash. fastboot reports an error "target didn't report max-download-size" before sending the file and then does nothing.
The new boot does not get flashed.
I already tried a different USB cable (using the original and a 3rd party), but the same.
I tried a different laptop with USB2 but that has the same error.
PC restarting does not help either.
Could you help me flash the boot?

I now deleted the stock boot.img from the lineage zip and replaced it with the magisk boot.
I then went to recovery and flashed the ROM again with checksum error of course.
Now I have Magisk installed.

Fastboot is not supported in this device.

Related

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

Accidentally flashed twrp into boot partitions... help!

So I let the latest OOS open beta 8 auto install via OTA. After the reboot, I lost twrp and magisk, so I went back to fastboot and wanted to boot into twrp, but I used the wrong command
Code:
sudo fastboot flash boot twrp-fajita-3.3.0-2.img
The word "flash" should not have been there! So this command overwrote boot_a. So I switched to slot B, and wanted to boot into twrp, but STUPIDLY used the same wrong command again!!
Now I can't seem to boot into system at all, and am stuck at recovery. I've tried a bunch of things, including flashing both boot_a and boot_b with a boot.img extracted from the open beta 7 via SuperR's Kitchen, but I'm still left in this state where if I fastboot boot twrp-fajita-3.3.0-2.img in order to flash the open beta 7 zip, it reboots only to oneplus recovery.
If I fastboot boot twrp-fajita-3.3.0-2.img in order to flash the open beta 7 zip, followed by the twrp zip, and with or without magisk, a reboot brings me back to TWRP, but where it does not ask for my encryption password and hence all my filenames show up as encrypted. Only if I fastboot boot twrp, then it gives me the option to type in my password and successfully decrypts the files.
Any idea how I can fix this?
SOLUTION: I think it was because I was trying to flash back open beta 7 after installing open beta 8 OTA. So after I found the download zip for open beta 8, I extracted the boot.img, flashed the boot.img to boot, flashed open beta 8 zip, and I could reboot and get into system. Phew!
Try flashing the latest Stock ROM via TWRP.
Yeah, like he said. Download the OB8 and flash it via TWRP.

Tried updating TWRP now can't get into recovery.

Bear with me, I had an older version and maybe just my method but I had messed up the custom rom I had on so I went to put a new one on and wanted to update TWRP at same time.
I installed the new custom rom, then installed TWRP and correctly clicked recovery.
However now recovery just goes into fastboot mode, I went into the dev settings and put usb debugging on, authorised it but each time it goes into fastboot it is not recognised and when I reboot into phone usb debugging has been disabled.
So now I can't get into recovery to flash a new rom, nor can I put twrp on by fastboot.
Stuck at what to do
Using Havoc OS
Try booting into the recovery from fastboot
Boot into fastboot and type
Fastboot boot recovery.img (recovery.img is the file saved on your pc)

After rooting android 10 with Magisk it removes installed TWRP

I flashed stock android 10 river (from lolinet).
I wish to root it and have twrp recovery.
But rooting with magisk removes the installed twrp recovery!
What I did:
—Downloaded both the img and the zip from https://dl.twrp.me/river/
—Copied the zip to the phone's external sdcard.
—I put the phone into bootloader mode (volume down and power button)
—Connected the phone to windows PC.
—Open a command window (in GooglePlatformTools folder) and ran the following command:
fastboot boot twrp.img (This temporarily booted TWRP on the phone).
—in TWRP. I installed the twrp zip
It successfully installed TWRP on boot partition of both slots.
So now I have twrp installed and working.
I now needed to root the phone
So I installed Magisk 23 on the phone
I extracted the boot.img from the android 10 river rom that I initially flashed to the phone and patched it with Magisk.
I moved the patched boot.img file to the pc and flashed it to the phone.
My problem:
flashing the patched boot.img rooted the phone, but when I go to recovery I get the phone recovery not twrp.
What am I doing wrong? I've repeated the process and get the same result.
How do I get a rooted phone and TWRP recovery.
Thanks for any help.
maybeme2 said:
I flashed stock android 10 river (from lolinet).
I wish to root it and have twrp recovery.
But rooting with magisk removes the installed twrp recovery!
What I did:
—Downloaded both the img and the zip from https://dl.twrp.me/river/
—Copied the zip to the phone's external sdcard.
—I put the phone into bootloader mode (volume down and power button)
—Connected the phone to windows PC.
—Open a command window (in GooglePlatformTools folder) and ran the following command:
fastboot boot twrp.img (This temporarily booted TWRP on the phone).
—in TWRP. I installed the twrp zip
It successfully installed TWRP on boot partition of both slots.
So now I have twrp installed and working.
I now needed to root the phone
So I installed Magisk 23 on the phone
I extracted the boot.img from the android 10 river rom that I initially flashed to the phone and patched it with Magisk.
I moved the patched boot.img file to the pc and flashed it to the phone.
My problem:
flashing the patched boot.img rooted the phone, but when I go to recovery I get the phone recovery not twrp.
What am I doing wrong? I've repeated the process and get the same result.
How do I get a rooted phone and TWRP recovery.
Thanks for any help.
Click to expand...
Click to collapse
One possibilty I thought of: I never flashed magisk zip through twrp. Maybe that is my problem.
I installed magisk manager and did everything through it. Where do I find the magisk zip.to install through twrp?
rename the apk to zip and flash via twrp
Cronoss said:
rename the apk to zip and flash via twrp
Click to expand...
Click to collapse
That is what I finally discovered was the right thing to do.
All is well now.

About to give up on flashing recovery to OOS 11.1.1.1

I tried "fastboot boot" almost all of KizuYuna's .imgs, tried fastboot boot the lineagerecovery.img. All I get is the fastboot logo and the phone just restarts into OOS... TWRP is same.
About to MSM downgrade to OOS 10 to get recovery working like I did before. Thought it would be better to flash a rom from OOS 11 to get better firmware compatibility but just wont work.
Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.
bpambrose said:
Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.
Click to expand...
Click to collapse
So you are saying MSM to 10 and then flash official 11.1.1.1 or fastboot flash boot magisk_patched-23000_11.1.1.1 (this is a full 11.1.11.1 OS flash? No need to use twrp from 10?)
Thanks
So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.
Fenopy said:
So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.
Click to expand...
Click to collapse
So you had to go through all the trouble because you had a bootloop issue when OTA updating to 11? I already got to 11 but am trying to fastboot boot a recovery because I want to flash a custom ROM... When I fastboot boot TWRP.img or LOS Recovery .img it just shows fastboot logo and restarts the phone with no recovery shown..

Categories

Resources