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.
Related
so umm .. is clockwork mod now bricking phones? I tried to use the app to backup the phone... and when it was shutting off i saw a couple of apps that stopped responding and then it shut off .. after several minutes of it not doing anything at all .. I took out the battery to manually get into recovery and back it up .. but .. it never came back on.
Damn thing is hard bricked. No recovery .. no vibrate, lights, and no boot of any sort when the power key is pressed and also no download/odin mode either .. completely dead.
i have/had the hard recovery on the phone and was the latest of recovery and rom manager too .. I was on the official ICS nightly ROM from a couple days ago.
sooo is this something that is happening a lot? I heard from someone that the phones have an unstable system partition that is causing it .. but only unstable after its rooted .. anyone hear anything about these things??
thanks!
Strapt said:
so umm .. is clockwork mod now bricking phones? I tried to use the app to backup the phone... and when it was shutting off i saw a couple of apps that stopped responding and then it shut off .. after several minutes of it not doing anything at all .. I took out the battery to manually get into recovery and back it up .. but .. it never came back on.
Damn thing is hard bricked. No recovery .. no vibrate, lights, and no boot of any sort when the power key is pressed and also no download/odin mode either .. completely dead.
i have/had the hard recovery on the phone and was the latest of recovery and rom manager too .. I was on the official ICS nightly ROM from a couple days ago.
sooo is this something that is happening a lot? I heard from someone that the phones have an unstable system partition that is causing it .. but only unstable after its rooted .. anyone hear anything about these things??
thanks!
Click to expand...
Click to collapse
What app are you referring to to back up your phone?
Sent from my SGH-T989 using Tapatalk 2
Same Here
My S2 got hard bricked too. I was on TDJ's DARKSIDE.UCLE2 with Blaze 4G LB7 radio. Thought about trying out CM9, which flashed just fine and was working well. But after i tried to back it up with CWM, it got stuck. Took the battery out and hasnt been on since. Wont power on, wont go into download. Ordered a USB Jig to try if it works. If not, gon send it on its way to samsung repair service.
snguyen0730 said:
What app are you referring to to back up your phone?
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
clockwork mod Rom Manager
BiGrOsOuTh said:
My S2 got hard bricked too. I was on TDJ's DARKSIDE.UCLE2 with Blaze 4G LB7 radio. Thought about trying out CM9, which flashed just fine and was working well. But after i tried to back it up with CWM, it got stuck. Took the battery out and hasnt been on since. Wont power on, wont go into download. Ordered a USB Jig to try if it works. If not, gon send it on its way to samsung repair service.
Click to expand...
Click to collapse
hmmm so its not just me then .. thats good to know .. and also sucks too .. so i wonder if that means that the Rom manager app is pretty useless now on the ICS .. or what the hell happened there.
Hold the power button for 10 seconds and see if something happens
Sent from my SGH-T989 using xda premium
JPOKeefe said:
Hold the power button for 10 seconds and see if something happens
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
oh I did .. and also times much longer with that ... same with trying to get it into download mode ... with and without a usb .. different cables ... different ports .. and so on .. not doing a thing at all
I already rooted the replacement .. but my deal though is that im concerned that it will happen again with Rom Manager .. seems like one other person has had this issue with it as well ... is Rom Manager something we should stay away from using now if this has been happening for others as well ..?
Okay first off yall deff need to stop taking battery out and also Do Not Take It Out While In Recovery hold power button until it reboots like dude said^ rom manager is not a reliable app anymore i wouldnt use it
Sent from my SAMSUNG-SGH-T989 using xda premium
casonswag said:
Okay first off yall deff need to stop taking battery out and also Do Not Take It Out While In Recovery hold power button until it reboots like dude said^ rom manager is not a reliable app anymore i wouldnt use it
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
This happened to me as well today... never had a problem with it before. Now all of a sudden today I used it to boot into recovery and phone shut off and never turned back on, can't get into download mode nothing... what a POS app, which should be removed or blocked access from all roms. How on earth would this app cause a hard brick... it makes no sense. What does it do when it sends a reboot to recover command.
This happened to me yesterday. I've been running CM9 for months with no problems. No problem using CWM on it to do backups. Yesterday I decided to use ROM Manager premium to back it up. I entered a file name, pressed the button, the screen went dark, and it's been dark since then. The battery was as 98%. It has not responded to any key combination since then.
I've never seen anything like it, and I've had 10 or so different devices that I've rooted with recoveries.
No replacement for titanium backup. Just for those reading this.
Hope you guys get your phones working tho! That sucks!!
Sent from my cell phone telephone....
I have been having a reboot problem on my t989, it has been turning itself after ive turned it off when i plug it into a charger.I have been trying to figure this problem out for the last to months and a havent pin pointed the problem. i have checked if it was the sd card and it wasnt that , it happened two months ago when i was running darkside evolution v8 tdj.and have tried many roms to see if it was darkside and it was not. but whenever I switch to a stock firmware such as GB or stock tmobile ICS the problem stops. i am currently running clones and drones. please if anyone knows how to fix this problem or knows whats causing this to happen it will be very appreciated. thank you!
Sounds to me like you already know the cause. When you go back to stock, do you also replace the recovery? I seem to recall there was a similar glitch in the tmo g2 where it would boot to recovery if it was powered off when attached to the charger.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
tronmech said:
Sounds to me like you already know the cause. When you go back to stock, do you also replace the recovery? I seem to recall there was a similar glitch in the tmo g2 where it would boot to recovery if it was powered off when attached to the charger.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Its not booting into recovery its turning itself on. And yes when I switch to the stock firmware I flash it via Odin.
Well, I would say to try at least one other rom. The phone has to at least partially start up in order to control the charge cycle. (Chainfire has a charge animation replacement for one of the galaxy s phones on the play story, IIRC) So at least part of the kernel starts...
Sent from my Polaroid Tablet using Tapatalk 2
Okay I will try that. And I was watching it do the self turn on and on the top corner very shortly it says something about safe mode and I'm guessing that's directly corrilated with the problem but how is it related is my question
I got my Galaxy Nexus 3-4 days back and have been using it pretty nicely. Suddenly today while activating bluetooth via an application called 'Notification Toggle', my phone crashed and the boot animations begun to come up.
The animation were taking a lot of time so I pulled the battery out, re-inserted it but was still stuck at the boot animation.
Then I charged my phone for about 45 minutes - 1 hour, tried booting up again but still stuck at that animation.
I am from India and the Galaxy Nexus is not launched here officially so it's not even under warranty.
Please help me, what can I do? I'm really worried and don't have much knowledge about Android (as this is my first Android phone).
My phone is running Android 4.0.4 ICS and is GSM unlocked.
I request any of you to please post a detailed solution so that I can get my phone up and running. I'm fine if there is any sort of data loss but I'll prefer to have my data restored.
Thanks in advance.
I wouldn't say that I've been experiencing the same problem as you described. Meanwhile, before Droid I was using IPhone 3G. And I can say that several times both of phones were completely stuck for lot's of hours or even a day/night without any reasons. But then, they become alive again without any sign of what has happened. I'm not experienced technically, but I think that each system has it's own recovery settings which continue to work even when system is off. Or when the system couldn't repair itself it's just restarting after sometime. If you bought your Nexus officially, and it's not have been used and "raped", then I think it should be back soon.
Sent from my Incredible S using xda app-developers app
Is it unlocked or rooted? if so I would recomend using fastboot to restore it to complete stock condition. If not..... I have no clue
Are you rooted or have a custom recovery? If so, just wipe data and reflash your current ROM.
If your phone is bone stock, you will more than likely have to download the device's stock fast boot images and flash them.
I'm not sure how this will affect your unlocked radio. Maybe someone else can help you from here.
Sent from my Galaxy Nexus using Tapatalk 2
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file.
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file.
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
The HTC legend always looks for legimg.zip or simular file name when booting into bootloader..
If you can't boot into android at all, even though you tried lots of roms and kernels it sounds to me like something has fried.
Sent from my HTC Desire HD using xda app-developers app
ranger4740 said:
The HTC legend always looks for legimg.zip or simular file name when booting into bootloader..
If you can't boot into android at all, even though you tried lots of roms and kernels it sounds to me like something has fried.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
No no the phone boots and works well. But if the phone just sits there and the screen goes dark to lock itself it'll do a quick reboot. If I lock it myself it'll do a quick reboot. However when its plugged in to a charger it won't reboot if that makes sense... Its like the screen doesn't like to be off when its off the charger lol
Sent from my HTC One XL using Tapatalk 2
Hey
If it goes straight into the bootloader, then it sounds like something has fried inside or there is something stopping it booting.
Have you flashed the boot.img with each ROM?
And yes, if it looks for a PD198IMG.zip it is normal.
If you need some extra help, post in the Ace Think Tank & you'll get some help pretty quickly
Ugh sorry guys I may have trouble explaining what its doing... It doesn't boot straight to bootloader.. .. It boots straight into the ROM like its supposed to. (CodefireX)... the device works flawlessly. Till the screen dims and sleeps. Then it reboots automatically. If I set the display option to sleep after 10 minutes, it works awesome for 10 minutes. Till it sleeps. Then it reboots. If I put it on the charger, the random reboots stop, and im able to lock and unlock the device like normal... If i unplug it while the screen is off, it reboots automatically...
I only posted a picture of bootloader to let you guys know which version hboot I have and s-on etc.
I shot a little video of it doing it. However for some reason YouTube won't allow me to upload.. And I'm scared a 2 minute 30 second video will rape my data plan if I upload to drop box....
Sent from my HTC One XL using Tapatalk 2
Have you tried replacing the battery?
No... That thought came across me also.. I'll stop by RadioShack today if I get a chance...
But it still makes me wonder... It didn't do this before I took that update... I'll flash early ROM and see if the aahk will take to it so it'll s-off... Then I'll try to run the original RUU... If its still rebooting like that I'll get another battery for sure...
Is there ANY custom kernels that'll let me play with the voltage? I haven't seen one yet that'll brings up a voltage tab in any freq app.. Tried a few kernels sense and aosp... Tried kernel tuner, setcpu, voltage adjuster, and no frills
Sent from my HTC One XL using Tapatalk 2
AAHK is retired.
InflatedTitan said:
Hopefully someone could give a few more opinions before I throw this thing in the trash can... I'm still having the reboot issue... I can use it for hours on end as long as the screen is on. It will stay on if its connected to any power source... But when its not plugged in and the screen locks it reboots about 3 seconds later...
Didn't do this before I took the 2.35 ota.. I've tried 15 different ROMs, different kernels, I tried overclocking and trying to get rid of deep sleep. Don't know what else to do. I'd love to try to raise the voltage but every kernel/ROM I use doesn't give me that option.
Also I'd like to mention when I boot into bootloader it immediately searches for pd98img.zip. is this normal? I never seen another boot loader look for a certain file.
Anyway, any help will be appreciated... I'd hate to get rid of this phone if its fixable...
This is the bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
ur battery is gone
Really? That sucks lol... Just don't understand why it don't do it as long as the screen is on... I can literally be on it for hours with any reboots... Oh well, thanks alot guys.. I guess I can rule this one from the update screwing me
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Really? That sucks lol... Just don't understand why it don't do it as long as the screen is on... I can literally be on it for hours with any reboots... Oh well, thanks alot guys.. I guess I can rule this one from the update screwing me
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Well coz ur battery doesnt hv the power to wake up the phone from sleep which I might add requires a bit battery power
Sent from my GT-I9300 using xda premium
I need some help with this issue. My tablet is stock out of the box. I have been using it since last Friday. But today I turned it off then after an hour later I turned it back on, it gets stuck at x logo. I really dont know what issue is called? I have tried to restart the tablet several times by holding the powerbutton, but it is still stuck at X logo, and I have tried to use recovery mode in bootloading, but I get no command message everytime.
If you don't have a lot on your nexus and don't mind wiping then just hold power and vol up, which will data wipe your nexus. I know when I first started my nexus it would go to the welcome screen and then bootloop if I didn't click the next button fast enough. But you're saying you've been using it so dunno.
or you could fastboot then flash twrp and try to clear cache/dalvik and see if that helps
mmikeee said:
If you don't have a lot on your nexus and don't mind wiping then just hold power and vol up, which will data wipe your nexus. I know when I first started my nexus it would go to the welcome screen and then bootloop if I didn't click the next button fast enough. But you're saying you've been using it so dunno.
or you could fastboot then flash twrp and try to clear cache/dalvik and see if that helps
Click to expand...
Click to collapse
Thank you for replying. I tried like you said holding vol up+power button, but I got no command message.
david84us said:
Thank you for replying. I tried like you said holding vol up+power button, but I got no command message.
Click to expand...
Click to collapse
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Just as a side-note, I've had 2 Nexuses 7 (the older versions) and BOTH of them did this to me when updating to a higher version of Android. I swore like a madman as I had to hard-reset the device thus losing nearly all my data. If anyone reports that this happens with the new Nexus, it might be the deciding factor for me to not buy it... unfortunately...
dark2099 said:
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but I still get no command message screen.
david84us said:
Thanks, but I still get no command message screen.
Click to expand...
Click to collapse
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
dark2099 said:
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for all inputs, but I am new/noob about these stuffs, and im still able to exchange, so I'm going to exchange for another one. Thank you everyone who tried to help me. Have a nice day.
It's really easy to do. I had the same issue as you and a factory reset corrected it. Just make sure to follow the steps and everything will be fine
dark2099 said:
Try using the freshly updated toolkit by WugFresh.
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Wugfresh has the best root toolkit for Nexus, period.
dark2099 said:
First hold power+volume down to go to boot loader, then select recovery, then in recovery do power+volume up. I think that's the proper order.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I'm having the same issue since last Saturday when I picked it up. Still running stock and it just would not boot up and it seemed no one else was facing any problems. So I did fastboot unlock, it reset the device and cleared all data. Since then, I've been running stock, and I'm still facing the issue. I'm not sure if it's actually an issue with stock or not.
Just had this same problem on a brand new nexus 7 only a couple of days old. I really can't believe Asus/Google has these problems in 2013. Unbelievable.
Do you have a custom recovery installed?
Just happened to me very weird.
Sent from my Nexus 7 using xda app-developers app
Have you guys tried 1 click factory reset?
It happened to me with old. Exchanged it. And happened today in new one this time I was able to turn it off then try again and it booted. Started after 6 days of flawless use. Weird.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
Just happened to me...
I just had my SECOND one do this to me this morning. I bought the 2nd Gen Nexus 7 last week and it did this within an hour of using it (after an update). I took it back and got another one. This morning the second one did this after a simple reboot. I never had this trouble with my 1st Gen Nexus 7. I'm about to start trying the tips listed in this thread before I return yet another one. I'm wondering if this is the first reboot since the 4.3 update... maybe that is the issue.
Try Fully Charging?
Something similar happened to me on the first one I got, not sure if it will happened to the exchanged one since I only had it for a few days.
It happened after I shut it down one night, battery was about 80% or so. Next morning, I started it up and it actually loaded up fine but after a minute, it just rebooted, stuck at the X, then rebooted to the Google logo, over and over again. Did a factory reset and cleared the cache and still would get into the boot loop after 1 minute of successful boot up. Battery was about halfway when I decided to just charge it fully.
After the battery was fully charged, everything worked fine again. I suspect that the battery was run down next to nothing, but indicated that it was halfway. To me, that indicates a hardware issue so I exchanged it. I am wondering if they are using cheap batteries to keep the cost low. Not sure anyone else has seen this happened to them.
Anyway, if you watch the X, the colors move around, then suddenly stop after a while, it reboots again.
Same thing happened to me this moring around 3 a.m, shutdown and restarted and it was still stuck on the x screen. Tried wiping the cache from recovery and nothing. Had to do a factory reset in order to get passed boot screen. Tablet is working normally now.
Getting stuck on boot screen occasionally occur on 4.3. It seems like an OS issue not the hardware issue. I have seen it once or twice on my stock non-rooted Nexus 4 running 4.3. Never happened on 4.1~4.2.
On the other hand, if you have rooted your 4.3 device, the chance of ****up at boot rises dramatically. The toolkit is, while an admirable work, not perfect and you have no one but to blame yourself.