hi,
i have and twrp working and root with magisk (EU rom). i used titanium backup to freeze the security app and after restart i got soft brick.
please help, twrp is stiil working.
eliran669 said:
hi,
i have and twrp working and root with magisk (EU rom). i used titanium backup to freeze the security app and after restart i got soft brick.
please help, twrp is stiil working.
Click to expand...
Click to collapse
Flash recovery rom through recovery.
eliran669 said:
hi,
i have and twrp working and root with magisk (EU rom). i used titanium backup to freeze the security app and after restart i got soft brick.
please help, twrp is stiil working.
Click to expand...
Click to collapse
You should not freeze a system app like that especially MIUI's security app.
Fix:
Flash the same ROM again in TWRP or Flash the Recovery ROM.
Related
Hi,
i have searched everywhere for an answer's to a few issues i have with rooting and restoring my phone.
i need help with a few thing's and i will divide them to section's:
TWRP ISSUE
i have rooted my phone with cf-auto root and my phone have root now.
i have also flashed TWRP recovery with FLASHIFY.
this processes went very well and smooth.
now i can boot into TWRP and make Backups.
the issue begins when i want to restore from backup.
i'm trying to restore my phone from a TWRP backup i made yesterday and after the recovery has finished
my phone starts to boot loops with samsung logo.
i have tried to do a fresh install of the original stock rom, flash the auto root then installed TWRP. i have ran the process again a few time's with no luck.
can someone please help me solve this issue?
TITANIUM BACKUP ISSUE
i have backed up my apps with TITANIUM BACKUP PRO after rooting the device.
i have tried to restore the wi-fi access point to earlier stage.
i went to see the wpa_supplicant.conf file and all access points are there
after reboot all access points are gone from the file.
can someone please help me solve this issue?
BOOTLOADER QUESTION
my previous phone was htc one m7.
when i wanted to replace the recovery or to check my devices details i ran a fastboot command's.
now all i can see is download mode and i can't ran fastboot command's from there.
there is a way to use fastboot command's on the galaxy?
is the download mod is the bootloader?
(sorry for that i'm newbie to samsung device's never had one before).
can you please help me out with the issue's above?
INFO FOR MY DEVICE:
Galaxy S6 Edge
Model: SM-G925F
Baseband: G925FXXU1AOCZ
Build: G925FXXU1AOD4 ISRAEL
thanks in advance,
Gilad
I have some problem with restore with twrp ;-( maybe problem is in kernel selinux ? ;-(
koko115 said:
I have some problem with restore with twrp ;-( maybe problem is in kernel selinux ? ;-(
Click to expand...
Click to collapse
gilad29 said:
Hi,
i have searched everywhere for an answer's to a few issues i have with rooting and restoring my phone.
i need help with a few thing's and i will divide them to section's:
TWRP ISSUE
i have rooted my phone with cf-auto root and my phone have root now.
i have also flashed TWRP recovery with FLASHIFY.
this processes went very well and smooth.
now i can boot into TWRP and make Backups.
the issue begins when i want to restore from backup.
i'm trying to restore my phone from a TWRP backup i made yesterday and after the recovery has finished
my phone starts to boot loops with samsung logo.
i have tried to do a fresh install of the original stock rom, flash the auto root then installed TWRP. i have ran the process again a few time's with no luck.
can someone please help me solve this issue?
TITANIUM BACKUP ISSUE
i have backed up my apps with TITANIUM BACKUP PRO after rooting the device.
i have tried to restore the wi-fi access point to earlier stage.
i went to see the wpa_supplicant.conf file and all access points are there
after reboot all access points are gone from the file.
can someone please help me solve this issue?
BOOTLOADER QUESTION
my previous phone was htc one m7.
when i wanted to replace the recovery or to check my devices details i ran a fastboot command's.
now all i can see is download mode and i can't ran fastboot command's from there.
there is a way to use fastboot command's on the galaxy?
is the download mod is the bootloader?
(sorry for that i'm newbie to samsung device's never had one before).
can you please help me out with the issue's above?
INFO FOR MY DEVICE:
Galaxy S6 Edge
Model: SM-G925F
Baseband: G925FXXU1AOCZ
Build: G925FXXU1AOD4 ISRAEL
thanks in advance,
Gilad
Click to expand...
Click to collapse
twrp restore option on the 925f edge is broken try chainfires flashfire to backup and restore
thank you for your kind advice i have tried flashfire and its working great
the TWRP issue is solved.
can someone please help me with the other issues above?
Hi
I am running a CM13 Rom at the moment but want to go back to stock, I need to root it to restore apps via Titanium Backup.
As I already have TWRP installed can I just flash the stock rom via twrp then install SuperSU? or do I need to go back to stock and then create a custom image in the kitchen
mattwilkinson11 said:
Hi
I am running a CM13 Rom at the moment but want to go back to stock, I need to root it to restore apps via Titanium Backup.
As I already have TWRP installed can I just flash the stock rom via twrp then install SuperSU? or do I need to go back to stock and then create a custom image in the kitchen
Click to expand...
Click to collapse
If you have twrp, then flash the rom with it. Then supersu and allow modification to system partition. To keep twrp for future, open file manager in twrp and browse to system. Delete the file "recovery-from-boot.bak", after this your twrp will not be replaced with stock.
The only reason you need to cook custom boot image is to make sure that your twrp is not replaced with stock and at the same time without losing ota due to system modification.
WHen I swipe to install supersu it just reboots immediately and does not install it....
mattwilkinson11 said:
WHen I swipe to install supersu it just reboots immediately and does not install it....
Click to expand...
Click to collapse
Unlock your bootloader, flash twrp again. In mount, mount system and remove the "mount system as read only" check. then flash supersu.
" allow modification to system partition " how can i do this ?
if i install super su after restart will made problem ?
Hello,
I have a honor 8 rooted since like one year but sudenly I cant' login in snapchat.
I heard about 'we cant log in snapchat when the phone is rooted', but I always did and never got problems before. I switxh everydays (i have 2 acount)
So i tried to uninstall phh's superuser then clear all cache, uninstall busybox reboot and verify that my phone is unrooted..(with the checker).
But still i can't login...
I don't have xposed or anything else
I wanted to try the trick with bluestack/titanium backup but it looks like we can't use snapchat with the last bluestack.....
So I don't know what to do now
If you have any ideas
Thanks
remi13014 said:
Hello,
I have a honor 8 rooted since like one year but sudenly I cant' login in snapchat.
I heard about 'we cant log in snapchat when the phone is rooted', but I always did and never got problems before. I switxh everydays (i have 2 acount)
So i tried to uninstall phh's superuser then clear all cache, uninstall busybox reboot and verify that my phone is unrooted..(with the checker).
But still i can't login...
I don't have xposed or anything else
I wanted to try the trick with bluestack/titanium backup but it looks like we can't use snapchat with the last bluestack.....
So I don't know what to do now
If you have any ideas
Thanks
Click to expand...
Click to collapse
Flash a unrooted stock rom... log into snapchat (you can make a full backup of ROM to restore to after) and then root and backup with titanium backup. Then copy titanium files to external sd and then restore the ROM backup and then snap backup
Yea but i haven't a custom rom
I jave b380 stock but maybe the problem is my boot.omg (prepatched pph's user)
Should y try to flash the b380 boot.img stock?
remi13014 said:
Yea but i haven't a custom rom
I jave b380 stock but maybe the problem is my boot.omg (prepatched pph's user)
Should y try to flash the b380 boot.img stock?
Click to expand...
Click to collapse
No. You cannot have xposed or root and many root apps. Not 100% sure but snapchat might even check selinux and safterynet
So flash complete stock ROM. (Official firmware will work) and then do it
I tried the unSU scrript from here https://forum.xda-developers.com/showpost.php?p=63615067
It said it delete phh's user then I flashed my stock boot.img but still can't login in snpachat lol
I also tried to install Magisk ( I heard it can hide root for some apps) but I have loopboot when I install It. So I flashed back my stock boot.img and it's ok
I don't know what snapchat check/detect, I don't have anything root anymore
remi13014 said:
I tried the unSU scrript from here https://forum.xda-developers.com/showpost.php?p=63615067
It said it delete phh's user then I flashed my stock boot.img but still can't login in snpachat lol
I also tried to install Magisk ( I heard it can hide root for some apps) but I have loopboot when I install It. So I flashed back my stock boot.img and it's ok
I don't know what snapchat check/detect, I don't have anything root anymore
Click to expand...
Click to collapse
Only I can tell you, which works for me: Flash complete stock and then login and reroot
Yea I guess I will do that, thinks anyways
I'll take the opportunity to update it to the latest version but I need to backup all
Whats is the best ways to update? I need to downgrade ? Or maybe I will try a custom rom like lineage
remi13014 said:
Yea I guess I will do that, thinks anyways
I'll take the opportunity to update it to the latest version but I need to backup all
Whats is the best ways to update? I need to downgrade ? Or maybe I will try a custom rom like lineage
Click to expand...
Click to collapse
Not familiar with honor devices. I wouldn't know. I'd just flash a rom for stock firmware with twrp
Hello to all !
I was on the stock rom 10.2.2.0 stable. I wanted to do OTA update to new 10.2.3.0. Since my phone is with unlocked bootloader and rooted with Magisk I unistalled Magisk before new update. After Magisk uninstaled phone goes to bootloop. Stuck on yellow Pocophone-unlocked logo.
Before whole procedure I did twrp backup, so I tried to do wipe and than restore but with no sucsess. I can go to twrp recovery through the fastboot. And I can do anything in recovery. Can do advanced wipes, can do(and I did it also) factory reset. Can choose specific restore folder and go through the whole restoring proces fine. But when I restart phone after restoring it can not boot but stuck on yellow Pocophone-unlocked logo.
Is there anything what I can do before I go to MiFlash procedure to flash stock rom ? Also... If I go to MiFlash tool, should I flash 10.2.2.0 stock rom ?
Thanks infront... !
Just flash the magisk-v18.1.zip (or whichever version you were using) from recovery and it'll boot again fine. There's no need to restore any backups.
Or simply boot to twrp then re flash the rom you're using...
Thanks for the replies...
I didn't tried to flash again Magisk. Didn't think about that. Lately last night I did reflash of 10.2.2.0 via MiFlash tool. So I started from new rom. Anyway... I still can't to restore earlier system via TWRP. Do you guys know why ? When I try to restore stuck again in bootloop in Pocophone yellow logo.
visinacgile said:
Hello to all !
I was on the stock rom 10.2.2.0 stable. I wanted to do OTA update to new 10.2.3.0. Since my phone is with unlocked bootloader and rooted with Magisk I unistalled Magisk before new update. After Magisk uninstaled phone goes to bootloop. Stuck on yellow Pocophone-unlocked logo.
Before whole procedure I did twrp backup, so I tried to do wipe and than restore but with no sucsess. I can go to twrp recovery through the fastboot. And I can do anything in recovery. Can do advanced wipes, can do(and I did it also) factory reset. Can choose specific restore folder and go through the whole restoring proces fine. But when I restart phone after restoring it can not boot but stuck on yellow Pocophone-unlocked logo.
Is there anything what I can do before I go to MiFlash procedure to flash stock rom ? Also... If I go to MiFlash tool, should I flash 10.2.2.0 stock rom ?
Thanks infront... !
Click to expand...
Click to collapse
Everything seems fine , i suggest you to give extra time like 1 hour or maybe more just plug in charger at night after restoring backup . I didn't see any problem if something else you didn't do . I suggest you to use orange fox it support ota updates .
Maybe some glitches with encryption?
I'm in the same situation, but I haven't updated yet.
Phone is rooted with magisk, but stock recovery is installed.
If I flash magisk-uninstaller via booted TWRP will I have a bootloop?
I'm not really complete sure how to update without flashing the full ROM and have to debloat everything again ...
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
The usual way can mean a lot, but most important, did you use Magisk 25.1?
Cheers
Tom
ne0ns4l4m4nder said:
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
Click to expand...
Click to collapse
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Lughnasadh said:
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Click to expand...
Click to collapse
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
AlkaDragos said:
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
Click to expand...
Click to collapse
In the past it has worked for some but not others. The key is to make sure you haven't made any modifications to any of the partitions. For example, if you are using a custom kernel it won't work unless you flash all the modified images back to stock beforehand.
Also make sure you patch your own boot image so there is a stock boot image backup Magisk can restore.