Hi there,
I've got CM10.2 running on my TF201 (currently on version from 20131211), it all works a lot better than before, thanks for the good work!
I am not allowed to respond in the thread about this rom since I'm to new here, hence in Q&A.
There are two things that I do not yet understand, and haven't found anything on in the entire thread:
the power button doesn't seem to work anymore, I can only reboot via a special app...can I even turn the tablet on again if I turn it off? I don't want to turn it off right now
the buttons in the nav bar are in the middle, how to get them back to the left? especially with the dock attached the center buttons are hard to reach...
Any suggestions/hints/tips/tricks?
more questions
Hi again all,
Like several others also reported, in my case my micro hdmi port no longer seems to work. Has anyone found a workaround for this yet?
And finally, the least of the issues, but I wanted to list it anyway: all of my keys on my dock-keyboard work, except for one: the power-off or lock-button (top row, rightmost button). A long shot perhaps, but could this be related to the other (main) powerbutton not working as it should?
All ideas and suggestions are appreciated,
Cheers,
Peregr1ne
power button works differently
Peregr1ne said:
the power button doesn't seem to work anymore, I can only reboot via a special app...can I even turn the tablet on again if I turn it off? I don't want to turn it off right now
Click to expand...
Click to collapse
Having used it for a while now, I found out that that the hardware power button on the tablet in fact does still work...but it works differently...
Under normal conditions when using my Prime (like now), it does not work: there is no way to "lock", power down, or reboot the tablet with hardware buttons; fortunatly there are apps available to trigger this software-based.
When the tablet is "sleeping" an attached to its dock, folding open the dock wakes the tablet up, and the power button is not required (nor doing anything if pressed).
If the tablet is sleeping but not folded closed or not attached to the dock however, the power button does activate the screen and bring up the login screen.
Anyone any ideas? Is this a setting I can adjust myself? Do I have to install something (a driver of sorts)?
All help is appreciated...
Cheers!
Peregr1ne said:
Having used it for a while now, I found out that that the hardware power button on the tablet in fact does still work...but it works differently...
Under normal conditions when using my Prime (like now), it does not work: there is no way to "lock", power down, or reboot the tablet with hardware buttons; fortunatly there are apps available to trigger this software-based.
When the tablet is "sleeping" an attached to its dock, folding open the dock wakes the tablet up, and the power button is not required (nor doing anything if pressed).
If the tablet is sleeping but not folded closed or not attached to the dock however, the power button does activate the screen and bring up the login screen.
Anyone any ideas? Is this a setting I can adjust myself? Do I have to install something (a driver of sorts)?
All help is appreciated...
Click to expand...
Click to collapse
I surely cannot be the only one facing these issues?
Is there really no one that can tell me has tips for me?
Regarding rebooting, as far as I can remember, the prime will boot if you plug it in to the charger.
Sent from my LG D802
Makrilli said:
Regarding rebooting, as far as I can remember, the prime will boot if you plug it in to the charger.
Sent from my LG D802
Click to expand...
Click to collapse
Ahhh, that is a reassuring thought, thanks!
I have not yet power it down, but I'm sure that will happen sooner or later, good to know it should power up in that case...
Peregr1ne said:
Ahhh, that is a reassuring thought, thanks!
I have not yet power it down, but I'm sure that will happen sooner or later, good to know it should power up in that case...
Click to expand...
Click to collapse
not sure myself, but maybe its the CM10.2 thats causing those problems?
have you tried going back to more of a stock ROM and try?
lil-devil said:
not sure myself, but maybe its the CM10.2 thats causing those problems?
have you tried going back to more of a stock ROM and try?
Click to expand...
Click to collapse
I agree, most likely it has to do with the rom, and I probably should try downgrading to confirm so.
I was hoping to run into someone who had run into the same issue and found a solution.
I'm not allowed to post in threads any place but here - yet...but a few more posts and I can
Peregr1ne said:
I agree, most likely it has to do with the rom, and I probably should try downgrading to confirm so.
I was hoping to run into someone who had run into the same issue and found a solution.
I'm not allowed to post in threads any place but here - yet...but a few more posts and I can
Click to expand...
Click to collapse
i guess just search the thread and read... cause most of those people actually don't go to these question threads
lil-devil said:
i guess just search the thread and read... cause most of those people actually don't go to these question threads
Click to expand...
Click to collapse
erm...I did, I went through all 21 pages...and I didn't find answers to the questions I stated above
Peregr1ne said:
I surely cannot be the only one facing these issues?
Is there really no one that can tell me has tips for me?
Click to expand...
Click to collapse
Same here. Power button and lock button work for some time after reboot. But touchpad disabling does not work at all.
I think I did not see it w/ 10.1 and not with early 10.2.
Touchpad enable/disable works for me, only the lock-button doesn't work.
Peregr1ne said:
Touchpad enable/disable works for me, only the lock-button doesn't work.
Click to expand...
Click to collapse
You'll probably get it to work if you take it away from the dock and use vol down and up buttons for a couple of times. For me it helps and after that the lock works for some time.
Just installed the latest CM 10.2 UNOFFICIAL on Saturday night. Started with the official 4.1.1 JB from ASUS (10.4.2.18), unlocked, made NVFLASH recoveries, flashed TWRP 2.6.3, then flashed the CM ROM. Works great, including the power button. Don't have the keyboard dock, so can't speak to those problems. Only real issue for us was make sure you clear all the stuff before you flash the ROM (and we did it again after as well).
Enjoy.
Cm 10.2 gapps?
ahw609 said:
Just installed the latest CM 10.2 UNOFFICIAL on Saturday night. Started with the official 4.1.1 JB from ASUS (10.4.2.18), unlocked, made NVFLASH recoveries, flashed TWRP 2.6.3, then flashed the CM ROM. Works great, including the power button. Don't have the keyboard dock, so can't speak to those problems. Only real issue for us was make sure you clear all the stuff before you flash the ROM (and we did it again after as well).
Enjoy.
Click to expand...
Click to collapse
Quick question....just unlocked my TP tonight, made all necessary backups, and want to flash the same CM 10.2 that you mentioned. Does the Rom come with GAPPS? I've read in the past that CM Roms don't include GAPPS. If not, how did you install/load them?
Thanks.
You are correct - the CM ROM needs the GAPPS loaded as well. Once I had the recovery module in I loaded the ROM and GAPPS together. The version I used was gapps-jb-20130813-signed.zip. Also it seems that TWRP likes to have the md5 checksums there as well. I seem to recall I got the checksum file for gapps along with the zip, but I had to generate my own for the CM ROM.
Thanks for the response. Downloaded gapps, and will give it a shot. I've got the Flatline recovery utility installed (and not TWRP). Not sure if one is better than the other, graphical presentation aside.
Lavman72 said:
Thanks for the response. Downloaded gapps, and will give it a shot. I've got the Flatline recovery utility installed (and not TWRP). Not sure if one is better than the other, graphical presentation aside.
Click to expand...
Click to collapse
Update: Installed TWRP, flashed CWM 4.3.1 CM-10.2 Cyanogenmod 10.2 Unofficial. So far so good. Haven't really noticed or experienced the "new tablet" feeling that has been mentioned just yet. I'll give it a few days to settle in.
Related
My touchpad has been getting crazy force closes within just starting up, I can't do anything I installed gapps, and now nothing works, not even moboot. I have tried webOS doctor to no avail. wtf am I supposed to do with my brick now?
Garrett07 said:
My touchpad has been getting crazy force closes within just starting up, I can't do anything I installed gapps, and now nothing works, not even moboot. I have tried webOS doctor to no avail. wtf am I supposed to do with my brick now?
Click to expand...
Click to collapse
can you boot into recovery at least?
Mine died also. It is like the battery is completely dead but I charged it overnight. Cannot put in usb mode or anything. Even plugging it into a pc does nothing .
I held the power and center buttton for 15 seconds and the screen came on saying I needed to plug it in.. charging it again now. But might be all right...
Sent from my YP-G70 using xda premium
duglas said:
Mine died also. It is like the battery is completely dead but I charged it overnight. Cannot put in usb mode or anything. Even plugging it into a pc does nothing ....
Think cm7 killed my touchpad also..
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Have you tried long pressing HOME + POWER?
have you tried WebOS Doctor to restore back to stock?
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if you got any love. You won't be the first or the last to get this issue.
I also had the black screen. Had to do the pwr + home to get it back. It may be because it was on really low power when I left it on my Touchstone. Oddly enough it was fully charged when I got it to turn on.
hydrogenman said:
can you boot into recovery at least?
Click to expand...
Click to collapse
Yeah I got it all the way back to where moboot is off and webOS is the only thing running but if i just install cwm and cm7 i still get the force closes from gapps, I've even tried wiping data cache and dalvik from cwm but it was a no go.
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
I can't switch on my HP Touchpad ! Mine don't respond to power and to reset neither (power + home + volume up).. Have you got any idea ? She's got batery and is plugged on sector !
pulser_g2 said:
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
Click to expand...
Click to collapse
Dude I got it to boot. Its obviously one of the many bugs, I had it working fine until gapps installed, you're not so high and mighty that you can tell other people what the deal is so come off it.
pulser_g2 said:
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
Click to expand...
Click to collapse
Good job, you got yours to work just like thousands of us did. But this is a alpha release and there is bound to be some bugs that people are going to encounter. If your really a "developer" Im sure you have messed up devices too before. Dont be such a queen douche about it.
lancelot54 said:
I can't switch on my HP Touchpad ! Mine don't respond to power and to reset neither (power + home + volume up).. Have you got any idea ? She's got batery and is plugged on sector !
Click to expand...
Click to collapse
Just hold down the power button and the middle button until the hp logo comes up, might take 15 seconds or longer, i woke up with both my touchpads off and unresponsive, after doing the above they are both on and fully charged.
friken amen
pulser_g2 said:
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
Click to expand...
Click to collapse
You're so right dude, I pretty much know what I'm doing and even I got a bit freaked when I got the black screen but I read the docs and went to the issues log to find he answer just like it says. This is an alpha release, albeit an absolute triumph in itself, and improvements will come.
Check the issues log peeps before clogging up the forums, the last few threads here are all answered or logged at least.
If you don't understand the instructions you shouldn't be following them! No offence to Garret though, I'm sure his is a real issue.
Garrett07 said:
Dude I got it to boot. Its obviously one of the many bugs, I had it working fine until gapps installed, you're not so high and mighty that you can tell other people what the deal is so come off it.
Click to expand...
Click to collapse
theusername said:
Good job, you got yours to work just like thousands of us did. But this is a alpha release and there is bound to be some bugs that people are going to encounter. If your really a "developer" Im sure you have messed up devices too before. Dont be such a queen douche about it.
Click to expand...
Click to collapse
Hahahahahahaha.....this is some funny stuff. You don't even know your *****ing about. Is pulser a "developer"?! That is too rich.
Question...
if you turn it off... (hold down the power + the home button for ~ 20 seconds)... then volume up and power do you get the USB symbol on the screen? If it's still not responding at all, try pluging it into the wall with your power brick for 5-10 minutes then try again...
If you can get the usb symbol, it's not bricked...
It may not be happy, but it's not bricked.
If you feel excitable... you can google for instructions on how to recover from precentral... ('cause you'll likely need to get your hands dirty and play with lvm via novacom to fix it)
You could try calling HP, but remember you chose to void your warranty when you loaded android...
Trickman2 said:
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if you got any love. You won't be the first or the last to get this issue.
Click to expand...
Click to collapse
Worked for me after I nerfed one crucial part of the install.
I think I'll wait till its out of beta to give it a whirl. I hate that feeling of not knowing if I messed up. I've had that feeling too many times going way to the days of my g1.
I don't think its cool to blame cyanogenmod for something you did to your device.
I leave it booted into webos overnight just to make sure and I can also charge it with the touchstone as it doesn't seem to work in android :-(
Sent from my HTC Sensation Z710e using Tapatalk
Is anybody having problems getting clockwordmod to work. After I flashed it, it loads, but none of the options take me anywhere. All the options on the recovery take me to a black screen with a hat. Let me know if you've gotten clockmod recover to work, and how you did it? Thanks
i am stuck too, cannot get out of black screen with hat
Not sure which version you're using. But the one on the development section had issues.
Sent from my EVO using XDA
shook187 said:
Not sure which version you're using. But the one on the development section had issues.
Sent from my EVO using XDA
Click to expand...
Click to collapse
I simply downloaded rom manager and told it to flash clockworkmod. So I'm not sure why I'm experiencing this problem. I even re-flashed it several times.
Use the Camera Button!!
mark22179 said:
Use the Camera Button!!
Click to expand...
Click to collapse
Lmao, took me five minutes to figure thus out. Now I don't feel so dumb
Sent from my ltEVO using Tapatalk 2
last i heared CWM was still broken. make sure it has been fixed before you use it. it would corrupt the /misc partition and it takes a few steps to get it fixed when you flash out of CWM into TWRP
Spyderekz said:
last i heared CWM was still broken. make sure it has been fixed before you use it. it would corrupt the /misc partition and it takes a few steps to get it fixed when you flash out of CWM into TWRP
Click to expand...
Click to collapse
Sorry I never came back to the thread, but I believe you are correct. I don't believe CWM works on the EVO LTE yet of what I've heard. As a result I'm just using TWRP which works great.
if you guys get stuck in clockwordmod, simply go to the main menu of it but hitting power button, then HOLD power button... capac lights will blink a couple times, and the device will reboot.
had this same issue.
also, use twrp for now. instruction to flashing it via terminal emulator is on their site! very useful and straight forward method! good luck
Use TWRP and for gods sake done use ROM manager.
Learn how to do things in recovery. Its painfully easy and work 100% of the time. Unlike ROM Manager.
Rom Manager cant save you when it causes a problem and the phone bootloops.
You can also install it via the goo inside app
sent from my EVO LTE
all you guys that are trying to use clockwork are not doing enough research or something because i have seen it over and over a thousand times that its not working for this phone. you have to use TWRP!!! dont ya think something is wrong when everyone thats trying to use it is having problems? lol
I've been running CM as my recovery for a couple weeks now. Sometimes in ClockworkMod, repeated use of the volume up/down buttons can trigger a 'back button disabled' message. When this happens, it becomes unable to select any of the menu options, leaving you with just the logo until you hit power again. For the CM version on the LTEvo, for some reason, the 'back button disabled' mode is the default starting point.
To overcome this, simply repeatedly press volume up &/or down in rapid succession; it usually takes me less than 10 seconds of pressing them. You will know that it worked when you see a message at the bottom stating 'back button enabled'. At this time, you can navigate and select menu items as normal.
Its still not 100% functional as a recovery, however, as USB storage does not work yet.
I've also been using ROM Manager to facilitate my back ups and restores with no problem.
So why would you use a non functional recovery over one that works 100%
Rxpert said:
So why would you use a non functional recovery over one that works 100%
Click to expand...
Click to collapse
For me, its just a matter of personal preference. TWRP is cool, and I used it initially when brought my LTEvo home and rooted it. However, I've used CM since my OG Evo, and I like it. Its simple, fast, and does what I need (except for the storage part, but then I only use that when I forget something).
geniustheanimal said:
I've used CM since my OG Evo, and I like it.
Click to expand...
Click to collapse
Strike 2
I understand that you want choice, but recoveries are probably the most important part of the phone for a rooted user.
Rxpert said:
Strike 2
I understand that you want choice, but recoveries are probably the most important part of the phone for a rooted user.
Click to expand...
Click to collapse
I don't disagree with you here. Nevertheless, I've been able to use CM for all the essentials I've required of it (namely wiping, flashing, backup, & restore) with zero issue. I may revert back to TWRP for the USB mounting, as it saves me restoring, loading, adding something, and then re-wiping again if I forget something when flashing, but I have no qualms hanging with CM for the time being.
Sent from my EVO using xda app-developers app
geniustheanimal said:
For me, its just a matter of personal preference. TWRP is cool, and I used it initially when brought my LTEvo home and rooted it. However, I've used CM since my OG Evo, and I like it. Its simple, fast, and does what I need (except for the storage part, but then I only use that when I forget something).
Click to expand...
Click to collapse
Yeah, I've been using CM for the same reason, I already know it and trust it. But I already switched to TWRP, and I figured it all out now, so it works.
Not trying to troll or anything, but the majority is correct. Clockwork is down and there is no telling when it will get fixed to work with our Evos. TWRP has been around for quite some time now and is trusted, so why not just stick with what's working? Especially when it comes to the important functionality like recovery.
XDA Premium
TWRP is superior: you can queue up files to flash. Plus, its touch interface is about a million times better than CWM's.
I recommend switching. If you're familiar with CWM, you might be wary (I was at first too), but you'll never look back.
Does anyone know if the internal power button board is connected to the board via mylar flex cable like the i9100? The button has quit on my daughters phone and was wondering if the button was the same as the international version. I can solder it in myself but wanted to make sure they were same before I ordered it. Google and XDA searches haven't turned up much. Thanks.
beaverslayer said:
Does anyone know if the internal power button board is connected to the board via mylar flex cable like the i9100? The button has quit on my daughters phone and was wondering if the button was the same as the international version. I can solder it in myself but wanted to make sure they were same before I ordered it. Google and XDA searches haven't turned up much. Thanks.
Click to expand...
Click to collapse
Don't know, but if she is willing to run custom roms, the new siyah kernel has a very nice swipe to wake feature she could use as a workaround till its fixed.
Sent from my SGH-I777 using Tapatalk 2
dandrumheller said:
Don't know, but if she is willing to run custom roms, the new siyah kernel has a very nice swipe to wake feature she could use as a workaround till its fixed.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I've rooted the phone and installed a custom kernel already. I think it was the dream kernel. She away at college but will research it and probably tell her how to do it. Glad to know there is a work around. Thanks!
dandrumheller said:
Don't know, but if she is willing to run custom roms, the new siyah kernel has a very nice swipe to wake feature she could use as a workaround till its fixed.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I can't seem to find anything about this feature on the Siya kernel thread. While googling I did see swipe2wake mentioned on the i9100 forum. Can you point me to where you saw that. Thanks.
beaverslayer said:
I can't seem to find anything about this feature on the Siya kernel thread. While googling I did see swipe2wake mentioned on the i9100 forum. Can you point me to where you saw that. Thanks.
Click to expand...
Click to collapse
Install newest siyah version from ktoonsez thread in I777 development forum. Install extweaks app from market. Open extweaks, scroll over to seen tab. Scroll down to slide2wake and check the box. Done.
Sent from my SGH-I777 using Tapatalk 2
Thanks!
beaverslayer said:
Does anyone know if the internal power button board is connected to the board via mylar flex cable like the i9100? The button has quit on my daughters phone and was wondering if the button was the same as the international version. I can solder it in myself but wanted to make sure they were same before I ordered it. Google and XDA searches haven't turned up much. Thanks.
Click to expand...
Click to collapse
Try asking Josh (XDA Name: Connexion2005) at MobileTechVideos.com. He does repairs for many android phones, so he could probably give you a definitive answer.
I would like to know this too, because mine have been acting funny lately, rebooting the phone or bringing the Power Menu when i press it to lock the phone. I have been using the Slide to Wake feature, and i haven't had any issues with it and its working perfectly fine as a workaround, but i would like to repair the phone. OP, if you get an answer, please post it here! Thanks.
djluis48 said:
I would like to know this too, because mine have been acting funny lately, rebooting the phone or bringing the Power Menu when i press it to lock the phone. I have been using the Slide to Wake feature, and i haven't had any issues with it and its working perfectly fine as a workaround, but i would like to repair the phone. OP, if you get an answer, please post it here! Thanks.
Click to expand...
Click to collapse
Will do.
Thought I should update this thread with what I've found so far. After doing some extensive internet research and studying photos, it looks like the sgh i777 has a different power button than the international version. On the i777, the button looks modular and soldered directly to the board. I finally got the phone in my hands and decided to change kernels and the ROM. She was running stock ics with the latest dream kernel. She also had a lot of suspect apps installed from the playstore. I downloaded 10/17/12 AOKP and 7/26/12 gapps, rebooted into recovery with the Quick Boot app, wiped data/factory reset, wiped cache/dalvik, formatted system, flashed AOKP, flashed gapps, wiped cache/dalvik again, booted back to recovery to be on the new kernel and then rebooted the phone. Button has worked every since and no more random reboots. May have fixed it, we'll see. The phone is only 10 month old so it's still under warranty, but it looks like it's been throwed onto the ground about 100 times so they probably wouldn't warrant it. If it gives me any more trouble I may open it up. Oh, and it's hard to believe she hasn't cracked the screen on this thing yet. She broke 4 iPhone screens in a year and a half before she got this phone. Pretty tough phone. For some reason, I can't convince her to keep a case on it.
The AT&T version does not have a flax cable like the international version. This literally just happened to my phone, and I took it apart a few nights ago to see if I could find the problem. I couldnt, but I'm taking it to a shop soon and I'll let you know if he finds anything wrong with it.
Hey guys... there are a lot of threads in here talking about Power Button not working on Galaxy Nexus and many other devices, but I couldn't find one about i777. I've had a lot of trouble with this, and I wanted to share how it started and how I finally got it to work back again (this was an unique case, none of the workarounds found could help me out).
First, my i777 was rooted and I always had Cyanogenmod on it. Since early CM9 builds to latest nightlies of CM10 (no stable version yet).
It always worked really fine for me (I live in Brazil), nothing to complain, but then I started to use CM updates to keep up with the latest nightlies and... BOOM, after another nightly my power button was off. It also didn't work on CM recovery screen!
First I tried using volume rocker to wake the device and locking widgets to lock it back again, But it never worked, the volume buttons only woke up my phone when they wanted to.
I also tried ButtonRemapping app, but it didn't work for me either. It was really frustrating, I spent days on it and started thinking it was a hardware problem, until I found a guy telling that wiping and reflashing a ROM could do the trick.
In order to accomplish that (I'm not familiar to ADB), I flashed ClockWork recovery Touch version (paid $2 for it, no problem) so I could select anything on recovery screen since the default selection button (Power Button) wouldn't help me out.
I re-flashed CM9 stable (thought it could be a CM10 issue), but again I had no results. Wiped it all over again, re-flashed CM9 again and nothing! No response from my power button.
I Then I tried CM10 nightly build. Nothing again. I was starting to give up and assuming it was a hardware issue
I Finally I decided to flash a SuperNexus ROM that I found here on XDA, Seemed very trustable, very nice comments about it. Again, nothing did the trick. I even tried to edit the key mapping files (under /system) but it was so hard I gave up on that.
I Suddently, after a few hours using SuperNexus ROM, I booted the device into recovery and the damn button started to work. The thing is that I don't know which event triggered the button to work back, I don't even have a clue of that. It simply started working back again, and since I see a lot of people complaining they can't get it back, I imagine that flashing a different ROM may help. Just wondering...
I A tip: DO NOT USE batch Titanium Backup to recover your apps. It simply replaces ClockWorkMod with default mode (non-touch) and I had a really hard time booting my phone again.
vphilot said:
Hey guys... there are a lot of threads in here talking about Power Button not working on Galaxy Nexus and many other devices, but I couldn't find one about i777. I've had a lot of trouble with this, and I wanted to share how it started and how I finally got it to work back again (this was an unique case, none of the workarounds found could help me out).
First, my i777 was rooted and I always had Cyanogenmod on it. Since early CM9 builds to latest nightlies of CM10 (no stable version yet).
It always worked really fine for me (I live in Brazil), nothing to complain, but then I started to use CM updates to keep up with the latest nightlies and... BOOM, after another nightly my power button was off. It also didn't work on CM recovery screen!
First I tried using volume rocker to wake the device and locking widgets to lock it back again, But it never worked, the volume buttons only woke up my phone when they wanted to.
I also tried ButtonRemapping app, but it didn't work for me either. It was really frustrating, I spent days on it and started thinking it was a hardware problem, until I found a guy telling that wiping and reflashing a ROM could do the trick.
In order to accomplish that (I'm not familiar to ADB), I flashed ClockWork recovery Touch version (paid $2 for it, no problem) so I could select anything on recovery screen since the default selection button (Power Button) wouldn't help me out.
I re-flashed CM9 stable (thought it could be a CM10 issue), but again I had no results. Wiped it all over again, re-flashed CM9 again and nothing! No response from my power button.
I Then I tried CM10 nightly build. Nothing again. I was starting to give up and assuming it was a hardware issue
I Finally I decided to flash a SuperNexus ROM that I found here on XDA, Seemed very trustable, very nice comments about it. Again, nothing did the trick. I even tried to edit the key mapping files (under /system) but it was so hard I gave up on that.
I Suddently, after a few hours using SuperNexus ROM, I booted the device into recovery and the damn button started to work. The thing is that I don't know which event triggered the button to work back, I don't even have a clue of that. It simply started working back again, and since I see a lot of people complaining they can't get it back, I imagine that flashing a different ROM may help. Just wondering...
I A tip: DO NOT USE batch Titanium Backup to recover your apps. It simply replaces ClockWorkMod with default mode (non-touch) and I had a really hard time booting my phone again.
Click to expand...
Click to collapse
LOL You could have gotten CWM Touch for free which sticks as long as you don't flash another kernel.
My power button failed recently, but my phone was under warranty. If you can access recovery, you can return it to stock and prepare it for warranty exchange, if yours is still covered, which is what I'm doing. Might want to look into it; call AT&T and find out if your warranty is still valid, it never hurts to try. And let me know if that's what you end up wanting to do and I'll try to help you.
Is this guy telling people to use Rom Manager?
Phalanx7621 said:
Is this guy telling people to use Rom Manager?
Click to expand...
Click to collapse
Seems like it
122ninjas said:
Seems like it
Click to expand...
Click to collapse
Guys, fell free to share your own tutorial.
Sent from my SGH-I777 using xda app-developers app
RatusNatus said:
Guys, fell free to share your own tutorial.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
U don't seem to understand then because there is a huge warning about rom manager in the stickies. If he is having people use that and you're defending him then u are just as guilty for being ignorant
I fixed mine by opening the phone, jiggling the power button a little, and putting it back together.
Sent from my SGH-I777 using Tapatalk 2
karate104 said:
My power button failed recently, but my phone was under warranty. If you can access recovery, you can return it to stock and prepare it for warranty exchange, if yours is still covered, which is what I'm doing. Might want to look into it; call AT&T and find out if your warranty is still valid, it never hurts to try. And let me know if that's what you end up wanting to do and I'll try to help you.
Click to expand...
Click to collapse
I'm in Brazil right now so I don't think I could count on warranty! But thanks for the advice
122ninjas said:
LOL You could have gotten CWM Touch for free which sticks as long as you don't flash another kernel.
Click to expand...
Click to collapse
I made a quick search about it but didn't think it was trustable. But thanks anyway.
brandonarev said:
U don't seem to understand then because there is a huge warning about rom manager in the stickies. If he is having people use that and you're defending him then u are just as guilty for being ignorant
Click to expand...
Click to collapse
Trying to help people who may have gotten as mad as I was with this power button issue. Doesn't it override this rom manager riot? I also found a lot of tutorials in here about ClockWorkMod, even in the stickies. Aren't you being the most ignorant of all?
vphilot said:
I made a quick search about it but didn't think it was trustable. But thanks anyway.
Trying to help people who may have gotten as mad as I was with this power button issue. Doesn't it override this rom manager riot? You are being the most ignorant of all.
Click to expand...
Click to collapse
No it doesn't because rom manager turns phones into paperweights
Sent from my Zanpakuto using Getsuga Tensho!
vphilot said:
I made a quick search about it but didn't think it was trustable. But thanks anyway.
Trying to help people who may have gotten as mad as I was with this power button issue. Doesn't it override this rom manager riot? I also found a lot of tutorials in here about ClockWorkMod, even in the stickies. Aren't you being the most ignorant of all?
Click to expand...
Click to collapse
There are tutorials about clockworkmod but it's not talking about rom manager. There's a sticky on not using rom manager. Recovery is built into the kernel. So no I'm not ignorant, just informed from reading, something more people should do
For those that experience issues with their power button or just don't want to press it (like me), Smart Screen ON uses the proximity sensor to wake the screen.
i was able to fix my wife's s2 power button by removing the 7 screws in the phone, the sim card and prying on the back piece around the power button with my finger nail. After a little prying and wiggling around the power button it started working again! And yes, I did it with the battery in and the phone powered on. Risky I know, but I didn't want to remove the battery and not be able to power on the phone back on. Plus there hasn't been a warrenty or insurance on it for long time. Must have got some dust or something in there, strange considering it stays in a case even when I owned it
I've done the phone opening and wiggling and I'm getting tired of doing it. Plus sometimes it just doesn't work. Mine just stopped working yet again after a month of working -.- any good solutions or workarounds for this problem?
Sent from my SGH-I777 using Tapatalk 2
Firemonkey5 said:
I've done the phone opening and wiggling and I'm getting tired of doing it. Plus sometimes it just doesn't work. Mine just stopped working yet again after a month of working -.- any good solutions or workarounds for this problem?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I assume the only long term solution is to replace it.
Does the i777 use the ribbon power button like the i9100 or the soldered one?
Thanks.
Had this same issue. If you can get the button working long enough, flash a siyah kernel which uses a touch recovery then make sure you never change it. If you switch roms, just flash the siyah kernel again right afterward..I use the swipe to wake option on Stweaks, then added a screen lock widget to my home screen so i can wake and lock my phone without the button. My button is currently working but I try to avoid using in case it feels like breaking again.
Also, if your phone is awake when you pull the battery, i will start automatically when you put the battery back in (at least mine always does) so you can technically power on and off like that as a last resort and get into recovery without the button as well. Just pull the battery, then hold volume up/down and replace the battery. keep holding the volume buttons until you see recovery. You need a touch recovery to do anything once your'e in there though.
The button appears to be a soldered piece though the vids i've found are for the 9100.- http://www.youtube.com/watch?v=EfNVmZ924Xs
found the part for the 9100 is GH59-10916A and i found it here- http://www.samsungparts.com/Products/Parts_and_Accessories/PID-GH59-10916A.aspx?model=
i emailed customer service but they couldn't tell me if it would work on a i777 or not. Haven't opened mine up yet to see.
Thanks. I'm seeing siyah in my future. It's actually my son's, now. It does NOT use the ribbon style button. I opened it and it is a block style but not the 4mm wide one you see on ebay and other places. I actually ordered one of those and when it came in, I saw that it was too small. The one in the i777 is actually 4.7mm wide and has three conductors on the back side. The other problem I see facing if I could even locate the proper switch, is room to fit the soldering tip between the switch and the sim socket(I think that's what was beside it).
Kapn.K said:
Thanks. I'm seeing siyah in my future. It's actually my son's, now. It does NOT use the ribbon style button. I opened it and it is a block style but not the 4mm wide one you see on ebay and other places. I actually ordered one of those and when it came in, I saw that it was too small. The one in the i777 is actually 4.7mm wide and has three conductors on the back side. The other problem I see facing if I could even locate the proper switch, is room to fit the soldering tip between the switch and the sim socket(I think that's what was beside it).
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this not the right part?
http://stellatech.com/samsung-gt-i9100-galaxy-s-ii-power-key-flex,a,en,810428.html
So I have an AT&T LG Optimus G (E970). However, I found out that it's pre-release hardware (yes, it says "nOt foR sale***" on the side of the phone, but it was in a case), and I've bricked it trying to root it the standard way (using LGNPST), and it now boot loops 3 times before displaying "Security Error" under the LG logo. I can't get it back into download mode, nor does a factory hard reset (the only mode I can get it into) work.
A bit of background info:
The original firmware was E97009j. It was unable to download the OTA JB update. I tried to install that stock update through LGNPST since the phone couldn't be seen through ADB. From there I planned on rooting and everything else. Yes, I should have never tried messing with pre-release hardware, but in theory, since it was a review unit, the hardware itself should've been identical to what is sold in stores. Also, and more importantly, I didn't realize it was pre-release until after I bricked it.
Luckily this isn't my daily phone, but I'd like to get it fixed...
Possible way to get back into download mode.
Start with phone unplugged, and when it gets stuck on security error hold power button for 10 seconds to force reboot.
Then at very instant it powers off, but before it powers on hold volume up + volume down + power and plug in USB.
If you are able to get into download flash the teenybin alt. with lgnpst.
adfurgerson said:
Possible way to get back into download mode.
Start with phone unplugged, and when it gets stuck on security error hold power button for 10 seconds to force reboot.
Then at very instant it powers off, but before it powers on hold volume up + volume down + power and plug in USB.
If you are able to get into download flash the teenybin alt. with lgnpst.
Click to expand...
Click to collapse
So that partially got me fixed. I was able to finally get it into download mode after trying your method about 4 times, and I did the teenybin deal. The "regular" teenybin didn't fix it, though it allowed it into download mode the proper way without trying more than once. I then did the alt teenybin, and when it rebooted, it showed a Google logo (instead of LG) with an unlocked icon at the bottom of the screen for about a second before the screen went black. Now I can't get it to turn on at all, though it could just need to be charged. When I plug it in, it shows a white battery icon with a lightning bolt for about 4 seconds before turning back off. I'll let it sit on the charger undisturbed for an hour or so and see what I can do then. As it stands right now, it won't go back into download mode or factory hard reset mode.
Out of curiosity, since I've flashed teenybin, my bootloader should be unlocked and I should have a recovery I can flash zips from now, right? I shouldn't have to jump through any more hoops with LGNPST or anything?
EDIT:
Um, this phone will charge even in this state, right? The LED on the power button isn't lighting up, and I can only sometimes get it to show that battery icon...
YES!!!
I'm into recovery now! I'm going to flash CM10.1 and report back!
EDIT:
I'm up and running now, though WiFi isn't working, nor is my earpiece on the phone. Though, the earpiece was an issue before I borked everything, so I'm pretty sure that's a broken bit of hardware there.
THANK YOU SO MUCH!
chrisliphart said:
I'm into recovery now! I'm going to flash CM10.1 and report back!
EDIT:
I'm up and running now, though WiFi isn't working, nor is my earpiece on the phone. Though, the earpiece was an issue before I borked everything, so I'm pretty sure that's a broken bit of hardware there.
THANK YOU SO MUCH!
Click to expand...
Click to collapse
I am glad you got it fixed! Setting WiFi to 2.4 GHz only may work.
adfurgerson said:
I am glad you got it fixed! Setting WiFi to 2.4 GHz only may work.
Click to expand...
Click to collapse
Wifi works under the stock AT&T JB firmware. Not sure why it didn't work under CM10.1 (it couldn't initialize it), but I'm good now. Thanks!
It may have been a radio issue, ROM zips don't include them. Teenybin would not have changed radio either, so you would still have had ICS radio.
adfurgerson said:
It may have been a radio issue, ROM zips don't include them. Teenybin would not have changed radio either, so you would still have had ICS radio.
Click to expand...
Click to collapse
Ah, that makes total sense. I just got everything setup and signed in on this ROM, so I'm running a Titanium Backup now. I'll switch ROMs and see what happens. Thanks so much for your help.
EDIT:
Yep, that did it. I didn't think to update the radios. I can't thank you enough, man. Aside from the earpiece issue (and I can just use a BT headset to get around it until I decide to pay to get it fixed), it's purring along now.
Sent from my LG-E970 using xda premium
chrisliphart said:
Ah, that makes total sense. I just got everything setup and signed in on this ROM, so I'm running a Titanium Backup now. I'll switch ROMs and see what happens. Thanks so much for your help.
EDIT:
Yep, that did it. I didn't think to update the radios. I can't thank you enough, man. Aside from the earpiece issue (and I can just use a BT headset to get around it until I decide to pay to get it fixed), it's purring along now.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Nice, glad you got it fixed. And thanks to adfurgerson for the assist.
Sent from my Nexus 7 using xda app-developers app
TangoXray said:
Nice, glad you got it fixed. And thanks to adfurgerson for the assist.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Autoprime explained how to get into download to me on irc, I just relayed the answer. I was glad to help after having a hand in bricking it.
adfurgerson said:
Autoprime explained how to get into download to me on irc, I just relayed the answer. I was glad to help after having a hand in bricking it.
Click to expand...
Click to collapse
Haha, it wasn't you who bricked it; it was me. Really, I should've just done TeenyBin when I first got it into download mode through LGNPST instead of trying to install a stock ROM to root. It really was a backwards way for me to accomplish what I wanted. You'd think that since I've had like 10 Android devices, all rooted and modded, I'd know better. lol
http://forum.xda-developers.com/showpost.php?p=41415103&postcount=248 It all worked out in the end.
chrisliphart said:
Haha, it wasn't you who bricked it; it was me. Really, I should've just done TeenyBin when I first got it into download mode through LGNPST instead of trying to install a stock ROM to root. It really was a backwards way for me to accomplish what I wanted. You'd think that since I've had like 10 Android devices, all rooted and modded, I'd know better. lol
Click to expand...
Click to collapse