HI, I believe it was the .14 update it asked me to update, but after downloading and unzipping, its been stuck on the Acer screen with Booting Recovery Kernal Image on the top left corner for over 4 hours. Can I try to turn off the tablet? Not sure what to do here. Thanks for your help.
This most recent update bricked my Iconia Tab as well. The recovery splash screen loaded, then after a few minutes that hung (the animation froze), and now any attempts to restart the machine go as follows:
Acer logo splash
Android splash
The main interface opens on "Android System", and the Tab immediately goes to shut down.
I'm completely locked out at this point. The shutdown does not turn the Tab off, it's just hung. I can force a shutdown, but restarting puts me back at square one. The reset button will shut down the machine and restart it but that's it.
The power gauge shows that battery to be completely drained, despite the Tab being plugged in long enough to be more than fully charged, and I had no battery issues as of yesterday before the update.
Plugging the TAB in to my desktop I can see the internal drive, I can copy from the internal drive, but I cannot write to or erase from the Tab.
At this point I'm at a loss as to how to interact with it to reset the settings.
Related
Hello, I fear I have bricked my nexus 7 (2012 wifi unrooted) and lost all of my data
What Happened?
Play store would crash on startup so I went to restart my tablet.
When turning my tablet back on it gets stuck on the four circles loading screen and does not load any further.
What Have I Tried?
Firstly I went into recovery mode and tried "wipe cache partition" as recommended elsewhere. This changed nothing
Then I tried to flash 4.4.3 on in hopes it would replace potential corrupt files (whilst also getting an early update )
I used this guide cultofandroid com/63876/install-android-4-4-3-nexus-5-nexus-4-nexus-7/
It failed. When running flash-all.bat (with -w removed) it would be stuck on "waiting for device" and my tablet would also be idley waiting to receive files.
I thought that my laptop could not 'see' my tablet but think it actually could because I tried restarting my tablet whilst it was plugged in still, and command prompt showed some messages (unfortunately I didn't take note and cannot remember what they said!) whilst it was restarting
State of tablet now
I now cannot even get into recovery mode
When I turn my tablet on the normal way it loads to a screen which shows the "Google" text in the center of the screen, an unlocked padlock at the bottom, and the fastboot options top right (clicking them does nothing)
When I turn on my tablet on into fastboot mode and try to get into reovery mode I get an error message in the top left of the screen saying "Booting failed"
I'm out of ideas.
Is there any way that I can get my tablet back working normally with all my data safe?
Thanks for any and all help/suggestions
Don't go into recovery mode, just leave it in fastboot mode and run the flash-all.bat.
(The -w might be needed, as it reformats your partitions. Yes, all your data goes but if there are faulty sectors, this is the only way)
Thanks, I left out the -w but it completely wiped the tablet anyway. Better than having a brick.
Before I assumed you couldn't flash with out getting into recovery.
For anyone else doing this be patient. The command prompt looks like it has stopped a couple of times but it hasn't. Its only finished when it says 'press any key to exit' (took 4-5 minutes for me).
Also when it reboots your tablet it takes a while and actually reboot mine 2-3 times before it loaded up.
Ever since receiving an OTA update a few days ago, my phone was never able to successfully reboot again. Instead, it does exactly this when I turn it on: Samsung logo appears when booting, then the At&t logo with the word "installing..." or "updating..." along with a loading bar at the bottom appears. The loading bar reaches 100%, but then it will say "update failed", and it reboots and the same process happens again. I've let the phone run on it's own for several ours to see if it'll ever snap out of the loop, but it just stays in the same never-ending cycle of constant rebooting and updating. My phone wasn't rooted and worked perfectly fine before the update, so I suspect something went wrong while it was updating. I tried pressing the home, volume, and power buttons in attempt to initiate a recovery boot and do a factory-reset, but nothing happens. And I've tried replacing the battery, SIM card, and micro SD card, but there's still no change. I still am, however, able to set it in ODIN mode, but I'm not sure what to do since I'm not techie/literate. Please help, I don't know how to get my phone properly working again.
I installed a new boot animation on my LG Ultimate 2 (LGL41C), and rebooted it. It then proceeded to boot fine, so I installed a different one. Now, I'm stuck. It'll bring up the boot animation, and restart it about every 48 seconds. I left it like that for 2 hours in the slight chance that it would get out of it on its own, but to no avail. So, I have TWRP on this device, and made a backup earlier today, so I was going to restore from that backup, but I couldn't boot into recovery. Taking out the battery will turn it off, and putting it in and doing anything with the power button, no matter what other buttons your pressing, will bring it into the boot animation. So, I thought I'll flash a ROM. Can't do that either. As I said, the power button will always bring the device into the boot animation, disregarding other buttons. I've plugged the phone into my computer, and the computer makes a sound, letting me know it's there, but doesn't bring up the SD card or Internal Storage.
Dear Galaxy tab experts!
I have read on several places in the Internet that some people has suffered
in a boot loop. The Internet recommends to do a hard reset via
the recovery mode. OK. Unfortunately, my device fails to enter the recovery mode.
My Samsung Galaxy tab 4 SM-T530 has been working fine for for about 2.5 years
until last weekend. Now it does not boot but stays in a reboot loop. That
means that The boot logo shows up for a while and disappears after
about 10 seconds.
I was searching the Internet and I wanted to try out the recovery mode
but I am not able to reach it. When I press Power + Volume Up + Home buttons,
the label "recovery booting ..." appears in the upper left corner of the
display for a while and thereafter, the boot loop continues.
Fortunately, I am able to shutdown my device by pressing
the Power + Volume Down buttons.
The tab has been used about 10 hours per week. I have never uploaded
any ROM or firmware.
The boot loop has started when I was charging my device. I used the
official Samsung USB charging connector as always. During the
charge process, I wanted to see the charge progress like I
have done it many times before but I only saw a grey battery and after that,
the boot loop has started.
I have no problem to do a hard reset and to wipe out my data.
My device contains no important personal data.
What do you recommend to get my device working again?
Thank you in advance!
Starting from the beginning: My phone crashed restarted several times and then black screen with blue led. Then I had t wait for the battery to die because none of the home power vol, power vol keys worked. Eventually got it into recovery mode selected wipe cache restarted same problem.
Now the phone even boot into recovery. It just stays on the blue screen saying "Installing system update" . The little recycling loading icon spins a couple times then its just stuck. Resorted to losing everything and installed smart switch and did emergency restore. Flashed a few times still no joy. Took it to shops they charged it turned it on and its reset to factory. Got it running again, only for it to go into a boot loop. Curious if it was actually fixed, i booted into recovery mode same issue and now back to square one. (I did let the battery die and started it up, came to the home screen and it started rebooting again to black screen and blue LED again.)
I do intend on sending it back but I am wondering could be that the recovery partition is corrupted?