SM-G920T on Nougat...won't boot past logo - T-Mobile Samsung Galaxy S6

I'm not sure if I triggered OEM unlock, but the phone wouldn't boot past logo after flashing Magisk, I reflashed the stock but it still won't boot past the logo despite stock binary. Any ideas?

Have you got the stock flash? Backed up existing?

i flashed superSU via TWRP. I have the same problem like yours before then I flashed superSU. it booted up well.

I updated Magisk and it worked. Without logcat, I have no idea what was going on to lag the phone on the bootanim.

Related

absolute cluster**** after attempting to move from 4.5.0 to 5.0

So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0

[SOLVED] BRICKED S7 (G930FD) when going from v14.0 to v15 using updater in Magisk app

I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
ssteward said:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
Click to expand...
Click to collapse
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
Sent from my MI 5 using Tapatalk
ssteward said:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.
I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.
Should I allow TWRP to modify the system by swiping right and try the steps above again?
Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.
The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.
This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?
I would be very grateful if you can suggest a way to repair my phone.
Click to expand...
Click to collapse
Dont flash unpatched boot images using twrp
flash unpatched boot image or v14 boot image(that you made earlier) using pc ODIN/ any other prefered tool. Just flash the boot.img nothing else or you can use fastboot to only flash boot.img, it works 100% all times,after flashing it should boot normal
then make a new patched boot image for v15.3 from magisk app just as you made for v14 and flash using pc,then it should boot normally
many phones seem to show stuck at boot logo after moving from v14 to v15(especially v15.1 and v15.2) and also some some devices with f2fs storage seems working weirdly with audio mods.
teddy0209 said:
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
Click to expand...
Click to collapse
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.
If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
ssteward said:
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.
If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
Click to expand...
Click to collapse
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
Supreme Genius said:
Dont flash unpatched boot images using twrp
Click to expand...
Click to collapse
Sorry, my mistake. I did flash boot.img via Odin. It was the original boot.img file that I fed into Magisk v14.0 so it could create patched_boot.img.tar that originally worked. I'm going to try that again now.
Didgeridoohan said:
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
Click to expand...
Click to collapse
That's good to know, thanks. I do have the full system from sammobile from which I extracted boot.img, so could try that if the 'lighter touch' approaches fail.
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
ssteward said:
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
Click to expand...
Click to collapse
Probably try that... Hope it's not a corrupt boot partition...
Sent from my MI 5 using Tapatalk
ssteward said:
UPDATE:
After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.
Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.
So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.
What next? A dirty flash of the stock rom?
Click to expand...
Click to collapse
did you flash the previous v14 patched boot image again using ODIN? this should work
same boot loop problem prevailed on my s7 active and lenevo k8 and flashing the v14 patched boot image and then making new v15.3 boot image gave a perfectly working magisk, although my redmi 3 was showing same boot loop problem and i have to flash the stock rom ( used twrp to restore nandroid backup but boot loop was not solved )
It seems your lots of permutations and combinations have damaged post_fs config of the kernel so you have only option left is to dirty flash the ROM.
teddy0209 said:
Probably try that... Hope it's not a corrupt boot partition...
Click to expand...
Click to collapse
Sounds ominous. How would I recognise this and fix it?
Supreme Genius said:
did you flash the previous v14 patched boot image again using ODIN? this should work.
Click to expand...
Click to collapse
I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
ssteward said:
Sounds ominous. How would I recognise this and fix it?
I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
Click to expand...
Click to collapse
Then you need to flash the ROM , if you got another device then you can make a patched v15.3 image and flash it
I used another phone to created a patched_boot.img.tar for v15.3 and flashed that with Odin but that gave me a boot loop. Trying this again but flashing no-verity-opt-encrypt-6.0 afterwards allowed me to get to the pulsating Samsung logo. So giving up on this approach, I dirty flashed my stock ROM and this worked but I was left looking at a pulsating Samsung logo for a nerve-racking 5 mins or more.
Thank you everyone for your help. I have my phone booting up again!
Now I need to work out install the latest Magisk successfully. If I try using the patched_boot.img.tar method with v15.3 then I'm back to the pulsating Samsung logo. Again. Using TWRP to flash the v15.3 zip gives the pulsating Samsung logo. I did select 'Preserve AVB 2.0/dm-verity. I also tried again with a clean stock ROM install and flashed the v15.3 zip and no-verity-opt-encrypt-6.0, as suggested by someone who'd successfully installed v15.3. I'm at a bit of a loss.
One clue, TWRP couldn't see the internal SD card data (iow /data). I wasn't able to check this option in the 'Mount' menu in TWRP either. I think this points to /data being encrypted. TWRP could see it yesterday, so perhaps I've inadvertently encrypted this. I was careful to uncheck 'Preserve force encryption' in Magisk Manager. I guess now that I've unbricked my phone, I should start another thread for this magisk install issue but any help or pointers to relevant threads that I may have missed would be great.
Thanks again for all your help.

[SOLVED]TWRP on STOCK?

TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
jhedfors said:
TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
Click to expand...
Click to collapse
I just went back to stock ProjectFI today using fastboot. After initial setup, I went back to fastboot to boot the 3.2.3-1-payton.img, then adb pushed both the twrp-installer-payton-3.2.3-1 and Magisk, installed them both at the same time and rebooted without incident.
EDIT: I used PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Thanks @johnjingle.
Not sure if it was because I had Magisk already installed first that was my issue, but flashing TWRP on a fresh boot image THEN flashing Magisk did the trick.

S10 stuck in bootloader loading screen after trying to flash Magisk to boot partition from the App

So basicly, I updated the magisk app and it said I have an update available.
I was on a custom rom named Blastui rom: https://forum.xda-developers.com/t/...-1-1-odex-v3-45-aroma-like-a-ferrari.4200153/
at the same time, i had twrp installed on recovery.
So i didn't want to earrase that.
Bec. of that i didnt check the "Install to recovery" option in the magisk app and flashed it.
After the flash, i tried rebooting, which failed on the bootloader loading screen.
Then I tried booting into recovery. didn't work.
Then I tried booting into download mode. didn't work either.
it just keeps rebooting in a period of like 5 minutes and then gets stuck on bootloader.
Pls help its my main phone

Stuck in boot loop

Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.

Categories

Resources