Database Users

[Q] Desperate Cry for Help :(

Heya XDA - I have no idea WTF happened to my tab. Received notification of a OTA upgrade yesterday, taking me to one of the most recent 3.1 builds (.10 if I remember) - this morning woke up to another OTA update message offering me to go to .11 - accepted, downloaded, tablet hung up during the OTA process.
Now here's where it gets tricky. No matter what I do, when powering up my tablet I get the "Power Off - Shutting down" screen, and a endless spinning circle as the tablet claims to be shutting down. I cannot access any part of the system - all on screen commands are dead, except for the Settings icon in the lower right hand corner - i can click it, enter settings - but the moment I try to select a catagory or change any setting, the system goes right back to the "Power off - Shutting down" screen.
I am way outside the 30 days I can get a trade in - really don't want to have to mail this thing off to Acer.
Here's what I have tried:
One of Vache's full ROM images for my Region - flashed via power and vol process- fails about 1/4 of the way through.
Clearing cache/data - managed to get the vol/power+rotation lock combo going that clears cache and data. Still cannot boot - once I power on no matter what I do I get the "Power Off - Shutting Down" screen.
Tried to do the factory reset via USB keyboard + "Home"??? button? Heard mention this opens up a menu of some sort that I can factory reset from, I have two different USB keyboards and cannot manage to make this happen. Anyone able to explain this? Can this help me?
What's so weird about this - once I power up, I get the "Power Off - Shutting Down" screen no matter what I do. During this time, my battery shows up as %15 - this a500 has been on the charger for hours and hours, overnight last night, was 100% this morning before I applied the OTA update. Even with tablet plugged in, the battery shows as only 15%. What's even weirder - with tablet power off and plugged in, I do not get the red or blue charging light from the power button.
Totally freaking out here, no idea what to do. Anyone able to help?
Edit: When trying to manually flash a update.zip - I am getting the Clockwork Mod (I think?) flash screen - a green droid guy with gears turning. This fails about half way through. I have installed ClockWorkMod before this problem - but cannot enter the clockwork menu by the normal vol/power combo - I am so confused
Edit again: From browsing other posts - seems I am not the only one with this problem. The most recent OTA update failed, every single reboot since then is useless - all I can get is the "Shutting Down.." screen. Trying yet another update.zip via MicroSD to see if I can actually restore my tablet
Edit Yet once more (Problem Resolved!) - no idea how - but after a lot of searching I found a full package with build number 4.010.40_COM_GEN1 - this update.zip flashed with no problems, and my Iconcia is UNBRICKED! Sorry for the panic, everyone

OTA .13 Failure
I have the same problem, but got there by a different path. After many attempts to upgrade to .11 from .7, I downloaded the full file .02 to .11, decrypted and moved update.zip into the external sd card. Used the power / vol- combination and the update to version .11 went on without a hitch. Shortly after that, I received a notice that .13 OTA was available. It appeared to install without a hitch but after it rebooted (automatically) the tablet came back and immediately displayed the never ending Power Off screen described above. I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA

alamotx said:
I have the same proble,, (trim) I would add that a two gears with a belt icon is sitting in the top left corner and "Android System" is noted beside that icon. I have tried every trick I have found in the forums to fix this:
1. Removed the SD card and shut down the tablet
2. Used power / vol- with portrait rotation lock turned on
3. Put the SD Card (with the .11 update.zip file ) back in and tried 1 and 2 again (no change: never ending power Off)
4. Tried power / vol+ with rotation lock. Saw the cach clear and looked very promising. Came back up with the rotating gears guy, but still went back to Power Off.
As soon as the power button is pressed the power icon goes red and stays there. Looks like the .13 update fools the device into thinking the battery is dean and it tries to shut down but never completes the cycle.
Acer A500
Rooted
Acer Recovery installed
.11 last successful update
US (Texas)
Failed .13 OTA
Click to expand...
Click to collapse
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?

Moving to Q&A.
PS: Every Q? thread should be posted in Q&A.

Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning

entropy.of.avarice said:
Exact same problem here. Downloading update.zip files like mad trying to find one that will work. Anyone have any idea what the hell is going on?
Click to expand...
Click to collapse
Me too... Ive tried 104.02, 4.010.22, 141.07, 141.02 none of them are getting me back... I can boot the tablet, but I now have no launcher icons for back, tabs, and home, and of course no clock and settings tab at the bottom. I have no root, and no CWM now. HELP!!!!

entropy.of.avarice said:
Thanks for that - sorry for mispost. Again, as noted in my original post - question answered, issue resolved. Total panic this morning
Click to expand...
Click to collapse
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks

Euclid's Brother said:
Please share your solution for the rest of the community.. if the solution is in a different thread, could you put a link here to the other thread with your solution?
Thanks
Click to expand...
Click to collapse
For sure - sorry about the delay on that, was just so excited to be unbricked after a day of futile effort, I needed a break.
Anyway - here's what I have figured out. Somehow during the ota update I received this morning something failed - the tablet rebooted, and regardless of what I did the moment I booted up I would get the powering down notification. System access was not possible. This was on a 100% stock official 3.1 version - even unrooted before letting the update run.
Tried one of the full ROMS from Vache's thread in the dev section, as well as a bunch of other backup images I was able to find. Every single one failed at about 25%.
After a lot of fail - I gave this thread a try:
http://forum.xda-developers.com/showthread.php?t=1187578
"Bricked Tablet...help!"
I used the link on the bottom of page one - the unencrypted update.zip user kjy2010 was kind enough to upload - here is the direct link - http://www.multiupload.com/WCT2FYLMQC
This one worked - put on MicroSD card and flashed via vol/power method - result - 4.10.40_COM_GEN1 - and I am unbricked! Iconiaroot 1.3 worked for getting root after install - slowing getting my tab back to normal now

A500 boots into shurdown screen

Hi
Someone asked me to look at their acer a500 tablet for them, when it boots as soon as it gets to the desktop, before the DE fully loads even, it comes up with a power off/shutting down message
And it shuts down
Tried the hold the volume up while powereing on and toggling the lock button factory reset 'fix' that seems to be posted everywhere but it didn't work, did once or twice get the android holding an exclamation sign thing once or twice but it did nothing from there
As far as I'm aware it's not been rooted so my question is, anyone know whether I can fix it by downloading a particular rom and trying to get that rom installed with a boot into recovery mode type thing?
Any suggestions I might try welcome

Fixed it now, found an update.zip file, applied that and it's back up and running
Thanks for looking to those that did

A500 suddenly died

Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.

Dopius_Fishius said:
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Click to expand...
Click to collapse
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD

Moscow Desire said:
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Click to expand...
Click to collapse
Thanks MD. I looked up the threads you suggested, and after a lot of screwing around I have installed the APX drivers and used blackthund3r's APX Flash Util 0.3 (The link is broken to the current version) to attempt a recovery of my tab.
Its now sitting at an Acer screen, "Entering Acer Download Mode" while the flash util is sitting at:
Nvflash started
[resume mode]
It's been there for about 10 minutes now, no progress to report. Is it worth just sitting it out, or now that the damn tab shows SOME signs of life, can I just restart it and reset to factory?

And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...

Dopius_Fishius said:
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Click to expand...
Click to collapse
erm for now i would make sure you have all backups of data, cpud etc,.. just incase. you can just sit em on your computer i always try to keep a nandroid of all 3 of my devices each month or so.:good:
edit: and of course keep the link for the thread MD recommended.

Gee. Sounds exactly like mine....
The only thing I haven't tried is an update .zip, but I don't hold out much hope.
Considering parting out at this point....

Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.

Dopius_Fishius said:
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Click to expand...
Click to collapse
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD

Moscow Desire said:
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Click to expand...
Click to collapse
Tried the update.zip - nada
Tried timmiedean yesterday, went into Acer Download mode OK, failed....
If dolps is like mien, the first time he tries to go into recovery, it will crash again...

It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....

tennessee_titan said:
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
Click to expand...
Click to collapse
I told you maaaannnn, go see me cousin in Jamaica maaaannnnn. She do some good things you see
Glad it's running again.
MD

First, is this a SOD?
I can kill it by booting into recovery and get it back by using Blackthunder flash tool to go into APX and letting it sit for 20 minutes or so. Close the program, unplug, reboot and it is back. I would like to use timmiedean (td) and go back to square 1, but it fails at the image detect ( displays ICS 4.0.3 Civato as the current image, a red X for the new image). Has td been proven to work reverting from ICS? Will a boot recovery reflash and a new ROM flash solve this? Is there another way to get out of ICS back to HC?
Any suggestions/comments welcome!
EDIT: I flashed FLEXxx V4. Shut it off, problem still there....

Really frustrated. Trying to use the timmiedean tool, but it requires that the unit be shut off in the middle of the process, which kills it. Does anyone know the whereabouts of the blackthund3r revert tool, or the .apx package for his flash tool. I can't find it...

I'm done with this one. On Ebay for parts.... GONE!!!
Have an A100 now, rooted, unlocked,. on Relix
1 more A500 coming next week

[Q] NFC error puzzle. USB debug not an option

Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!

Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.

notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).

Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris

flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.

S8 Freezes and Reboots after every boot.

Had the S8 for about 3 to 4 months, rooted it four days after getting it; no issues whatsoever, it worked perfectly. Yesterday, after a day of not using the phone, I attempt to use it and find that everytime I try to boot it, it freezes after 10 seconds and reboots.
I have tried flashing stock rom of android oreo for the device and am currently trying to see if nougat will fix my issue.
Edit: After attempting to go into android recovery, I am told the device "fails to open recovery_cause", with an unknown error.
I'd really appreciate some help with this, as I've done almost everything I can think of to fix it.
Edit 2 (5/9/19): I've successfully flashed a version of android pie, which successfully boots into the initial setup screen. Same issue however, after around 10 seconds, no matter what I do, the s8 freezes and reboots.
Given up with the phone, tech support already recommended to go on here to post a question. A new phone has been ordered, and the S8 will be sold in non-working condition. If anyone has any idea about how to solve this still, please say something; if not, have a great day .
Thank you.

Hello,
I have the same problem.
I contacted Samsung with Samsung Members.
They said that i had an app who make the phone crashing during the boot !
They said the proof is your phone don't crash when you make an secure boot :
Turn the device off.
Press and hold the Power key past the model name screen.
When “SAMSUNG” appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key.
Continue to hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
Release the Volume down key when you see Safe Mode.
Uninstall apps that are causing a problem.
Click to expand...
Click to collapse
With this secure boot, no problem during boot
The only problem, is that i have only "official" apps donwloaded with Play Store, and i never find the app that cause the reboot :s