Hi, You guys may remember me from around 2 years ago when I was scrambling for answers about my nexus 7 2012 edition being hard bricked from "Fastboot Erase Bootloader". Well shortly after that I got the motherboard replaced everything worked fine after that. In fact the tablet worked flawlessly (whilst un-rooted) for over 2 whole years.
But then...
in the last 3 days something very unusual started happening. After downloading an audio recorder app the tab started crashing and freezing while it was in a locked state (screen off and supposed to be on stand by mode). The only way I could get out was a long power button press. Then this issue began to get progressively worse. The tablet started freezing/crashing whilst I was doing normal stuff on it and sometimes the device would automatically shut off while frozen(and it was doing this repetitively). I did some basic diagnostics on it including taking off the back cover for inspection (didn't see anything unusual however I am not an expert on motherboards) so I then booted in safe mode which didn't change anything. After that I tried clearing the system cache. That didn't change anything either. Then suddenly out of the blue the tab started getting stuck on the google logo. It does feel like my tab is going through a slow and painful death. I have not rooted this tab or updated the android version or anything of that sort since the motherboard replacement and I am absolutely clueless as to what could have happened here. And this time It literally doesn't make any sense to me. Does this really mean two motherboards F***ed in a row?
I would be very grateful if anyone could enlighten me on this new problem and "safe" steps to take in resolving it (if it is reversible).
PS: I have ADB (sideload mode only) and Fastboot up and running.
Update
I think I have made a break through. I finally decided to clear the data so I went in recovery mode and pressed the option to wipe data and factory reset however it got stuck on "Formatting data" so eventually I pressed the power button to force restart it and this time it actually got passed the google screen but then I was stuck with an endless 4 circles animation playing so I pressed the power button again and this time it booted to the google screen and then went black and showed the google screen again and black again over and over again. Now I am even more confused however I am not sure if this is still a hardware problem.
Any ideas guys????
I've had lots of issues with my first nexus 7, though never as bad as yours. Factory reset always solved it at least temporarily.
That being said, recently got tired of staying stock and jumped to the unofficial PureNexus (Android M) + pico Gapps + parrotmod + DC kernel and the N7 has been running smoother/faster than ever. Since you can't even get into the normal OS at this point, and you can clearly access the bootloader and recovery, why don't you try out a custom ROM setup?
Well thanks but unfortunately that is not much use
Now I can't even get the boot loader unlocked, I type "fastboot oem unlock" and I get this
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 6.733s
Also the factory reset option in recovery appears not to work (still hangs at the 4 colored circles animation), clearing cache option gets stuck, I don't know which sideload would work.
Any clue what the hell is going on here?
Related
Couldn't find a similar thread so I thought i'd post my problem.
Beginning last night, after watching a video using Pulse I realized the sound wasn't working. I restarted the Nexus 7, had the sound working again, but the device froze during the video (in pulse), and then reset on its own.
Since then, the Nexus 7 will reboot, then once on, will freeze after 30 seconds - 2 minutes, reboot again, and just loop in that pattern. Sometimes when it turns out, I'm not even able to unlock it before it reboots again.
Even if I turn off the Nexus 7 when I get the chance, it will turn on itself and continue the freeze -> reboot loop.
Right now I've been letting the loop continue until the battery runs out to see if it fixes the problem. Until then, has anyone else faced this issue? Any solution?
Details: An unrooted Nexus 7, few apps, only thing off market was to enable flash, got the device 2 weeks ago
Bump to see if anyone has a solution.
Will post a video of what happens when I get home from work.
Haven't heard of this before.... what happens if you boot into bootloader? Perhaps you just need to do a full wipe and re-install.
It actually freezes on bootload.
When I do a force turn off (power and volume down), it will turn off, then turn on by itself and continue the bootloop
Will try to upload a video of what is happening soon.
I have the exact same issue.
Can't restore or reflash because it won't go into bootloader\recovery.
What it WILL do is reboot incessantly. SUffice it to say I'm pretty pissed. This just happened suddenly.
I had not rebooted in a few days so I rebooted, and now it won't stop.
The only change I have made is I disable the magazine app because I read that it's a battery hog and I just do not use it. I can;t imagine disabling the magazine app would result in a full on boot loop where even recovery fails...
-M
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
kevlars9 said:
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
Click to expand...
Click to collapse
I have the same kind of issue. Left to itself the device reboots until the 'Google' display every 1 minute or so. When trying to get into bootloader it freezes when the Android on its back shows up....
So it seems no flashing is possible. BTW this happened when I tried to uninstall an app, similar scenario to some others reporting this type of problem.
I guess the next stop is the Chocolate Factory helpline :/
I contacted the Googleplex helpline at 6 am Pacific time and Anthony kindly promised a replacement unit for next week... No tech explanation or other info was revealed. Purchase from Google Play in the UK.
Finally given a solution, though a very annoying one.
Basically, since you have about 30 seconds - 2 minutes everytime it loads up, I was just told to try and see if I can factory reset from settings within that time frame. Took a 3 attempts (sometimes it would reboot while loading), but eventually got the factory reset going. Luckily I've only had this thing for less than 2 weeks and didn't have much stuff needed to back up.
Right on, glad to hear you got it sorted - in my case. though, this solution would not have worked, as mine never booted all the way through but got stuck at the boot logo (just in case others are reading this with similar problems). So it sems there are at least 2, possibly more, problem scenarios of this type.
My replacement unit from Google Play just arrived - impressed by the speed of proceedings (inside 2 working days from reporting to receiving in Scottish Highlands). Let's see how this one pans out...
HEy problem plss help Boot loop on N7
Hey my nxus wint get out of a boot loop and i cant get in to recovery mode by bootloader this have ben going on for some time and it started when i flashed a new rom ( Paranoide android )on my Nexus 7:fingers-crossed:
Eternal 2013 Nexus 7 reboot loop
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
I have a very similar problem. However, it began from no changes to my system. I am on Legolas' All-F2FS Recovery and the SlimKat F2FS system. At first I got stuck in a boot loop, and could get into fastboot, but cannot boot back to the custom recovery. Now, I get past the bootloop but cannot get past the loading screen, and still cannot get into recovery. I've tried wiping cache, I've tried reloading the recovery via fastboot -- but since all I have is fastboot access, I don't know what else to do. All my partitions are F2FS, so I am afraid to try moving back to any standard ext4 recovery. I am very interested in this thread, as I feel our issues are related. Keep me updated, and I will do the same if I find anything useful.
Any help I suspect is appreciated by more than just myself.
BTW, removing back and leaving battery unplugged for a while (which had helped with other bootloop issues) did not fix this one, nor did the cold boot from fastboot with usb plugged in to boot recovery.
superdave132 said:
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
I found a fix that worked for me!
I have Minimal ADB & Fastboot installed on my computer. If you're comfortable with the idea of connecting to your Nexus when it is in bootloader download (Fastboot mode), you can try this.
First, I downloaded a full reset file from https://developers.google.com/android/nexus/images:
The ones you'll want are either:
this one for 4.4.2
this one for 4.4.4
I unzipped the appropriate one directly into my ADB directory, and then executed the "flash-all" script by literally typing in "flash all" into the prompt.
This installed all of the default bootloader, recovery and system back onto my Nexus 7 (btw two names for the nexus are "Grouper" and "nakasi"). Then, I was able to clean boot into a reset Nexus 7 system. It was still unlocked. From there, I was able to reinstall a custom recovery (I went with TMW), and even reinstalled a custom ROM (I always stick with SlimKat, personally).
Note: You should also wipe data from the custom recovery once you've installed it.
Second note: In order to be able to load this stuff, I believe you have to unlock your system
To unlock your system in fastboot: fastboot oem unlock
I sincerely hope this helps you (and anyone else stuck in a similar situation to where I found myself). I had completely set my system up with F2FS, and now I'm back to EXT4. BUT, I have a custom recovery, custom rom and root access. Can't complain.:highfive:
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911
I've been lumbered with an original Nexus 7 (ME370T) that's in a bad state. The device has been attempted to have a factory reset done, by using the 4th button under the plastic casing, (under the volume down button). Its now stuck in the "Erasing" screen. It did have stock OS and bootloader.
I have tried accessing the bootloader using volume down and power buttons, but it only ever reboots into the factory reset mode, where I'm greeted with the green android wiggling its ears with the caption "Erasing", and I've left it doing that for several hours, with no sign of any progress. I've pressed some combination of volume buttons, and managed to get it to display the text under that splash screen, where all it says is "Formatting /data..."
I don't know whether I could use ADB or fastboot with the device in this state as I'm sure it needs to be booted into the bootloader for USB communication to work, and the bootloader was still stock/locked anyway.
Any ideas? It would be a shame to bin the whole thing, as I was sure that they are always recoverable in some fashion, perhaps JTAG, although I have no experience of that.
Same issue, exactly the same... Probably another broken EMMC - I know the OP is 3 years old but maybe someone reads it who found something I missed
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
[update]
OK so after failing to flash any zips (or anything!) to the device, I left it on in fastboot mode while I went to work. Now upon coming home the tablet is just a black screen! The laptop recognises it because Windows makes that chime sound when its plugged in via USB. But other than that, I can't get a response out of it Button combinations don't seem to help so now I'm not sure what to do!
Can anyone help me please? :crying:
Unless the bootloader is locked, you may have made a mistake trying to flash the ROM and trying to install a custom recovery. Anyways, if you hadn't made any changes yet to the system, I would have said check the battery first because it may be malfunctioning and not the phone it's self. I know from experience that it may have been the battery considering the way you said it was not reading the battery percentage right and shutting down. And that "bootloop", this was probably happening because it didn't have any power to start up the device as this is exactly what my device did when I had a faulty battery. My best bet is to 1 try to get a new battery, and then 2 see if your system is still intact otherwise try and reflash with the stock ROM (through adb or any computer to android debugger) and then reinstalling the right recovery that goes with the device or that of which is c-o-m-p-a-t-a-b-l-e.
Using CM12.1 on my SGH-T999
I exactly got the same issue, nothing I particularly have done as far I know, my tablet suddenly rebooted and now is stuck on Asus logo with the little circle that keeps turning.
I tried to let it go till my tablet get completely discharged and also tried to charge it completely, nothing change.
And when I wanna access to the recovery, I just get the green android mascot with the message "ERROR!". So I can't even access the recovery to reset my tablet :crying:
Edit: Tried a fastboot erase userdata and an erase cache, still bootlooping
Sorted
The only way I fixed this was by returning it to the shop and having the device replaced! Not the ideal solution, but it worked. :good:
MrLewk said:
The only way I fixed this was by returning it to the ship and having the device replaced! Not the ideal solution, but it worked. :good:
Click to expand...
Click to collapse
I guess I will have to do the same
MrLewk said:
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
Click to expand...
Click to collapse
Asus has the firmware (Nougat) for this Z300M but I've no idea how you would get this loaded. Something to learn but as long as the OS is available you should be able to get back stock, latest OS............
zls
I replaced my GNEX10 battery last january. Aside from the battery calibration being off... (which eventually corrected itself!) it's been working fine. As of late it had rebooted itself while I was using it a few times. A few days ago, it had enough battery such that I left it on overnight. I picked it up the next morning and the notification lamp was flashing so I knew it was still on. I tried to wake it up without success. Usually a quick tap on the power button should do it. Nothing. So I rebooted... and on the google logo it stuck. I knew that a factory reset was probably in order since I didn't do it when I replaced the batter... I got it into the recovery screen... but I could not get the menu. I likely didn't press the right volume rocker. Then I tried again... booted to the bootloader, and selected recovery. This time, and since, only the google logo comes up. No andy on his back with "no command". It just tries to boot into something. I can't do a factory reset this way.
I tried the Nexus Root Toolkit. I can only get it to recognize the device if it's in the bootloader... when I try to use it to boot to recovery, same thing and the NRT says waiting for device... and gets no further. I tried to use it to flash (stock?) recovery but the N10 just sits there on the twrp logo screen and nothing more after temporarily booting into twrp. Just keeps saying "waiting for device"
Anyone have any suggestions! Getting seriously bummed!
So one more data point... I manually rebooted into the bootloader after trying to flash the stock recovery using the NRT. Then it appeared to flash the recovery image.... here is the bit of the log where it ended up:
Checking Fastboot Connectivity
fastboot devices
R32CB04GHGT fastboot
+ Fastboot Device Connected
Flashing Stock Recovery to RECOVERY partition...
fastboot flash recovery "C:\usr\NRT\data\Recovery_Stock\recovery_stock_mantaray_5.1.1_LMY49J.img"
Temporarily Booting TWRP...
fastboot boot "C:\usr\NRT\data\Recovery_Custom\TWRP\twrp-3.0.2-0-manta.img"
Flashing 'undo-perm-recovery-signed.zip'...
Waiting for your device...
That's where it ended up... not getting any further. Once again, attempting to boot into recovery gets it stuck on the Google logo.
How screwed am I? Is there a thread somewhere in the forum anyone can point me at?
Well, in spite of the crickets... I understand. I've managed to resurrect my Nexus 10. Alas there are no good contemporary replacements. The last so-called nexus table google put out there was too damn expensive in the first place and they seem to have abandoned the tablet market to others.
So the key question here: So long as I can get this tablet into the bootloader is it generally possible to reflash a stock image? I'd like to know of any types of caveats etc. The mystery I have still though is: How or why did my N10 get into this state (of of only being able to get to the Google screen) in the first place? I didn't have any questionable apps installed etc. I was totally on stock. One thing that did happen a week or two prior to my tablet going belly up... was somehow the thing lost my google account info and gmail had none of my accounts in place... it was very odd.
I did have to wipe the system because evidently you can't flash anything onto a locked bootloader (the Nexus Root Toolkit by wugfresh is up to date so far as the N10 is concerned at least). I know I could have resorted to using fastboot.exe and the adb directly but this was a touch easier. Alas the backup options for it say you need an unlocked bootloader which seems to be a chicken/egg issue if you've always been on stock.... so it goes.