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
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:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
ThuanBui said:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
Click to expand...
Click to collapse
I'm having the same problem!
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
andr0idfreak said:
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
Click to expand...
Click to collapse
I've done this many times but still no luck
ThuanBui said:
I've done this many times but still no luck
Click to expand...
Click to collapse
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
monkeying. around said:
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Click to expand...
Click to collapse
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
sideloading 4.4.2 and stuck on boot loop
ThuanBui said:
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
Click to expand...
Click to collapse
bro mime nexus 4 has stuck into boot loop after upgrading from 4.4 to 4.4.2 .i was sideloading the zip dont know whats the issue ......i was rooted but went to stock via nexus roottool kit to get OTA . any suggestion
joshnichols189 said:
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
Click to expand...
Click to collapse
all you got to do is download the toolkit and flash the software your phone is using and put it in fastboot and begin
:good::good::good::good::good::good::good:
Hey . i recently tried Lollirock
which i didnt like so wanted to go back to stock
I tried following https://developers.google.com/android/nexus/images
seemed that it went fine, how ever it left me with a Google Screen and it wont boot
then i tried this ,
https://support.google.com/androidtv.../6121450?hl=en
which also went fine and did a factory reset ,
but still only the Google Screen,
any ideas on what to do next
this is resolved
http://forum.xda-developers.com/nexus-player/help/stuck-google-screen-t3043711
Three Nexus Players stuck at Google loading screen
I have had 3 different Nexus Players get stuck at the Google loading screen in the past week. Recovery mode from the bootloader doesn't work. Has anyone else seen this? Any work around?
I am also experiencing the same symptoms. Factory reset results in the same Google screen.
I’m getting the same thing starting this week. Factory reset has done nothing. I’m running stock everything, unrooted Oreo. Someone help!
I was wondering if anyone else has any ideas on this issue. If I plug in my nexus player, it takes around a minute to get up to the white google logo. I have tried holding the bottom button as I plug the player in, but I am unable to get to get any result out of it. I never get to the point where the droid is on his back. I am just stuck on a loop with a white google logo on a black background.
I wonder what happened that Google broke all our players. Mine is doing the same thing - stuck at the black and white 'Google' screen. Has anyone been able to recover and reboot?
MallCop said:
Has anyone been able to recover and reboot?
Click to expand...
Click to collapse
A good number of people have been reporting that they were able to flash back (either to stock or other options), but there haven't been a lot of details on if they were already unlocked. I haven't been able to get fastboot or ADB to identify my Nexus Player from Linux, and I wasn't unlocked and hadn't enabled USB debugging before this happened.
I left my player unlocked and I can't remember if I enabled usb debugging. My problem is I can't even get into the recovery. Holding the bottom button down has yielded me nothing.
erehwon6811 said:
I left my player unlocked and I can't remember if I enabled usb debugging. My problem is I can't even get into the recovery. Holding the bottom button down has yielded me nothing.
Click to expand...
Click to collapse
Getting to the recovery (android on his back ) screen yields NOTHING. I was in the same loop and just had to be patient. Hold the button, wait until the GOOGLE screen goes away, then it will come back and eventually for me, I got to the screen with the android on his back (took like 5 minutes). Problem is that when I did a factory reset, I am still have the same problem. I did not think Google was updating these anymore. I have 6 of these and 2 are bricks now. Unplugged the rest until I can tell what is going on.
Best Buy has a offer where you can get a $30 coupon off of a nvidia shield for recycling a streaming media player. I'm tempted to see if they'd take the player in that condition. I hesitate since I haven't been able to clear my data from it. I just wonder if this a permanent brick.
Mine just randomly restarted as I was navigating the menu and now I'm stuck on the boot animation as well. I never rooted the thing. I guess I'll start going through the recovery options. Hopefully it didn't die on me.
I was in the same boat...last week got the corrupt data message so I factory reset...seemed to work fine for a couple of days and then got stuck on the Google screen...factory reset didn't help this time..
I installed TWRP and loaded lineage 15...looks like I am back in business...
I just had the Google black screen as well. I did the following, as I was running into the same errors as everyone else here stating that the reset hadn't worked.
I started by using the button into the recovery and reset - didn't work.
I then went into fastboot, and tried manually flashing the latest image from google and didn't work.
I typed fastboot oem unlock (forgot it wasn't unlocked).
I then sent the flash all script and everything went great. Now working.
Hopefully that helps others.
Well today, it rebooted into the boot splash again. I guess this thing is cooked...
Man we are all experiencing a very similar thing. This is too strange to be coincidence. I turned on my TV, saw the Nexus Player interface, then when I tried to interact the screen went black. I restarted the nexus player, and it went into the stuck on Google loop. It has been rooted / lineage rom in the past, but i have been running stock Android factory images on it for over a year now. I enabled debugging, so I connected it to my pc and checked that it was unlocked.... heres where it gets weird....
The unified android toolkit says it is locked, but when it tries to unlock it, it says its already unlocked. So i ran fastboot oem unlock manually and it says already unlocked, as does the bootloader screen. OK. Flash factory imaging using flash-all.bat, everything goes fine, then it sticks on Google screen again. I am going to try an older factory image then im going to try lineage brb...
just had the same result with 7.1.2 and 7.1.1 and 7.0.0 factory images.
flashed twrp, booted into recovery, and flashed latest lineage.
stuck on lineage logo for 10 minutes now....
seems like google bricked out Nexus Players. I am pissed.
jessehclark said:
Man we are all experiencing a very similar thing. This is too strange to be coincidence. I turned on my TV, saw the Nexus Player interface, then when I tried to interact the screen went black. I restarted the nexus player, and it went into the stuck on Google loop. It has been rooted / lineage rom in the past, but i have been running stock Android factory images on it for over a year now. I enabled debugging, so I connected it to my pc and checked that it was unlocked.... heres where it gets weird....
The unified android toolkit says it is locked, but when it tries to unlock it, it says its already unlocked. So i ran fastboot oem unlock manually and it says already unlocked, as does the bootloader screen. OK. Flash factory imaging using flash-all.bat, everything goes fine, then it sticks on Google screen again. I am going to try an older factory image then im going to try lineage brb...
Click to expand...
Click to collapse
That's pretty much exactly what happened to me. I was navigating around the menu, got the black screen and when I restarted it, I got stuck on the Google screen. It's the only Android device I have that I never rooted so it's completely stock. To say that this is frustrating is an understatement. Although it's old, it gets used heavily by the kids.
I keep having a similar issue but I've been able to flash back to 7.0. Nexus auto updates and within a week I'm back in the same boat having to reflash...
i also just had two nexus players die this weekend. something is up.
Yes, something seems to be up, mine died earlier today, too many people to just be coincidence. I was casting to it and it just rebooted and is stuck on the google startup animation. Stock, never unlocked or rooted, been rock solid up until now. I use it as a DVR so I figured maybe my external hard drive had crapped out and was causing a hangup since the light isn't on anymore, but same symptoms when unplugging it and trying to reboot.
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.
Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery ModeRebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD CardYou may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe ModeThis problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery ModeWhen you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)