Install Live Boot!
It came to my attention that live boot still worked during some boot loop issues. So I was able to see what was happening and where. It was very educational actually.
Now this won't work with all boot loops as you need to boot into it in the first place. But it worked for a boot loop related to installing Xposed.
Related
I successfully rooted my phone using this method:
http://forum.xda-developers.com/showthread.php?t=2130276
Then I tried the following method to modify multi-window on the phone:
http://www.andromods.com/tips-trick/verizon-galaxy-note-2-adding-all-apps-to-multi-window-bar.html
And ran into this problem on this step:
4. Copy and replace “FlashBarService.odex” to “/system/app” folder, as well as “services.odex” to “/system/framework” folder. If you have difficulty to replace services.odex, reboot your device. In case you experiencing bootloop after replacing services.odex, then you need to pull out and reinsert the battery, if the bootloops remains, just flash the root image with ODIN to fix it.
PROBLEM: THE PHONE FROZE. THEN WHEN I REMOVED AND RE-INSTALLED THE BATTERY AND TURNED IT ON, IT LOADS UNTIL THE 4GLTE SCREEN AND REMAINS THERE INDEFINITELY.
- I did what it directs to do with the battery but it didn't work.
- I don't know what it means to "flash the root image with ODIN"
I've tried this to fix it:
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
and I believe maybe another thing with odin. Odin usually fails, maybe it's just my USB drive. But i have no idea what to do, or what to even look up to learn how to fix it because I don't know what my problem is called.
Can anybody help me by giving me a method to use or steps to follow or some information?
Try this
http://forum.xda-developers.com/showthread.php?t=2040264
It is called a boot loop by the way
God bless the American people.
barrackOBAMA said:
It is called a boot loop by the way
Click to expand...
Click to collapse
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Milimbar said:
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Click to expand...
Click to collapse
That's right, you understand. and perhaps I just don't know what it means but, I don't think it "freezes" on the 4GLTE screen, it loads until that screen and then continues to be animate, rings appearing and disappearing, loading indefinitely. I don't know if that's anything different, but just in case that clarifies anything.
and I tried http://forum.xda-developers.com/show....php?t=2040264 but to no avail. it always fails @ or immediately after the RECOVERY step.
Any ideas?
Interesting thing happened today which has basically put my phone in a death spiral state. The battery died and after charging it a while I went to power it back on and found it in a boot loop state. I can get into the bootloader, but from there if I select recovery it reboots and the white bar on the right side of the screen fails to fill up, then the phone reboots. I've tried flashing two different versions of TWRP from the bootloader and it still exhibits the same issue.
HBOOT 1.12.1111
RADIO 1.12.11.1210
S-OFF
I was running CM10.1 without much issue until the power issue.
Any thoughts?
Thanks to Zanzibar for helping me work through this on IRC. Eventually the steps outlined here: http://forum.xda-developers.com/showthread.php?t=2338391&highlight=boot+loop did the trick.
fastboot erase cache
fastboot reboot
The device started booting but hung on the CM logo for far too long. I hard rebooted and installed an updated version of TWRP and then wiped and flashed the ROM over again. More updates to follow.
Well the device worked for the night but when I rebooted it this morning it immediately began the boot loop situation again. I RUU'd once and it got stuck in another boot loop. I got it to boot after hard powering down and it loaded the factory ROM. I rebooted back to the bootloader and flashed TWRP 2.5.0.0 and tried to reboot. Another boot loop. Hard power cycling didn't solve it either, so I pushed the RUU for a second time. Now the device refuses to boot into anything other than the boot loader -- the initial issue from this post -- and no amount of hard power cycling makes a difference.
The phone is currently showing as LOCKED in the boot loader so I dropped it off at the Sprint store to see if they could find anything physically wrong etc. More updates as they are discovered in the hopes that if someone else ever experiences this, they have something to reference.
Thanks for posting. Did you solve the problem? I think I'm having something similar.
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.
Hi all
My WF Swift (which has CM-13 on it) is stuck in a boot loop; keeps going to the TWRP 2.8 recovery screen even when I use TWRP to reboot the handset for normal startup. I've seen the Boot Loop guide (https://forum.xda-developers.com/showthread.php?t=2426426) which is very useful however if I follow it I will end up wiping the data on the phone which I still need.
My question is, before I follow the Boot Loop guide (steps 1-3), how do I grab all the data of the phone?
Thank you in advance.
QS
EDIT: I do know *nix, and have adb ready. If you have concise instructions that would be great! The phone should already trust my machine so that shouldn't be an issue.
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.