I 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.
When 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.
my galaxy s2,it is rooted,and i have another problem : the phone restarts by itself and gets stucked in the boot loop, i never flashed a new rom ,it is running the stock rom,Someday i needed to factory reset the phone so i rebooted into recovery mode (power + home button +vol up) ,. I booted into recovery mode but the power button does NOT react as 'select' button although it works just fine for power on and off. I select a function and press [power] an the first line becomes the selected. pushing it again just flashed the screen. But pressing it long turns the phone off,and even after the factory reset from phone directly(with out going to recovery mode)
I have android 4.0.4 recently i flash recovery and boot with TWRP recovery img accidentally with rom installer now my android is not booting no factory mode worikng nor recovery mode.. i am unable to connect android with pc becuase its shuted down..
My 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.
After installing cwm recovery twice, now my tablet(micromax fun book pro)does not boot..it only goes in recovery mode on starting...Major problem is, in this recovery mode my volume keys have stopped working , only power button works for for selecting 1st option I.e reboot.
So unable to do anything, can't even select a ROM backup that I have in SD card..
I flashed + rooted (strangely in that order, which means I must have rooted my phone ages ago.. and then locked my bootloader after flashing..?)...
I do have Rom manager installed... but I don't quite recall how I ended up flashing the stock rom onto the phone.. Anyways, as I did seem to reset my phone, I upgraded all the apk packs and I'm pretty happy with the speed upgrade + ext2 internal space expansion.
As I now want to create a nandroid backup, so I can always come back to my current status, when I want a clean reinstall..!
My main question is that as I seem to have skipped creating a CWM recovery... if I do so now, will I loose all my data and go back to the basic stock rom?
The problem I'm facing right now is that I'm unable to boot into the recovery mode using either "adb reboot recovery" or the power on + vol buttons / menu button. (which means that I don't have the recovery mode installed.....)
So.... will I loose my current upgrades + phone settings (reset into factory mode), if I flash the recovery mode?
- home button is not working - call button is not working unless you're into the contacts application (doesn't work from home page) - Astrid application has lost all of the TODO tasks. - It doesn't asks for the unlock graphical code!
It lost all of its battery yesterday night while surfing on the browser. My phone is an HTC MAgic Vodafone, using Android 1.6 Any ideas on how should i proceed? I soft reset the phone already.
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 am a new member and a relatively new owner of an X10i. Overall I am happy with the phone but I am hoping some can answer a question. When I press the home button (middle one) I get a prompt to select to 'Complete Action using Home or Timescape' This is quite annoying. I want the default action to be Home (not Timescape) but despite ticking the box in the prompt it still pops up this box.
I have a strange problem after using cm10 for a few weeks. suddenly my home and volume buttons aren't working most of the time. When I want to decrearse/increase volume and press the volume button (no matter if i press it fast again and again or if i wait a few second between pressing) it only goes one step louder every 5 seconds. Also when I want to lower volume. i also cant use cwm recovery cause my home button only works maybe once per hour. Now I have twrp touch recovery.
What i tried: - wiped everything several times - flashed gb and ics stock firmwares - flashed different kernels
I have rooted my phone a couple of times and the last time I did it ran really hot (as hot as 107 degrees) so I did a factory reset and after words it runs fine other than the fact that the lock screen and the home Key dont work anymore.
So I have stock android 2.1 installed on my phone. I haven't gotten the OTA update. I tried to manually update, but recovery mode doesn't seem like its working - I see the triangle/question mark but there is also a phone laying down right next to it. No combination of keys will get me to a menu to apply the update.zip. I tried flashing back to 2.01 and 2.0 and updating from there - but the recovery mode stayed the same. Does anyone know where to find the full Froyo stock .SBF files?
Friends of Jupiter Huawei g525-u00and have been asked Ram Kastvm able but Alanmshkl. Already green screen after power ... not that fast boot mode will not go into recovery mode and not the original ROM using loam bottom half Vbala White gets going
Couldn't find exactly what I was looking for in the forums. Yesterday, my home button stopped working on my Motorola Droid (1). It just gets really aggravating when I'm in the browser and I have to keep hitting back until it exits. Does anyone know if there is any way to fix this?
With in the last week or so my home button doesn't seem to want to work. It will work for a while, but out of the blue it stops. I have to turn my cell phone off, turn it back on and it starts to work again.
Until it stops working again.
Anyone having the same issue? Anyway to resolve it?
I have a Samsung Galaxy S Plus where, after flashing CWM with Odin, and installing cm11, I'm stuck on an infinite boot animation. But that is not the big issue. I need to enter Recovery Mode, where I have a backup, but the problem is that my Volume Up button is not working, so I can't use the Power Button and Volume Up(I also don't know what could possibly wrong with it) one to get there. So I was wondering if there is some other method to enter Recovery, I suppose by computer. I think that when I used Odin, the device restarted being in Download Mode, and I think that it hasn't to be On to do that.
I guess as I rooted my att GS3 just fine and flashed a new aokp rom and was up and running but started to have intermittent flickering. It prompted me to reflash rom with CM10 and this is were my problems began. I wiped data/factory reset, cache partition,Dalvik cache, mounts & storage format cache, and accidentally format emmc which I think is my problem. I was able to still reboot to CWM recovery but I can't do much more than that, and now I can't get to CWM recovery mode at all. Have tried to boot and reflash from ex/sdcard no good. PC doesn't recognize phone to do recovery from backup and I didn't do internal backup which I now know was dumb. Is there anything I can do to get back up and running or did I screw myself and have to get a new phone?
However, now when I try to install Cyanogenmod I can't get into recovery?? When I go into bootloader, at the bottom it says "Fastboot Status - FAILInvailed Command". And when I click on Recovery, the Google logo shows up with an unlocked image below it. It flashes a few times and then reboots the phone regularly.
i have rooted my karbonn A7+ successfully after that i did a big mistake... i have flashed rom without CWM recovery..i did this=> opened power button + volume up key for recovery mode and applied direct rom through the option apply update from sd card in result i found that my mobile got stuck on boot animation.. after that i've cleared user data and wipe partition chache and now its showing BLUE SCREEN only .
I've just bought an Oppo phone (with MTK6589 chipset.) 2 days ago I decided to root and flash CWM recovery to my phone. Rooting gone well and the phone is now rooted. Then I flashed CWM with Mobile Uncle Tool. It said that I flashed sucessfully, I got no error. But when I reboot the phone to recovery mode, nothing happend, the phone just did a normal reboot! I tried to flash other third-party recovery mode such as TWRP and MIUI recovery but I got the same problem: the phone couldn't get into recovery. The screen with a text "Recovery mode" appeared in 3s and the phone just did a normal reboot. I couldn't even format factory, all I got was just a normal reboot. I even tried many tools on Google Play and MTK flashtool but there were no hope. Now my phone is working normally but can't get into recovery mode.
before doing anything , when i enter the recovery mode it shows a picture of an Android and a Triangle next to it " Which should be the background image of the recovery mode " and there's no menus or anything , nothing appears even if i press power or volume buttons
So now after i rooted the phone , installed another recovery.img with MobileUncle , it just keeps stuck on the phone's logo and doesnt even show that triangle picture and it doesnt show anything but the phone's logo
I tried a lot of different recovery.img files but none worked, Then I tried a recovery img that worked for another guy who has the same mobile kind , it worked for him but didnt work for me
Even after flashing it with MobileUncle , still i get the same problem..
All what i edited in the root files was the boot sound and animation and i even restored the stock ones back and still the same problem
and the last_log file in System(Root)/cache/recovery Includes this
PS : Oct 15 is the last day i ran the stock recovery that only shows up the background image of recovery .. So all the recovery runs after flashing new recoveries till Oct 23 arent logged in last_log..