Hi, i'm using my s10 with a root for ~2 months.
Today i tried to update magisk.
After the reboot, the phone got stuck on boot loop, cant enter in recovey more because of alert of unlocked bootloader.
You may try to boot into safe mode.
This is what I (a bit casually) did.
This mode disables Magisk modules then phone is getting bit more manageable, you eventually can come to point where you may make changes or at least flash working ROM again.
Related
I'm not an expert in Android, nor am I an expert with computers, just an average joe in the Android world. Since the time I got myself into this community I never stopped learning something small. I was able to root my phone, install custom firmwares, unroot my device, do a NANDroid back up. All of this done with the help I got from an online source. Now, I'm looking forward to do further tweaks in my device's system. It might sound risky, but I'm enticed by how far an android device can be further improved. But before I do any of this, I'd like to know the appropriate steps to do when something goes wrong like what if device ends up on boot loop.
Questions:
1) What is boot loop?
2) What causes boot loop?
3) Is it the same with a bricked phone?
4) Can the phone be recovered from it (boot loop / brick)?
5) What should be done when a phone is on boot loop?
I humbly ask everone to share a bit of your knowledge about this.
Thank you.
1 - Is kinda of obvious. Bootloop is when your device is stuck at some of bootscreens (model screen, Samsung logo screen) and it doesn't boot properly. Even if you remove the battery and insert it again to turn it on, it doesn't turn on.
2 - There are various reasons: incompatible kernel, incompatible rom, edits on build.prop, rom poorly flashed. And, for our device, if you try to reboot into recovery directly and it has CWM installed, it may enter on recovery bootloop.
3 - I''d say it is a "soft bricked phone". If you has access to recovery or download mode, congrats, you can undo the mess. But if you can't, you got a hard brick. So, it will need repairs.
4 - As I said before, if you has access to recovery or download mode, it is possible to recover it.
5 - It depends. First I would undo my last actions. If I don't have success, I would reflash stock rom, it's almost guaranteed.
So, it happened to my phone when I attempted to do a "Recovery Back Up" using "[ROOT] Rashr" app. I had a Recovery Boot Loop, which boots only into Recovery Mode. But it's fixed now. Here's the thread: http://forum.xda-developers.com/grand-quattro/help/s-o-s-device-boots-cwm-t2981980
This is a reference for those who have the same problem.
I know this is a known issue, but the thing is that most solutions i have found regard looking into the phone's settings.
The thing is I can't even boot my phone any more. The moment I get the Galaxy SIII GTI9300 logo the phone simply freezes there forever.
It's been like hours like this. I even tried removing the battery for half an hour and put it back. It just won't boot any more.
I didn't install a custom ROm after rooting, the phone was freshly rooted and didn't got to that step yet.
I rooted the device by using the toolkit http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1703488
which surprisingly worked pretty fast and I was able to confirm that my phoen was rooted by installing a root-only app (Root Uninstaller)
then i got a message asking me to update the SU binary and when i accepted the update the phoen restarted never to boot again.
I didn't even get the chance to get the ClockworkMod yet.
Now I don't even have ClockworkMod's menu at the beginning, i have nothing. only the classic boot mode that allows me to download software via Odin (which always fails no matter what package I try)
please help me, i have no other device than that right now....
Download-Mode
Hello and good morning,
have you tried to boot into download mode ?
It's the same like s3
Take the battery out for a few seconds . put it back in and boot into download mode again and it should work
I had flashed a custom ROM on my phone maybe a few months or a year back. I think I remember trying to reflash it trying to fix some bugs but it ended up getting stuck in a boot loop. I think after several tries it booted into TWRP recovery and I had factory reset it (these details might be a little fuzzy as I tried all of this months ago just never got around to posting this since I needed to focus on schooling) but now when I try to boot it, it just boots to the LG logo screen and gets stuck. I can boot into S/W upgrade mode and I had tried to restore it using the LG support tool but it recognizes it as the latest version and will not reset the phone. So right now I am at a loss and need some help to restore the phone and to hopefully flash it again. Thank you!
Hi guys, i need help.
was using my phone this morning and suddenly it restarted itself.
the phone passed through boot icon and went to "almost" into launcher screen.
my phone is rooted and thought that it might be due to software, hence i flashed stock firmware into it.
so now it is in stock rom and stock recovery.
but the phone still restarts.
it will still pass through the boot icon and since it is fresh installed, it goes to the setup screen, but from the the phone restarts again.
it seems like it restarts everytime it finish boot.
thinking that it might be screen issue, so i go into (stock)recovery mode, i try to navigate around in it by going to wipe phone, install from storage, and the phone doesnt restart.
please advise what might be the cause or issue since i had already flashed stock rom, so i guess rom isnt a problem, and phone doesnt restart when it is in recovery mode...
Hello all, I am having some issues after attempting to root my Razer Phone 2. The root failed but I initially had TWRP installed, and afterwards I tried to flash the factory image. This is where things started getting strange; I flashed the factory image and it seemed to run, but then I got a TWRP screen come up that said it was attempting to uninstall something, but that failed. It then went back to the initial boot screen, and then looped between the boot screen and the TWRP screen a few times after which it just resided on the boot screen. I initially was unable to get the bootloader to come back up on the phone but found it was still running in the background and I could interact with it via my PC. I have tried a few more times to flash the factory image but to no avail. I am still in the loop and I am not sure if there is anything that can be done.