Help! bootloop after flashing twrp and magisk - Samsung Galaxy S7 Questions and Answers

i made a mistake and forgot about active theft protection (pin on every restart) while i was flasjong twrp and magisk, now phone enters twrp recovery for a second and turns off..i tried with kies but nothing

noniboyba said:
i made a mistake and forgot about active theft protection (pin on every restart) while i was flasjong twrp and magisk, now phone enters twrp recovery for a second and turns off..i tried with kies but nothing
Click to expand...
Click to collapse
Put into download mode and just flash TWRP with Odin, leave Magisk alone until TWRP is successfully installed. You can install Magisk from within TWRP afterwards.

and with twrp in place what do i do? to find and flash fresh system? it would be the best if i could somehow get to pin screen and decrypt data normally..i messed up big

SOLVED
i reinstalled twrp and flashed custom los system

noniboyba said:
i reinstalled twrp and flashed custom los system
Click to expand...
Click to collapse
Is it working now?

cooltt said:
Is it working now?
Click to expand...
Click to collapse
yes!

Related

How do I upgrade TWRP from enchilada to Bluspark?

I currently have official twrp installed and I want to install bluspark twrp so that I can flash pie.
What is the correct way to do this?
When I tried to boot into twrp and flash bluespark the first time I was stuck at a black screen with a blue led on.
Any help would be appreciated.
Thanks,
Chris
Did you delete the twrp folder in internal storage before upgrading to bluspark twrp
Stern52 said:
Did you delete the twrp folder in internal storage before upgrading to bluspark twrp
Click to expand...
Click to collapse
No I didnt. I did not know I had to do that.
Edit.. Got back in the phone with nothing lost.
Still want to upgrade to bluspark twrp.
chriskob said:
I currently have official twrp installed and I want to install bluspark twrp so that I can flash pie.
What is the correct way to do this?
When I tried to boot into twrp and flash bluespark the first time I was stuck at a black screen with a blue led on.
Any help would be appreciated.
Thanks,
Chris
Click to expand...
Click to collapse
Who says bluspark TWRP is needed? I used official TWRP 3.2.3.0 and had no problems. Go to recovery, flash pie, flash official TWRP 3.2.3.0, reboot to recovery, flash Magisk 17.1 (17.2 might work, but I used 17.1 so I can't say if it will or not), and reboot to system. That is what I did. Everything works great, I did not lose any data, and kept root.
Thanks I will give it a shot.
Sent from my ONEPLUS A6003 using Tapatalk
chriskob said:
Edit.. Got back in the phone with nothing lost.
Still want to upgrade to bluspark twrp.
Click to expand...
Click to collapse
how do you get back to original twrp? seems mine also stuck there
Just download the blue_spark_twrp.zip and flash it in your current TWRP, i did that about a week ago and everything is fine.
hertz9511
when you flash Oos rom it auto flashes Oxygen recovery.
nksonfire
when you change twrp you need to clean what is in Twrp Folder or delete it. This way you don't have any conflicts.
Did this today also, went and used fastboot command and got blackscreen and white LED on, heres what to do.
Just put the bluspark twrp.zip on your phone, boot into enchilada TWRP and flash the zip, it installs fine, dont actually need to flash the image.
Vivasanti said:
Did this today also, went and used fastboot command and got blackscreen and white LED on, heres what to do.
Just put the bluspark twrp.zip on your phone, boot into enchilada TWRP and flash the zip, it installs fine, dont actually need to flash the image.
Click to expand...
Click to collapse
That is exactly what I did and ended up with the black screen and blue led on.

Can't factory reset my phone

Hello,
So in the first place I want to let you know, that I'm a total noob at this. (This is my first android phone after years of ios)
My problem is that I wanted to update my system from 9.5.7 to the newest 10.0.1. I was rooted, so I checked a few youtube videos how to update to have root after the process.
So anyway, I followed one of these videos. . There was a strange thing in the beginning too. When I hold the power button and then pressed the recovery mode, instead of twrp, the bootloader load up. So I fastbooted the twrp with my computer and did the thing that way. Now I have my phone on 10.0.1 with no magisk only the manager. If I try to fastboot twrp from computer the phone just stucks at fastboot text. I tried to do factory reset to have a clean system, but when I did it, it reboots and it boots into twrp, but that twrp says 0MB to storage and everything.
Sorry for my incompetence, I hope it is understandable.
The question is, how can I factory reset my phone?
Mondaji said:
Hello,
So in the first place I want to let you know, that I'm a total noob at this. (This is my first android phone after years of ios)
My problem is that I wanted to update my system from 9.5.7 to the newest 10.0.1. I was rooted, so I checked a few youtube videos how to update to have root after the process.
So anyway, I followed one of these videos. . There was a strange thing in the beginning too. When I hold the power button and then pressed the recovery mode, instead of twrp, the bootloader load up. So I fastbooted the twrp with my computer and did the thing that way. Now I have my phone on 10.0.1 with no magisk only the manager. If I try to fastboot twrp from computer the phone just stucks at fastboot text. I tried to do factory reset to have a clean system, but when I did it, it reboots and it boots into twrp, but that twrp says 0MB to storage and everything.
Sorry for my incompetence, I hope it is understandable.
The question is, how can I factory reset my phone?
Click to expand...
Click to collapse
Switch the slot in twrp then reboot
Then try factory reset.
twinnfamous said:
Switch the slot in twrp then reboot
Then try factory reset.
Click to expand...
Click to collapse
If I switch and reboot it stucks in bootloader :/
Mondaji said:
If I switch and reboot it stucks in bootloader :/
Click to expand...
Click to collapse
Have you got into twrp
twinnfamous said:
Have you got into twrp
Click to expand...
Click to collapse
What do you mean? With fastboot I can't because it stucks on the fastboot logo. If I try a factory reset then it boots into twrp, but that twrp is not very useful, because nothing works.
what version of twrp you have?
immppa said:
what version of twrp you have?
Click to expand...
Click to collapse
3.3.1-4 guacamole
Mondaji said:
3.3.1-4 guacamole
Click to expand...
Click to collapse
You need twrp 3.3.1-70 for Android 10. Also, did you disable all Magisk modules before updating the phone, updating while having modules enabled will cause a bootloop. You should check the forums more often as there are some guides for newbies.
Kaz205 said:
You need twrp 3.3.1-70 for Android 10. Also, did you disable all Magisk modules before updating the phone, updating while having modules enabled will cause a bootloop. You should check the forums more often as there are some guides for newbies.
Click to expand...
Click to collapse
Oh okay! Yes I not only disabled them, but removed them. Actually my phone isn't in bootloop it's working in android10 but cant factory reset. I hope that the twrp version is the cause! Thank you!!
Mondaji said:
3.3.1-4 guacamole
Click to expand...
Click to collapse
Mondaji said:
Oh okay! Yes I not only disabled them, but removed them. Actually my phone isn't in bootloop it's working in android10 but cant factory reset. I hope that the twrp version is the cause! Thank you!!
Click to expand...
Click to collapse
Yeah, twrp 3.3.1-4 doesnt support Android 10. Also np
Just flash all stock firmware with MSM tool

URGENT: disabling magisk made OP6 stuck on bootloader, How to recover from it?

I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.
JerryGoyal said:
I had latest magisk (stable version) installed and tried to disable it from magisk manager->uninstall->restore images.
when i restarted the phone it stuck on bootloader screen.
I tried to got to twrp recovery mode and it's stuck on the flash screen.
Why would magisk manager put a button which is not working at all and bricks the phone? Please guide me what to do.
Click to expand...
Click to collapse
Maybe you did something wrong and this isn't Magisk fault ?
Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data
J0nhy said:
Go to twrp and wipe system and vendor DO NOT REBOOT, flash OOS zip and twrp again, and it shall work,
NOTE: you will NOT lose any files or data
Click to expand...
Click to collapse
too late for me i wiped all data. Thanks though, it shall help future readers.
next time, before wipe, try to flash magisk uninstaller first
Try to flash stock boot image.

Problem with flashing custom ROM (error 255)

Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear
flying_shitnugget said:
Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear
Click to expand...
Click to collapse
change your recovery..
Baim alif said:
change your recovery..
Click to expand...
Click to collapse
Mind elaborating? What do you mean exactly?
flying_shitnugget said:
Mind elaborating? What do you mean exactly?
Click to expand...
Click to collapse
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?
flying_shitnugget said:
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?
Click to expand...
Click to collapse
try to boot recovery with power button and volume up
Baim alif said:
try to boot recovery with power button and volume up
Click to expand...
Click to collapse
yes, that's what i did. i also tried booting into from fastboot and still nothing.
flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
hmmm... try this bro..
https://androidfilehost.com/?fid=6006931924117927913
flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.
celephrn said:
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.
Click to expand...
Click to collapse
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c
flying_shitnugget said:
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c
Click to expand...
Click to collapse
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.
celephrn said:
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.
Click to expand...
Click to collapse
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?
flying_shitnugget said:
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?
Click to expand...
Click to collapse
Could solve the issue, I'd give it a shot!
celephrn said:
Could solve the issue, I'd give it a shot!
Click to expand...
Click to collapse
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)
flying_shitnugget said:
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)
Click to expand...
Click to collapse
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
so i flashed the firmware as you said, now neither orangefox or twrp throw me the error "unable to locate storage device", i cant mount the storage to the pc and cant copy the custom rom stuff as well
celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
UPDATE: i finally ****ing did it. So here are the steps that i took (incase anyone has to go through this **** as well)
1. flash MIUI on mobile device using MiFlash (at least i did this by shorting 2 pins on the back)
2. (VERY IMPORTANT!!!) instantly boot to fastboot using Power button + Volume down. this has to be before android starts setting up the phone
3. flash recovery with the image that celephrn provided in this thread
4.boot to recovery by holding Volume up + Power button
5. install the miui update that celephrn provided in this thread
6. reboot to recovery
7. install orange recovery zip that celephrn provided in this thread (phone reboots to recovery)
8. now you can reboot to system (Do NOT (!!!) set the phone up, just let it work its things until you see the MIUI setup screen)
9. Now, finally you can dirty flash your custom rom (and GApps)
10. after flashing the new rom android will throw you alot of errors so you will have to wipe Dalvik/Cache, System, Data and Internal Storage.
11. now you can flash your Rom clean and you're good to go
(huge thanks to celephrn, helped me out after me struggling for a few good weeks with this damn phone)
Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help
Farrellclay said:
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help
Click to expand...
Click to collapse
so far, what have you done

I accidentally bricked my phone

Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Did you try with Miflash?
try with MiFlash. Flash stock rom in fastboot mode
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Thelm76 said:
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Click to expand...
Click to collapse
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
dhaern said:
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
Click to expand...
Click to collapse
Well that the thing I tried when I accidentally replaced my boot partition... And my phone was only booting on twrp or fastboot... also the weird thing I found is that /data/adb didn't exist
But many thanks to you all it works now.
I'll maybe try to make a guide on how to install Magisk on the Xiaomi EU weekly rom, as android 11 is only supported by the canary build. (if I manage to find a way to properly remove defective modules in TWRP :fingers-crossed
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Tecardo said:
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Click to expand...
Click to collapse
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
If you want everything to work you need to format data!!
Thats the point why using android 11 roms is hard, twrp cant decrypt it (until you flash rom with a10 and then a11 because partition is encrypted in a10 style)
Thelm76 said:
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
Click to expand...
Click to collapse
That's easy to fix, you installed Android 11 or? Don't use pin, use gesture. Twrp can't decrypt android 11 pin right now
Thelm76 said:
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Click to expand...
Click to collapse
NO flash only fastboot boot twrp.img

Categories

Resources