General :: Can't Boot Into Recovery - How To Access Phone
Oct 22, 2012
I've been trying to track down a solution to my problem, but every solution seems to contain a "Boot into recovery mode" line which I cannot do. I attempted to update a rom that I had installed, and now I am stuck at the google logo with the unlock icon. I cannot boot into recovery with the volume keys and power, and now I cannot figure out how to use adb to recover the phone, as it cannot recognize it.
Is there anyway I can access this phone while it is in this state from my computer and recover it somehow. I tried following leads that people have posted in other threads, but it seems like most suggestions involve "Use adb", yet every adb tutorial involves the phone being in recovery mode. I've tried to uninstall and reinstall drivers via Wug's Toolkit, but when I plug my phone in, I am not able to install the drivers properly. I try to run adb items through the console, yet it does not recognize my device.
Is there anyway to install the necessary software I need and recover my phone while I cannot get past the google logo screen?
I try to understand android boot sequence on my JB (under CM10). I found some docs and there should be specific partitions (boot, recovery, system, cache, data).
My understanding of the boot sequence is now:
A) normal boot: 1) Power ON -> 2) bootloader -> 3) boot-partition where i flashed the kernel aka boot.img -> 4a) system-partition with the OS (libs, UI, etc) where i unpacked over CWM my customROM.zip -> 4b) data-partition, where i unpacked google-apps.zip and installed all the apps -> 4c) cache-partition with user data
B) recovery boot (adb reboot recovery): 1) Power ON -> 2) bootloader -> 3) recovery-partition with CWM where i may unpack all the .zip stuff to proper partitions, or restore from sdcard, etc.
Is this correct? I wonder, because i didn't installed CWM into recovery-partition. It cames from install of CM10 (fastboot -i 0xfce flash boot boot.img), so it must be in boot-partition and not in recovery?
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
# ls -lha /sdcard/clockworkmod/backup/2012-10-04.18.49.55/ d---rwxr-x 2 system sdcard_r 4.0K Oct 4 18:56 . d---rwxr-x 3 system sdcard_r 4.0K Oct 4 18:49 .. ----rwxr-x 1 system sdcard_r 1.6K Oct 4 18:54 .android_secure.vfat.dup ----rwxr-x 1 system sdcard_r 54.6M Oct 4 18:55 cache.yaffs2.img ----rwxr-x 1 system sdcard_r 360.2M Oct 4 18:53 data.yaffs2.img ----rwxr-x 1 system sdcard_r 212 Oct 4 18:56 nandroid.md5 ----rwxr-x 1 system sdcard_r 214.6M Oct 4 18:51 system.yaffs2.img #
So, i think i didn't understand the boot sequence and partition schema corectly.
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 have a Nexus one and I have made a bit of a mess of it when loading a custom rom. Previously I'd rooted (without unlocking) the stock (2.2) rom before loading Cyanogen 6, later Cyanogen nightlies and finally eViL-NXSense-v1213. I was rather enjoying the last one but had severe stability issues which I think was due to using Titanium Backup and restoring data. I was in the process of re-imaging to eViL-NXSense-v1213 after clearing the SD card, data and various caches when something seemed to happen to the recovery image. I can get into the boot loader but if I select Recovery it shows the Nexus One logo indefinitely and doesn't respond to the power button being pressed, the same happens if I turn it on from cold.
Is it possible that the recovery image has somehow been corrupted? If so what can I do to restore a recovery image that will enable me to install a custom rom. I would prefer not to unlock the boot loader but will do it if necessary.
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.
Phone: UK Galaxy S Issue: Recovery boot error message in red writing
Multicsc : can not access to / system/csc/VOD/system/
Background: I have been trying to root my phone from information found in a youtube video. All went well and the little ninja bloke with the sniper rifle was in the app list. Tried installing busybox and was told that the phone was not rooted�..
I think I ran the root application again and at some point I started getting this error message when in recovery. I have since run the one click root method to unroot the phone and the little nija dude is no longer there. Since I rooted the phone it will no longer connect to my wireless network, it finds the network and attempts to obtain an ip address. After a few min it times out and tries again. When I load the phone recovery the error message is still present.
I did a full wipe, including cache, and got stuck in a boot loop. I pulled the battery, and when I hold down the volume and power button to boot into recovery so I can restore, the phone vibrates three times very quickly, then nothing. I can turn it on and go into boot loop, but that's it.
I have a new ace 3 LTE S7275R. I tried installing CWM recovery found here: URL....I tried with odin 3.07 and 1.85Every time, odin shows success, but when trying to boot into recovery, the phone gets stuck at "recovery booting...."The phone is otherwise working...getting CWM to work? how can I return to stock recovery at least?
So I just got my S4 rooted and everything seems correct. I then installed Rom Manager so I could start demoing some of the ROMs out there. Went through all the steps to flash Rom manager as the recovery but I cannot get my recovery to go to CWM, it just keeps going to the stock android recovery. I have googled the crap out of this and am coming up with nothing. in fact I have written several android apps but this just does not work.
My device is a Verizon Samsung S4 model SCH-I545 running android version 4.2.2 Kernal: 3.3.0-690088se.infra@S0210-13#1
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.
i wanted to upgrade my galaxy s2 g i9100 and since that time i hve not been able to use the phone again.
i tried rooting it but after that i can not boot recovery anymore all that comes on the screen is SAMSUNG GALAXY SII with a yellow triangle.even if i press the up volume key+home key+power nothing happens.
I have a Karbonn A6 phone given to me by my friend because it was locked. It's asking for gmail user/pass but he doesn't have it. I tried to boot into recovery mode using Power+Volume Up button but all I get is a white triangle with an exclamation mark in it. I can't seem to go beyond that. USB debugging was perhaps not enabled unless it was enabled by default. There is no camera button, only power and Volume Up/Down. What do I do?
I just need to get this phone working somehow. Is there a way to use a computer and a USB cable to get it running?
I have tried using rom manager, holding the power button and selecting reboot recorvery, and by holding the power button and x. Each way I see the white m twice then the phone just boots up. I am running cm7 7.0.3. I have only had the phone for a week, I am trying to wait for the vigor. It worked fine Friday when I flashed cm7
I'm on a Galaxy S2 running Gingerbread 2.3.4, my baseband version is I9100XXKI1 and my kernel version is 220.127.116.11-I9100XWKH4-CL487028root@DELL136 #2
Using Odin3 v1.85 and S2 Root. (Superoneclick kept freezing on me)
My aim is to install Cyanogenmod 7.1.
So far I started off by trying to flash it with XWKDD Insecure, which I believe is wrong? However after rooting it, I installed ClockworkMod Recovery, downloaded the ROM and tried installing it - which is where the problem started - I kept getting the error in recovery mode 'Invalid whole-file signature'.
It just wouldn't boot in to ClockworkMod Recovery.
So after some digging around I managed to find a file to flash to my device for the CWM Recovery mode, tried it, and it worked. However, I still couldn't install Cyanogenmod from my SDcard.
I tried it a few times, wiped/formatted a few times and ended up getting my device stuck in a bootloop.
So, I've managed to get it out of the boot loop, and started fresh...
I flashed it with XWKH4 Insecure, unrooted, rerooted etc. I've downloaded CWM again, downloaded the Cyanogenmod again, tried installing it, and once again it's gone back into Androids recovery and failed to install because of the 'whole-file signature' and failing to verify it.
I did post this in Q&A as well, however it doesn't seem to be as popular a forum as this one, I'm not really looking to wait for days for a response.
I rooted my phone using Z4 then used Titanium Backup for backing up and then recovery. Now while rebooting into recovery mode the phone took a long time in booting so I removed the battery and tried to reboot. But the phone makes the signature sound and after that only displays the following word 'spice'.
I flashed Omega rom today for my galaxy note 2. It uses Aroma installer which i think could be the problem. Basically I cant boot into recovery. The rom is also very laggy where people on its development thread are praising it stability! The device will stay on the 'Samsung galaxy note II gt17100' bootscreen when i try to.boot into recovery.
i have a cheap alwinner a13 tablet (simmtronics xpad x720) from indian manufacturer. It is stuck at cwm recovery it countineously boots to cwm after restart.I have no backup stock rom. But i can sideload zip from adb or external ed. And not able to mount internal sd or wipe cache.
ok, so I put the PB31IMG file on my sdcard, and the dinc_ota. I changed dinc_ota to update. (I did not name the file update.zip.zip) I powered down, I entered bootloader, and it loaded the PB31IMG and whatever. then I hit volume down and selected recovery. this brought me to clockwork recovery. I noticed the isntructions said to boot into STOCK recovery. well, I like a dummy ignored that and tried to apply the update.zip thru clockwork.
This is what I got:
So, is this because I tried doing it through clockwork recovery? is it because I didn't apply the first OTA update we got? what does that mean exactly anyways? is it saying I need to install the leaked froyo ROM, and then update the radio? How do I boot into stock recovery and not clockworks recovery? does this count as applying the update.zip once, meening if I do it again I'll brick my phone? should I sell this thing and get a samsung flip phone because I'm too stupid to own a Dinc?
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.
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 18.104.22.168 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 Have An Ainol Novo 7 Crystal Tablet..(Rooted With TWRP Recovery&Cyanogenmod 10.1 Installed).It Was Working Fine Till This Afternoon But I Don't Know What Happened Next..I Turned Off My Device And I Tried To Turn It On Again After Some Time But It Wasn't Booting...
I Don't Even See Any Boot Animation Or Android Logo That My Device Used To Display While Booting,The Screen Of My Device Lights Up Though..And I Can't Even Boot Into Recovery (I Have TWRP Installed),When I Try To Boot Into Recovery I Don't See The Android Logo That I Used To See But The Screen Of My Device Lights Up And Doesn't Boot Into Recovery.. I Tried Removing TWRP Recovery From My sd card And Booting Into Recovery But The Screen Lights Up For Like 5 Seconds And Then The Light Goes Off..
My Samsung Note 10.1(N8000) got stuck on boot screen at stock. No recovery only download mode. I don't know why, it was flat for about 2 weeks before I noticed.
Roms always and still flash successfully if I get the right version of odin, i think i have about 15 different odins from trying to fix this.
Things I've tried:
1.Flash stock rom 2.Flash custom recovery 3.Flash different versions of both 7+ 4.Re-partition and repeat 1-3 5.Wipe the memory and repeat 4 with many many roms
why my tablet stopped the first time and why no roms are working to recover it. What is happening here? Is it corrupt memory or motherboard etc hardware? Is there a god .pit file or god rom that could work to make something happen? What should i try now?
This shows a successful flash which had no effect on the tablet afterwards
I'm having trouble booting my LG Optimus G into recovery mode. I've rooted the phone and installed ClockworkMod recovery. When I try to boot into recovery, either from the ROMmanager app or by holding Volume Up and Power, it comes up with the LG logo and gives this error: Secure Booting Error! Cause: boot certification verify. It just stays like that until I press and hold the power button again until the phone shuts off entirely. Then I'm able to boot into the stock operating system and the phone works fine, but I can never get it to boot into recovery.
The error I mentioned above seems to be a well documented error on the internet, but it seems like other people that are having the trouble are completely bricking their phones. Mine is able to come out of it. All the solutions I'm finding pertain to a phone that's completely bricked and involve taking the phone back to stock. My phone works fine with the stock ROM, but I'd like to play with some custom ROM's.