I have a major problem and I do not know if there is a resolution but I figured I would ask.
I have a Nexus 10 NOT rooted, that had an unlocked bootloader that was on Lollipop and today I got the message for the factory update to 5.1..
It was saying system installing for more than 2 hours with the line at about 40 for these 2 hours so I figured it was not working and I shut off the Nexus... I then figured I would simply start from scratch and do a factory reset.. loose all data etc etc,
When that finished it was cycling on and off with No Command and that is where it is,
The only thing that works when holding down power and volume and getting the menu where there is Startup, Fastboot, Recovery, Power Off is Power Off.
If it goes with restart it will show No Command and then nothing and No Command and then nothing etc etc..
Everything else does nothing,, I have no ADB or Fastboot
I could not use android toolkit (at least with functions I tried as I needed Fastboot or ADB and have neither.. Only thing tool could do was reboot into fastmode but nothing else.
My question is there any hope for this Nexus 10 with corrupted (probably) files that cannot be put in USB debugging mode or anything else or should I just trash the Nexus 10 It was working beautifully with 5.0.1 and I am sorry that I chose to update with the latest 5.1.
Any suggestions apart from trashing my formerly great tablet are appreciated
People NRT 2.04 solved this problem..Thank you WUG
Related
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 guys
I tried the one-click root toolkit for mac from android rootz.
Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help
When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset
My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok.
Sent from my Nexus 10 using Tapatalk HD
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
scooterbaga said:
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
Click to expand...
Click to collapse
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
bg1906 said:
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
Click to expand...
Click to collapse
Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time.
With a now bootable device, I'm off to replace the recovery... Thanks again.
Hello everyone, I'm new in this forum and have just bricked my Nexus 7 .
I was not very happy with my Nexus 7 with JB version 4.2.1, it lagged and took long time to load apps etc. I used the Nexus 7 toolkit to unlock my bootloader, flash recovery and then tried a few custom roms. I eventually flash the official 4.1.2 firmware from google but the constant notification for firmware update annoyed me and I decided to root and get rid of the firmware update notifications by installing fotakill.apk.
But when I tried to root using the Nexus 7 toolkit, I chose the option to sideload the zip files for rooting automatically. It asked to flash my boot loader to a lower version (3.34, mine was 3.41) and afterwards it rebooted the device and eventually got stuck at a screen with these lines:
now send the package you want to apply
to the device with adb sideload <filename>
after a long time without anything happening, I suspected that things went wrong and pressed the power button for a few seconds and the device turned off. Now I cannot turn it back on, when plugged in it doesn't show the charging battery, also I cannot boot into fastboot mode by holding Volume down + Power button. The screen stays black the whole time.
I even tried to open the back power and pull the battery out and in again and try to turn on the tablet, nothing happens. I remember the battery level was like roughly 90% the last time the tablet was working, so I don't know what went wrong .
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
semeru said:
Hold power + vol down button about 30 seconds
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I tried that but nothing happened .
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Westervoort said:
Press all buttons on the side simultaniously untill fastboot/bootloader mode appears. This should work, no matter if your device is booted or not, or soft bricked or whatever. Then: http://forum.xda-developers.com/showthread.php?t=1907796 .
If it doesn't work however (like after 30-60 seconds), then connect your nexus 7 to your PC. Go to device manager and identify your device. Does it say apx-mode or something like that? Then your device is possibly hard bricked and you might find some answers here: http://forum.xda-developers.com/showthread.php?t=1879228 .
Your should not have used rootkits. Most of these topics appear after people using toolkit. Learn to use fastboot. It's the only program you'll need for the nexus 7. Yes, it's a command line tool but at least it forces you to think before flashing. For example, it was not necessary to downgrade your bootloader. I really don't get why you did that. Also, if you want to run a stable 4.1.2 without the annoying update messages, you can, for example, flash cyanogenmod 10. It's stable, very smooth, and way better than stock.
Click to expand...
Click to collapse
Thanks I did a search and finally found an answer. I was running fine on my N7 with PACMan and suddenly it got stuck booting up. So I booted into recovery and reflashed the ROM, and wiped dalvik and cache. When I rebooted it went to "Android is upgrading" like usual after wiping dalvik, then it got stuck there. So I rebooted again and nothing. Just a blank screen. Your suggestion of holding all the buttons down for 30-60 seconds awoke my Nexus. I'm going to wipe everything and start over.
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
So let me begin with what I'm running.
Stock bootloader-locked.
Nougat 7.1.2 Beta from Google (On the beta program)
No root. Completely stock.
When I updated to 7.1.2 I started having this problem, the phone did not start up right after the update. It took a few hours to finally get the phone to come on, when I did I opted out of the beta and went back to 7.1.1, flashed back, phone started, yay!
Except.....
Now if I shut the phone down now I cannot get it to power on at all, doesn't respond to anything, no stock bootloader by pressing power+vol down, nothing.
The only way to get this phone to load up is I have to wait until the battery fully dies, charge to full and then power on the phone and it will start. Even after all this I still can't power down and enter stock recovery/bootloader.
Any idea on what's going on?
Chewmasey said:
So let me begin with what I'm running.
Stock bootloader-locked.
Nougat 7.1.2 Beta from Google (On the beta program)
No root. Completely stock.
When I updated to 7.1.2 I started having this problem, the phone did not start up right after the update. It took a few hours to finally get the phone to come on, when I did I opted out of the beta and went back to 7.1.1, flashed back, phone started, yay!
Except.....
Now if I shut the phone down now I cannot get it to power on at all, doesn't respond to anything, no stock bootloader by pressing power+vol down, nothing.
The only way to get this phone to load up is I have to wait until the battery fully dies, charge to full and then power on the phone and it will start. Even after all this I still can't power down and enter stock recovery/bootloader. Any idea on what's going on?
Click to expand...
Click to collapse
Interesting. You can't button press and get into bootloader? That's hard wired. Maybe a bad power button? I was going to suggest wiping cache from recovery as a first step, but you NEED recovery mode to do anything. At a minimum I would go into Dev Settings and allow both OEM unlocking and USB debug straight away. This way you can use ADB, and if you end up in a bootloop you can still unlock the bootloader and flash images and maybe a recovery . Do you know which 7.1.1 build you are on? Set up ADB/fastboot and try adb reboot recovery from within the OS. Maybe get you into recovery so you can at least wipe cache to start. Later, you may also be able to sideload an OTA from stock recovery (if adb reboot works). If the OTA doesn't fix it, you may need to do a factory reset. ADB will also allow you to pull any valuable files off the device.
I've actually signed up again and am running the beta 7.1.2 OTA Google beta program.
Security patch: January 5/2017
Baseband version: angler-03.79
Kernel version: 3.10.73-geac7D674
[email protected] #1
Tue Dec 13 10:11:12 UTC 2016
Build Number: NPG05F
I've been back and forth with 7.1.1 and 7.1.2 and it does the same thing with each build.
I tried unlocking with Wugs toolkit but as soon as I get to power off device and go into bootloader I can't get the bootloader screen to show up and I need to wait until the phone dies and charge to 100% and then start the phone regularly.
I do have ADB installed on my PC but anytime I need to get into bootloader I'm screwed.
Chewmasey said:
....I do have ADB installed on my PC but anytime I need to get into bootloader I'm screwed.
Click to expand...
Click to collapse
Thanks for providing lots of good info on where you are at.... most ppl dont. I'm also on 7.1.2 but with zero issues. OK gotcha, so using NRT, under advanced tools you have tried rebooting to both bootloader and recovery, and it failed. You didn't say YES, I enabled USB Debug/ OEM Unlock in developer options. By any means possible get into your OS and enable OEM Unlocking and USB Debugging now before it's too late. You've got to get into your bootloader/recovery and you are still locked with no access to ADB. There is a great driver install/ diagnostic tool in NRT to help you confirm all drivers are there and working. Sounds like you are ready to unlock/wipe in an effort to recover your phone. I think you can recover from this, but you'll probably lose your userdata.
I have the phone up and running right now. I have already went into developer options and checked OEM unlock and have debugging enabled.
When I go into NRT and go to unlock, it connects etc but when it comes to the point of power off device and boot into bootloader the screen is blank. My PC only recognizes the phone as an Android Interface after this and then I have to wait until the phone completely dies and a recharge to power up the phone.
I would try NRT again right now but I'm scared I will be without my phone all day tomorrow.
Damned if I Do, Damned if I don't.
Chewmasey said:
I have the phone up and running right now. I have already went into developer options and checked OEM unlock and have debugging enabled. When I go into NRT and go to unlock, it connects etc but when it comes to the point of power off device and boot into bootloader the screen is blank. My PC only recognizes the phone as an Android Interface after this and then I have to wait until the phone completely dies and a recharge to power up the phone.
I would try NRT again right now but I'm scared I will be without my phone all day tomorrow.
Damned if I Do, Damned if I don't.
Click to expand...
Click to collapse
When the phone is not responsive and you have been discharging it, have you tried holding the power button down for at least 2 minutes? In many cases this forces the phone to restart, but it takes a long time. That may shorten the wait between getting the phone back up.
Did you only start using NRT after the problem, or it was working fine beforehand in bootloader mode (fastboot). There is a separate driver for fastboot, I'm trying to see if that was working before. Since you are trying to unlock, it sounds as if you are past trying to save any data on the phone. NRT uses both ADB and fastboot, but you may have better luck using the command line from your PC. In my previous post I linked to Google's ADB/Fastboot binaries. Instructions are pretty basic. If you can get that setup you can try communicating with the device from the command line. Even if the is screen off, try sending fastboot devices.
Tried everything, gave up bought a used 64gb Nexus 6p.
Last time fiddling with the phone Everytime I touched the power button the red LED blinked.
I'm thinking either the motherboard or the battery.