J6 SM-J600FN - Is it possible to install TWRP without boot-loop? - Samsung Galaxy J Questions & Answers

I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.

As far as i know, trying to root stock rom isn't easy. I could be wrong but idk. You can try by:
1. Flashing stock
2. Flashing TWRP
3. Format data
4. Flash DM-Verity and Disable Force-Encrypt then flash magisk.
And i think you can't flash kernels on stock. I could be wrong but idk.

Hey, how did you even install TWRP?
Before I tried installing it my model number was "SM-J600 FN/DS" and now after the install, when I plug it into my pc it says that it's "FN-600G." Whenever I try to boot it in system mode it's stuck in a loop.
I haven't tried flashing the newest firmware yet because I can't even download it for my country.
Sorry, I am a total newbie and can't seem to fix it.

Al-Ameen Adewunmi said:
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
Click to expand...
Click to collapse
Hi Guys,
Did you manage to do this? I was experiencing the same bootloop issue and I think it is the version of Twrp (I was using 3.3.1-0).
I used Odin to flash a lower version 3.2.3 found here after which I flashed this DM Verity + Magisk.
Root Success!

Related

help: my phone keep booting into twrp recvery

hey'
every time i boot my phone it bootloop into recavery
what to do?
mega unbrick guide...
timrock7 said:
mega unbrick guide...
Click to expand...
Click to collapse
but in the guide it's you see nothig but a black screen i have recavery https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
it hapen when i exedantly press the istall update of the ota (i had OxygenOS 4.0 and i perss on the update of 4.0.3)
You should never install an update through the phone's update setting while using a custom recovery. The updates are designed to work with the stock recovery only.
If you can still boot into and use TWRP, use it to flash the full ROM of OOS 4.0.3.
If you can't boot into TWRP, try to see if fastboot works and manually sideload a working ROM in.
Otherwise, you're going to have to use the unbrick guide. Your phone doesn't have to be completely bricked to use it. It simply reverts the phone to a truly factory-fresh state (relocks bootloader, wipes everything, etc. - At least method 2 does anyways).
I got stuck in the same situation some time ago, and in order to solve it I had to flash the stock recovery, let it restart, it tried to update (and failed) and then it booted to system again. Hopefully that way you can avoid installing everything again. Once the device boots you can try to update with the stock recovery and revert to twrp if you want.

Pixel C OTA using Flashfire - stuck on "waiting for fastboot command"

I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.

Stuck in logo after flashing twrp

Hello.
I was trying to complete https://forum.xda-developers.com/xperia-m5/development/kernel-stock-marshmallow-kernel-root-t3453072 this guide to keep all my drm keys. But I got a bit lost in moment when I need to "flash_dk". Then I installed twrp recovery and after it found out how to pass through Dk thing. But after installing twrp phone wont boot into system. I tried to complete all guide and didnt mind about twrp but phone still wont launch into system. Im a bit afraid and dont know what to do. It wont suprise me if its normal way of completing this guide but I've done something wrong. What to do ?
Jeffrrey said:
But after installing twrp phone wont boot into system. I tried to complete all guide and didnt mind about twrp but phone still wont launch into system. Im a bit afraid and dont know what to do. It wont suprise me if its normal way of completing this guide but I've done something wrong. What to do ?
Click to expand...
Click to collapse
Probably you have softbricked your device by flashing TWRP before installing the modified kernel. This triggers DM verity on Marshmellow. DM verity prevents the phone from booting up if you change the system.
You should reinstall the original firmware with xprerifirm trough Flashtool, then proceed with creating the modified Kernel. When that's done flash a Xperia M5 compatible TWRP version from the Xperia M5 forum and make your first Nandroid Backup.
Everlastingman said:
Probably you have softbricked your device by flashing TWRP before installing the modified kernel. This triggers DM verity on Marshmellow. DM verity prevents the phone from booting up if you change the system.
You should reinstall the original firmware with xprerifirm trough Flashtool, then proceed with creating the modified Kernel. When that's done flash a Xperia M5 compatible TWRP version from the Xperia M5 forum and make your first Nandroid Backup.
Click to expand...
Click to collapse
Flashing magisk through adb sideload worked. Thanks for your time, I don't know how to close threat

A70 Bootloop after Magisk flash *not enough posts for Dev*

Hey guys:
FIRST OFF: I don't have enough posts in order to stick this in Dev, SORRY!!!
I have read all related posts and stickies but still can't get this sorted out.
Let's get some background... I'm looking at rooting the phone with Magisk. This did not work directly and I was guided by another "how-to" to do it via TWRP instead.
Flashed the vbmeta and TWRP without issues. Booted into TWRP and tried to flash Magisk, which gave me an error at first. It was an old version so I tried a later version, which flashed "successfully," but after a reboot I'm stuck in a loop that reaches the SAMSUNG Galaxy A70 screen, then reboots to show that the bootloader is unlocked, and again and again and so forth...
What did I do wrong? And is there any way for me to fix the boot loop?
Holding in Volume Up does allow me to boot into TWRP so I don't feel as though the phone is bricked.
Any help will be appreciated, preferably that that gets my phone rooted, but even just getting it back to normal will work for me
Thanks in advance,
ShOrTyNoLeGs
Follow this guide
https://forum.xda-developers.com/ga...root-galaxy-a70-twrp-los-17-1-magisk-t4100655
After flashing magisk using twrp, you should reflash stock recovery, Reboot into it then select reboot system BEFORE 1ST BOOT to prevent bootloop.
Factory reset after flashing magisk in twrp will fix all bootloop.
Or follow the guide in my signature for successful root. But you wouldn't have twrp that way, just stock rooted rom

Bootloop after uninstalling Magisk any solution?

Hi guys i rooted my m30 using magisk for few months ago and i realized i cant use any bank application in my phone and that is really uncovenient. so i decided i want to unroot my phone, i tried to uninstalled the magisk from the application, after the system reboot my phone stuck in bootloop. the only way to escape the bootloop is to install magisk again. can someone help me to unroot my phone without any problem from bootloop? Any replies is appreciated
Bootloop after uninstalling​Experiencing a bootloop after uninstalling Magisk, either through the app or with the apk renamed to uninstall.zip and flashed through recovery, might mean that the boot image hasn't been restored correctly or that dm-verity otherwise triggers.
Try one of the following:
Restore your stock boot image (there's a copy of it stored in /data, named stock_boot_<sha1>.img.gz).
Flash a no-verity zip directly after uninstalling Magisk/restoring your stock boot image.
Dirty flash your ROM/factory image/firmware package.
Clean flash your ROM/factory image/firmware package.
contackcontact said:
Hi guys i rooted my m30 using magisk for few months ago and i realized i cant use any bank application in my phone and that is really uncovenient. so i decided i want to unroot my phone, i tried to uninstalled the magisk from the application, after the system reboot my phone stuck in bootloop. the only way to escape the bootloop is to install magisk again. can someone help me to unroot my phone without any problem from bootloop? Any replies is appreciated
Click to expand...
Click to collapse
Have u rooted ur device running on latest April 2021 patch? I also want to root but stuck....
Btw you can install latest firmware using odin it will solve all prblms

Categories

Resources