s3 mini with a twrp 2.8 that hangs - Galaxy S III Mini Q&A, Help & Troubleshooting

I had cm12.1 on it and only wanted to clear settings in android.
It had to reboot and stuck at twrp begin screen that keeps flashing.
Only odin works now and tried installing another twrp and cwm too, all succesfull but still that twrp boot logo flashing even when cwm installed.
Normally i can manage but have no idea now. If recovery worked it was fine but just thru odin seems that twrp is write potected almost.
Any clues someone
rebooted manually also, uncheckedauto reboot box after flashing twrp new rom
nothing, still stuck

Related

(Xiaomi Mi5) TWRP not loading and stuck in bootloop

Device:
Xiaomi Mi 5 32gb (Not pro)
Rom: Cyanogenmod 13
After flashing CM, my phone was stuck in a bootloop. So I decided to do the standard wipe in TWRP, and then reflash CM. My phone is still stuck in the bootloop, and now TWRP won't load. I tried flashing a newer version of TWRP 3.0.2-1, but booting into recovery still gives me the same "loading page". What should I do?
Also, I made the noob mistake of making no backups.
Edit: TWRP is now loading, but I'm still stuck with CM bootloop.
TWRP 3.0.2.0 works fine for me. I also had problems with 3.0.2.1 no touch input possible
How did you get out of the TWRP boot loop? I'm in the same situation. Your help would be appreciated.
Sent from my MI 5 using XDA Free mobile app
Edit: I reflashed 3.0.2-0 using fastboot and now it works fine. Looks like Xiaomi.eu ROM automatically installs 3.0.2-1. Reflashing 2-0 can correct it. Somehow the recovery booting takes some time ... Don't panic.
Me too. I have problem with recovery for mi5.
I enter recovery but it said cannot mount data. I cannot install other rom.
Can yoy help me???
i had the same problem with cm13 and trwp 3.0.2.1
to leave the loop just press the on button long time and try to flash to trwp 3.0.2.0 in fastboot.
Over all i just was able to flash the ressurection rom. the cm13 i stoped after 35 minutes of loading.
Ressurection works fine for me.

TWRP 3.1.1-2 doesnt stick on reboot. [Lastest Open Beta]

Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
I had the same problem so I flashed it TWRP again then flashed another ROM and it stuck. I have no idea why it does that either.
chowchillacharlie said:
Hi all.
i previous had TWRP installed and the latest open beta but temporarily went back to stock recovery to fix a dm-verity issue. Now, whenever i fast boot flash TWRP it doesn't stick. every time it boot into the OS it seems to revert to stock recovery.
after doing multiple flashes only 2 of them actually asked me if i wanted to change the read write permissions, the other times it just booted into TWRP without a promt.
any suggestions?
on a side note, if i was to get it to boot into TWRP then wipe and install Paranoid Android might that get it to stick?
Thankyou.
Click to expand...
Click to collapse
Flash SuperSU or magisk before booting to system...and it Will stick...

HELP!!!

I was rooting a device for the first time, a new tablet SM-T385i. I got twrp and installed it using Odin(AP). From there I could boot into twrp recovery. I put the Supersu file into my downloads folder and booted fro the first time into twrp. I couldnt find any of the file folders in the install section so I went to mount and checked system. Still nothing. I tried to check data but didnt work. i panikced and went to reboot system. It got stuck on the boot screen over and over, showing the samsung logo. then i booted into twrp and wiped the data. Then i reinstalled twrp and i could see my tab on my pc now. Put supersu again and flashed with twrp. iT SAID MIGHT TAKE SOME TIME BUT then it just switched off. i TRIED TO BOOT INTO TWRP BUT FAILED. i went to the downloader again and installed twrp again. still shows the boot logo and switches off again. at this point i can go to the downlader and i can see the logo thats all. HELP!!!!!!!!!!!!!!!!
Search your rom/other one (custom OS) and install it via TWRP. After that (when your rom booted normally) - try to install Magisk.
https://forum.xda-developers.com/showthread.php?t=3747480
Sent from Redemi 4X (Resurrection Remix based on OS 7.1.2)

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.

Custom recovery won't open...

My phone name and model is redmi 9c (angelica) variant..i will get straight to the point..i installed an updated version of my from 12.0.22 to 12.5.4.0 through orange fox recovery...i flashed the recovery by dirty flashing where i just cleared cache and delvik ART or something...then just flashed the whole update zip file through recovery.. everything was working and no problem then i just thought that i would open the custom recovery and it will not open and will kept itself stuck in recovery image or start image of the recovery not open or closing.. nothing worked until i thought i should just factory reset my phone but it won't factory reset itself and will get stuck on that same custom recovery logo and i had manually force it open like i did by press and holding the power button until it vibrated..it opened like normal shut down or restart...so i my phone couldn't be formatted so what i did was to download the fastboot version of my phone that i had installed and took the recovery.img file and flashed it through another phone through bugjaeger app..since i don't have a pc that all i could do and it worked the stock recovery came back and i can wipe my data if i want....but if i installed the custom recovery.img once again it won't work and will get stuck like that time so i want a solution where i can get custom recovery back again...and i gave my full story because someone might be in a similar position as me and by doing something that i did might just help them and also i want a solution to get my custom recovery back plz someone help me.....
you should know that there is a version of Pbrp Vendor R (Miui 12.5), it is the one that works but has encryption, it is unfortunate but if you have MicroSD you will have no problem installing magisk
wulan17 Custom Recovery
My Android Custom Recovery Builds
www.pling.com

Categories

Resources