A boot loop feels like an emergency because the phone will not stay on. Your hands shake and every forum post seems to shout a different command. The secret is that there is no single magic command that fixes every loop. There is a calm order of commands that rescues most loops without wiping data. Learn that order once and a boot loop stops being a disaster. It becomes a repair job with clear steps.
The emergency order starts outside the system. Recovery mode is your workshop because it runs without the broken system. From recovery you can inspect modules and copy files and disable the last change that broke the boot. The device bridge on a computer extends that workshop with commands that list and rename and pull files. Together they give you eyes and hands inside a phone that will not boot normally.
Practice the order while the phone still works. Learn the button combination for your model and test that recovery opens. Install the device bridge on your computer and confirm the computer sees the phone. That rehearsal takes ten minutes on a healthy phone and it saves an hour of panic on a broken one. The same calm preparation helps when you read about fixing a boot loop without wiping personal files because both guides share the same rescue order.
Reach recovery and confirm the connection
Power the phone fully off first. Hold the power button until the looping stops even if that takes longer than usual. Then hold the button combination for your model until the recovery menu appears. The combination differs by maker so learn yours in advance and write it on a card near your computer. A phone that reaches recovery has a working bootloader and a working recovery image. That fact alone rules out the worst kind of failure.
Connect the cable and run the device check on the computer. The check should list the phone as a recovery device. If the computer sees nothing then change the cable and change the port before you assume the phone is dead. A bad cable has ended more rescue attempts than a bad flash ever did. Confirm the connection before you run any repair command because a blind command on a disconnected phone helps nobody.
Find the last change with one list command
List the root modules from recovery and look at the dates. The most recently changed module is your prime suspect. System updates change the code that modules hook so a module that worked yesterday can break today. List the modules and compare the list with your written change log. The suspect list should be short. A short list means a fast repair and a long list means you have been changing too much without notes.
Disable the suspect by renaming its folder. Renaming is safer than deleting because it preserves the module for later study. Reboot after renaming only that one module. If the phone boots then you have found the culprit and you can decide later whether to update it or remove it. If the phone still loops then restore the name and rename the next suspect. One suspect at a time keeps the evidence clean.
Rescue files before deeper repairs
A phone that reaches recovery can often expose its storage to a computer. Copy the photo folder and the documents folder and the downloads folder before you attempt a system reflash. Verify that the copies open on the computer. A rescue that you never verified is a hope and not a rescue. Once the files are safe you can attempt stronger repairs without the fear that a failure will cost you memories.
adb devices
adb shell ls -lt /data/adb/modules
adb shell mv /data/adb/modules/SuspectModule /data/adb/modules/SuspectModule.off
adb pull /sdcard/DCIM ./rescue-dcim
adb rebootAttribution: the commands above use the standard shell syntax of the platform toolset and the device bridge and they are shown here so you can read every step before you run it on your own device.
Study the list command in the block. The time sorted list puts the newest module at the top so you spot the suspect at once. Replace the placeholder module name with the real folder name from that list. The pull command copies the photo folder into a rescue folder on the computer. Create that folder before you run the command so the copy has a clean destination.
Use the slot switch on A and B devices
Phones with A and B slots keep a fallback system on the inactive slot. A failed update usually leaves the previous system intact on that slot. Recovery or the bootloader can switch the active slot back to the working system. That switch can restore a booting phone in seconds without touching your data. Learn whether your device uses slots and learn the slot command for your model before you need it.
Check the current slot first and note it down. Switch to the other slot and reboot and test. If the other slot boots then the failed update was the problem and your data survived on the shared data partition. If the other slot also loops then the problem lives in shared data or in a module and the module method becomes your main path again. Slot knowledge turns a scary update failure into a two minute recovery.
Common mistakes
The worst mistake is running a factory reset from recovery before trying the module method. A reset wipes the data partition that the module method would have saved. The second mistake is flashing a random firmware file found in a panic search. A wrong region or wrong model file can turn a soft loop into a hard brick. Verify every file against your exact model code before you flash it.
The third mistake is skipping the cable check and the connection check. Owners often declare a phone dead when the real fault is a worn cable or a loose port. Test the cable on another device first. Readers who want the full data saving method should also study fixing a boot loop without wiping personal files because it expands every step in this emergency order.
Frequently asked questions
What if recovery mode will not open?
Try the button combination again with precise timing and a charged battery. Try a different cable and a different power source. If recovery still will not open then the bootloader or the recovery partition may be damaged and a maker repair tool or a specialist becomes the safer path.
How do I know which module is the suspect?
The newest module and the newest updated module and the last system update are the suspects. Check the time sorted list and your change log together. A module that changed just before the loop started is guilty until proven innocent by a successful boot without it.
Can the emergency commands damage my data?
The list and rename and pull commands do not touch user files. They only rename a module folder and copy files to a computer. Avoid delete and format commands in this stressed state because those are the commands that destroy data with a single typo.
Write the rescue steps on paper
Paper beats a phone note during a boot loop because the broken phone cannot display its own rescue note. Write the recovery button combination and the slot commands and the module rename steps on a card and keep that card with your computer cable. A card survives a dead battery and a black screen and a panicked mind. Update the card whenever your module list changes so the suspect list on the card matches the phone in your hand. The automatic snapshot habit in the module that automates a system backup on every reboot pairs with the card because a snapshot plus a written rescue order covers both the data and the method.
Practice the card steps in order on a healthy phone twice a year. Enter recovery and list the modules and rename a harmless module and restore its name. That rehearsal proves the card is accurate for your current system version. System updates can change recovery menus and button timing without warning. A card tested last year may describe a menu that no longer exists. Rehearsal keeps the card honest.
Share the card location with someone you trust so a rescue can start even when you are away from the phone. A family member following clear steps can list modules and rename a suspect while you travel home. Keep the language plain and avoid abbreviations that only you understand. The partition knowledge in understanding A and B partition flashing belongs on the card in plain words too because a slot switch is often the fastest rescue and it should not require expert knowledge to attempt.
Teach the rescue order to a friend who also roots phones so knowledge spreads beyond a single owner. Walk through recovery entry and module listing and the rename step together on a healthy phone. A friend who has rehearsed the steps can guide you by voice when your own phone loops and your hands shake. Shared knowledge also improves because a friend may spot a flaw in your card or a faster step you missed. The root community stays resilient when rescue skills are common rather than rare. Your calm during a future loop may come from a rehearsal you shared today.
Keep a spare cable in your rescue kit because cables fail more often than phones do. A cable that charges fine may still fail at data transfer speeds needed for rescue commands. Test the spare cable for data transfer on a healthy phone before you store it in the kit. Label the tested cable so nobody swaps it for an untested one during a tidy up. Redundant cables cost little and rescue attempts fail completely without a working data connection. The humble cable deserves the same respect as any software tool in the kit.
Keep the rescue card updated after every module change so the suspect list never goes stale. A card that names modules you removed months ago sends a rescue down the wrong path at the worst moment. Update the card in the same session as any module install or removal. That paired habit takes thirty seconds and it keeps the card trustworthy for years. A rescue card is only as good as its last update and a stale card is worse than no card because it creates false confidence.
Conclusion
Boot loops lose their terror when you know the order. Reach recovery and confirm the connection and list the modules and disable one suspect and rescue your files. Each step is small and each step leaves your data safer than the step before it.
Your concrete next step is to rehearse recovery entry today on your healthy phone. Write down the button combination and test the computer connection and list your modules once. That rehearsal turns a future emergency into a familiar routine. For the complete data saving version of this rescue read fixing a boot loop without wiping personal files next.
