Can't seem to find an answer for this, but I can't seem to shut my TF700 off completely. I followed the NVflash guide, and then after installing the alternate bootloader, I can't seem to shut off my tablet. When i select shut down, it appears to be shut off, but it drains the battery. I think that when I tell it to shut down it is going into apx mode because to get it to boot back up, I have to hold the power button for like 6-7 seconds.
Anyone have similar issues? I haven't tried restoring the original bootloader yet, but I thought I would ask first if there is an easy work around for this? I have the same issue weather I run the stock rom, clean rom, CM10...anything.
toprunner2786 said:
Can't seem to find an answer for this, but I can't seem to shut my TF700 off completely. I followed the NVflash guide, and then after installing the alternate bootloader, I can't seem to shut off my tablet. When i select shut down, it appears to be shut off, but it drains the battery. I think that when I tell it to shut down it is going into apx mode because to get it to boot back up, I have to hold the power button for like 6-7 seconds.
Anyone have similar issues? I haven't tried restoring the original bootloader yet, but I thought I would ask first if there is an easy work around for this? I have the same issue weather I run the stock rom, clean rom, CM10...anything.
Click to expand...
Click to collapse
Just for diagnostic purposes: have you tried installing "Quick Shutdown" from the Play Store? (Can be found here: https://play.google.com/store/apps/details?id=com.grrmode.quickshutdown&hl=en )
I'm just wondering what the issue is, since the app seems to use a different shutdown routine (pretty much instant). Let us know what the result is!
Related
Alright, allow me to summerize to you guys the series of screw ups that happened in the day that I've had my captivate.
Basically, it's like this. I got this phone from my brother (it used to be his). Now when I got it, I began basically erasing his contents and setting up mine. The Phone is on the Cognition OS and everything seemed fine.
Now, when I tried to set up my google account, it said I had to do a factory reset, I did that. Then I realized the market place app was no longer there :/
I did another factory reset, still didn't help, and started looking around for info.
I told my buddy this and he said he could fix it. So he get's the update.zip for rooting the phone, sets it up on the SD card, and goes to root the phone normally. Except when he restarts the phone after, it doesn't go to the set up screen, so he just starts it normally and enters the setup screen by holding home+volume up+power.
Then he presses the reinstall packages, and the phone seems to get to work on the update pack...
Now, every time I turn on the phone the voice says "converting data partition to optimize extension four", turns off, then repeats.
I've looked up this problem and it seems to have something to do with voodoo, but the causes in the other cases the causes were different.
Can someone please help me out here? I've also tried doing a hard reset by holding the volume down button and pressing power, but nothing seems to take me to the recovery mode.
HELP.
Did you pull the battery during this our did you let it run? Should let it run.
Does your phone boot up at all?
At&t or rogers?
Do you have a windows pc with usb drivers installed?
What its your build number, located under battery, something like 1008?
Answer these questions and we can get you back up and running
-Well after he did the reinstall thing we let it run for like 15 minutes, then he pulled the battery out.
-The phone only shows the AT&T screen, say's the "converting data partition..." thing, then goes blank and does it again. I've let it run for like 10-15 minutes before having to turn it off because I couldn't have the speech going off.
-I have a windows PC, and but I'm not sure if I have the drivers installed. I have Kies installed and when I plugged the phone in before Kies could recognize the phone (though it wouldn't fully connect, it would just say "connecting" on the kies screen).
-The Model is SGH-I897, that's the only relevant thing I see under the battery, that good enough?
Thanks a lot.
No, your phone has a build, on phone under battery, the word build is not listed. Something between 1006-1012
If we are going to do this you need to be active, I can not wait 20 minutes in between responses
Sorry the internet kinda crapped out actually.
And I see a 1007 between the bar codes, that it?
Yes
Before we get started try this
Take battery, sim, ext sd our of phone
Plug usb into pc but not phone
Put battery back in
Hold volume up and down, while holding plug in usb
Screen should come on with android with shovel
You can pull the battery again
Confirm this happened
Yep, it happened.
It may be easier if we use gtalk, log in on your pc using google id, send me an invite [email protected]. This way we know when each other respond
Just sent u the inv
I am having the same issue.. Chairchair did your problem get resolved?
Can anyone help?
James
liquorsh0tz said:
I am having the same issue.. Chairchair did your problem get resolved?
Can anyone help?
James
Click to expand...
Click to collapse
Have you gone back to stock and then reflashed? Seems like some files are getting corrupted. Because you have a voodoo kernel I would follow these steps. Make sure to back up.
1. Use Odin to flash a non vodoo kernel.
2. Flash stock rom and master clear
3. Reflash rom of choice if it is 2.2
3a. If you want 2.3 follow the tut on it.
4. Breath a sigh of releive lol
My phone runs perfectly fine until I enable Gps location. Once I enable GPS location, it freezes, then it reboots my phone and it slowly do a system check, then it continuously rebooting the lg logo screen. I tried taking out the battery and put it back in, even took out my battery for a day and it still does the same. I'm not sure if it's the hardware problem, but it's a pretty rare case, since I read most of the threads in forums, people said it can be fix once you pull out the battery, but somehow it's not working for me. Anyone knows the reason why? Btw, my phone is not rooted or used any 3rd party program.
Ah. Posted too soon. There's a master reset that I believe is Power and Volume Up. Try that.
Unfortunately, it's still not working. Is there any other possible way? Or else I have to call in and return it.
Try turning off the phone, then press power + vol down and hold it until you see the word android. This should do the factory reset.
efrem989 said:
My phone runs perfectly fine until I enable Gps location. Once I enable GPS location, it freezes, then it reboots my phone and it slowly do a system check, then it continuously rebooting the lg logo screen. I tried taking out the battery and put it back in, even took out my battery for a day and it still does the same. I'm not sure if it's the hardware problem, but it's a pretty rare case, since I read most of the threads in forums, people said it can be fix once you pull out the battery, but somehow it's not working for me. Anyone knows the reason why? Btw, my phone is not rooted or used any 3rd party program.
Click to expand...
Click to collapse
It sounds like the permissions are not correct, or perhaps that your ROM was not flashed correctly. I have seem this problem happen numerous times due to bad firmware flashes or ROM issues. I would just download a new copy of the latest CM 7 ROM or whatever your favorite ROM is and flash it through CWM.
Thanks guys for the help. I found out that you have to hold down first then power button for around 30 second and then the droid animation comes out. I was so close to returning it. Thanks!
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 guys,
I was running Cataclysm/EX last week when my phone started randomly rebooting about 10-20 times a day, often getting stuck in a boot loop. I've since switched to Euphoria, but it only helped to reduce the number of lockups and reboots to about 5-10 a day.
Before I go stock and unroot the phone, I wanted to know if there are any tools or terminal commands that could help me track down the issue. Running cat /proc/last_kmsg just gives me a wdog_reset as my last reboot reason.
Many thanks!
Sounds like a faulty power button to me unfortunately.
Flash stock firmware with fastboot, if you can. If it reboots in the bootloader, or recovery, it's definitely the power button... And flashing could be dangerous, since it could reboot half way.
But a clean flash of a few roms, and it's the same with all... Sounds like power button for sure.
Quite a common issue.
Thanks Darth,
Would a faulty power button give a watchdog reset error on last_kmsg though? Seems like it thinks some software is hanging before resetting the phone.
To your point, I haven't had a reboot in about 12 hours, so perhaps the random nature of the issue points to the power button.
Do you know of any guides to fix the issue? I've opened up phones before so would at least give it a shot.
doron07 said:
Thanks Darth,
Would a faulty power button give a watchdog reset error on last_kmsg though? Seems like it thinks some software is hanging before resetting the phone.
To your point, I haven't had a reboot in about 12 hours, so perhaps the random nature of the issue points to the power button.
Do you know of any guides to fix the issue? I've opened up phones before so would at least give it a shot.
Click to expand...
Click to collapse
Not sure about the error. Sorry.
As far as checking out the button, just google "nexus 5 power button stuck", you'll find lots on it. Throw in "xda" in your search for results from here.
If it does it after flashing the stock firmware and no other apps.... It has to be something hardware related, power button or something else anyway.
I'd try that first.
I've never played with one myself, sorry. ?
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.