General :: How To Boot To Recovery Without Home Button
Feb 3, 2014My home button was broken.I can boot to Download mode via JIG USB only. When my phone bootloop.One way to fix it ,is flash a new ROM using Odin Have other way?
View 1 RepliesMy home button was broken.I can boot to Download mode via JIG USB only. When my phone bootloop.One way to fix it ,is flash a new ROM using Odin Have other way?
View 1 RepliesWhen 2.3.5 update on Samsung Galaxy S finally arrived, I've rooted my phone as seen on androidadvices.com. This version is not stable so I wanted to go back to stock ROM but in the mean time my HOME button stopped working.
So, there I was, not able to go to download mode to flash stock ROM. Than I googled that you can go to download mode through adb and I did and flashed backed stock ROM.
AND THEN, IN AN ACT OF ABSOLUTE STUPIDITY, I'VE GONE TO RECOVERY MODE THROUGH ADB.
And now I can't get out. My phone is working, software is ok, only HOME button is not working. ADB dont see phone any more and phone is always rebooted in recovery mode.
How to Replace the ok / Home in recovery?
because the ok / home I do not work!
like Samsung tab no buttons his home
ok button / his home was replaced with a volume ...
My matter is that the Home button in recovery mode isn't working so i can go up and down with volumes button but i can select nothing,
View 4 Replies View RelatedMy galaxy k's home button has been broken. And i wannted to use recovery.So I attached it with my computer, used cmd(adb reboot recovery). After that i was able to go in recovery. But after that I couldnt reboot it. I tried to use cmd. But it cant find my device.
View 2 Replies View RelatedI had a problem with my old Vodafone Smart II phone Alcatel V860, and I put another original ROM on it. Everything was fine. I rooted also the phone, not a problem. But when I went into recovery mode I noticed something weird, only my volume keys up and down are functional to make selections in TCT recovery console, but not also the select button (the home button). This worked before! I also noticed much more options in the recovery console than before, but what good? I can't select options from the recovery menu whatever I do, just navigate through them.
View 2 Replies View RelatedI want to try out 2.2 but when I try to boot into recovery mode (or what it is called) using home + start i get an image where i see a device and a red triangle with a "!" in it.
Running original 2.1 now.
i have successfully ported CWM Recovery to my ZTE Merit/Avail/Roamer using the CyanogenMod gingerbread source (i did not use the unofficial port that was built from the ZTE Blade because the screen is upside down)
everything works just like it is supposed to--absolutely flawless. build went through without a hitch.decided that i instead wanted to use the "home" key to select menu options in the CWM Recovery instead of the "power" button that is default (had to uncomment BOARD_HAS_NO_SELECT_BUTTON in the BoardConfig.mk because there is no camera button on this phone)
so i copied the recovery_ui.c from the working Blade source (which uses the "home" key instead of the "power" key), placed it into my ZTE Roamer (Merit/Avail) source and added BOARD_CUSTOM_RECOVERY_KEYMAPPING := /device/zte/roamer/recovery_ui.c to my BoardConfig.mk
there is no problem reading the location of the file so don't suggest to change it..but when i compile i get these errors and it is not built
Code:
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: out/target/product/roamer/obj/EXECUTABLES/recovery_intermediates/recovery.o: in function get_menu_selection:bootable/recovery/recovery.c:470: error: undefined reference to 'device_handle_key'
[code]....
who is not some novice that knows nothing about building a recovery.img from CyanogenMod source, i can use the home button instead of the power button. is there any easier way to change this than by using a custom recovery_ui.c?
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:
Quote:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00040000 "system"
mtd1: 00600000 00040000 "appslog"
mtd2: 06580000 00040000 "cache"
mtd3: 1a400000 00040000 "userdata"
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
Quote:
# 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.
My phone was working just fine and randomly the lock button stopped working and the home button brings up the power screen!
View 1 Replies View RelatedI 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?
View 4 Replies View RelatedSo 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 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
View 4 Replies View RelatedI'm on a Galaxy S2 running Gingerbread 2.3.4, my baseband version is I9100XXKI1 and my kernel version is 2.6.35.7-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'.
View 2 Replies View RelatedI 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.
View 1 Replies View Relatedi 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.
View 5 Replies View RelatedI just tried to install an custom rom at my Android, i unlocked it on HTCdev`s site, but i think i was a little fast with the DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
I then bootet the phone into fastboot, and did the command fastboot flash boot boot.img, this worked very fine but now the phone wont boot.
I think maybe the phone is unlocked, but it is S-ON. I have tried diffrent recovery modes with the fastboot flash recovery recovery.img etc, but none of them are working.
Now im sitting with a phone that wont boot at all, what to do?
Is it possible to keep going on with the custom rom install, or can i resett the phone into the stock rom?
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:
CODE:.......................
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 5.0.2.0 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'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 am using a verizon galaxy nexus
I got the cat /proc/mounts here -
Code:
root@android:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
[code].....
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
[URL]
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.
I have an htc one x. I recently flashed the cm9 rom and im not to keen on it so i know want to return to my old standard one.
When i go into recovery to try and restore my old rom it doesnt let me the phone just restarts and boots into the cm9 rom and not clockwork recovery. I think it would be a good idea to wipe the rom and clear my cache but i cant as i cant go onto cwm.
How to boot Xperia neo L in recovery mode using phone buttons ? I have tried so many combinations but not getting right way.
View 1 Replies View Related