I've unlocked/rooted/flashed many Android devices in the past, including many Nexus devices. I've run into some problems here and there, but I've always been able to get around them. This time seems to be different, so far anyway.
I started with the WugFresh Nexus Root Toolkit - I know how to do it manually but this just has everything included, the drivers, adb.exe, fastboot.exe, etc.
I told it to unlock the tablet, and it rebooted the device into Fastboot. The tablet asked me if I wanted to unlock it and I said yes. Then, NRT booted me into TWRP and gave me instructions to do a factory reset from TWRP (a step I've never had to do manually before). I tried to factory reset but TWRP told me it failed. Weird. Anyway, I decided to reboot the device from TWRP and see what happened.
All I see is the swirly, colourful "X" logo forever. It never boots into Android. I can reboot by holding down the power button, and I can get into fastboot by holding down the power button with Vol-. In Fastboot, I only have the "start" option (which works, but never gets past the "X"). I can't use the volume keys to select "recovery", etc.
From Fastboot, my computer does not show the tablet under "fastboot devices" in the command prompt. It does, however, show my (working) nexus 4 in fastboot devices.
So, without working android, I can't use ADB. Without fastboot connecting with fastboot.exe, I can't push through recovery. Without a working fastboot menu on the physical device, I can't try to go into whatever recovery is there or whatever.
And worst of all, at this stage I can't even turn my device off. It's just sitting here either in the fastboot menu or with the colourful "X". It's just sitting in its original box getting warm and using up its battery.
Any ideas? This is supposed to be a present for my wife for tomorrow - I don't really want to give it to her like this.
Just used wug's kit to root my second nexus device. Both times, it said failed during the factory reset. Wierd.
Put it in bootloader mode by pressing BOTH volume keys and power. There you should see the arrows and you can go to recovery but you shouldn't have a recovery installed yet. Instead, use the wugkit to download and flash a system image, hit the flash stock + unroot button. I also had to do that on both devices for some reason. After it flashes, your bootloader will remain unlocked and you will have a clean, bootable 4.2.2 rom. Then you can root from there.
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Sorry I may have misread. If you are already in fastboot mode and your having a problem with your computer recognizing it, check your device manager for an uninstalled item, either adb something or android something. Then just follow the instructions in the toolkit to install the drivers. But try the flash and unroot button first and see what the toolkit says.
Same thing happened to me but luckily I had found this video before I started the unlock, root process.
Watch: https://www.youtube.com/watch?feature=player_embedded&v=T1Se7Hr9Cww
Seeing this guy missing getting the proper recovery menu really helped in understanding that it can be tricky.
I took the sage advise of others and did all the manual steps to unlock and root (no toolkit). The following link below is super whether your N10 is on Android 4.2.1 or 4.2.2 with instructions for Linux, OSx and Windows. Includes videos and pictures:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
hlaalu said:
Just used wug's kit to root my second nexus device. Both times, it said failed during the factory reset. Wierd.
Put it in bootloader mode by pressing BOTH volume keys and power. There you should see the arrows and you can go to recovery but you shouldn't have a recovery installed yet. Instead, use the wugkit to download and flash a system image, hit the flash stock + unroot button. I also had to do that on both devices for some reason. After it flashes, your bootloader will remain unlocked and you will have a clean, bootable 4.2.2 rom. Then you can root from there.
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Sorry I may have misread. If you are already in fastboot mode and your having a problem with your computer recognizing it, check your device manager for an uninstalled item, either adb something or android something. Then just follow the instructions in the toolkit to install the drivers. But try the flash and unroot button first and see what the toolkit says.
Click to expand...
Click to collapse
Hey mate, just wanted to say thanks. I don't know what is was that made the difference in the end, but your suggestion to use both Vol+ and Vol- together with power did the trick. I got it all working brilliantly now, thanks to you.
I'm still so confused. Why does Vol- and Power get into fastboot that doesn't work? I've never seen this behaviour on a Nexus device, or any Android device in general. It's wrapped up in a box ready to be given away in a few hours - but I will have a play with this fastboot because it's certainly weird. Definitely not like my Nexus 4 or 7.
Big thanks again. Hours of pulling my hair out and you saved me!
I believe the reason is the volume buttons are reversed. So when you think your pressing vol- your really doing vol+ lol.. That's what I did. Vol+ + power = download mode and it won't do anything from your computer. J think its an Odin mode.
Also for future reference you cannot unlock, and then use TWRP to do a factory reset. You will get a cache error. The only way it works the first time is to unlock, wipe through stock recovery, flash twrp and boot to success. But have to complete 1 boot before changing your ROM.
I've gone through multiple N10's and each of them had this behavior, I think its a bootloader bug since unlocking the device is supposed to perform a factory reset automatically.
Sent from my Nexus 10 using Tapatalk HD
Glad you're up and running!
Sent from my Galaxy Nexus using Tapatalk 2
Related
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.
Delete
subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck
Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"
hello
after i try to unlock the bootloader my nexus stuck in "X" (with toolkit 2.0)
and the recovery mod is not work (Attachments)
I had the same problem when unlocking mine, reboot into fast boot and use the volume buttons to change the select option to recover and hit power, you should get a picture of an android with a red triangle that's normal , then try a couple times to hit the power and both volume buttons to boot into the stock recovery and then do a full wipe and factory reset (wipe both cache and dalvik cache just yo be safe) you may have to do this more then once, I did but it fixed the problem
Sent from my Infected HTC Rezound using xda premium
Just get back into recovery and factory reset. This is a common issue when unlocking bootloader.
Please help as I seem to have placed my Nexus 10 into a Bootloop state through Nexus Root Toolkit 1.6.8 by WugFresh. I have been attempting to enter into Recovery following the steps outlined here (http://forum.xda-developers.com/showthread.php?t=2239524). However, the tablet never seems to enter Recovery mode. At best I get a blank screen that eventually comes around to an unusable Bootloader. By unusable, I mean the volume buttons do not progress through the options. If select Recovery on a functional Bootloader and simply press the Power button. The tablet will cycle through to an Android with the red symbol.
Now the Toolkit no longer even see's my device even though Win 8 Device Manager shows the Android Bootloader Interface. There are no devices listed with the exclamation point warning symbol.
This is only my third attempt at Unlocking and Rooting a device. The first two times were successful on an HTC phone and a Samsung Tab 7". I do not know where to go from here and really need help fixing my Nexus 10.
Thank you in advance for any help you can offer.
Edit: I figured out how to access Recovery. I needed to use power + volume up once on the screen with the Android avatar and red symbol.
OvrTehBottm said:
Please help as I seem to have placed my Nexus 10 into a Bootloop state through Nexus Root Toolkit 1.6.8 by WugFresh. I have been attempting to enter into Recovery following the steps outlined here (http://forum.xda-developers.com/showthread.php?t=2239524). However, the tablet never seems to enter Recovery mode. At best I get a blank screen that eventually comes around to an unusable Bootloader. By unusable, I mean the volume buttons do not progress through the options. If select Recovery on a functional Bootloader and simply press the Power button. The tablet will cycle through to an Android with the red symbol.
Now the Toolkit no longer even see's my device even though Win 8 Device Manager shows the Android Bootloader Interface. There are no devices listed with the exclamation point warning symbol.
This is only my third attempt at Unlocking and Rooting a device. The first two times were successful on an HTC phone and a Samsung Tab 7". I do not know where to go from here and really need help fixing my Nexus 10.
Thank you in advance for any help you can offer.
Edit: I figured out how to access Recovery. I needed to use power + volume up once on the screen with the Android avatar and red symbol.
Click to expand...
Click to collapse
In stock recovery, wipe the data (it may be called system reset or something) u should be good to go.
Sent from my Nexus 10 using Tapatalk 4
OvrTehBottm said:
Please help as I seem to have placed my Nexus 10 into a Bootloop state through Nexus Root Toolkit 1.6.8 by WugFresh. I have been attempting to enter into Recovery following the steps outlined here (http://forum.xda-developers.com/showthread.php?t=2239524). However, the tablet never seems to enter Recovery mode. At best I get a blank screen that eventually comes around to an unusable Bootloader. By unusable, I mean the volume buttons do not progress through the options. If select Recovery on a functional Bootloader and simply press the Power button. The tablet will cycle through to an Android with the red symbol.
Now the Toolkit no longer even see's my device even though Win 8 Device Manager shows the Android Bootloader Interface. There are no devices listed with the exclamation point warning symbol.
This is only my third attempt at Unlocking and Rooting a device. The first two times were successful on an HTC phone and a Samsung Tab 7". I do not know where to go from here and really need help fixing my Nexus 10.
Thank you in advance for any help you can offer.
Edit: I figured out how to access Recovery. I needed to use power + volume up once on the screen with the Android avatar and red symbol.
Click to expand...
Click to collapse
If the suggestion of newell79 didn't work you can try to flash the Factory image..
Sent from my Galaxy Nexus using XDA Premium HD app
[Solved]
mrgnex said:
If the suggestion of newell79 didn't work you can try to flash the Factory image..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Before discovering how to enter Recovery properly, I did end up flashing to stock. Unfortunately, I am unable to get ADB to recognize my Nexus 10 using Wug's scripts, even though the ADB installer see's the unit. I believe this is a Windows 8 issue, but I am not 100% positive. That said, I did further research and found another method using the Fastboot command line which did work. My Nexus 10 is now unlocked and rooted. I wish I had kept the thread's URL to the other method.
I wonder if my issue's come from not uninstalling the Samsung G3 through device manager as I did my Nexus 10. I did uninstall though the USB app found within Wug's, but that may not have been enough. That is certainly something I shall try in the future.
I'm having reral trouble gettng my n4 into fastboot. all the buttons work, vol up, vol down and the power on all work fine but if I try and press all 3 simultaneously I just boot the device normally. I've managed to get to fast boot just once in 2 dozen tries. what is the trick? I've tried pushing all 3 at once, I've tied pressing both vol up and down, holding thm, then pressing and holding the power button too. always just vibrates, and boots normally.
just now while trying on the last attempt it booted normally but the screen had 'safe mode' in the bottom left corner. that freaked me a bit. turned it off, then on again and it went away. wtf is 'safe mode' and how did I get it?
I want to...I think...root and flash a rom the proper way, step by step using efrant's guide on here, rather than a script from the toolkit, but since I can't seem to get to fastboot I'm stuck
this is all just to get to 4.3 really....I rooted using the toolkit and OTA updates haven't been running so still on 4.2.1 and thought I should sort that out. had a bit of a 'mare l2 nights agot when I unlocked the bootloader to go about returning to stock and forgot that would wipe the device...losing lat weeks holiday photos in the process I think the tool kit and one press type 'unlock, flash this, flash that etc etc' commands lulled me into not thinking for myself so perhaps I ought to do this properly!
BTW, I'm currently with a locked bootloader, stock 4.2.1 rom, stock recovery reflashed, no su binary (cinfirmed by attempting to run SU app, and it not finding the binary). I've been waiting for the OTA update to push to the device again (I've forced checkins but to no avail) to attempt to run it, should it run properly now or have I to do something more?
You need to hold power and volume down, if that doesn't work then try adb reboot boot loader
Sent from my Nexus 4 using Tapatalk 4
justin11141 said:
You need to hold power and volume down, if that doesn't work then try adb reboot boot loader
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
thanks. tried holding volume down and then also power as well and again it booted normally. looks like adb commands it is then. bit of a pain to have to hook to a pc to do this....not that I'm a regular custom rom flasher/swapping between roms and nandroid backups etc but it would be handy....I learnt that with my old desire.
has anyone else had problems getting there holding the buttons?
oh and I found what safe mode is from the google nexus 4 site. a mode where the apps don't work so you can check for problems that they may be causing. how I got to it doesn't match with the descried way though...just a weird glitch I guess.
okay I'm all sorted for now. I used the toolkit and flashed the entire set of stock .img after downloading the archive from google
now on 4.3, and as far as I can see that is with stock recovery, system, radio the lot. I've left it unrooted (so no su binary, no busy box, no su app - although the phone is currently synching and downloading my apps again..I guess this will come too) so if I understand things correctly future OTAs will run.
I've left the bootloader unlocked as efrant, in his 'how to' guide says
'Do NOT re-lock your bootloader after you are finished. The is no need. 2) Having an unlocked bootloader does not affect anything related to the ROM/GoogleWallet/OTAs. Nothing at all.' and he explains that unlocking in the future to enable fastboot commands to work and hence flash roms in the future results in a wipe of data. So...I think...I'm up to date, stock, safe and future OTAs will run....i hope. I do understand though, that should the device need to back to Google I should relock the bootloader first or they will know I've been playing around (where possibly I shouldn't!)
okay....think I can go ahead and set up again. :victory:
Ooo good! and whatever I've done I can get into the bootloader fine now :victory: simply holding vol down and then pressing and holding the power button now works every time. good.
Hi,
my Nexus 7 (2013) is stuck on Google screen...
a few days ago I downloaded a lot of movies via utorrent, and utorrent kept crashing. So i forced stop, removed the app, reinstalled it from google play and continued.
My nexys then suddenly freezed for about 1-2mins before i shut it down via the power buttom, and since then it wont start...I've tried almost everything.
The device is stuck on Google screen. I've tried to boot it through the bootloader, recovery mode etc, but it's still stuck on the google screen. downloaded the nexus root toolkit to unlock my device, but it keeps tellin me i've to enable USB debugging. which I can't since my device won't start.
I've downloaded the SkipSoft Android tookit, but not too familiar with the tookit so haven't really tried anything yet (also not sure which android version i'm running)..
Is there ANYTHING i can do?
EDIT: tried using skipsoft android tookit to unlock bootloader, but when coming to the stage where i've to chose yes or no, the device get stuck and the power button does not respond => I can't chose Yes..
EDIT: So I've tried a few things but nothing seems to work..
downloaded a new adb+fastboot directory from another thread. Fastboot commands seems to work, but when i try and erase boot/cache etc the cmd does nothing...had this line for about 10min:
erasing 'boot'..
nothing happens.. when i unplug my device an error message shows (too many links).
so, fastboot won't erase my boot nor my cache, so i tried to fastboot flash bootloader bootloader.img, and it says my bootloader is locked.
fastboot oem lock --> bootloader is alrdy locked
fastboot oem unlock --> stuck at "YES", just as i was when trying with different toolkits.
fastboot -w update image-razor --> Error, failed to load 'img-razor'
soo i'm getting kinda desperate here...
remeber, this was all from a stock rom, no root, no custom rom, just from a freeze when dl movies from utorrent...
i have been stuck like that before. get into to the bootloader screen from where its hung at the google splash screen. once there you can fastboot a factory image.
from the google screen:
1. hold volume up, volume down and power until you get to the screen with the android and its belly open
2. connect to pc
3. download factory image from HERE
4. unzip the tar file you just downloaded and place the contents in your platform-tools folder
5. double click the file named flash-all.bat
6. wait for it to finish and it should boot up just fine.
jase33 said:
from the google screen:
1. hold volume up, volume down and power until you get to the screen with the android and its belly open
.
Click to expand...
Click to collapse
say what? Hold vol.up, vol.down and power until i get to bootloader?
when i press vol up, vold down, and power, holding them all in together from the google screen the device shuts down..
Do you have a youtube tutorial gudie or something?
EDIT:
Also, I've never rooted or done anythign with this tablet except downloading a few apps etc...this crash happened when downloading from utorrent...
The key combination is to be used from being powered off.
Fuzzra said:
The key combination is to be used from being powered off.
Click to expand...
Click to collapse
Yeah, and from what i can read it also needs an unlocked bootloader, which i don't have..
just keep holding the keys down. it will shut down. keep holding it will try to boot back up and take you to the bootloader screen. you do not need an unlocked boot loader. all my nexus devices have locked bootloaders, are rooted and run custom roms.
jase33 said:
just keep holding the keys down. it will shut down. keep holding it will try to boot back up and take you to the bootloader screen. you do not need an unlocked boot loader. all my nexus devices have locked bootloaders, are rooted and run custom roms.
Click to expand...
Click to collapse
shuts down, then nothing... tried holding it down for about a minute.
skampflens said:
shuts down, then nothing... tried holding it down for about a minute.
Click to expand...
Click to collapse
like this
jase33 said:
just keep holding the keys down. it will shut down. keep holding it will try to boot back up and take you to the bootloader screen. you do not need an unlocked boot loader. all my nexus devices have locked bootloaders, are rooted and run custom roms.
Click to expand...
Click to collapse
also, should add that i tried to unlock oem via the cmd, tried to flash boot.img but nothing..
when typing fastboot oem unlock, it got stuck at "Yes" when trying to unlock bootloader, and when typing flash boot, it said error, cannot flash boot.img..
AND i'm not running a custom rom, just the standard stock rom
one step at at a time. lets get you to the bootloader screen first. all good things happen from there.
jase33 said:
one step at at a time. lets get you to the bootloader screen first. all good things happen from there.
Click to expand...
Click to collapse
uploading a video....
only way i can access fastboot is via volume down and powerbutton..and that's when the device is shut down
<iframe width="560" height="315" src="//www.youtube.com/embed/SRfrjR9Y8fI" frameborder="0" allowfullscreen></iframe>
OK. but you can get there. yes?
jase33 said:
OK. but you can get there. yes?
Click to expand...
Click to collapse
Yes, I can access bootloader (fastboot mode).
tho i don't know which version i'm running..
it's either 4.4.2 (KOT49H) or 4.4 (KRT16S).
however, when running flash-all it says "fastboot is not recognized as an internal or external command"
http://www.youtube.com/watch?v=SRfrjR9Y8fI&feature=youtu.be
dont worry about version. it does not matter. lets focus on your connection to the device. do you have ADB setup on your pc? if you dont, go to THIS thread and get minimal ADB & fatboot from shimp208. install it and run it.
jase33 said:
dont worry about version. it does not matter. lets focus on your connection to the device. do you have ADB setup on your pc?
Click to expand...
Click to collapse
Yeah, at least i think so.. downloaded the adb bundle pack..
plug in your device and type "fastboot devices". tell me if you see a serial number display
jase33 said:
plug in your device and type "fastboot devices". tell me if you see a serial number display
Click to expand...
Click to collapse
nope, it says "fastboot" is not recognized as an internal or external command, oparable program or batch file.
http://www.youtube.com/watch?v=RLjLdHxuENg&feature=youtu.be
ok. you dont have fastboot. go and install Minimal ADB and Fastboot
jase33 said:
ok. you dont have fastboot. go and install Minimal ADB and Fastboot
Click to expand...
Click to collapse
serial nr does show!
great! have you downloaded the factory image for your device yet? get it HERE if you have not. make sure you get the right one. if your device is wifi only select that one, if it had mobile data and a sim card get the one for mobile..
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
copolii said:
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
Click to expand...
Click to collapse
The reason starts the only option is because your only holding volume up when going into fastboot. Hold power and volume up AND DOWN. All at the same time. Trust me I had the same issue but googling helped me find out you gotta hold both buttons
Sent from my VS980 4G
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
Click to expand...
Click to collapse
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
I finally got it to boot.
boot into bootloader (hold vol-up+vol-down+power)
choose reboot bootloader
choose shutdown
turn it back on
Seems like it needed to be shut completely off not just rebooted after the flash. Perhaps a reboot maintains weird memory fragments or something? Crazy talk, I know.
Edit: you shouldn't have to wait long to see if it works. Mine jumped to the "Upgrading apps ..." screen straight away.
The very first boot on my n7 and n10 took about 20 min, after that they have normal boot time, I believe this may have something to do with encryption but never bothered to check as I just did something else while it booted
Side note, the n9 has an initial boot time of at least 5-10 min (can't recall but it took forever it felt like) and this is optimized hardware for the software so no surprise that there is a huge long boot time on the first go
Also I flashed both manually erasing all partitions first through fastboot then flashing each one individually... Just another side note
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
Click to expand...
Click to collapse
Ive tried to connect to the device in adb, fastboot, I can only get it to adb sideload mode.
Sideloading gives the message Wrong footer instalation aborted.
How did you manage to flash the image? All drivers did install properly it seems.
Boot loop
thedarksavant said:
I finally got it to boot.
The same was happening to me, after unlocking it it began to loop, even after I wipe it was still looping.
I followed your steps of going into reboot recovery then power off. -- issue resolved!!
Thanks!
******
Click to expand...
Click to collapse