Hi
I can't seem to find an answer to this anywhere.
I'm having an issue with the youtube app, it won't launch after it has been updated, so I hope that a cold boot can fix this, however I can't do it with the usual trick.
When I hold the volume down + power button, I get a menu where I can choose the following:
Enter SD Down mode
Factory reset
Exit update mode
Does anyone know how to perform a cold boot on the LTE version of the Infinity?
A "cold boot" on all devices works exactly the same: Turn it off (not only standby), turn it on. Anything more is either voodoo or includes modifying storage content.
Okay, I thought a cold boot was real
Can you help me with my youtube issue then?
When I open youtube, I get the messge "The application Youtube has stopped". The only way I can open it, is if I remove the application update, but I would really like to use the newest version.
A cold boot is very real.
We have a [How-To] All-In-One Guide For Asus Infinity (TF700) in which all these things are discussed. Right here: http://forum.xda-developers.com/showthread.php?t=1833212
It very clearly says:
Note: Make sure your device is OFF before using this.
** Cold Boot - FastBoot - Wipe Data Menu **
Press Volume Down + Power untill you see a white text on the screen then release the buttons. Use Volume Down to navigate and Volume Up to confirm your selection.You have 10 seconds to make your choise, or else the system will do a Cold Boot by default.
So don't press anything when the white text appears and it will cold boot.
_that said:
A "cold boot" on all devices works exactly the same: Turn it off (not only standby), turn it on. Anything more is either voodoo or includes modifying storage content.
Click to expand...
Click to collapse
Please don't answer if you have no idea what you're talking about. A cold boot clears the cache, a regular boot does not.
No, as I said in my first post, this way doesn't work on the LTE model.
I'm open to all ideas, but I have also tried it with the volume up button, which just tells me that no USB cable is plugged in.
ShadowLea said:
Please don't answer if you have no idea what you're talking about. A cold boot clears the cache, a regular boot does not.
Click to expand...
Click to collapse
Where is this cache located that is cleared with this procedure?
http://forum.xda-developers.com/showpost.php?p=32365090&postcount=13
Not sure if the above link is relevant to the YouTube crash bug.
I remember reading on one of the Android forums about a fix by setting YouTube to the english language or something like this.
---------- Post added at 11:26 AM ---------- Previous post was at 11:22 AM ----------
_that said:
Where is this cache located that is cleared with this procedure?
Click to expand...
Click to collapse
App caches are available under: settings\apps\downloaded\clear cache, uninstall updates, disable (if available)
Thats OK said:
App caches are available under: settings\apps\downloaded\clear cache, uninstall updates, disable (if available)
Click to expand...
Click to collapse
Yes, but app caches have nothing to do with cold boot. Cold boot is power on, executing the bootloader and starting an OS, that's the definition of cold boot since 50 years for any computer.
And I argue that the procedure with holding Volume- and waiting does *exactly* the same as a normal power-on. To everyone who claims it does more: please provide a reproducible way to prove any differences. Otherwise it's voodoo.
@ Thats OK - Thank you very much. Changing the Android language to English, has fixed the youtube app.
_that said:
Yes, but app caches have nothing to do with cold boot. Cold boot is power on, executing the bootloader and starting an OS, that's the definition of cold boot since 50 years for any computer.
And I argue that the procedure with holding Volume- and waiting does *exactly* the same as a normal power-on. To everyone who claims it does more: please provide a reproducible way to prove any differences. Otherwise it's voodoo.
Click to expand...
Click to collapse
I remembered a while ago I did ask Asus tech support about "cold boot" vs normal power cycle and he said: A cold boot is different from a normal power cycle (hit the power button to turn off and on). With normal power off/on, it will not clear various caches in ram, kind of like you restart a computer from a restart button, versus you unplug the power cord then plug it back in. a cold boot it performs a "clean" boot. He provided example like video display, if you experiencing flickering or color fade or color spot on the screen a normal boot will not address the issue but a cold boot will. I did ask him about what are "various caches" and being told that they are hard ware cache like graphic, preloaded ram space etc..(too much technical at this point). And yes you're right he said it has nothing to do with application cache or data. Again a normal boot is NOT same as cold boot. He said the right way to do a cold boot (he refered a cold boot as hard reset, they are the same under Asus technical term), you must unplug your device, then power down, then do the button combinations, navigate to the Android icon then execute it. A cold boot does resolved issue like FC, weird screen issue, stutter, lag etc...(it will not resolved issue if software bug, or hardware issue). The last thing he said is hitting reset with the pin hole is same as cold boot (clear various caches).
buhohitr said:
I did ask him about what are "various caches" and being told that they are hard ware cache like graphic, preloaded ram space etc..(too much technical at this point).
Click to expand...
Click to collapse
Voodoo spread by Asus support to keep the customer busy.
All those "various caches" are made of RAM. So they lose their content when the power is turned off, and are initialized when the system is booted. When the bootloader screen appears, these caches are already as clean as possible.
Let's try to find some evidence. The Tegra 3 TRM says:
* Frozen boot: The RTC partition power transitions from OFF to ON
* Cold boot: The main partition power transitions from OFF to ON with no previous state available, SW must construct all state from scratch. Boot ROM is executed. DRAM is brought on-line.
* Warm boot: The main partition power transitions from OFF to ON with previous state available, SW checks for the preserved state integrity and restores the saved state from DRAM, which was in self-refresh prior to warm-boot. This is also called Deep Sleep wake-up or LP0 exit.
Click to expand...
Click to collapse
As you can see, "cold boot" is the only one that involves the boot ROM (which starts the bootloader) - or vice versa: any reboot that involves the bootloader screen is a cold boot.
buhohitr said:
A cold boot does resolved issue like FC, weird screen issue, stutter, lag etc...(it will not resolved issue if software bug, or hardware issue).
Click to expand...
Click to collapse
No doubt on that. Running programs can have an impact on each other and on the system performance. But as long as nobody provides a plausible explanation what exactly that magical button fiddling in the bootloader would really do differently, I don't believe it makes a difference *how* you reboot.
LiquidoDK said:
@ Thats OK - Thank you very much. Changing the Android language to English, has fixed the youtube app.
Click to expand...
Click to collapse
No problem my friend!
So glad to be of some small help.
Enjoy YouTubing!
jim
_that said:
Voodoo spread by Asus support to keep the customer busy.
All those "various caches" are made of RAM. So they lose their content when the power is turned off, and are initialized when the system is booted. When the bootloader screen appears, these caches are already as clean as possible.
Let's try to find some evidence. The Tegra 3 TRM says:
As you can see, "cold boot" is the only one that involves the boot ROM (which starts the bootloader) - or vice versa: any reboot that involves the bootloader screen is a cold boot.
No doubt on that. Running programs can have an impact on each other and on the system performance. But as long as nobody provides a plausible explanation what exactly that magical button fiddling in the bootloader would really do differently, I don't believe it makes a difference *how* you reboot.
Click to expand...
Click to collapse
I don't think that Asus developers just waisting time to put the extra icon in there just for fun. So it's just common sense that on our PC, we could unplug the power cable or hit the switch on the power supply to get cold boot. However on the infinity, there is a non removable battery build in so you can't removed or unplugged it. In short, a cold boot is like take out the battery of the infinity..make sense!!
buhohitr said:
I don't think that Asus developers just waisting time to put the extra icon in there just for fun. So it's just common sense that on our PC, we could unplug the power cable or hit the switch on the power supply to get cold boot. However on the infinity, there is a non removable battery build in so you can't removed or unplugged it. In short, a cold boot is like take out the battery of the infinity..make sense!!
Click to expand...
Click to collapse
This is a nice theory, and it would really make sense, but if you do this "cold boot" procedure, the power stays on, as you can verify for yourself. And also on the PC there is no difference between booting from soft power off (power button) or hard power off (switch on power supply).
The whole thing is more like if you press F8 on the PC - you get a boot menu, but then you can still select to start Windows normally.
Is it not possible that the cold boot icon in the bootloader menu actually clears the cache partition (which doesn't get cleared on a normal power on/off cycle)?
I would have to believe that the cold boot does do something different than simply powering off and on - why else would they include it?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Is it not possible that the cold boot icon in the bootloader menu actually clears the cache partition (which doesn't get cleared on a normal power on/off cycle)?
Click to expand...
Click to collapse
I tried it - it doesn't. And it would not have any major effect, because the cache partition is only used for communication between Android and the recovery.
jtrosky said:
I would have to believe that the cold boot does do something different than simply powering off and on - why else would they include it?
Click to expand...
Click to collapse
Maybe just to start Android normally if you changed your mind? Just like the "Start Windows normally" option in the Windows bootloader if you pressed F8.
Related
Today I accidently entered Safe Mode on my ICS 4.04 Haipai i9200 phone and a user in our thread knew that most Android phones have this feature. Here is what I wrote and it applies to most Android phone systems. If you see the words, "Safe mode" in the lower left corner of their phone and or experiencing boot loop due to force closure. Here is what I wrote:
robarnold is right about Safe Mode and the article he posted (which is now linked in my quoted reply) provides more information about Safe Mode. Please see the attached picture to see what Safe Mode looks like on our phones. If your phone were to enter Safe Mode, those words would appear on all your screens. As per the article, most if not all your apps will be suspended or not work.
Basically there are two known ways to enter Safe Mode:
1. Android detects a problem with a newly installed app and force-closes it while entering into Safe Mode.
2. A combination of key presses at power application;
Newly installed app force-closes the system
The gist of the article provided by Rob says that if a newly installed app causes system conflicts, Android will force close that app to prevent it from possibly doing malicious harm. At the same time, Android will suspend the majority of all other apps and display "Safe mode" in the lower left corner of your phone as per the picture.
The reason for this is to provide the user an opportunity to clean the system of the app which is causing the force closure. Chances are it the most recent app installed but it could be a combination of apps that are coming into conflict with one another.
If you suspect a newly installed app of causing this problem and you see Safe Mode on screen, STOP, COLLECT YOUR WITS and BREATHE NORMALLY. You have several options.
SAFE MODE OPTIONS
1. Press the System or Menu Button in the lower left corner and navigate to Manage apps.
2. Find the most recent app you installed.
3. Force close it.
4. Disable it if possible.
5. Remove this app.
6. Reboot the boot to see if the Safe mode is gone.
If the Safe mode label is still present, the article suggests that it may be necessary to press several keys to achieve the removal of the Safe mode label and its effect of suspending the other apps. In essence, we now move to the second discussion of entry into Safe mode:
1. Safe mode can be entered by pressing buttons at start-up. Most likely, this is what I did today as I was getting ready to leave for an appointment. The Safe Mode label freaked me out and when I could use the Rebooter app or any other app, I became scared.
2. I don't know exactly which buttons I pressed but it mostly likely was the System and Home (center big button) and maybe even the Escape/Back button on the right. My phone slipped slightly as I turned it on and my left thumb was flying as I manuevered my left hand to balance the phone.
3. The right combination of buttons, which supposedly are the same to enter Safe Mode, are the same to exit Safe Mode.
4. If you are certain you entered Safe Mode by accident - meaning you know you did not recently or just now installed an app that force closed Android, then you just have to find the combo to exit it.
5. The article suggests that pressing the volume buttons might clear the Safe Mode on the first reboot after initial entry into Safe Mode.
6. If the Safe Mode label disappears after pressing the volume buttons, your phone is okay.
7. If the label is still present, try rebooting the phone again.
The article suggests as per my experience that if you cannot clear the Safe Mode, your last resort is to do a factory reset of the phone. Fortunately in my case, I had ClockworkMod Recovery available and restored my system via a backup recovery.
ronbo's Final Thoughts
Hope I never see Safe Mode again (and, I won't go looking for it) but I recommend you learn how to do a Factory Reset by pressing and holding the Volume Down Button with a simultaneous press of the Power Button. You want to see the Factory Test and Reset Menu when you are calm. TRUST ME ON THAT!
robarnold said:
Hi,
Yes safe mode exists and is a useful if not essential tool for those of who like to experiment with their Android devices.
I'd suggest that it will always be worthwhile to know how to access Safe Mode and recover from it if you are going to install unsigned apps.
The following link may more useful to those who would like to know more:
http://www.tested.com/news/feature/3071-how-to-use-androids-safe-mode-to-save-a-phone-from-boot-loops/.
Cheers
Rob
Click to expand...
Click to collapse
help me with sony arc s cant get it off
Safe Mode = Wet Phone
Just a quick note for anyone who runs into the variation of this problem that I had today.
Using my Nexus S today in the rain. Phone got wet. Specifically, damp got into both the Power button and the Volume rocker.
The result was when the phone was restarted (after I removed the battery and dried it out) it came up in Safe Mode.
Which is how I wound up here.
(Minor site quibble: in the course of registering here and making this ONE post, I've been subjected to FOUR captchas. I like sharing information, but this is really WAY more nuisance than is worth it for me.)
whoa !!! I just did boot up my xolo a500 in sage mode . I was shocked . so I just pulled my battery and re insterted it . now its normal
Appalbarry said:
Just a quick note for anyone who runs into the variation of this problem that I had today.
Using my Nexus S today in the rain. Phone got wet. Specifically, damp got into both the Power button and the Volume rocker.
The result was when the phone was restarted (after I removed the battery and dried it out) it came up in Safe Mode.
Which is how I wound up here.
(Minor site quibble: in the course of registering here and making this ONE post, I've been subjected to FOUR captchas. I like sharing information, but this is really WAY more nuisance than is worth it for me.)
Click to expand...
Click to collapse
I have this same issue except my phone doesn't have a removable battery (evo 4g lte). My down volume button doesn't work and I can't seem to escape safe mode no matter what I do help?
Sent from my Nexus 7 using Tapatalk 2
guih said:
I have this same issue except my phone doesn't have a removable battery (evo 4g lte). My down volume button doesn't work and I can't seem to escape safe mode no matter what I do help?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Same issue..
skywayskase said:
Same issue..
Click to expand...
Click to collapse
Try the adb command
Adb reboot
sent from my super advanced mini fridge
A work-around for phones stuck in safe mode due to water damage etc but that seem to work fine otherwise is to convert the (trusted) apps you need from data apps to system apps (move the .apk from /data/app to /system/app after installing via the Play Store). You may need to use Mounts2Sd or something similar with an sd-ext partition if you don't have enough space in your internal /system partition for all the apps you need. (With Mounts2Sd, placing the apps in /data/app-system on the sd-ext partition will fool the phone into thinking the apps are in /system/app and you can then use them in safe mode). If anybody is aware of a simpler script that does the same thing, please lmk.
If this helps you, please hit the Thanks button.
i have this on my tab 3 i can't exit from it tried reboot and factory restart and shut down
what is the solution ?
Same issue here...
Appalbarry said:
Just a quick note for anyone who runs into the variation of this problem that I had today.
Using my Nexus S today in the rain. Phone got wet. Specifically, damp got into both the Power button and the Volume rocker.
The result was when the phone was restarted (after I removed the battery and dried it out) it came up in Safe Mode.
Which is how I wound up here.
(Minor site quibble: in the course of registering here and making this ONE post, I've been subjected to FOUR captchas. I like sharing information, but this is really WAY more nuisance than is worth it for me.)
Click to expand...
Click to collapse
I am facing the same problem. I had used my phone in rain. Now the volume down and power button are not working. And the most irritating part is that it rebooted into Safe mode which I dont like. Done factory resetting which took me from safe mode but the volume down and power buttons are still not working.
Anyone knowing how to get rid of these, please share it... Thanks in advance !!!
Lawrence kunhi said:
I am facing the same problem. I had used my phone in rain. Now the volume down and power button are not working. And the most irritating part is that it rebooted into Safe mode which I dont like. Done factory resetting which took me from safe mode but the volume down and power buttons are still not working.
Anyone knowing how to get rid of these, please share it... Thanks in advance !!!
Click to expand...
Click to collapse
How did u get rid of "safe mode"? I have vol down stuck and phone always goes into safe mode
I tried a factory reset from setting>backup and reset>factory data reset and phone shuts down...the i have to press power button and phone gets into safe mode again.
got the same problem with my lenovo a859. it got wet and now just boots into recovery where i can not choose any other options besides the first (reboot system now). Is there any way to start the phone/ do a factory reset?
I have a parental control program on my kids phone.
Safe mode of course enables to erase it.
Is it a way on a rooted android to disable it?
Turn off safe mode
Yes, safe mode does exist. It is the default mode in your android phone without extra apps installed. When in safe mode you cannot use your favourite apps. I understand it can get irritating some times.
You can try rebooting your phone. It worked for me.
---------- Post added at 04:40 PM ---------- Previous post was at 03:51 PM ----------
If that does not work, here's a guide that helped me exit safe mode
Eagleman71 said:
I have a parental control program on my kids phone.
Safe mode of course enables to erase it.
Is it a way on a rooted android to disable it?
Click to expand...
Click to collapse
Did you find a solution to your problem?
Is there anyway to completely disable safe mode, e.g. by adb?
i just had an episode of an issue that worries me.
I had the tf700 docked and put to sleep by closing the keyboard/tablet. 8 hours later, I pressed the power button and nothing turned on. I thought somehow the battery completely drained, so I plugged in power adapter and still nothing. I tried holding down power and nothing.
Then I undocked, and plugged in ac adapter. After holding down power button for quite a few seconds, i get th screen to come on and the message to confirm tuning the unit off. Apparently the unit has been on but the screen off.
After I rebooted, I find the unit sluggish as if I/O issues again.
I am on firmware .26 US latest. It has been fine until now.
My biggest concern is that I remember a friend of mine describing this issue with his TF101, and said the only way to get it back on was by plugging in the power adapter.
Anyone else can shed some light on this?
I've had this on my SGS2 a few times, and on my previous phone (LG O2x as welll) -- in both cases it was related to issues with deep sleep (and on the SGS2 standard custom kernel undervolting), implying that changing kernels would cure this (or make it immensely worse, hahaha ). Having said that, I do recommend following this issue closely, and if this happens again, I'd reflash .26 from a full wipe. If it then still does it, I would suspect some hardware issue.
Again, to at least provide you a bit of reassurance: I've never encountered the error on my SGS2 again after flashing a (very, very nice) kernel, and the O2x only does it very infrequently now (but has crappy kernel development, at least when I checked last, so I'm still not very satisfied. Might tryCM9 with it or something...).
MartyHulskemper said:
I've had this on my SGS2 a few times, and on my previous phone (LG O2x as welll) -- in both cases it was related to issues with deep sleep (and on the SGS2 standard custom kernel undervolting), implying that changing kernels would cure this (or make it immensely worse, hahaha ). Having said that, I do recommend following this issue closely, and if this happens again, I'd reflash .26 from a full wipe. If it then still does it, I would suspect some hardware issue.
Again, to at least provide you a bit of reassurance: I've never encountered the error on my SGS2 again after flashing a (very, very nice) kernel, and the O2x only does it very infrequently now (but has crappy kernel development, at least when I checked last, so I'm still not very satisfied. Might tryCM9 with it or something...).
Click to expand...
Click to collapse
Before doing any of that I would do a "cold boot." That can solve your problem in its entirety before having to use drastic measures.
superflysocal said:
i just had an episode of an issue that worries me.
I had the tf700 docked and put to sleep by closing the keyboard/tablet. 8 hours later, I pressed the power button and nothing turned on. I thought somehow the battery completely drained, so I plugged in power adapter and still nothing. I tried holding down power and nothing.
Then I undocked, and plugged in ac adapter. After holding down power button for quite a few seconds, i get th screen to come on and the message to confirm tuning the unit off. Apparently the unit has been on but the screen off.
After I rebooted, I find the unit sluggish as if I/O issues again.
I am on firmware .26 US latest. It has been fine until now.
My biggest concern is that I remember a friend of mine describing this issue with his TF101, and said the only way to get it back on was by plugging in the power adapter.
Anyone else can shed some light on this?
Click to expand...
Click to collapse
happened to me too, I did a "cold boot" and it seems fine now.
buhohitr said:
happened to me too, I did a "cold boot" and it seems fine now.
Click to expand...
Click to collapse
what is a cold boot?
it has only happened once, so its probably infrequent. However, I am more afraid of the inopportune times it cn happen. What if it happened when i am away from home with no ac adapter, like on a plane? I won't be able to boot then?
superflysocal said:
what is a cold boot?
it has only happened once, so its probably infrequent. However, I am more afraid of the inopportune times it cn happen. What if it happened when i am away from home with no ac adapter, like on a plane? I won't be able to boot then?
Click to expand...
Click to collapse
Here is how to "cold boot" (copy and paste from other thread), should resolved your issue.
1. Press and hold down “power button” until the system shuts down.
2. Remove the SD card from Eee Pad.
3. Press and hold down “Volume down” button first, and then press and hold down the “Power” button until the screen appears with 2 icons, one is a droid and one is wipe data and upper left corner should said cold boot linux.) now let go your fingers. Make sure do not press any buttons until the screen mentioned screen appears. If you don't see the 2 icons in the middle of the screen re start from step 1.
5. There’s a line “Press <Vol_Up> to execute, <Vol_Down> to cancel wiping data. Press Volume Up button to execute the “Wipe Data”.
6. After the “Wipe Data” process is done, it will reboot automatically. Then Eee Pad should be able to enter the system successfully.
oh, so cold boot means wiping all apps? have to reinstall everything from scatch r use ttanium backup?
Hi, just wanted to add, happened to me also on my tf700,... I tried factory reset, didn't help, then I tried buhohitr advise of doing a cold boot wipe and that seems to be good.... is only been one day since I tried it, But so far so good... and yes, a wipe does delete your apps if you do a proper wipe.
Thanks!
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.
Whenever I turn off or reboot my phone from the ROM's power menu the system takes a second or two to close apps and then turns off. While the reboot utilities turn off the OS the moment I press the reboot/power off option on the menu.
Are these utilities safe to use as they seem be like yanking the power cord off of a running device?
(I'm on 5.0 preview and the power menu is limited to just Power Off for now, and I'd like convenient options to go to recovery/bootloader, but not at the cost of corrupting OS files, thanks)
thanks so much people, but don't everybody speak at once.
the_rebel said:
thanks so much people, but don't everybody speak at once.
Click to expand...
Click to collapse
That's a sure fire way to get an answer.
It kinda worked.
the_rebel said:
It kinda worked.
Click to expand...
Click to collapse
Not really. I didn't give you a useful answer. I didn't know the answer the first time I read the thread. You're right that it needs to unmount the filesystems cleanly when shutting down, but whether that's what is happening when you shut down via the power menu that causes the delay I don't know
I use the "reboot" command all the time though, and I haven't lost any data yet
Yeah it usually works safe enough, but I vaguely remember an year or so back on my N4 it created some problem, and I stopped using any abrupt reboots. Stopping to use those was easy on custom ROMs anyway.
The logic is sound. If there's some file activity going on, an abrupt reboot will cause file system corruption - hell we use safely remove on USB drives too, this is a whole computer.