Had my G tablet for a month now and I've rooted it a couple of times (to tnt lite,) but I've since resorted to the latest update from the mfg. Its fast enough and I can get most of the aps I'm intersted in with the stock cfg.
Problem is, it occasionally hangs, usually in the middle of a web surfing session. The hang is complete, meaning I can't even shut down. the only remedy I've found is to set the tablet aside and wait till the battery runs down. Then I charge it, boot up, and everything's back to normal again.
Has anyone else seen this happen and is there a way to prevent/cure it?
thanks.
Rich
First off you say you rooted a couple of TIMES? Do you mean flashed a couple of times? Regardless if it locks up again then hold the power button till it powers off. Then you should be able to reboot.
thanks, but...
when I say its locked up I mean locked up. The on/off button is inoperative. I've held it for varying lengths of time, up to 15 seconds and nothing happens.
When I said that I had rooted it several times I mean that I've taken it from stock to tnt lite twice. Its now unrooted and stock again and working fine. (till the next time it locks up, that is-)
but thanks for replying
rich
zookarama said:
when I say its locked up I mean locked up. The on/off button is inoperative. I've held it for varying lengths of time, up to 15 seconds and nothing happens.
When I said that I had rooted it several times I mean that I've taken it from stock to tnt lite twice. Its now unrooted and stock again and working fine. (till the next time it locks up, that is-)
but thanks for replying
rich
Click to expand...
Click to collapse
Try doing a factory reset as well as wiping the internal memory. There are several ways to do this, but only one way on stock. I won't ask you to go back to using Clockword Mod if you no longer have it on there so I'll go through the stock way first, and then the CWM way in case you have it installed.
Prep: Copy out anything you figure you need from there. I don't recommend backing up because if you back up a corrupt or faulty app then you're going to restore it and your problems with it.
So copy your stuff off that you don't have otherwise, maybe downloaded wallpapers or whatever. Best method is just to copy them right to your PC I'd say. Do this from both internal storage and the SD if you have that installed as I recommend you wipe that as well.
Stock:
Go into settings to security and do a factory reset. After the factory reset, don't bother setting up, go back into the settings and to storage and wipe the SD card if you have one installed. You'll have to unmount it first I think. After that, wipe your internal user storage. This is going to 1. reset the tablet's OS and system software/settings to factory defaults and 2. remove any gunk that may have gotten on there and is messing things up. Since Apps generally don't overwrite their settings on purpose, I recommend wiping them and putting them back over clearing data/clearing cache for each app. You start over with more or less a clean slate this way.
Clockwork Mod:
Go into CWM and wipe your data as well as the cache. Wipe Dalvik as well, for good measure. When the tablet starts back up, go to storage and wipe the SD as well as the internal storage, again, just for good measure.
Once you're all done, power the tablet off and then on again and do your thing.
If the tablet STILL messes up after a few days then it could mean that there's some hardware at fault. My tablet has never frozen like that before to the extreme where I'd have to sit and wait for it to die...and afaik that's def. not something that should occur often. I have seen other members report it, but they've usually done some 'heavy' tweaking like repartitioned their internal storage and other things like that.
People may recommend that you re-partition, etc. but I'd just try to exchange it and try my luck at another unit before getting into all of that UNLESS you have indeed partitioned or altered the internal storage manually before this started happening - in which case you may have it partitioned incorrectly and should def. try getting it back to the default using CWM, HOWEVER, if you did not do this and all you really did was install TnT lite then I'd do the exchange.
Good Luck.
thanks
Your advice and your instructions on how to address this problem are VERY helpful. Thanks.
rich
Related
Ok. So i have completely screwed up my phone. I have rooted my phone and installed a few different ROMs on it. I have clockwork recovery installed on my phone and I was using it to clear my data to install a new ROM. I cleared my /system and then did a "reset data/factory reset" and I believe the factory reset is what messed everything up. Now when I boot up my phone it shows "Google" and has a little progress bar that gets to 100% and does nothing after that. My phone will show up on my computer as an ADB device but nothing more. When I boot into my bootloader, it freezes up completely. The volume keys and power button don't do anything.
I have clockwork mod installed but I can not get into it. My last ROM installed was Slim ICS from slimroms[DOT]com (I can't post links yet ) I'm not sure if that is needed but I thought I might throw that in.
Any help would be much appreciated. I am without a phone right now because of my toying around with it.
EDIT: I have solved my issue. I just came back to tell what I did in case someone else hits this problem. Every time I took the battery out and put it back in, my phone would instantly turn on. After about a million times of taking my battery and putting it back in, I noticed that every so often it wouldn't boot up (either because I put the battery in weird and readjusted it or left the battery out for a long time). Whenever my phone would not boot up on its own and I booted into the bootloader, everything would work great. Once I realized this, I left my battery out for about half an hour, put it back in, and everything worked out great. I installed a new ROM and my phone is back to the way it was.
Hi All,
I've recently updated my Desire S to CM10.1 using a ROM off here --> [ROM][XXYYYZZ][UNOFFICIAL] CyanogenMod 10.1.
Everything has been running fine until I found the "Simulate Secondary Displays" button under Developer Options and decided it would be cool to see what it does...
The kicker:
a) Screen is now stuck exactly where it was on the Developer Options prior to selecting a screen resolution
b) Holding down power button for any period of time does nothing
c) Holding down Volume up + Volume down + Power for any period of time does nothing
d) The computer recognizes the phone as it makes it's lovely "new device found" sound, but stupidly, at some point I've disabled USB debugging so can't use adb to reboot as it returns authorisation error (The authorisation option doesn't pop-up on device screen as it's frozen).
I've read about this exact problem happening on other phones after selecting this option but they all seem to be able to use either b) or c) to get back to bootloader to reflash the ROM.
So, my question: if I let the battery die, what are my chances? I've read myself out of pulling the battery due to eMMC issues. Unfortunately the damn battery was mostly full so could take a long while to drain :S
Thanks!
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Pulling the battery out doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
SimonTS said:
Pulling the battery ut doesn't cause eMMC issues. The problem is caused if you pull the battery out and then put it straight back in. Remove the battery, leave it out for a minute or so and then put it back in and manually boot into recovery.
Click to expand...
Click to collapse
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
So let the battery die (takes about a day), boot to recovery, wipe data (or figure out where this setting is stored and delete the relevant file), no problem. I don't see the issue here.
Click to expand...
Click to collapse
Apologies, it wasn't a particularly open question. It was more out of frustration that there is an option available that will always freeze the phone when it isn't supported on the device.
I let it die then used recovery to clear cache and davlik cache and booted fine until freezing on the "Optimising apps" screen. Let it die again, clear all data, clear cache, clear davlik cache, restore nand successfully.... Boots to HTC then black screen, no response to anything, same as when it first froze.
EDIT:
Repeat same process but clear cache and davlik cache after nand restore... black screen, no response. Cant even tell if it is actually doing anything. Charge light doesnt come on when plugged into pc whilst on black screen.
All I can think of now is flash the CM10.1 ROM again or maybe restoring the original nand from before CM10 but will have to be after work. Is this behavior indicative of a larger (potentially physical) problem?!
PoZER937 said:
Ah, that's interesting. Is there any reference material available to explain why that is the case? What is physically happening here?
Click to expand...
Click to collapse
From what I remember - there was some in-depth discussion on one of our threads about 18 months ago - the actual cause is that re-inserting the battery while the circuitry is discharging causes a spike which can be high enough to blow the eMMC.
Just to let you know, reflashed CM10.1 ROM and all is well in the world again Thanks guys for replying!
However, NAND restore did not work. As the NAND backup is supposed to be the be-all and end-all for phone recovery, should I be concerned this failed?
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Meth_Badger said:
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Click to expand...
Click to collapse
If I read your post correctly, you selected the right icon which is a Wipe data from your bootloader. When you executed that Wipe data, it will wipe everything on your internal SD including your /media folder or your personal files and data... The chance is very slim unless someone knows how to recover data from a wipe. Technically, your data is still there but it is only a dumb files which contain only 0's and 1's. Some recovery tools may be able to retrieve your data but I don't have that knowledge.. I hope that someone will be able to help you out and good luck...:fingers-crossed:
I'm afraid LMK is right: Your data is gone.
Do I suspect correctly that you interrupted the Wipe Data process after selecting it "accidentally"?
Choosign Wipe Data from the bootloader causes the BL to write a command to the misc partition to start the recovery and wipe the data partition. If you interrupted the process, there's no telling what and where that got corrupted - unless you just let it loop and pray that it finishes the wipe process which would erase the BL command. Connect it to power and let it loop for a few hours. What have you got to loose?
But your data is gone either way - sorry.
Morning, cheeky question(s)
Where are you located, and would you be interested in selling your bricked TF700? I have a broken screen among other things and would be interested in buying your tablet for spares if you are getting a new one?
PM me if you are interested.
Thank you
Freddie
I'm not all too sure what the Icon on the left wad, but I'm sure it said RKU or some sort. I would have given up all hope if I had hit the wipe data on the right.
Days recovery aside, is there anyway I can get my looped tablet to work? I plugged it into a comp and it didn't recognise it.
So heres the story....wife has had lg g2 since it came out with 0 issues. About 3 days ago the phone starts doing some crazy ****, flipping through screens by itself, opening and closing apps, deleting things, rebooting, changing system settings. This was after earlier in the day she had downloaded some random games for my son to play (not sure if this was the cause/is at all relevant, just trying to be as detailed as possible).
My first though was that one of the games may have had some virus/malware **** going on, so did a factory reset. The reset was successful, however the issues continued. Next though was to root/unlock/install custom rom. (I have done this to all my phones, with minimal issues, so i felt fairly confident in doing so) So i rooted, installed twrp 2.7.0.0, and flashed this rom - ATT-stock-rooted-D80020K.zip - and all seemed well. Phone booted and behaved normally for the rest of the day (12 hours or so). Plugged in charger, went to sleep.
Next morning, wake up, grab phone, and its showing the LG logo (like when you first power it on). Restart (power button long press) and it boots into TWRP, and i go looking for the rom file to reflash, and its gone. All files are gone. In the file explorer in TWRP, i can see the files,(data, system, boot, and so on) but when i click on them there in nothing in any folder. All downloads gone. Everything.
But i can still get into TWRP, so i thought ok, ill just plug into pc, mount the phone, copy appropriate files, reflash rom, and all will be good. WRONG. I cannot get TWRP to mount the phone, and at this point ive got a pretty expensive paperweight.
All my unlock/flash/root experience has been on HTC devices up to this point, and i have never had an issue like this.
If anybody can advise what to do next, Im listening. Ive exhausted my knowledge on the subject at this point and NEED HELP PLEASE.
Thanks in advance.
Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3
Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.
Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.
Probably the cleanest solution HERE