Database Users

Phone won't boot after flashing the SuperSU - SOLVED

Hi!
EDIT: Never mind, problem solved. Sorry.
I have finally decided to root my G900F (6.0.1). I flashed TWRP through Odin without problems, booted to TWRP to make it permanent, booted normally to check that all is well. After that I made a full backup in TWRP and flashed the BETA-SuperSU-v2.49.zip. After that, my phone no longer boots (hangs on the Galaxy S5 screen with a blue indicator LED).
I can still boot to TWRP.
How can I fix my phone? Please help. What did I do wrong?
I did try wiping the cache partition but nothing else.
Hopefully the solution does not require a full wipe.
EDIT: I see what I did wrong. I have accidentally flashed an old SuperSU.
Can I use a backup I made with a TWRP?
EDIT2: Luckily the restore did work! Will try to flash a more recent SuperSU.

flash it again but with latest version of supersu. It will work

Spawnknight said:
flash it again but with latest version of supersu. It will work
Click to expand...
Click to collapse
Yup, it did work beautifully. Lucky for me that I remembered to make a backup before rooting.

TWRP or Other issue?

I"m having issue with flashing roms, kernels and restoring on my device and i'm not sure if its cause a process was done incorrect and/or a TWRP.
I have a 2017U. Bootloader is unlocked, TWRP 3.1.0, and currently on stock B19 (no root, via TWRP with Draken's Stock system).
Here are the issues I"m facing:
1. Unable to Restore backup. I've made a backup and selected Boot, System and data. Also selected "compression". Restore shows complete, but device freeze on boot screen (the one says hit vol for more options).
2. Issue flashing kernel. I tried flashing Beastmode (a couple of previous versions up to the most currect R45). I keeps booting back into Recovery. I then tried flashing the stock kernel from Freeza and it still boots into recovery.
3. Flashing Roms. This one is possibly a rom issue, but just wanted to throw it out there any ways in case it's not. Flashed Bad Boys rom. Works fine when installing with SU or Magik, but doesn't boot if it select "no root"...
Any help/advice is appreciated.

You either need to flash supersu, or no-dmverity to patch the kernel to bypass this security feature.

3.1 is also not ready according to twrp thread.
Sent from my ZTE A2017U using Tapatalk

Thanks guys.
Just having a difficult time with TWRP recently. I wasn't able to restore properly on 3.0.4.
Every time i tried to restore, it says i need to uncheck mount system partition read only. Do need to flash the no-dmverity after i restore?

TWRP Loop, again

After reading up and being waived off the Official TWRP I originally used the open source (which I cant find on my phone or desktop) TWRP for my recovery.
I've been playing around with different ROMS on my Oneplus5 and ran into a TWRP loop after restoring from one ROM to another. It was suggested, and I followed the advice, to flash the Official TWRP and no more TWRP loop.
A week or so later, trying to restore from the Resurrection ROM to xXx ROM and I'm back in a TWRP boot loop.
I've tried different wipes before restoring and still looped.
Tried flashing this version of TWRP to recovery https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134 and it was no help.
Any suggestions?

Try flashing no verity op5.zip

I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.

jhs39 said:
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
Click to expand...
Click to collapse
Thanks, it was getting a bit frustrating and before your solutions posted, in the interim I used Method 2 from here:https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727 loading the stock bootloader wiped my device clean (all pics, my files, my TB folder gone) but I was able to load a ROM and boot (I hate Goggle, they can f up just about anything, but that god for their backup/restore, it got me up and running from scratch quickly ). I will give the blu spark a shot and @ se7ensde take a look at your suggestion.
It is a shame that TWRP restore is such a problem, and a random one at that. I have restored from ROM to ROM to compare them without an incident until....

Back to stock Nougat?

I have a Moto X Style XT1572 Indian version. I updated it to stock Nougat 7.0 via OTA when it was rolled out in India. Later in January I unlocked the bootloader and installed unofficial TWRP recovery for flashing custom ROMs. I did take a full backup of stock ROM immediately when I installed the recovery. Since then I'm using custom ROMs built for Nougat modem.
At present, how can I go back to stock Nougat? I did do a full wipe (except internal memory) and tried to restore the stock Nougat backup which I took in January. The backup always gets successfully restored. However, when the phone boots up completely and reaches the language selection screen(the first screen when the phone boots up), the phone reboots and goes into a bootloop just displaying the bootloader unlocked screen. The only option I have then is to flash any custom ROM again and they do work perfectly. So what must be restricting the stock backup to boot? Also, is there any other way to go back to stock Nougat?

anyone, please?

AsquareX said:
anyone, please?
Click to expand...
Click to collapse
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.

jason2678 said:
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.
Click to expand...
Click to collapse
I'll give a try to the fastboot version.

Phone stuck at Decryption unsuccessful :crying:

I am stuck at encryption failed when I flash stock oreo rom. I tried formatting data using twrp and flashed no encryption file as well but nothing works.:crying::crying::crying:
I just want to use the stock oreo rom again with root.
Pls help:crying:

Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.

jl10101 said:
Which ROM did you try and flash / install?
Try upgrading your TWRP to the latest version too.
Click to expand...
Click to collapse
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now

Deadmeat03 said:
I used partition dl mode to flash the stock oreo rom over 7.0 to keep the root. Then i flashed custom kernal for stock 8.0 but it didnt work. I have done the same procedure before and it has worked like a charm. But it keeps on giving the encrytion error when i try it now
Click to expand...
Click to collapse
Odd. If I had to guess anything, it would be that not all the partitions were flashed when going from Nougat to Oreo.
I once flash a Nougat ROM from an Oreo ROM and I had the same encryption issue and lost everything.
That was the last time I would trust myself again and not do a backup.

Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...

Prowler_gr said:
Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track...
Click to expand...
Click to collapse
I tried that as well. With stock recovery is says data is corrupted and doesn't do anything. I think it might be a problem with patched lg up because when i use normal lg up to flash oreo it works. But I cant root then.

I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.

In the same boat as OP
scottyrick said:
I would try changing to 3.2.3-4 TWRP and then trying the procedure again. It seems that the 3.3.0 TWRP does not decrypt properly sometimes.
Click to expand...
Click to collapse
Hi
Looking for a way to keep TWRP and root ... any help appreciated
I've got a US996 with the same issue as the op. I have the latest TWRP 3.3.1-0. The phone was working fine until I upgraded twrp but I might have done a mistake resetting phone outside of twrp.
I can still get back into twrp but I haven't been able to install zip files without getting that decryption unsuccessful message when booting to system.
When getting back into TWRP using hardware buttons sometimes there is a prompt asking "keep system read only?" which I never chose and swipe to allow modification. I think this happens after
I pull the battery after getting the decryption unsuccessful message. There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
...but if my phone is a us996 and is still
unlocked, would it matter if I did select it? Wouldn't I be able to reinstall twrp using adb again on a computer after Oreo is reinstalled?
To do Prowler_gr's suggestion which guide do I follow (sounds like I should do the second option)
"Flash stock recovery from KDZ through patched LGUP & do a factory reset .
After stock recovery completes the wipe do a battery pull, flash TWRP via fastboot, format data, flash Kernel & Magisk & you should be back on track... "
1-[GUIDE][UNBRICK] Patch LGUP to unlock features & unbrick V20 (Variant mismatch fix) to use lgup
or this guide
2-Ultimate guide to unbrick LG V20(Only Variants with .KDZ)[No OS Firmware Update Loop]
Thank you for any guidance on this...

There is a reset system that I could chose under the decryption unsuccessful message but I'm assuming that will make me lose twrp
Click to expand...
Click to collapse
Don't blame me if this goes wrong but I'm pretty much 100% certain that you mush press the rest button. This has happened to me a few times I'm sure. You won't loose twrp. Whatever resetting goes on in the background I don't think it's an actual Factory Reset.
Edit: Just to be clear you taking about a white screen with I think in dark blue or black text ENCRYPTION UNSUCCESSFUL and something like "reset phone" option directly under it, on the upper half of the screen?

Hi ezzony
Yes you are thinking of the right decryption unsuccessful page. I get it when booting to system
after installing Oreo and magisk 19 and having wiped everything (format data too). I will get the exact wording of it tonight
Thanks!

downgrade twrp i has same prob twrp 3.3.1 gives issues

ghet2rockuu said:
downgrade twrp i has same prob twrp 3.3.1 gives issues
Click to expand...
Click to collapse
Hi ghet2rockuu
I downgraded twrp and that got it working Thank You! see also Phoenix591 thread [Recovery][Unofficial for the moment]TWRP 3.3.1-0 : 2019-05-17 #625
Thank You !