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
Related
i can't boot into recovery mode (vol up+home+power) when i try to enter to recovery the screen display android logo and write under it "downloading...
do not turn of the target"
i have philz recovery flashed
i can boot into download mode
i tried to reflash philz recovery 5.15 using odin but it write fail in the 1st box of odin
what can i do
thanks
redahashem86 said:
i can't boot into recovery mode (vol up+home+power) when i try to enter to recovery the screen display android logo and write under it "downloading...
do not turn of the target"
i have philz recovery flashed
i can boot into download mode
i tried to reflash philz recovery 5.15 using odin but it write fail in the 1st box of odin
what can i do
thanks
Click to expand...
Click to collapse
Try releasing your fingers upon seeing Samsung Galaxy Note 2 i.e upon boot up. Did you check if your volume button works? It seems that what you did was power+home+vol down that is why your on downloading mode. Hope it helped.
reinkut said:
Try releasing your fingers upon seeing Samsung Galaxy Note 2 i.e upon boot up. Did you check if your volume button works? It seems that what you did was power+home+vol down that is why your on downloading mode. Hope it helped.
Click to expand...
Click to collapse
thanks for reply
1- the volume buttons works fine
2- the displayed screen is not the download mode (in download mode the yellow triangle appear, and a warning appear and ask you to continue press volume up,and an information of the device appear on the top of screen etc...)
3- i hold press the vol up+home+power until the "samsung galaxy note 2" appear and then disappear for the first time, in the past the "samsung galaxy note 2" appear second time then i release my fingers, then it disappear and then the device boot into recovery.
but now the "samsung galaxy note 2" doesnot appear the second time,and the "downloading" screen appear
Not loading onto Philz recovery mode screen
I added or rooted using Odin on my Note2 running android 4.3 however when I enter boot recovery it loads with the following options:
Reboot system Now
Apply update from ADB
.
.
.
.
Apply update from cache
It did say Pass on Odin when I followed the process to install Philz.
Not sure what I am doing wrong. Please suggest
Hi,
This morning my rooted + xposed Selfie rebooted without any reason and now it is stuck in ASUS logo bootloop!
I can enter fastboot mode ("Fastboot Mode!!!" is written on the top of the screen) but I cannot enter recovery mode.
I tried to reflash boot, recovery and system images but nothing changes.
What's happened and what can I do?
Thanks!
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?
Hi all,
I have a Lenovo TB3-730X tablet.
Recently I wanted to flash a custom ROM but it turned out it was not compatible and the tablet was messed up.
What I did before reaching at this messed up state was:
1) Flash TWRP recovery
2) Copied the custom ROM into SD card and installed it, the installation failed and boot failed. The tablet stuck in the logo screen forever
3) I tried to install the stock ROM back using PC and SP Flash Tool but the latter never managed to connect to my tablet.
4) I manually copied the system.img and boot.img from stock ROM into SD card and tried to install them manually using TWRP by selecting "System Image" and "Boot" partitions respectively. After this and before rebooted the tablet, TWRP reported that "No OS is installed". I went ahead and rebooted the tablet anyway and now it keeps restarting. It shows the logo screen for few seconds and then restarts over and over again. I cannot connect to TWRP recovery mode anymore as the Volume-UP / Volume-DOWN + Power button are being ignored. I am not sure if the TWRP was gone after flashing the boot with boot.img. Also the tablet cannot be connected to the PC at all because it keeps restarting and it doesn't get stable to the logo screen as before so that the USB connection cannot be established. This means I cannot use "adb" from PC to connect to recovery mode using "adb reboot recovery" command
I really stuck here and would appreciate any help.
Thanks in advance!
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.