I unlocked and rooted my phone the day I got it on launch day and haven't had any problems until now. My phone randomly turned off and is now stuck in a bootloop. I never installed a custom rom or anything and only rooted to install some root only apps. It just gets to the first screen with Google and the unlocked lock at the bottom and then the google and the lock kind of flicker and move side to side and change colors and then it starts over again.
I'm currently lost, kind of freaking out, and have no idea how to fix this. Any help? Thanks!
Go into fast boot mode and flash stock images.
Sent from my Galaxy Nexus using xda premium
Tried that, but the phone won't turn on at all. Completely dead. Going to Verizon later today, hopefully for it to be replaced. I don't really understand how this happened...if I was messing around with ROMs I would assume it was my fault, but I haven't been.
OK, for some reason my a100 started acting funny today. I went to restart it and it wouldn't get past the Acer screen. So I figured I would do a hard reset. It still won't get past the screen. I am on ICS, was rooted and that's all..no different rom. I have been trying the paper clip method but doesn't get past the first Acer screen. A few weeks ago I had installed the ACER recovery from the market, but never really was able to figure it out. I seem to remember doing a backup with it but that's all.. I've tried the other reset method by holding the volume up and power, and toggling the screen lock switch. It just goes to the recovery but then has an error..recovery verified failed.. is there a way to hook this thing up to a PC like my old DROID x and sbf? See my pic of the recovery error..
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
OK, for some reason my a100 started acting funny today. I went to restart it and it wouldn't get past the Acer screen. So I figured I would do a hard reset. It still won't get past the screen. I am on ICS, was rooted and that's all..no different rom. I have been trying the paper clip method but doesn't get past the first Acer screen. A few weeks ago I had installed the ACER recovery from the market, but never really was able to figure it out. I seem to remember doing a backup with it but that's all.. I've tried the other reset method by holding the volume up and power, and toggling the screen lock switch. It just goes to the recovery but then has an error..recovery verified failed.. is there a way to hook this thing up to a PC like my old DROID x and sbf? See my pic of the recovery error..
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Means you run a custom recovery but have a locked boot loader. Not much you can do if you're no longer on the a200 boot loader to unlock again, you either need cwm/twrp or android running to flash anything at all.
Other option is a stock recovery but emmc corruption leading to the failure. Either way, not much to do besides contacting Acer.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
Thanks for the quick reply..how do I know what bootloader I'm on?
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
Thanks for the quick reply..how do I know what bootloader I'm on?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Upper left corner is a version number, also what color the acer logo is.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
It's the first Acer logo..kinda white/silver looking...how did this happen all of a sudden? It always ran fine..I never did unlock the boot loader, just rooted it to run certain apps..but why won't the stock pin hole method work?
Sent from my DROID4 using Tapatalk 2
Here's a pic with the logo..
Sent from my DROID4 using Tapatalk 2
Well you mentioned a recovery backup which means a custom recovery which means unlocked boot loader. Based on that, the a100 boot loader was restored somehow and locked you out of recovery.
Then you say you never unlocked it, which then means emmc corruption of either the recovery partition or even a portion of the boot loader.
Either way the outcome is the same, a trip to acer.
Custom ROM or not, emmc failure will happen to all a100s eventually, when depends on usage. Acer chose to use a defective problematic emmc on the a100 which is known to brick.
The only potential way around it is to use Linux society / godmachine kernels and his twrp recovery. It may or may not prevent it, but its better then nothing. As its timing is almost random (to us) its nearly impossible to tell if its effective or not.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
hey pio, does increased flashing of custom zips, whether rom, kernel, mod etc. increase the risk of failure? i would think flashing read only memory repeatedly would result in premature wear lending to faster ultimate failure.
your opinion?
Sent via G2x on CM7 b135.1 w/faux 52 kernel
Well.. maybe it did not let me do a recovery... I seem to remember trying anyway. I definitely remember not getting very far with the recovery app itself..and I never unlocked the boot loader because I liked the stock from.. So even if I would not of rooted it it would still do this? I will look in the box for a number for Acer..I lost my receipt though..will they still help me? The Linux thing you mentioned..is that preventative or something I could do now?
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
Well.. maybe it did not let me do a recovery... I seem to remember trying anyway. I definitely remember not getting very far with the recovery app itself..and I never unlocked the boot loader because I liked the stock from.. So even if I would not of rooted it it would still do this? I will look in the box for a number for Acer..I lost my receipt though..will they still help me? The Linux thing you mentioned..is that preventative or something I could do now?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Nothing can repair a tab with emmc failure. The kernel is preventative.
Log onto Acer.com and go through their chat with a rep process. There they'll tell you if its covered or not and what to do about sending it in for repair if that's what is decided upon.
That recovery app wouldn't work without being unlocked, so if you never did that then you never had a custom recovery and that leaves hardware failure if some sort.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
---------- Post added at 05:23 PM ---------- Previous post was at 05:17 PM ----------
justjackyl said:
hey pio, does increased flashing of custom zips, whether rom, kernel, mod etc. increase the risk of failure? i would think flashing read only memory repeatedly would result in premature wear lending to faster ultimate failure.
your opinion?
Sent via G2x on CM7 b135.1 w/faux 52 kernel
Click to expand...
Click to collapse
Yes and no. What we came up with is wear leveling is causing it. The emmc controller accepts a command from the kernel it can't actually do, then begins to blank the emmc, usually killing the gpt. Its been covered elsewhere, so I won't get to crazy on details, but it will happen stock or not. /cache usually triggers it as its most written to, however anything can trigger it.
Flashing and wiping cache can accelerate this issue. My tab had it after 3 months, usually it seems to be 6+ months of normal use to see it. Completely stock ICS never flashed seems to go a year or so, maybe.
Mine had failure pretty quick as its a dev device, in particular developing the black hole nullifier which writes zeroes over each partition. Flashing ROMs and wiping twice or even up to 8 times in a day accelerates the issue also.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
What should I say is the problem? That all sounds pretty complex..lol
Sent from my DROID4 using Tapatalk 2
Well..that was pretty painless..gonna mail that sucker tomorrow.. I had 113 days left..thank bejeezus.. lol
Sent from my DROID4 using Tapatalk 2
droidxxxxx said:
Well..that was pretty painless..gonna mail that sucker tomorrow.. I had 113 days left..thank bejeezus.. lol
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I was gonna say tell them its not booting lol glad it worked out.
Tapatalked from my Galaxy Nexus - Kuroikaze B4
I gave a brief description.. and chose "system hangup" as the issue.. Acer in Texas will be fixing it hopefully.
Sent from my DROID4 using Tapatalk 2
After they fix it..hopefully it won't do it again..I sent it off today..
Sent from my DROID4 using Tapatalk 2
I had the same issue. I tried installing a stock rom from ext SD, and several other recovery methods found in various threads, but when I started the tab up, whilst holding volume button farthest from the rotation lock and toggling the rotation lock, it actually reset everything back to the day I brought it home. It booted into the original HC, and I was able to get the ICS OTA update. Seems to be none the worse for wear at this point.
Sent from my A100 using xda app-developers app
Ok..got my tablet back yesterday from Acer..they fixed it very quickly..props to their warranty department. Now..I assume I got a new main board replacement..which is great..but now..I am on the original honeycomb os..I have tried the update wanting to return to ICS..but it says none is available. Also the market is not upgrading to the Play store..and it forces you into landscape, even if the lock is disegaged. Also, the market is not finding all my apps..and even not recognizong ones I've paid for..and worse of all..is the honecomb camera..it sucks..no panorama..which I was using daily at work. Can I get ICS back? Anybody else having this issue with a repaired a100?
Sent from my A100 using xda app-developers app
droidxxxxx said:
Ok..got my tablet back yesterday from Acer..they fixed it very quickly..props to their warranty department. Now..I assume I got a new main board replacement..which is great..but now..I am on the original honeycomb os..I have tried the update wanting to return to ICS..but it says none is available. Also the market is not upgrading to the Play store..and it forces you into landscape, even if the lock is disegaged. Also, the market is not finding all my apps..and even not recognizong ones I've paid for..and worse of all..is the honecomb camera..it sucks..no panorama..which I was using daily at work. Can I get ICS back? Anybody else having this issue with a repaired a100?
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Slap this stock ICS ROM on your microsd card, named update.zip. http://forum.xda-developers.com/showthread.php?t=1611696
Power off, then press and hold the power and the volume rocker closest to the corner simultaneously for about 5 seconds. The tab will vibrate and update to ICS. Let it sit until it is done. Then there should be a few updates if you check for updates.
Ok..will try that later tonight..it doesn't need to be unlocked or rooted for this?
Sent from my SCH-I535 using Tapatalk 2
droidxxxxx said:
Ok..will try that later tonight..it doesn't need to be unlocked or rooted for this?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It only needs unlocked for custom or modded ROMs, thats a stock leak (if its what I'm thinking) and passes the bootloader locks and recovery fine.
I recently rooted my GS3 because I had heard many pros of rooting your phone. So I did. A few days after, I decided to mess around with my boot animation and when I rebooted my phone the screen stays black, but everything else comes on i.e my phone vibrates when I get new calls and messages. So, I was wondering if I needed to do a hard reset or something? I currently have CyanogenMod 10 installed and was planning on converting back to the Stock Android ROM. Any tips or advice would be appreciated. Thanks!
Try reflashing the same rom to see if it overwrites the boot animation.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Does the screen ever come on or is it just blank when you boot it up ?
Sent from my SAMSUNG-SGH-I747 using xda premium
Edit: I flashed the Stock 4.1.1 ROM back on and everything seemed to be working fine until recently. I can't get my phone to connect to the WiFi at my house. It recognizes other networks, but not my home network.
Hey, everyone. I know this issue has been reported before, but NONE of the solutions are working for me. Perhaps I just have a bad Nexus.
I received the device for Christmas and it has worked perfectly fine. Super fast, fluid, responsive. Then, suddenly, I was using the device and it randomly rebooted. I thought, "whatever, this happens to all devices at one point or another". But then, after I turned it on, it got stuck on the Google startup screen for at least 5 minutes. I decided to restart and try again, but this time, it got stuck on the google screen, rebooted on its own and got stuck on the google screen again, repeating this cycle over and over.
So I went into Recovery mode to wipe the cache and do a factory reset. Not even this would work. The factory reset worked, but when I started up my tablet again, it froze at the Google screen. Eventually, it would just continue the cycle of freezing and rebooting. This is ridiculous. A brand-new, unrooted Nexus 7 on 4.4.2 should not be completely unusable. My warranty is up on the 18th, so I will probably just return it, unless someone has an idea.
Thanks.
domjd56 said:
... so I will probably just return it, unless someone has an idea.
Thanks.
Click to expand...
Click to collapse
That'a your best option. If you haven't modified it in any way then use your warranty.
I agree. Since you did not root it, there is probably something wrong with your tablet and you should get it exchanged while you can
Sent from my Nexus 7
I am going through the EXACT same thing and no one has been able to help.. What I did to fix it was re-flash the 03.15 bootloader and that allowed it to start. I think there's some tablets out there that "don't like" the new bootloader included with the KitKat update and I'm glad to see that it's not just me... At least you are able to return yours. I purchased mine back in August last year
I have a a Samsung galaxy note 4 Verizon, it started rebooting continuously after getting an update.
When I power it up, it shows a message 'Updating app 1/246 and increments it up to 103/246 but then it reboots. I noticed that phone heats up pretty bad. If you leave it alone it will start rebooting at app number 21 or so.
I am willing to put a custom rom or anything else that will work, but since I cannot boot it up, there is nothing that I could do. Please help.
I am a software developer myself but not into android / phones.
Thanks,
Model Number
Please note that the model number is SM-0N910V
agilani said:
Please note that the model number is SM-0N910V
Click to expand...
Click to collapse
My best suggestion would be to install odin on your computer as well as Samsung drivers and odin it back to stock. There are many guides on the very subject here on the forums. That or install Samsung smart switch on comp and phone and do an emergency recovery though that. Good luck!
Sent from my SM-N910P using Tapatalk
agilani said:
I have a a Samsung galaxy note 4 Verizon, it started rebooting continuously after getting an update.
When I power it up, it shows a message 'Updating app 1/246 and increments it up to 103/246 but then it reboots. I noticed that phone heats up pretty bad. If you leave it alone it will start rebooting at app number 21 or so.
I am willing to put a custom rom or anything else that will work, but since I cannot boot it up, there is nothing that I could do. Please help.
I am a software developer myself but not into android / phones.
Thanks,
Click to expand...
Click to collapse
Have you tried calling Samsung Customer Service (at 1-800-SAMSUNG)? They helped me to get my phone working again, although as it turns out I did have hardware problems, so I had to send it in to them and pay $70.31 since it was long out of warranty (2+ year old phone). Hopefully your problem is just software and they should be able to help you get that fixed without sending it in to them.
Hey there Fellow, i had the same problem, nothing wrong with the system. Just change the battery. Goodluck. I bought one for $7.
Do a hard reset and restore your phone to its factory settings.