General :: Phone In Boot Loop - No Recovery Or Download Mode
May 18, 2014
So I have a Samsung Galaxy Ace 2 X (GT-7560M) and basically I tried to flash CM11 on it, and when after the reboot, the phone was stuck in a boot loop and I can not access nor the Recovery mode nor the Download mode. I did try a USB jig and still no luck.
I have an Android tablet (Diablotek D2-721, very cheap I know, but it serves its purpose) that is stuck in a boot loop. The real problem here is that this device apparently does not have any sort of recovery mode and being in a boot loop means it does not get recognized by ADB or any firmware flashing software.
I researched all day yesterday perusing forum after forum but almost every single solution requires booting into recovery.
I've rooted my samsung galaxy mega 6.3 GT-I9205 but I got stuck in a boot loop after trying to change my boot logo using a app called root tools. Before that everything with root worked fine.So I tried recovering the phone by going into recovery mode and wiping all of my data/factory reset and also wiping my cache. Both of these thing did not work.
So after that I went into download mode and tried to instal something I believe CWM. But now I can't even go into recovery mode because when I try, the phone says that it's going into recovery mode and then just reboots... and goes into a bootloop.
I've been working on this phone from start to finish about 9 hours, over two days..I've Google just about every combination of words to do with the title and everything in between but nothing seems to come close to what i actually need to do as nothing works.
i have an LG Optimus 2x / p990, it had ICS on it but was far too slow to handle this, it needs something a bit less hardware intensive to run smoothly, so i went ahead an found cyanogenmod stable...7.2 i installed sdk after an hour of finding out how it works i finally got adb and fast boot working.
to cut a 9 hour story short, I've managed to get myself to the point where i wiped the phone of everything but CWM partitioned for ics via the AIO software but CWM will not let me install any ROM onto the phone. to be more precise it says i have installed CM 7.2 successfully! (I've tried this via the CWM via external SD card and side load) i reboot the phone it's as if I've never done a thing, no trace or suggestion I've even attempted it on the internal card... nothing
i'm at the point now where i'm quite happy to just have my phone back now and install ICS 404 but can't use the LG kdz install software as the pc doesn't see the phone as an LG p990 because it's recovery and i can only get it to come up as internal and external memory cards.
Can get my phone working will do, preferably the CM 7.2 if not back to ICS 404? i should have backed up but i had no idea it could be so complicated just to put an OS on a tiny computer. I've tried that exit recovery.zip thing and it did nothing :/
I bought it from Etotalk, so it came rooted, and with their custom version of the Lenovo Stock ROM and their custom version of CWM 5.5 installed.I tried formatting my SD card and then doing a factory data reset from within the operating system. (I was intending to install MIUI V5 after rebooting into recovery).
However, on rebooting, the device is now caught in an infinite boot loop, and I am not able to boot into recovery mode (by holding down power and both volume keys). It loads the initial splash screen, then shows a few seconds of the Android character and some whirring cogs before rebooting.
I am able to boot into Factory mode (power and volume up) or Meta mode (power and volume down). Factory mode has a number of options, but they are all in Chinese characters, which I am unfortunately not able to read.
I did notice that my SD card seemed to be write protected when I tried to format it in my computer and to copy on the new ROM - I solved this by putting it in a different phone and reformatting it. I wonder whether the factory reset process has write protected something it shouldn't have?
I've got the latest Android SDK Tools, MTK Droid Tools 2.4.8, SP Flash Tool 3.1312, some additional ADB drivers (120827 v3.7) that I'm not sure how to install, the latest MIUI V5 ROM (3.8.16), and the latest stock Lenovo ROM (S118 from Need A ROM, just in case I need it).
So just an hour ago I got an OTA update for my LG L9 and of course installed it. It asked me to reboot and so I did, but it got stuck in the Clockworkmod recovery and when I try to reboot the phone it just boot loops in the recovery no matter what I do.
Tried wiping, formatting everything I possibly could, but still the same.Also installed cm10.1.2, but it boots every time in the recovery after like 2-3 seconds after the LG logo appeared. The same was on the stock rom.I was running the stock jb rom which was rooted and with cwm recovery installed.
Just FYI in case anyone wants to know: For download mode, with the phone turned off, fold the number 1 key on the QWERTY keyboard and the power button simultaneously For recovery mode, with the phone turned off, hold Volume Down, CAmera, and Power simultaneously. You navigate with volume UP/DOWN, select with HOME, Menu toggles to "Manual Mode", whatever that it.
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up.
I've been reading and I've downloaded the ROM Manager from the Marketplace. I've also downloaded a ROM to install. I have tried to boot my phone into recovery mode (pressing X while powering back on) and all I get to is a screen with the exclamation mark and a phone under it.
My EVO 3D (Sprint) is rooted and is on android version 2.3.4 and I believe it's not an android official release, this is how it was given to me. I'm trying to install CM10.1
I installed ClockworkMod 126.96.36.199 using ROM Manager and since then I haven't been able to boot into recovery mode. I can get into bootloader but not recovery. I've tried powering it on with the volume button down, using the recovery reboot option, and tried using "Reboot into Recovery" in ROM Manager, but I keep seeing the same thing. It boots with the HTC logo then goes black then at this point i believe I should be seeing recovery mode but instead I see the HTC logo again and then it just boots like normal. Is there something I did wrong and is there a way to get recovery to work again?
I updated my galaxy s gt-i9000 to cyanogenmod 10.1,1. everything worked great.... I got a wild hair and decided to upgrade it to 10.3.0 but it went into a boot loop. I then broke out oden, and long story short I soft bricked it. I now actually got my phone to let me restore my backup that I did before I updated it, and it completed successfully. But it only boots into recovery mode. What I can do?
I used my galaxy ace (I had the low memory icon) when playstore has updated an application, then suddenly all my applications are set to "force stop" including Holo launcher, so I rebooted, but the I had teh cyanogenmod 7 icon repeat (bootloops) I cann't access to the recovery mode (I had RAMDUMP mode (ARM9 mode)) I can access to the "downloading" mode so I wanted to flash a stock rom (even three in fact) with odin multidownload 4.38 but nothing happens when Odin has restarted my phone, I had the little android image that works then a message like: "E: failed to mount storage (invalid argument)" and the phone started to reboot loop I've tried dozens of manipulations unsuccessfully kies does not see my phone I do not know what to do,
PS: I've tried all the manipulations removing the battery / SIM card and sd waited 5 minutes, I was able to put the phone in Emergency Mode DLOAD but it nothing happens the only real thing that still works is the "Downloading "mode , but I think my recovery mode was crushed and I cann't access it even when I can flash with odin I always have the problem of "E: failed to mount storage" (the same style as him [URL]...
I'm trying to update my phone and it won't boot into download mode :X so I'm trying to do it with adb my problem is I can't get adb commands to work because I don't know what the path should be in the variables :C my location for adb is "C:Program Files (x86)Androidandroid-sdkplatform-tools.adb.exe".
Since I installed Virginity v12 on my S3 Mini I can't boot it in Recovery or download ! I have tried with buttons, with reboot menu... even from Clockwork ! It just boots normally on system ! How do I fix it ?
I've been running Kangerade since shortly after it came out... And loving it.. Yet today I saw my phone was rebooting - and waited (figured it over heated or some such..) and waited... And waited... That android boot image does stop being cute after a while... Crap.. Just cycling... Go into recovery... Umm.. No seriously.. Go into recovery.... Go on.... Nope. (apparently latest ROM MAnager screwed up CWmod..) So... Can't load my phone... Can't restore backup..
I am using sony ericsson x10 mini mobile phone. I want to install custom ROM cyanogen 7 gingerbread. But I am facing problem while booting this in recovery mode. I have tried the following.
downloaded custom rom for xperia mini and copied in to sdcard
installed ROM Manager Premium (not purchased, downloaded from google search and it is working fine)
installed root explorer S1 tool
Rooted from superoneclick
downloaded xRecovery and copied into system folder
Flash tool - showing bootloader unlocked, and dont know how to flash phone.
msm7227 - used for unlock boot loader
I have rooted my phone successfully, all above things did successfully, when i am trying to boot my phone into recovery mode then it is not boot in that mode instead it boots in normal mode. What I am doing when phone starts and sonyericcson appears then i continuously pushing button many times but it boots in normal mode. So what I have to do to boot my phone in recovery mode. I have read and tried many guides in your forum but nothing works.
My samsung i5500 wont boot normally so I want to try booting it into recovery and resting it. I've tried power, center key and volume down. which I thought was the recovery combination but it just comes up with an icon saying downloading and does nothing. Any recovery combination or another way to fix.
my device is galaxy ace s5830i..i have already rooted my device and used CW Recovery and taken a copy of my original system.i wanted to set up a custom rom i restarted and reset and deleted the cash then installed the rom.i think it was Retribution beta then i wanted to update to that custom rom (MindCR ICS) all i did i restarted my phone of course went into R mode and reset and deleted the cash then installed that next custom rom .
after installing completed when i rebooted it only gave me (samsung galaxy ace s5830i) logo and doesn't open the system when i restart it doesn't go into recovery or download mode it only gives me again the same logo.i used odin v 1.81 and the latest version it doesn't recognize the phone and i can't go into download mode.
I tried to do a cyanogenmod update, but something went wrong and now I can't boot into android. I've tried going back into the recovery mode to reflash the rom, but it freezes there. I've also tried flashing clockworkmod recovery through ODIN and download mode, but the download back never moves at all, so I'm not sure if I can't use download mode or if it's just that ODIN isn't doing anything.
I was listening to music as I always do. I didn't realize it but the phone (Rezound) drained a bit faster than expected and died completely. So I went to to charge it, and left it overnight, off naturally, now when I power it on, its stuck on a boot loop.
It goes throught the startup animation, and once it gets to Sense, in the few seconds before the radios kick in and it finds the cell service, it reboots and starts all over again. Only way to get it to stop is pulling the battery out.
I started to do the hard reset, but when I got to the window for it, all I saw was Factory Reset (I guess they are the same) so I selected the option for reboot.
The light to charge does show its charging, and at one point, when I had it plugged in this morning, and managed to swipe the ring to get to my swipe lock screen, it was saying I was at 99%. then it goes all slow and then rebooted.
I used the factory wall charger, and its drained I think once or twice before, and I have done the FoxKat method of calibrating before this. Not sure if its a battery thing, since it will power up, or not.
I'm stock, non rooted, on GB.
I don't really want to do a factory reset as I'd like to have my messages saved. I did save them last week when I saw ICS was available, but i have some new since. I'm pretty sure my pictures and videos will be saved during the reset. I don't think that folder gets wiped. However I was going to try going to a VZW store to see about a new battery. The phone is new since June.