I noticed many average users out there, bricked their devices so here's a guide for you to unbrick it:
Bootloop is a state when your phone is not able to boot properly and it is stuck on the Bootanimation It is the commonest thing that Android users face with their phone or tablet device and this can be fixed easily by performing certain steps by booting the device into stock or custom recovery mode. Here is our detailed guide that will help you fix bootloop on your device.
1-How to Recover When your Android Device is Caught in a Bootloop:
The reasons for getting a bootloop on your Android device might be anything.Here are some major reasons why your Android device is caught in a bootloop.
-After installing an official or custom ROM
-Flashing a wrong ROM or Kernel
-Running an incompatible app or game
-Wrong Permissions fix for an app or file
Installing a custom mod or theme
Most often we face a bootloop just after flashing a stock or custom ROM over an old one. This might be a major factor behind the bootloop issue on your device. Suppose you have flashed a new version of firmware over the old version. Your old data still remains on the device and the new firmware will use the Dalvik Cache from the old ROM that might not be compatible with the new system files and it will result in a bootloop. It mostly happen just when your device tries to reboot after you have flashed a stock or custom ROM. If this is the case, here is the solution.
Method I-If your device is on stock firmware, that also means it does not have a custom recovery like CWM or TWRP not installed on it, do the following steps:
Pull out the the battery of your phone, wait for about 30 seconds and reinsert it to its place.
Boot your device into ASR (Android System Recovery) mode. The method involves a hardware key combination and varies from one phone to another. For Samsung phones, for example, the key combination is Volume Up+ Home + Power keys. The tablets which generally have no Home button, you can enter the Recovery mode by pressing and holding the Volume Up + Power keys simultaneously.
In the Android System Recovery, scroll down to “wipe cache partition”. option using the volume rockers and select it using the power key.
When you have wiped the data/factory, go back to the main menu and reboot the device by “reboot system now” option.
If the device is still stuck on Bootanimation pull out the battery again and repeat the above steps. This time also “wipe data/factory reset” and then reboot device
The bootloop problem should be fixed now.
Method II-If you have a rooted device with CWM Recovery installed and your phone is caught into a bootloop after flashing a custom ROM or mod, do as follows:
Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
Go to “Advanced”
Choose “Wipe dalvik-cache”
Now go to “Mounts & Storage”
Choose “Wipe /cache”
Reboot your phone
The bootloop should be gone now. If it still persists, do this.
Boot the phone again into CWM Recovery
Now go to “Mounts & Storage”
Choose “Wipe /data”
Choose “Wipe /cache”
Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
Note:
If wiping the data/factory reset, and cache partition does not help you, or you are not able to boot into the Android System or ClockworkMod recovery on your device, you can try installing the official firmware on your device.
In case the two methods described above do not bring your device to normal state, the problem is a little serious but still not out of control. The following method is same as installing the official firmware described above, but it also involves flashing a PIT file along-with the firmware. This file is used to re-partition the corrupt partition on Galaxy devices.
source: DroidView.
Hope this small info help.
Related
I've just flashed the new gingerbread rom (http://forum.xda-developers.com/showthread.php?t=1009177). I've found an option in the clockworkmod recovery that allows you to reboot in download mode. I did that and flashed with odin but now when the phone starts it says:
-- Copying media files...
Successfully copied media files.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to 'system/csc/TMB/system/',
Successfully appliced Multi-CSC,
Then I have the following options:
reboot system now
apply update from sd card
wipe data/factory reset
wipe cache partition
When I select any of these options nothing happens (I don't know if this matters but volume up is down and volume down is up). I've also tried to reboot the phone in download mode but it takes me to the android system recovery window. If I plug the phone to the laptop it takes me to the android system recovery window
I'm currently applying for several jobs and I NEED my phone to be operation ASAP. I would REALLY appreciate if someone could please assist?
Does the 3-button-combo work? if so go into Download mode and flash a full ROM like Darky's resurrection
After that you can try flashing JVK again or wait with experimenting until you have 1 or 2 days when you don't need your phone
or, if you have a full nandroid backup (I strongly recommend creating one regularly) just flashing any custom kernel and restore All.
Edit:
It seems like the first post has changed a bit after my post.
That is the problem. The download mode won't work. I press on volume up+volume down+on button and it still takes me to the android system recovery window.
I need to find a way to get into download mode so that I can flash the phone again.
If this happens to anyone use the three files from the first post which has bootloaders included, tick re-partition with .512 PIT and flast it again.
rawfa said:
That is the problem. The download mode won't work. I press on volume up+volume down+on button and it still takes me to the android system recovery window.
I need to find a way to get into download mode so that I can flash the phone again.
Click to expand...
Click to collapse
That's not the correct combination of keys. You should not press volume up+down.
Don't play with your phone if you need it, and don't install custom ROMs if you can't follow instructions buddy.
you should apply a proper kernel, froyo kernel doesnt work on gingerbread!!
Hey,
Very strange query but here goes. Rooted phone a while back and installed CM13 along with recovery. Was trying to update TWRP{ by downloading .img from their website, went to flashing, selected the file and hit recovery. Said it was succesful so attempted to reboot. Plugged in to charge and was charging but when I tried to switch it on, it was stuck in Cyanogen Bootloop (blue alien stayed on the screen for 10+ minutes). Tried rebooting to recovery by hitting power + volume down and instead of booting to TWRP, it takes me to a Cyanogen recovery screen where I see the following options:
Cyanogen Recovery.
- Reboot system now
- Apply update
- - -apply from ADB
- - -choose from emulated
- Factory reset
- - -system reset
- - -full factory reset
- - -wipe cache
- Advanced
- - -reboot recovery
- - -reboot to bootloader
- - -Wipe system partition
- - -view recovery logs
Here's what I tried as troubleshooting. Tried to do a system reset, factory reset and wiped cache and tried to restart my phone but no luck. Still stuck in boot loop with CM logo. Tried to reboot to bootloader but the screen is stuck with the 1+ logo for about 5 mins so gave up on that.
Basically, right now I can't access anything on the phone, can't find any way to reinstall a ROM and when I plug it into my Macbook, it is not recognised. So I'm screwed sideways. I had TWRP recovery set up so I have no clue how this happened but can anyone please help me with this.
If data isn't at risk try the Qualcomm recovery tool one the oneplus forum it's by nammand bhal (definitely butchered the name) but all data is lost and resets the phone to out of box conditions locked bootloader and Oos 2.2.1 so this is often a last measure (tool is Windows but may have Mac variant and the file is quite big)
My suggestion is to try to boot to bootloader again and flash TWRP
hmm mac book I don't have much experience with those
If you have a Windows pc you can use adb or on Mac if it has it. Also when it come to being found by a computer in recovery it should but again don't have a mac
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
AJay27 said:
CM13 replaced your TWRP recovery with Cyanogen Recovery.
Try to boot into fastboot by holding volume up+ power buttons. If successfull, flash TWRP Recovery, boot into it, wipe everything and do a clean install of the ROM.
Macbook won't detect your device unless it is booted up, in recovery or in fastboot mode.
Doesn't it detect while you are in CM Recovery??
Try selecting Apply Update and Update from ADB. It should detect the device atleast now. If yes, try sideloading.
Click to expand...
Click to collapse
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
justicesourglide said:
I knew I would regret getting that macbook at some point
Borrowed a friend's PC and was able to flash TWRP recovery. Was then able to boot into it and do a clean install. Ended up installing Oxygen OS this time. Do you know why this issue occurred so I can research how to prevent it next time.
Click to expand...
Click to collapse
Actually I don't think the issue was with the Macbook since I have unlocked, flashed custom recoveries and sideloaded ROMs on several devices including OP2, OP3, Nexus 5, etc on mine. It might have been some accidental flashing error, which unfortunately ended up bricking your device.
Hi guys
So, i've been at this for most part of today. Looked all around and tried everything i found, and im still clueless.
I've done this steps twice, with the second time being more step-by-step instead of bulk actions, always starting from miui 8 global stable rom:
1 - flash twrp via fastboot with twrp-installer.bat for redmi 3s
2 - reboot into stock bootloader with power + vol+ and choose recovery to boot into twrp
3 - in twrp, slide to modify system and disable dm-verity in advanced options
4 - reboot into stock rom and power off phone
5 - boot into twrp in the same way as in step 2
6 - clean dalvik, system, data and cache partitions
7 - flash lineageos 13 from lsferreira and gapps
8 - reboot into custom rom and power off phone
9 - try to boot into twrp in the same way as in step 2 - NOK, just gets stuck at the MI logo
10 - reboot into custom rom and reboot into recovery from the power menu, twrp OK
11 - flash something, like goodix fix or xposed
12 - reboot into custom rom, verify installed packages OK
From this point on, i can not get back into recovery, either stock bootloader or twrp. Tried from the power menu, vol+ button, reflashing twrp through fastboot and adb, booting directly from recovery.img from fastboot and even reflashing stock recovery. The rom always boots fine and so does fastboot.
I saw some posts saying to hold both vol- and vol+, but this just seems to boot the phone in some deep recovery mode, judging by the drivers that the PC tries to install (EDL maybe?)
The only way i can get the bootloader/recovery (the vol+ chinese menu) back is to reflash stock miui 8 through miflash tool, which gets me to the starting line.
Will anyone be kind enough to point me to the blatantly obvious mistake im making?
I think I found a solution. I flashed a different twrp recovery (the one provided by fedosis, by cofface) instead of the one linked in every how-to in both this and miui's forums.
Now i can boot to recovery everytime.
Hi, everyone.
I have a galaxy s8 SM-G950FD. I have once flashed TWRP and rooted the device successfully.
Then I tried to install a custom ROM but I got bootloop.
After that, I flash official ROM to unbrick my device. But since then, whenever I tried to flash TWRP again I got this message "Verification failed unable to restart your device the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
My device is still working fine but I want to try to flash a new ROM (even if I may brick my device forever). I don't know what to do. Can you guys give me some advice ?
Thank you!
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
But I cannot boot into TWRP. How can I do that ?
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
MikeTheTechSavvy said:
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
Click to expand...
Click to collapse
I cant flash/get into TWRP. I tried to boot into stock recovery and do a system wipe/factory reset. Then I flash TWRP again but nothing seem to happen. I tried to boot into recovery and it get me to the stock recovery not TWRP.I did unlock OEM, used Odinv3.12, twrp-3.1.1-2-dreamlte.img.tar.
I had the same issue.
After Odin has flashed the Recovery it performs an auto reboot (if checked in Odin). So at this reboot hold Vol up + Home + Power as soon the screen goes of. You need to be quick. Then it should boot into TWRP.
True, Samsung's stock recovery is very persistent lately and if you tick the auto-reboot you have to be very fast in switching to Recovery mode combo.
Otherwise you can choose not to tick auto-reboot, force restart the device after the TWRP flashing was successful and immediately switch to the Recovery combo.
Here you go: two ways of doing this.
LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).
LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand