Database Info

Fighting a lost cause?

I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.

Have you tried booting into recovery?

(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.

Continuous reboot with HTC One S - almost certainly a HARDWARE problem - any ideas?

This is kind of a last resort - to see if anyone has any experience with this problem. I have Googled around for similar problems and haven't quite found the same issue anywhere.
OK, so let me emphasise, this is not a bootloop - there is clearly some kind of hardware or firmware problem where the phone is interpreting the power button as being pressed.
I can power on, and the phone will get to various points before then rebooting, as though the power button were being held down:
- often it only gets to the splash screen and then reboots
- sometimes I can get it into recovery, but whatever option I happen to highlight (I have about a second or two to do so) just gets selected as though the power button were pressed
- sometimes the phone will even boot and can be used for a little while (enough even for me to back up the files off it), but sooner or later a message will pop up saying something along the lines of "Continue holding power button to reset", again - OBVIOUSLY the system thinks the power button is pressed down.
The problem happened while the phone was under guarantee, the repair place kept it for weeks, eventually "replaced the motherboard" (so they say) and it seemed to work for a time. Now the problem is back and there is no more warranty. A reputable repair place has had a look and said they can't do anything.
I have tried taking the top cover off and fiddling with the microswitch (only thing I could think of) to see if there is anything obvious going on there, but that doesn't seem to be the cause of the problem.
Any ideas, before we ditch the phone as a $XXX loss?

Just to update - I managed to catch the phone when it wasn't going crazy, go into fastboot and flash CM10.2. Could've restored to stock I suppose, but I am concerned that may somehow have been the cause of the problem in the first place.
As of 12 hours later the phone is behaving itself. Can't be sure a new ROM is what did it, but fingers crossed...

HELP PLEASE-My Shield Tablet turned off and will not come on at all!

Last night I was using the tablet as normal. I sat it on the pillow next to me to grab my TV remote and I saw a pop-up on the screen out of the cornerbofbmy eye ,which was out of place. There was no reason for any kind of pop up.
This wasn't a notification. It was a pop-up window right in the center of the screen. The same place where the the window appears when you hold power down and you get the menu of Power, Restart, etc…
And in fact, all I saw of this pop-up was "… .. is turning off" and then it did.
But, it immediately came back on and the Android logo appeared like always then TWRP recovery screen flashed for a second and it went off. I have not been able to get it on since.
I have held the power button in for 30 seconds and I have tapped the power button. I have done every combination of power buttons with volume button and then repeated those with it plugged into the pc.
I just removed the back of the tablet and the battery out reading spot on. I'm confident that the battery is not the issue.
Now I'm lost on where I go from here. Is there a method to bypass everything and fire up the screen to see if that works?
I'm open to anything.
Any help would be life saving.

2kool2Bcruel said:
Last night I was using the tablet as normal. I sat it on the pillow next to me to grab my TV remote and I saw a pop-up on the screen out of the cornerbofbmy eye ,which was out of place. There was no reason for any kind of pop up.
This wasn't a notification. It was a pop-up window right in the center of the screen. The same place where the the window appears when you hold power down and you get the menu of Power, Restart, etc…
And in fact, all I saw of this pop-up was "… .. is turning off" and then it did.
But, it immediately came back on and the Android logo appeared like always then TWRP recovery screen flashed for a second and it went off. I have not been able to get it on since.
I have held the power button in for 30 seconds and I have tapped the power button. I have done every combination of power buttons with volume button and then repeated those with it plugged into the pc.
I just removed the back of the tablet and the battery out reading spot on. I'm confident that the battery is not the issue.
Now I'm lost on where I go from here. Is there a method to bypass everything and fire up the screen to see if that works?
I'm open to anything.
Any help would be life saving.
Click to expand...
Click to collapse
It sounds to me like you got the ota that killed your tablet. Is it the original shield tablet? You should check the serial to see if it was recalled. I don't know the address but just Google Nvidia recall battery, you'll find it
Sent from my SM-G386T1 using Tapatalk

Yes, it is an older tablet compared to the newer "K1 no stylus" version however, when checking the battery number it said it was a B01.
The idea ilof getting the kill switch never occured to me as a possibility due mostly to the above mentoned not being a candidate but also because i didnt realize the kill switch completely shut it off and somehow render the power switch useless.
I was thinking it caused a bootloop or something like that. My tablet has zero signs of life.
I will have to approach Nvidia tomorrow and hopefully get this somehow sorted out.
If this was in some way my fault and I misread the battery info i still shouldnt have recieved the kill switch because I never activated a replacement. Correct?
Is this is somehow reversible? I imagine its not since I can't power the damn thing on. I have 3 other Shield Tablets in the house. 2 OG tablets and 2 new K1s. If there was a method to use a working tablet to resuscitate my dead one, that'd be interesting.
I'm getting ahead of myself tho. I feel this is an Nvidia error and should be taken care of by them.

Word if caution there's guys going around on craigslist emailing about shield tablets that are for sale asking for serial number to verify warranty..only to submit a claim for the recall tablet .. Happened to my brother..

Please help me with my phone.

Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.

rawon3 said:
Hey everyone who reads this.
I'd like to start my topic with apologising if I post this in the wrong section.
So, I have a LG Spirit H440N LTE for about 3 years now, maybe a little less. I've always taken good care of it, both physically and in updates / security wise aswell.
My phone has been working flawlessly until the last 2 days. 2 days ago i was charging my phone, and when it vibrated (meaning its 100%) I pulled the cable off, and pressed the power button (power button locks - unlocks the screen) the screen didn't turn on. I was like "wow that's strange" but didn't care much, i just kept pressing the button every 5-6 seconds, nothing.
At that point I pulled the battery out, let it sit for a short time and then put it back, start the phone, I felt the vibration (meaning it's starting up) but no screen, so my first idea was that I need to get a new firmware and completely reinstall my phone, as it seems like it got bricked.. for no reason, by itself ? Strange thing but I accepted it and literally been googling for 9 hours now and I find more and more issues.
After I got LG FlashTool, drivers, and even 3 different firmwares, I wanted to start the phone in download mode to start upgrading, but even though I held down "volume up for 5 seconds and then put the usb cable in" nothing happened, no screen, my PC didn't recognise the phone either.
So I got a little bit mad and pulled the cable out from the phone, I wanted to remove the battery, but out of nowhere the phone suddenly started loading in, screen working completely fine, i could do whatever i want, so my first thing was to do a hard reset. After the hard reset I set up my usual stuff (important apps etc) and I locked the screen so my battery won't go down. Little did I know, I ****ed up again, because ever since that happened, I can't get my screen to work again. I tried everything I could but my PC still doesn't recognise the phone (even after a LOT of drivers being installed), charging the phone doesn't do anything. Regardless if I remove - put back the battery no screen, no screen in download - hard reset mode either, it's just completely black.
I'd like to have some sort of help, because I am just completely out of ideas, I really feel like a firmware change could fix the phone, but if the computer doesn't recognise it, I have no idea what to do.
Click to expand...
Click to collapse
You might be having hardware issues, such as a faulty power button. If you are the type of user that frequently presses the power button to lock/unlock the screen, this leads to excessive wear on the button components, this is why some users prefer to use the "tap to sleep" and "tap to wake" feature, to avoid wearing the power button out. On my LG, this feature is called "KnockOn", it's located in Accessibility settings.
Sent from my LGL84VL using Tapatalk

Question Z flip 3 bootloop

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.