I wanted to root my device, 930F with Oreo installed. I flashed TWRP 3.2.3 with Odin, and had Magisk at my internal storage root directory.
When I restarted the device TWRP was gone, so I flashed it again with Odin and starting TWRP it asked if it could make modifications to be permanent, I allowed the modifications. When I tried installing Magisk, I couldn't find it as my whole internal storage didn't show anything (encryption maybe?)
And then I tried restarting without having done the root but now it just boot loops at the Galaxy logo.
What should I do?
Update:
I copied Magisk to my micro SD and was able to install it with TWRP. After restarting the phone did pass the part where it was boot looping, but it stops at:
----------
"Verification Failed
Unable to restart your device. the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
----------
This is the dm-verity that I have read about? Is there a way to not need a factory reset?
I've seen this thread: https://forum.xda-developers.com/galaxy-s7/help/to-magisk-data-encryption-s7-t3667007
Tried flashing with TWRP the TIMA tweak and verity disabler, but still had the same error.
Anyone have any ideas or should I just clean install the stock firmware back?
Related
Hello there,
I´m stuck in fastboot with the message "Software status: modified" and "This device is corrupt. It can´t be trusted and will not boot." I have entered fastboot, then used temporarily TWRP 3.3.1.0 to flash magisk (root) and now i can´t boot. Stuck in middle between root and stock kind of... what steps are now possible to solve the problem of not booting. Do I have to do go back to stock by putting the ruu.zip on sd card and reflash in download mode or is there any workaround for the software status message. I don´t want to loose my encrypted user data by the full wipe of RUU. I also have to state that my U12+ was on the latest Pie Update (Android 9.0). At the moment I can enter fastboot, download mode and temporarily twrp, however i am not sure if that A/B security structure of the partitions cause that "corrupt" message. Thanks in advance!:good:
Since I ran out of solutions I decided to flash a RUU.zip and went back to stock. If anyone still finds a way to install magisk via temporary twrp on pie and to fix the "corrupt device" security message please leave a step-by-step guide.
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
kaotik123 said:
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
Click to expand...
Click to collapse
Damn it, so I booted into twrp and then flashed latest magisk v23 zip but when it finished it said failed to mount partition in red and now the phone just boots to fastboot mode.. I can get back into twrp.. and all my files are still there in file manager.. but it won't boot into my phone.. only fastboot mode. Any advice?
First, boot into TWRP and delete all Magisk Module files and folders:
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
I had the same and it seems a module was causing fastboot mode. If that doesn't work try downloading and flashing the stock boot image for your OOS version in TWRP (remember to flash TWRP again before reboot). At least then you will have your phone back.
Today i tried to root my samsung galaxy j4+ SM-J415FN i failed. I Flashed TWRP using odin successfully but this is where the problems started. I tried to mount and access partitions to flash rmm lock bypass so i would not get locked out and no verity opt encrypt but i could not access the file. I could not connect to pc using usb. I decided to search on the forum. I cleared cache, dalvik, tried to format and repair partitions but it didn't work. After try to boot to OS i seen "recovery is not seandroid enforcing" error. I decided to flash stock recovery. I was stuck in only boot loop but the error stopped happening. Then i decided to re-flash the entire firmware and now im left with working os but i flashed polish rom but the language is not polish... its fine but how can i flash TWRP correctly without screwing everything up and root? i got every zip i need i think and custom kernel (i read that to root i need to flash custom kernel i didn't flash any zips and it because i could not access files from pc or on partitions (i read in a post on the forum that on android pie i need custom kernel to do rooting)).
So how do i flash it correctly and root without screwing up everything again?
And by the way version of TWRP i used is twrp-3.6.0_9-1-j4primelte.img.tar
The RMM/LG lock did not trigger
Bootloader unlocked
Edit: i found out that i flashed t mobile firmware
Oh yes and screen locks were and are disabled
TWRP showed that data partition size is 0mb
I'm also searching for a stable way to root J415FXXU6.
Tried the old method, but can't use lockscreen on it.
Edit:
Tested this tutorial so far lockscreen and root are stable
Galaxy J4 Plus : TWRP Magisk Root
This blog has move and will not be update again.For new update please follow ▶▶
langithitam.wordpress.com
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.
Hi, I run LineageOS 19.1 on my Vayu. It is obviously unlocked and I have Rooted it with Magisk.
I have put off updating the System but did it just now through the Updater in the Settings. From 20220916 to 20221104.
I ran into a Bootloop and went into Fastboot, installed TWRP with ADB sideload. (Had stock Recovery before)
I then tried to just revert back to 20220916 (which was not so smart). I tried to sideloaded the boot.img, but it showed "failed".
--> Still in Bootloop after Rebooting
Now I am unable to flash any boot.img or boot at all.
I tried to flash something else (Magisk.zip), which worked. I have removed all magisk modules, tried to boot with
magisk --remove-modules.
Does anyone have any Ideas? I don't really want to Reset my Phone, even though I have abundant Backups.
Thank you )
Moving back to old version almost all the times is not possible without full reset, new version contains new scripts and possibly new files, how would you explain this for system?
By flashing old version over new one, you probably messed up your system, might as well just backup your data and start from scratch.