The tablet is stuck in something like a bootloop; it boots with my chosen background image and will run for about 45-60 seconds before rebooting. I have just enough time to enable developer options and turn on USB debugging. When it reboots, USB debugging is OFF and developer options are disabled.
I've attempted to Factory Reset, but it sticks on the Clearing Cache/Data screen for days without completing.
I've used fastboot to unlock the bootloader and flashed stock version 5.1.1 (LMY49J) straight from Google. This appears to work (completes without errors in windows powershell or bootloader screen) except when it reboots into bootloader, it has to be unlocked again. After flashing, all of the user data (i.e. background image, apps, etc.) is still in tact. I've also used Wug's Nexus Root Toolkit v2.1.9 with the same result. No custom ROM's have ever been used.
I have found some mention of formatting a partition, but no specific instructions.
Any help on this would be appreciated.
cw75 said:
The tablet is stuck in something like a bootloop; it boots with my chosen background image and will run for about 45-60 seconds before rebooting. I have just enough time to enable developer options and turn on USB debugging. When it reboots, USB debugging is OFF and developer options are disabled.
I've attempted to Factory Reset, but it sticks on the Clearing Cache/Data screen for days without completing.
I've used fastboot to unlock the bootloader and flashed stock version 5.1.1 (LMY49J) straight from Google. This appears to work (completes without errors in windows powershell or bootloader screen) except when it reboots into bootloader, it has to be unlocked again. After flashing, all of the user data (i.e. background image, apps, etc.) is still in tact. I've also used Wug's Nexus Root Toolkit v2.1.9 with the same result. No custom ROM's have ever been used.
I have found some mention of formatting a partition, but no specific instructions.
Any help on this would be appreciated.
Click to expand...
Click to collapse
Your memory has gone bad... I've had this exact thing happen to my Nexus 7. If you boot into recovery, and terminal in, you can recover any files. If you cange anything, you will find out much if not all of your system is now read only. Everything you change is going to cache. As soon as you reboot, they changes are lost. If this describes your system, you need either a new motherboard or a new tablet. Sorry.
Sent from my LGLS992 using Tapatalk
Related
Okay so my Nexus 7 is rooted with TWRP Recovery, I've been running CM10 and the other day I decided to restore the stock ROM from a TWRP nandroid. I restored the backup and upon boot the Wi-Fi wouldn't turn on, just said "Turning Wi-Fi on...".
I tried wiping cache and dalvik cache in recovery, didn't change on boot so I wiped the cache and dalvik cache again and fixed permissions and again the Wi-Fi wouldn't turn on.
This time I tried reflashing the stock nandroid but still the same, "Turning on Wi-Fi...". At this point I thought I try a Factory data reset in TWRP, this was a mistake because now I am now stuck at the start up screen and I select my country and the next screen is the Wi-Fi selection screen and I'm still getting the same Wi-Fi issue. Can't boot into recovery because I can't get to my homescreen and can't cold boot to recovery because of the recovery bug.
Now I didn't panic when this happened because I have a reasonable amount of Android experience and I thought worst case scenario was I would flash the factory image. What I forgot is after rooting my Nexus 7 I had to replace my PC and I haven't connected my Nexus 7 to my PC since changing it so I don't have the drivers installed on my PC and obviously i can't enable USB debugging....
Where does this leave me guys, my Nexus 7 boots but get to the Wi-Fi selection screen and Wi-Fi won't turn on so can't progress any further. I can't boot to recovery either to try and flash another ROM or backup.
My options I can thnik of atm is either a way to boot to recovery, unfortunately I can't use Flashtool because of the driver situation. So other than forcing a way into recovery is there a way to bypass the Wi-Fi start up screen? I read something about tapping the four corners from top left in a clockwise rotation to bypass the screen but I can't get this to work...
Any help or advice would be appreciated.
P.S. I don't have ADB on my PC either, having install issues on my new Win7 PC. Could be the stupid Norton that came with it blocking the SDK manager exe file from running but would this help without being able to turn on USB debugging?? I'm an ADB virgin.
Hi,
Did you find a way around this? Have the same problem
G
[/B]
JayJ-1974 said:
Okay so my Nexus 7 is rooted with TWRP Recovery, I've been running CM10 and the other day I decided to restore the stock ROM from a TWRP nandroid. I restored the backup and upon boot the Wi-Fi wouldn't turn on, just said "Turning Wi-Fi on...".
I tried wiping cache and dalvik cache in recovery, didn't change on boot so I wiped the cache and dalvik cache again and fixed permissions and again the Wi-Fi wouldn't turn on.
This time I tried reflashing the stock nandroid but still the same, "Turning on Wi-Fi...". At this point I thought I try a Factory data reset in TWRP, this was a mistake because now I am now stuck at the start up screen and I select my country and the next screen is the Wi-Fi selection screen and I'm still getting the same Wi-Fi issue. Can't boot into recovery because I can't get to my homescreen and can't cold boot to recovery because of the recovery bug.
Now I didn't panic when this happened because I have a reasonable amount of Android experience and I thought worst case scenario was I would flash the factory image. What I forgot is after rooting my Nexus 7 I had to replace my PC and I haven't connected my Nexus 7 to my PC since changing it so I don't have the drivers installed on my PC and obviously i can't enable USB debugging....
Where does this leave me guys, my Nexus 7 boots but get to the Wi-Fi selection screen and Wi-Fi won't turn on so can't progress any further. I can't boot to recovery either to try and flash another ROM or backup.
My options I can thnik of atm is either a way to boot to recovery, unfortunately I can't use Flashtool because of the driver situation. So other than forcing a way into recovery is there a way to bypass the Wi-Fi start up screen? I read something about tapping the four corners from top left in a clockwise rotation to bypass the screen but I can't get this to work...
Any help or advice would be appreciated.
P.S. I don't have ADB on my PC either, having install issues on my new Win7 PC. Could be the stupid Norton that came with it blocking the SDK manager exe file from running but would this help without being able to turn on USB debugging?? I'm an ADB virgin.
Click to expand...
Click to collapse
Yes mate, sort of. Honestly think I fluked it though...
I booted into the bootloader, let the drivers install, updated them manually using the Wugfresh toolkit and choose from bootloader on Wug's NRT and I was able to flash the factory image.
Also unless your running an older version of Android, (4.1.x) you should be able to boot to the bootloader and then recovery....
Sent from my 16GB Nexus 4 using Tapatalk 2
Thanks for replying. So you just rebooted into bootloader, then plugged into pc and used root kit? Where you on the bootloader screen or recovery? And then just use root kit to flash factory image and unroot? Am I going the right way? Thanks again
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
That worked, great thanks
Sorry I didn't reply sooner mate, was busy. Guessing from your edit you sorted it yes??
Sent from my 32GB Nexus 7 using Tapatalk HD
Hi All,
I tried to complete a manual update of the 4.3 OTA on my Nexus 4 this evening, however unfortunately it didn't work and my phone would not boot past the 'Google' screen. After wiping the cache, and still having the issue, I decided to do a factory data wipe/restore. However the problem still persisted.
With this, I thought the only way past this was to install the factory image. I installed the 4.3 factory image just fine (after going through the various steps, including unlocking the bootloader) and it was up and running for a while installing apps. However, with this, the device had a black/blank screen for a fair few minutes and after leaving it I thought I might has well reboot. Unfortunately, this time is did not boot again.
So; off to do the same previous steps again.... fastboot oem unlock (as I relocked the device previously), load bootloader, etc, etc. Got to the system update, and it passed an error saying that fastboot is not available on a locked device. Strange as I had unlocked it, but there is was on the menu "LOCK STATE - locked"....
I am now at the stage where I can't actually keep my phone unlocked. I can complete the command fastboot oem unlock, but once I complete fastboot reboot-bootloader, the device is stating it is locked again. - This is where I need some help, PLEASE.
Sorry for the long post, but wanted to describe the situation. If you need further info from me, just let me know. I'm hoping someone far wiser than I am can help me resolve this issue...
Any help on this? - It would be much appreciated.
I too have the same problem with my phone
but my phone is 4.2.2. rooted and wouldn't load past the 'google' boot screen
I can still go into clockwork recovery mode and I wiped cache, did factory reset and I can't even access my phone through the computer
My nexus 7 2012 has been giving me issues for the past two weeks, freezing/rebooting/turning off during sleep. I've done a factory reset before with no problems, but today during the factory reset it was giving me errors, failed to erase, cannot read e:/, things like that, then it froze up completely.
Now I can get into bootloader mode, but Recovery adb mode does nothing, like there is no recovery data on the tablet. Using the wugfresh nexus 7 toolkit I've been trying to do the Force flash stock option because my debug mode was never enabled when the device was on. Only problem is nothing happens. When I try unlocking the tablet it just freezes up causing me to have to hold the power button down for a minute. Flashing the stock fails as well, in the dos dialogue that comes up everything it does fails because it's not unlocked. When the tablet tries to load up I'm stuck with the google logo and the bootloader Start menu on top of the screen.
Any suggestions?
Did you tried it with fastboot or only with toolkit?
Not sure what you mean. On the tablet itself I can really only do three things now...Turn it on, which only goes to the Goolge logo screen, which has the menu on top (start bootloader/recovery/turn off). If I hit Recovery I get an error that says Failed to Boot. I can go onto the bootloader page, which I did to use the toolkit. Only problem is the toolkit wasn't able to do anything. Everything I tried failed, including the force flash option.
Which desktop OS are you using? Do you have the Android SDK installed?
try the universal adb drivers : http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Adb should work now :good:
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
Hi,
Yesterday my Nexus 4 decided it no longer wants to boot up. It just sits on the boot animation and doesn't progress any further. I don't think I have done anything to cause this - it was working fine the day before and I haven't installed any new updates/apps or really changed anything on it.
It is running android 4.4 with stock recovery etc and no root or bootloader unlock. Unfortunately I need to recover the data stored on the phone because I don't have any recent backups but I can't figure out how to do that. I vaguely remember turning on usb debugging as a precaution many months ago but I can't remember whether I actually left it on or not.
Any suggestions on how to recover the data? I've already looked at quite a few threads on this, but most require an unlocked bootloader which I can't do because that will wipe all the data. I can't use adb pull because the device doesn't get detected. I'm not that experienced with adb, fastboot and command lines so some help would be appreciated.
I have wiped the cache through recovery mode and tried using the "sideload adb" mode in recovery mode and neither worked. I also can no longer get the options to appear in recovery mode for some reason.
Thanks for your help.