Rooted, unlocked but stuck...can't install a Recovery! - Samsung Galaxy Tab S6 Lite Questions & Answers

Hi, pulling my hair out here, I have flash and reflashed with odin, magistik, just can't seem to get a custom recovery installed for my Galaxy Tab S6 Lite wifi sm-p610 with android 13. (using stock android 13 firmware)
I tried Twrp, lineage. recoverys, both result in boot loop. Do I need to flash a android 10 to accomplish a recovery install, can someone help?

Hi, had the same problem. I followed this guide: https://wiki.lineageos.org/devices/gta4xlwifi/
But as you i got in a boot loop and the fix is to install first the correct firmware (LINEAGE 19 -> ANDROID 12), you can use odin to do that. After this you can flash the lineage 19 recovery and then install the ROM. Be sure to enter in recovery mod immediately after flashed the recovery.

Related

[Q] Unable to install TWRP Recovery after CM12 YNG1TAS1K0 update

Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
acemccloud1 said:
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
Click to expand...
Click to collapse
Same problem dude...
I too got same problem, but now solved. Use all in one tool box by gohel.vishal first unlock bootloader, 2] resart phone 3] now enable usb debugging 4] again use toolbox to fash custom recovery 5] after flashing remove battery and restart into recovery, thats all.
Issue fixed using this thread:- http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847
(Remember to disable "Update CM recovery" option in Developer Options)
remove battery after install recovery before restarting phone

Phones boots into recovery every single time after flashing. [SM-A500F]

Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Jacker31 said:
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Click to expand...
Click to collapse
Hello:
- First, TWRP to use and it is the only one that does not give me trouble installing ROMs Marshmallow (as Resurrection Remix, AICP or CM13) is the v3.0.0.1 of mygalaxya (download here). Steps for install: here
- Second, if you are in ROM Stock 5.0.2 and just want TWRP to install Xposed, I recommend using the v2.8.7 (here) does not give problems at all, although no use to install ROMs Marshmallow.
- Third, it is not necessary deodex the ROM to install Xposed, since there is a modified version of Xposed that works perfectly both as Deodex and Odex ROMs, you can download it from here.
If after using TWRP 3.0.0.1 (or higher) and enters Recovery restart always, I recommend the v2.8.7 flash on it for a normal boot.
I hope the information is usefull. :good:

cant root my op2

Presently i'm running on stock oos 3.1
1.Unlocked bootloader
2.flashed hybrid recovery
3.flashing super.su-2.78.
After flashing it stucks at boot logo...it doesnt show up...how to root???
facing same problem here
Since OS 3.** you need to flash SuperSU when systemless...If you have no idea how, simply flash the below SuperSU and you'll be root..Cheers !
https://www.androidfilehost.com/?fid=24591000424961865
Edit: No need to reinstall your OS, simply flash it on top of the one that's boot looping on TWRP or Hybrid recoveries
hemanth kumar said:
Presently i'm running on stock oos 3.1
1.Unlocked bootloader
2.flashed hybrid recovery
3.flashing super.su-2.78.
After flashing it stucks at boot logo...it doesnt show up...how to root???
Click to expand...
Click to collapse
Since OS 3.** you need to flash SuperSU when systemless...If you have no idea how, simply flash the below SuperSU and you'll be root..Cheers !
https://www.androidfilehost.com/?fid=24591000424961865
Edit: No need to reinstall your OS, simply flash it on top of the one that's boot looping on TWRP or Hybrid recoveries

Yoga Tab 2 Pro - 1380F --> Magisk possible?

Hi Everybody,
did one of you manage to get Magisk running on your 1380F?
I'm on latest Firmware / ROM and rooted by temporary booting CWM and flashing SuperSU, like in the tutorials over here.
If I flash Magisk, no matter if pre-rooted or not, via Magisk Manager or CWM --> The tablet recognises that the boot image was manipulated, doesn't boot anymore.
It jumps directly to the stock recovery...
Any ideas?
Thanks in Advance,
McK
How did you go about flashing via the temp cwm? I'm trying to flash the stock from but cant find a recovery for this lenovo 1380F. I tried using the tetherd temp cwm and selected T3, it appears to run fine with no errors but I don't see the recovery menu on the device

gts4lv: magisk rooted twrp + stock works, but lineage19/20 boot loops

Hi,
Disclaimer:
First post here, sorry if opening a thread here instead of replying to, e.g.
https://forum.xda-developers.com/t/rom-official-gts4lv-gts4lvwifi-13-lineageos-20.4536203/
is not correct. I've read the forum rules, and searched for similiar issues with that device, but at a glance did not find something alike.
Appologies in advance if I did a mistake or overlooked something, I'll try to learn and do better next time.
Device: Samsung Galaxy Tab S5e LTE, SM-T725, gts4lv
Bootloader: unlocked
Aim: magisk rooted twrp in recovery, lineage20
Following these instructions, I'm able to root the latest stock rom with magisk, flash that via odin, and get a magisk-patched twrp recovery:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
https://twrp.me/samsung/samsunggalaxytabs5elte.html
(Details:
Get the current stock via frija, extract AP, patch via magisk on device, adb pull to host, flash stock with odin (magisk'ed AP,BL,CP,CSC).
Reboot device into stock, finish magisk app install. Reboot once. Device rooted. Installed TWRP app, granted root permissions to it, download twrp for device, patched image with magisk, flashed that to recovery via twrp app.
Sucessfully tested twrp, looks good.)
Trouble begins when I install lineage via twrp adb sideload, following
https://wiki.lineageos.org/devices/gts4lv/install#installing-lineageos-from-recovery
with the difference using twrp instead of lineage recovery.
Coming from the magisk-in-twrp-recovery rooted stock, I did a factory reset (wipe cache/dalvik cache/data), and twrp adb sideloaded the latest lineage20 for that device.
Console command outputs look good, no obvious errors. After the initial reboot, I got a recovery boot loop.
Going back to square one, reverting to magisk rooted stock using odin.
Then, I also tried sideloading lineage19, same result.
For the record: I initally started the lineage installation also flashing NikGApps or MindTheGApps (arm64), and the fdroid priviliged extension afterwards, but got the boot loop there.
I wiped system/data/cache/dalvik, went back to magisk-in-twrp-recovery rooted stock as described above and then tried with just lineage, but still a bootloop.
Do I maybe have to once again flash the AP with the VBMeta.tar via odin prior to moving from the rooted stock to lineage?
I am a bit hesitant to do so, because
https://topjohnwu.github.io/Magisk/install.html#important-notes says
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
Not sure if the VBMeta step is only required to initally unlock the device.
I am thankful for any advice how to narrow down the issue.
Best regards
I tried to install lineage+twrp+magisk/root at the same time without great result as well.
I was able to install lineage and twrp, but when I was there it was impossible for me to "activate" Magisk
So I switched back to custom rom + twrp + magisk/root. All good, but that's not what I was searching for.
I installed Lineage from Odin, then flashed twrp. https://wiki.lineageos.org/devices/gts4lv/install.
Try this guide, if you'll have success please let me know how you did it.
See my post here https://forum.xda-developers.com/t/rom-13-official-crdroid-9-4.4541563/post-88458655
Issue is with patching twrp with magisk it seems. Use either stock Lineage recovery or follow instructions I posted.

Categories

Resources