I recently updated my TF to 8.6.5.19 Firmware With CWM & Root and I noticed my volume up is not working, the down works fine, I have tried rebooting, Factory Reset and still nothing. It worked fine when I did the update with CWM but now it just stopped. I am not sure if it is software or hardware, I tried rebooting into CWM and it will not work either. I also noticed the backing has separated from the bezel and you can see the rubbers around the volume keys, I have never noticed and issue before with the volume, the volume down seems soft to press as the volume up seems a little bit harder. I wanted to send it for RMA but It is rooted and I do not know how to unroot it. I was told by someone that ASUS will not fix it if you root the tablet. If anyone can let me know what I could do to fix it or maybe someway to reflash the update again or unroot it. I would greatly appreciate it.
A solution....
Well i guess not many people can help you if they dont get the hands on it. Usualy u cant find out if it works or not. Best way is plug it in your pc open properties on your computer and go to hardware and see if the APX activates this is how u can find out if it really work if not here you have a program to get directly to recovery ...
---> https://market.android.com/details?id=com.modaco.transformerrecoveryboot&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5tb2RhY28udHJhbnNmb3JtZXJyZWNvdmVyeWJvb3QiXQ..
It works fine because i have tried it...
I have tried to get into APX mode many times but it does not work, it just starts the tablet, It is installed on my PC for I have used it before numerous times to install updates and to root it. The only option I can get is the volume down menu which I cannot select "Up" so it boots to the Wipe Data/Android screen. I want to RMA it but I cannot get anyone to let me know whether they will fix it if it is rooted.
This isn't going to help you much but I had an identical problem where the volume Up button stopped working. It was the impetus for me finally sending the unit in for repair - came back a month later with the volume up button functioning but the power button broken and the entire unit virtually unusable. This was a hardware repair as they did something to make the button feel totally different. Second RMA did fix things though.
Mine wasn't rooted though - way too many issues on this thing for me to risk the warranty. Good luck to you though.
Well I bought and downloaded the Asus Transformer Recovery Boot and it works like a charm for getting me into CWM but still no APX mode
Im sorry but i only want to help...
I insist please turn off your TF plug in usb to pc then turn it on pressin VOL + and START and go to mi pc properties hardware and u will see it goes in apx keep trieing it has to work sometimes it takes a little the screen on TF is black all the time just look at pc do it and wait count at least 8 seconds before letting loose the power bott and not more than 10 secs the VOL + if u do it wont work... TRUST ME ON THIS i have tried it on a TF 101 and a TF 3G both rooted now...
Related
my girls volume wont turn on at all? anyone ever hear about this problem? it isn't rooted....
not sure if it will help, but try this: from the home screen, press the menu button, then choose settings>sound>volume, and check the settings for the various volumes, i.e incoming call, media, system, etc. when my phone was stock like hers, sometimes one or more of those volumes got pushed down to 0 for some reason... it was annoying, and it seemed to happen especially to my notifications volume every time i rebooted the phone! hope that helps
I'm having the exact same issue
Hey everyone. So I bought a sidekick 4g on craigslist the other day. I checked it out and thought everything was okay, but I was wrong. So far no response from the jerk who sold it to me without telling me about this problem.
The phones volume up key doesn't work 90% of the time. If I reboot the phone or leave it off for a while, the volume up key will work for a few minutes and then stop again. The funny thing is the volume up key works when I want to reboot (holding vol.up + vol.down and power button at the same time).
So is there any fix for this? Will rooting it and loading a rom fix it? Also I am new to all of this, is it even possible to root and load generginger 2.0 with a broke volume up button? The phones firmware is all up to date.
Thanks for any info and help everyone.
i'd suggest using this thread: http://forum.xda-developers.com/showthread.php?t=1275116
root the phone, and then go back to stock with the heimdall and see if that fixes the problem. and if it does then you should try rooting it again and install one of the Custom ROMs because the stock OS on this phone is garbage out of the box.
but i'm no expert either, it just seems strange that only when its been on for a bit that it stops working. that it works when you boot it seems to suggest that its a software issue? somebody help me out here guys lol
I've just installed the new Revolution HD 3.2.1 and the latest Kernel 16b.
The tablet is very fast and stable now, no more reboots. There are only two things that happens and that's Dolphin browser crashes sometimes and when my tablet is off and I want to start it up, I have to use my power cable otherwise it won't start up. If I want to use the battery only it won't start up. Is the anybody else with the same issue?
how long are you holding down the power button waiting for start up?
slackhouse said:
how long are you holding down the power button waiting for start up?
Click to expand...
Click to collapse
20 or more seconds. Normally it worked fine but lately it went from bad to worse to nothing!
Same here
Mine is doing the same thing. I flashed another ROM (was using Revolution) thinking it was the ROM, but no. I have done a lot of reading and still am not sure of what is causing it. Some say the power button is wonky and the tablet needs to be sent back to Asus, but when it is booted up the button reacts just fine to sending it into and bringing it out of sleep. I am perplexed.
gbweller said:
Mine is doing the same thing. I flashed another ROM (was using Revolution) thinking it was the ROM, but no. I have done a lot of reading and still am not sure of what is causing it. Some say the power button is wonky and the tablet needs to be sent back to Asus, but when it is booted up the button reacts just fine to sending it into and bringing it out of sleep. I am perplexed.
Click to expand...
Click to collapse
Exactly, the only time the button refuses to work is when the tablet is off and I want to turn it on when it's not on mains power. But as soon as I put the main power cable in the tablet I don't even have to push the button it just goes on
and if I want to flash something and I push the power button and the volume down button, it works. But the main power cable must be plugged in.
RMA'ing mine
After researching until I was blurry-eyed I decided that it has to be a hardware issue. I unrooted following the Unlockr guide and flashed the most recent stock build (.24) from Asus's support page so I could send it in for service. (I couldn't get a download for the stock ROM from the Unlockr link and that's why I used the one from Asus...just unzipped main folder and moved to SD card from my PC, then inserted card into the TF101. As soon as SD mounted a notification popped up saying that there was an update ready to install.)
Also, another strange thing is that I can't connect it to my PC. It just says USB device unrecognized. I tried EVERYTHING and no luck. I really would have thought that returning it to complete stock would have solved that issue but no. Hopefully when it comes back I'll have that functionality back too. I have my doubts but we'll see. Maybe one of those custom kernels I flashed that were associated with Megatron's ROM did something with the firmware that flashing stock couldn't change. I really have no idea and I don't recall trying to connect to my PC with it while I was on Megatron's ROM so I don't really even know at what point it stopped working. I will say that it was my favorite ROM.
Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N
Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app
Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.
Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.
I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app
XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.
In case anybody comes back here, I'm just gonna drop this in.
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
hi every body!
I have an original shield tablet, also it effected by kill switch.
I try to delete the TegraOTA.apk by following the instruction of @Bogdacutu http://forum.xda-developers.com/shield-tablet/general/kill-kill-switch-shield-tablet-xx-t3179489 then it's ok for a month.
But the trouble is when I change the IMEI (successfull) then update OTA3.1.1 via recovery. At this time, any thing also ok, but I did't delete TegraOTA.apk again, then turn on wifi for try to get OTA4.0 directly. unfortunately the tablet was shutting down after one minutes, then automatically boot to recovery before change to black screen . I understood that skill switch is activated!!! Although IMEI different !
Now when connect to PC, it become a APX device, in details http://forum.xda-developers.com/wiki/Nvflash
I try for some of solution but all of them not work. Also solution of @carlompms
good evening,
I received my recall tablet yesterday, before connecting the new one, I installed a new rom, for now I have 2 tables to work.
in the process I do not know what I did my tablet brick in apx mode.
for exit apx mode I connected to the PC, press power button until you hear the disconnect sound on pc(tablet turn off)
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
It may work for you too
Click to expand...
Click to collapse
Then if @Thepiewarrior, if you can read this post, please instruct for me that, how can you clear your trouble before: http://forum.xda-developers.com/shield-tablet/help/unlocked-bootloader-rooting-shield-t2995472 tks.
So, after my trouble, every one should remember that, must be deleted the TegraOTA.apk before go to online, then maybe all of solution try to change IMEI may be should't work.
Now, I waiting for some of solution from the expert (such as nvflash...), maybe there're some of member like me...