I have ZTE Blade V880 with CM7.1 signed ROM. All of the sudden the home button doesn't work.
I tried booting back to recovery and try the test keys and confirmed that the home button is working there so definitely not a hardware issue.
Tried booting back but still it wont do anything.
Tried reflashing (without wiping) but still a no go,
I downloaded KeyEvent Display from google play,all keys responds except the home key.
So in short, Home button works on clockworkmod recovery menus but not working when the rom is loaded.
Currently using Button Savior as a work around but I want to know whats really wrong and fix it.
(BTW, my first post so call me a n00b )
It's an old rom, try CyanogenMod 7.2 or the latest nightly build from here: http://download.cyanogenmod.com/?device=blade You will probably need to wipe data too.
actual fix
wbaw said:
It's an old rom, try CyanogenMod 7.2 or the latest nightly build from here: You will probably need to wipe data too.
Click to expand...
Click to collapse
Been using the same rom for months now. Its the first time it hapenned. I can't go using nightlies because I am using my phone for work. Any Ideas aside from wiping?
Not really anything you can do except wipe. You can use Titanium backup to backup & restore any important app data. If it worked before then that rules out your phone being newer than the rom, it must just be a weird bug. Nightly builds of CM7 are stable for the Blade, I don't think there have been any real changes for months (since just after cm 7.2) & there aren't likely to be any further changes.
Did a full-wipe and flashed cm7.2, home button now works. Its still wierd it happened.
Sent from my Blade using xda app-developers app
Related
Hello All,
I would like to report that the newest version of ROM Manager which I have installed on my device caused a touch-screen problem.
I transferred the ROM to my SD card and used the newest version of ROM Manager to flash it.
After it was done, I turned on my device and found out the touchscreen completely broke. I could see the visuals on my screen, but I could not click on any buttons and the touchscreen is rendered useless.
I tried to manually enter the bootloader (switching off the phone, click once on the power button and hold on the vol down key until you see a white screen than click to recovery) to flash another ROM, but no matter which ROMs I flashed, the touchscreen did not work at all.
So I decided to RUU my phone back to it's original condition and send back to HTC (RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26 .03.02.26_M_release_155891_signed)
and after it complete the flash, the touchscreen works again.
So I would just like to conclude that the newest version of ROM Manager caused problems with ClockworkMod 2.X
Thanks.
Many ROM's HAVE to be flashed using version 3+ of Clockwork recovery.
Based on the fact that there are still a LOT of people that are using the same combination I would say this is a rare occurrence.
Thank you for your post but I urge people not to take this as a definite. May I ask why you chose to use 2X not 3x of recovery?
Mr_JMM said:
Many ROM's HAVE to be flashed using version 3+ of Clockwork recovery.
Based on the fact that there are still a LOT of people that are using the same combination I would say this is a rare occurrence.
Thank you for your post but I urge people not to take this as a definite. May I ask why you chose to use 2X not 3x of recovery?
Click to expand...
Click to collapse
For me ANY of newer recoveries higher than OLD ONE 2.5.1.3 doesnt work proeprly :/ Thay don`t restore my roms properly. I wish i could have newer one but all ot them causes bootlopps or tones of FCs after restore.
Thats why IM USING 2.5.1.3
Krzysiec said:
For me ANY of newer recoveries higher than OLD ONE 2.5.1.3 doesnt work proeprly :/ Thay don`t restore my roms properly. I wish i could have newer one but all ot them causes bootlopps or tones of FCs after restore.
Thats why IM USING 2.5.1.3
Click to expand...
Click to collapse
I used to get that, there's a certain way of doing it that I found works.
Restore a backup using the older CWM recovery
Boot into the ROM and flash CWM 3.x using ROM Manager
Backup the ROM using ROM Manager
ROM should now restore properly.
I've got the 405.3 version of Sense rooted as a backup that didn't work on CWM 3.x but after doing it this way it works fine.
If you have more than one backup then flash the older CWM and repeat the above steps. The way the older versions backup seems to cause problems if you try to restore using a 3.x CWM.
Sent from my Desire HD using XDA App
Cwm 3.x works fine with me, when the backup isn't from à 2.x one...
Sent from my Desire HD using XDA App
Me too, cwm 3.x works fine for me
Sent from my Desire HD using XDA Premium App
My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA
Tone-Fu said:
My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA
Click to expand...
Click to collapse
The new clockwork 5 has alot of issues. You should try to reflash clockwork mod 3 or 4
Sent from my HTC Vision using XDA Premium App
Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.
Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer
Nipqer said:
Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer
Click to expand...
Click to collapse
This. I think he's using the power button or volume buttons to move and select, which is incorrect.
You have to use the trackpad to scroll and select items.
So why are you trying to flash the new recovery through fastboot? Just pull your battery and boot into MIUI normally, then go to ROM manager and flash CWM 3.0.2.4, it will work. If it doesn't flash properly, go into the settings and select "wipe recovery before flash".
Tone-Fu said:
Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.
Click to expand...
Click to collapse
I have met the similar problems too.
and I solved it via reflashing the recovery using the ROM manager.
So you can reflash your clockworkmod recovery 5.0.2.0 by ROM Manager, I guess that will work.
Cheers for the replies Nipqer & martonikaj.
The trackpad thing might be the issue but I can't tell because my wife's gone out with the phone! I'm used to using the recovery on my GS2 and DS2, which doesn't have the trackpad etc. so I may well have been using the volume rocker and power key on muscle memory.
Though it is interesting that that method obviously worked in previous iterations of the recovery.
Oh and in answer to your question I was trying to use FastBoot because I perceived the problem to be due to the flash via ROM manager.
@Sunkins - Yeah, I think ROM manager was working just fine. The problem seems to be down to the man in the loop! Cheers for the advice, mate.
I would recommend recovery 3.0.2.4 as it is rock solid, and seems to be the most reliable.
I made the switch from CM7 (froyo kernel) to MIUI Gingerbread a few days ago.
The "cool factor" on my phone has definitely improved. MIUI is sweet! I've no idea why I held my nose up to it for so long.
Anyway.
It seems The DXC 1.9.23 MIUI that I flashed seems to have automatically updated me to CWM 5.0.2.0.
Bummer. My understanding is these backups aren't compatible with 2.5.0.7?
I THINK that may have something to do with my problem...maybe.
I can't seem to get the "Power Menu" to reboot me into CWM.
I wanted to flash my old BootAnimation back on now that I've decided to stick with MIUI.
Holding the power button and selecting Reboot into CWM brought up an expected SU dialog.
I accepted. I'll attach a screenshot of the package...as it just seems funny to me.
Nothing happens.
No reboot. Nothing.
All the other options work.
Hotboot...bootloader...stock recovery...reboot...
https://lh3.googleusercontent.com/-v...001_063054.jpg
Also, that file on my SD card that it's referencing to doesn't seem to exist.
But I've no idea if that is normal or not.
=] <----Noob.
Rebooting into CWM via ROM manager works fine, however. So I'm confused.
Any ideas?
Hey Jubakuba! I too recently installed MIUI on my Droid X over the Gingerbread kernel. After searching through multiple forums and posting all my troubles, I've come to the conclusion that MIUI and CWM don't play so nicely together. Apparently you must use ROM Manager for all flashing, backups, and recoveries. I was using Droid2Bootstrapper and it caused my phone to factory reset every time, the result being a loss of any settings I had on MIUI (it looked like I just flashed it), Torch not working at all, themes not working, and a factory reset on every subsequent reboot. Try using ROM Manager for all your backup/flashing needs. I'm putting MIUI back on my phone as we speak and I'll be testing ROM Manager out. If you need me to post my results, I will. Good luck!
Sometimes you have to reflash CWM after installing a new ROM. Do it through ROM manager and see if that helps.
So i just installed the freegs4 rom and i have done everything according to the forums including reverting my twrp installer and it installs and works just fine until i have to restart the device. As soon as the device is restarted it freezes at the samsung splash screen and i have to wipe the rom again and reinstall. Ii can use it until i have to reboot then it same thing all over again
bigdaddybx2 said:
So i just installed the freegs4 rom and i have done everything according to the forums including reverting my twrp installer and it installs and works just fine until i have to restart the device. As soon as the device is restarted it freezes at the samsung splash screen and i have to wipe the rom again and reinstall. Ii can use it until i have to reboot then it same thing all over again
Click to expand...
Click to collapse
Make sure you dont have a bad download. Also try flashing a different kernel. Btw this goes in the question section
ROMANTiC KiD said:
Make sure you dont have a bad download. Also try flashing a different kernel. Btw this goes in the question section
Click to expand...
Click to collapse
I have tried different downloads and when i use a different kernel the wifi will not turn on, i have also done the md5 validation on the rom and its fine. sorry about posting in the wrong area im new to this.
Sounds like your phone might be in factory mode.. Did you wipe EFS in recovery?
Sent from my SPH-L720 using Tapatalk 4
bigdaddybx2 said:
So i just installed the freegs4 rom and i have done everything according to the forums including reverting my twrp installer and it installs and works just fine until i have to restart the device. As soon as the device is restarted it freezes at the samsung splash screen and i have to wipe the rom again and reinstall. Ii can use it until i have to reboot then it same thing all over again
Click to expand...
Click to collapse
When it freezes on that first reboot, try a battery pull and see if it will boot. If it doesn't, try another battery pull.
Mine actually did that a few times too (freeze on the SAMSUNG screen after first reboot).
freegs4
i have a question i had 2.0 working great.
i have tryed to update to 3.0 multible times.
i went from stock md5 right to 3.0 and have issues with the phone rebooting it works ok but once restarted it will not start back up. i also cant get wifi to work.
i have even downgraded to twrp 5.0.2.
i have flashed my phone back to stock md5, than root than wipe everthing than 3.0 and same issues.
i flashed back to stock md5, than root than stock md9 than wipe than 3.0 still issues
i flashed to rooted and odexed md9 wipe than 3.0 still issues.
i have download both direct and torrent and still stumped why the phone freezes after it reboots and no wifi at all after installation.
anyone have any clues?
tabodt said:
i have a question i had 2.0 working great.
i have tryed to update to 3.0 multible times.
i went from stock md5 right to 3.0 and have issues with the phone rebooting it works ok but once restarted it will not start back up. i also cant get wifi to work.
i have even downgraded to twrp 5.0.2.
i have flashed my phone back to stock md5, than root than wipe everthing than 3.0 and same issues.
i flashed back to stock md5, than root than stock md9 than wipe than 3.0 still issues
i flashed to rooted and odexed md9 wipe than 3.0 still issues.
i have download both direct and torrent and still stumped why the phone freezes after it reboots and no wifi at all after installation.
anyone have any clues?
Click to expand...
Click to collapse
Try a different kernel
Sent from my SPH-L720 using xda app-developers app
So i got my phone replaced and installed the software on it and im no longer having the issue i stated above but i do have a new issue with the call recording. I installed it through the aroma installer and then used update me to install it manually like i was reading in the thread. Everytime I try to make a call (with out even pressing the record button) the screen goes black and there is some call recording icon in the left hand side of the status bar. soon after this i get an error that says com.android.phone has stopped. I have tried to reinstall stock with out call recording but it keeps doing it as if the call recording is there. Am i forced to reset and reinstall the rom?
You might want to give Highway55's MF9 ROM a shot. It has the wifi hot spot mod *and* the status bar toggle already built in. I wrote lengthy post on 9/26 detailing my experience with Highway55 along with the simple steps I took to implement the additional mods that I wanted (including call recording).
ROMANTiC KiD said:
Try a different kernel
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ROMANTiC KiD said:
Make sure you dont have a bad download. Also try flashing a different kernel. Btw this goes in the question section
Click to expand...
Click to collapse
I think the FreeGS4 ROM has its own AGAT custom kernel. So I don't think you want to do that...
And I've had a few issues with V3.0.0 myself. I just downgraded back to V2.0.0
Salil999 said:
I think the FreeGS4 ROM has its own AGAT custom kernel. So I don't think you want to do that...
And I've had a few issues with V3.0.0 myself. I just downgraded back to V2.0.0
Click to expand...
Click to collapse
Ive had everything running good with chronic kernel and also tested with the kernel it comes with. No problems really.
Sent from my SPH-L720 using xda app-developers app
I loved the built in ad-blocker, but noticed it interfered with hulu plus, watch ESPN, and sometimes xfinity player. I've since removed the ad blocker, but was wondering if there was a work around so that I could keep the ad blocker, but have it not block ads for these apps? Or is there a way to get these apps to work with the ad-blocker in place?
I'm a bit of a newbie with rooting and flashing but have been pretty successful up until now. I installed TWRP 2.3.6.2 and CM 10.2 on my Verizon LG G2 about a month ago.
Since then I've been updating with nightlies with much success.
When the 11.0 build showed up in the CM updates list I downloaded it and installed. It failed and I had to flash an older 10.2 nightly. My device became pretty unstable after this. Most GApps were gone or somehow corrupted. I re-installed a number of them but Google Play still didn't work.
I tried updating again to an 11.0 nightly today and again it failed. I then flashed a recent 10.2 nightly that had worked for me and now my phone is stuck an infinite spinning Cyanogenmod boot screen.
I have tried every combination of holding power and volume down to try to get into TWRP to try flashing another nightly but my device just continues to reboot to LG then Cyanogenmod spinner over and over.
I decided maybe I needed to reinstall TWRP (looks like there's a new version from today). I tried to access my device with it plugged into my computer using fastboot and adb push loki_flash and it returned "device not found."
I'm totally stuck now... no idea what to do next. Would be so grateful for some guidance on how to get my device functional again.
Thanks.
One additional comment: I've tried doing Power + Volume Down during LG logo but it doesn't do anything.
I managed to get into a Hardware Key Control Mode screen by holding Power + Volume Up + Volume Down which had some options about answering calls or turning off alarm using hardware keys.
Cannot seem to do anything to get to TWRP.
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
tophy0 said:
I somehow just managed to get to a screen that says "Factory hard reset. Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel." It says "Rooted" in the upper left corner.
The screen doesn't respond to Volume Up or Volume Down and I just let it sit there for a few minutes. It reverted back to the infinite CM spinner.
At this point I'm pretty much at a loss for what to do -- and afraid to do anything to mess things up even more.
Should I be trying to go back to stock? http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This screen is what you want to see. Push Power a couple of times. It won't erase your settings. It'll boot into TWRP.
tophy0 said:
Thanks for this suggestion -- I'll try to get back to that screen and do this. Also the CM spinner was stuck for 8 hours last night... so definitely not a function of bit of a delay for first install of a custom ROM.
Click to expand...
Click to collapse
Phew, that worked! Back into TWRP.
Any additional guidance on what I should be doing to try to get back into a stable version of CM? I have many builds of CM 10.2 in internal storage that I could pick from. But before I try another one of those should I attempt to clean things up at all? Seems like my current configuration must have some sort of conflict that's leading to all the instability. I do have Titanium Pro installed so I believe I should be able to get my apps + data back as long as I don't completely clean out everything.
Thanks again for the help.
Also mods: just realized that I should have posted this thread in Q&A not General. Sorry about that! I don't think I can move it over myself or I would.
I think what I would like to do now is update TWRP to 2.6.3.3 and then install 11.0 using this build: http://www.droidforums.net/forum/lg-g2-development/258385-rom-wip-cyanogenmod-11-g2-vzw.html
Not sure how to update TWRP from 2.6.3.2 to 2.6.3.3 though. When I originally set up TWRP I used adb / loki-push but it's a bit of a blur how that worked since I was just following step 1-2-3 instructions.
Sorry for being such a noob with this stuff. Any additional guidance would be awesome.
As I suspected, flashing any CM ROM now leads to an infinite CM spinner so I think I need a plan B to get my device working again. At least I can now get to TWRP thanks to the help above.
Not sure where to go from here.
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Makrilli said:
Did you try to wipe data, cache, dalvik cache and system? Then install cm. I think this is why you got a bootloop :/
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
tophy0 said:
Yup, when I finally got into TWRP I did this and was able to install a version of CM 10.2 that actually loaded.
All my apps and settings are obviously gone now so it's a good time to make the leap to TWRP 2.6.3.3 and CM 11.0. Trying to figure out how to do that now (in the proper forum!):
http://forum.xda-developers.com/showthread.php?t=2563982
Thanks for the help.
Click to expand...
Click to collapse
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
madisonjar said:
I htink the wipe would have helped from the beg. Any time you jump roms I suggest doing a wipe. Also one thing you may want to look at is a backup of all your settings and everything, I use titanium and it has helped me out in situations like this in the past.
Click to expand...
Click to collapse
Thanks, makes a ton of sense.
I also use Titanium to backup. When I do a fresh install of TWRP and CM 11.0 can I restore my system data in addition to apps + app data? I'm not sure to what restoring extent system data could create conflicts with the CM 11.0 build. For example will all the Google Mobile Services system data from my CM 10.2 build create conflicts?
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
tophy0 said:
What I really want is to easily bring back ~150 apps + all of my SMS messages, Contacts, Email settings, Homescreen layout and settings, etc. Not exactly sure what's achievable.
Click to expand...
Click to collapse
You can safely use TB to restore user apps, their data and trebutchets data if you use that. Backing up sms and contacts with TB, I'm not sure about that as I used other app "super sms backup". And about emails I have no idea. Also it's not a good idea to restore settings, better to set them again
Sent from my GOOPHONE i5C using XDA Premium 4 mobile app
antinorm said:
To get to TWRP:
* Hold Power until the phone shuts off
* Hold Power+Volume Down until the LG logo appears
* Release Power+Volume Down then immediately hold them both down again
You'll get a message to the effect of 'Press Power to permanently erase all user settings.' Do that (if you have a custom recovery installed, it'll just boot into that).
Also keep in mind that the first install of a custom rom like CM will sit on that logo screen for a couple of minutes.
Click to expand...
Click to collapse
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
WCM3 said:
I owe you man! Saw the erase data screen and almost freaked out. Pressed power and it booted to TWRP.
Thanks again!
Mike
Click to expand...
Click to collapse
You know, I was wondering as well of how to get to TWRP if a rom didn't boot. I got to that screen too and thought it would erase the phone. This is good to know and should be a sticky somewhere.