Yesterday I updated a few apps, not the system. Today my phone somehow reboots and goes into boot loop.
I try to go to recovery mode, but it still reboot.
Here is the symptoms:
Go to recovery mode
Shows your device can't be checked for corruption.
Shows Google sign
go to back to step 2.
Nexus Root Kid cannot fix it.
Any help?
Related
i recently flashed my phone with Gapps in order to upgrade to CyanogenMod 11, after that i downloaded an app called Reboot Recovery to boot my android into recovery mode. I didnt boot android up into recovery mode manually due to the irregular booting it has recently (such as boot up then shutdown sequences) after that the screen went black with only 2 words in blue "recovery booting" then shutdown again. I attempted to boot it up with power button but the 2 words appear again and shutdown once more, also tried manually enter recovery mode, that also did not work, and i took off the battery, tried to charge with phone etc....to no avail. Please help.
Flash recovery with Odin and try again
I tried to install the gapps aplicataion , so I enter to recovery mode.
then I entered accidentally to 'wipe cache pratition" and then I turned off the phone.
After that I try to turn on the phone and this stuck on this screen (first iamge).
So I treid to back to recovery mode and when I enter to recovery boot in the bootloader its restart my phone and now its stuck on this screen (second image).
please help me to solve it
I tried to root my razer phone today and when I succesfully booted into twrp and had flashed twrp and magisk on both patitions I accidentally formated the data and factory reset, and then when I restarted my phone I can´t load into recovery mode, download mode, bootloader or system.
There must be a way to enter recovery mode since I was in it when I formated the data and factory reset.
I also have a microsd in my phone with a clean factory image of the device but I cant install it since I cant enter recovery mode.
When I start my phone it never leaves the loading screen
Any ideas?
EDIT: Nevermind I solved it the phone had just really weird button combination for entering android recovery.
Every time i tried to flash a ROM i got: ERROR 7. I Then tried to repartition: https://forum.xda-developers.com/ne...partition-nexus-7-2013-repartition-t3844386.i am not sure if something went wrong there. Afterward i wanted to reboot into recovery, but it seems like i cant get back into recovery mode. While i am able to reach fastboot mode, when i try to go into recovery, after a few seconds it jumps back to fastboot mode. Any idea how i can get my nexus back to the recovery mode
https://forum.xda-developers.com/nexus-7-2013/general/restock-stock-restore-repartition-t3995981
I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.