Database Users

[Q] waiting for you device to finish booting back up...

Nexus 7
Android 4.1.2 JZ054K
using Nexus Root Toolkit v1.5.5
I've done: 1. Initial setup- full drive installation
2. backup
3. Unlock
everything went as expected according to the procedure.
4. the Root, it went through it procedure until it got to:
--waiting for your device to finish booting back up...---
been waiting on this screen forever, the Nexus 7 screen shows the android w/ the "Start" tab.
done this procedure several times w/ Nexus Root Toolkit v1.5.4 and several time w/
Nexus Root Toolkit v1.5.5
nothing has changed, don't know if my Nexus 7 is unlocked or rooted.
pls help. any ideas, suggestions...
thanks in advance

Try to reset the device to factory and try again. Take it slow and make sure you're following each step.
If all else fails, Google, Google, Google...
Good luck

I had this same issue today when rooting my new 32gb Nexus 7. Wug's tool wasn't autoselecting the right version (4.1.1 when I had 4.1.2) and it was doing the same thing, hanging on the "waiting for your device to reboot" message. Make sure the firmware version on the Nexus matches the version Wug's tool is detecting.

zombiest said:
I had this same issue today when rooting my new 32gb Nexus 7. Wug's tool wasn't autoselecting the right version (4.1.1 when I had 4.1.2) and it was doing the same thing, hanging on the "waiting for your device to reboot" message. Make sure the firmware version on the Nexus matches the version Wug's tool is detecting.
Click to expand...
Click to collapse
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod

No success on this issue!!
zaphodmuc said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
Click to expand...
Click to collapse
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.

Same Issue
mike_24_11 said:
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Click to expand...
Click to collapse
I have been trying the NRT 1.6.3. The issue of Waiting for your device to finish booting back up.... repeats.
No solution yet.

mike_24_11 said:
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Click to expand...
Click to collapse
So.....you come into the Nexus 7 forums to try and get help with your Nexus 4......OK
ananiah2011 said:
I have been trying the NRT 1.6.3. The issue of Waiting for your device to finish booting back up.... repeats.
No solution yet.
Click to expand...
Click to collapse
Dont use a toolkit, its that simple. In the amount of time you have wasted on that toolkit, you could have learned the manual method and realized it wasnt as hard as you thought

Booyah
zaphodmuc said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
Click to expand...
Click to collapse
Thanks!!! worked like a charm

Bohefus said:
Thanks!!! worked like a charm
Click to expand...
Click to collapse
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
Where do I change the USB connection from MTP to PTP . I mean where do I find the dropdown on the device or on in the program?
I can't find any USB settings. I will probably feel a little stupid when I'm told where to find these settings but I'd been knocking my head against the wall long enough

ibbeebee said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
Where do I change the USB connection from MTP to PTP . I mean where do I find the dropdown on the device or on in the program?
I can't find any USB settings. I will probably feel a little stupid when I'm told where to find these settings but I'd been knocking my head against the wall long enough
Click to expand...
Click to collapse
kind of like the one located in Settings>storage>menu>USB Connection?

Pirateghost said:
kind of like the one located in Settings>storage>menu>USB Connection?
Click to expand...
Click to collapse
Well I probably would never have found the setting without help, I couldn't find anything called menu so I tried the 3 dots next to the search button, Bingo the jackpot!. Now to see if I can back up the device .
I may be back but let's hope not
Well I'm back!!
I have been through the driver config Guide & the new drivers seem to be installed But I can't see my tablet in explorer anymore & my Device is open in a screen I haven't seen before
A big button at the top of the screen
START
then an up & down arrow
FastBoot Mode
Variant -flo32C
HW VERSION -rev_e
BOOTLOADER VERSION - FLO-04.04
CARRIER INFO - NONE
SERIAL NUMBER -07e1eda6
SIGNING -yes
Secure BOOT - enabled (in green)
LOCK STATE - unlocked
& I'm rather nervous about touching any of it
I'm about to start the driver process again but will wait for some advice
OK I did not follow my own advice & have rebooted the device & it has loaded normally& is now viable on my computer again .
I will wait for some feedback before proceeding Thanks in advance for any assistance Regards Beebee

Hi I repeated the process & have success at last.
I have backed up the device & am about to root it.
What are the advantages & disadvantages of ticking Custom Recovery . I've done a Google search but I finish up being sidetracked for hours when I do that So will just ask you

[Q] Changed pixel desnity, wont turn on. Help!

After a successful day of unlokcing and rooting my new tablet, I decided to try and experiment with the dpi to try and get some phone based apps working using an app called "LCD Density Modder" I changed to Mdpi - 160, and the tablet turned off. It restarts to the Goolge logo, with an unlocked lock then dies again. What went wrong and how do I fix it? Help me out guys :crying:

Try holding down the power button for 10-20 seconds.
If that doesn't work, leave it plugged in for a couple hours and try again.
Sent from my Nexus 7

It turns on, and fastboot will show up, but Android will not boot. Or if it is booting, it's only a black screen. Is there any way to erase the pixel settings I've applied through recovery or the Nexus 7 toolkit? Or am I totally missing the point?
Edit: The screen does actually appear to be lit. Just black

theshafe said:
After a successful day of unlokcing and rooting my new tablet, I decided to try and experiment with the dpi to try and get some phone based apps working using an app called "LCD Density Modder" I changed to Mdpi - 160, and the tablet turned off. It restarts to the Goolge logo, with an unlocked lock then dies again. What went wrong and how do I fix it? Help me out guys :crying:
Click to expand...
Click to collapse
do you have a custom rom recovery installed? go into your recovery and wipe data/factory reset. or if you flashed a custom rom, go into the recovery wipe data/factory reset and reflash your rom.

I've tried this, to no avail. After the Google logo, a portion of the screen flashes pink and the tablet goes dark again

You can use wugs toolkit to reinstall a factory image, or you can sideload one using fastboot command, wugs method is easier. The file you edited is the build.prop if you still have adb access you could use adb shell to edit the file and change the settings back. Sadly I don't have a clue as to the default settings for dpi in the n7 build.prop.
Cheers Danny

After attempting to factory reset, and trying all these methods I realized that USB debugging is now disabled :crying:

Have you tried booting into recovery (power and volume down) whilst the tablet is connected to the PC via USB? I found that helps you get into recovery sometimes from bootloops etc.
Cheers Danny

Yes, I can get into recovery and fastboot but any attempt at booting Android results in a black screen

Kk come down.. Boot into Fastboot download wugfresh toolkit, and click the flash back to stock and unroot option and check the box that says device will not boot.. Problem solved
Sent from my Nexus 7 using Tapatalk HD

I tried to, but the drivers wont install because it won't boot
Forgive me, I can do all this but I'm a little slow :silly:

Shafe when you rooted your tablet how did you go about it?
Did you use a toolkit? If so which one?
What type of computer did you use, windows, Mac or Linux?
If it was windows which windows was it, XP, vista, 7, 8?
There are known problems in getting drivers to work with certain windows etc. But if you used a toolkit to root then you must have had working drivers at some point during the process.
Any more info you can provide will help get to the bottom of this
Cheers Danny

I used the not so creatively named Nexus 7 ToolKit v 4.0.0 on windows 7. I've had the drivers and just reinstalled them from the toolkit, so they are now on there again. The problem is that I factory reset and since Android won't boot, I have no way of enabling USB debugging

Grab wugs from here
http://forum.xda-developers.com/showthread.php?t=1766475
[Toolkit] Wug's Nexus Root Toolkit v1.6.1 [Updated 11/30/12]
And follow Francis instructions posted above, should sort your problem. You won't need more drivers as you already have them installed.
Cheers Danny

I tried this a couple times, but after trying to flash stock + unroot it says my ADB device was not found because USB debugging isn't on

Found a guide that will allow you to restore stock through fastboot
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
I am not experienced enough with fastboot to really be of more help. Hope this does the trick.
Cheers Danny

Yep, I found this a few minutes ago and am giving it a shot. I'm inexperienced also, but I guess I'll have to learn! Thanks brother

Forget all toolkits and use fastboot, you'll gain twice that way; working N7 and also you'll have gained some knowledge.
It's a lot easier than it seems.
Sent from my Nexus 7 using xda premium

[Q] Mystery Solved - i cannot flash IMG to 4.3

Hello guys
Solve this one !
I have tried pushing a root img to the device with command prompt
I've tried CF-Auto-Root-manta-mantaray-nexus10
Ive tried Wug's Nexus Root Toolkit
And all get stuck at the same point - while flashing the img, but nothing gets flashed.
EDIT
I have found what MAY be the reason... one of these:
1/ changed computer, in this case to a laptop from desktop
2/ when using Wugs Nexus Root Toolkit, and when plugging in the Tablet and saying yes to USB debugging message that pops up on the tablet, THIS TIME I selected the checkbox saying "Always do this" (or something) before saying OK...
And job is done no problem... after about 12 hours of trying everything I could think of.
Bizarre.

Nexus 10 - bricked. Black glowing screen

I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks

lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.

Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597

Stuck in Boot, fastboot locked, no adb sideload

Hello,
I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.
I have attempted a few solutions I have found either on xda or on other pages but the gist of what I’ve attempted so far is thus:
I have tried to reflash android stock after obtaining it from google : https://developers.google.com/android/images (MTC19T) but the oem option was unchecked so “fastboot flashing unlock” returns with an error.
I have tried to apply an OTA update, again I obtained the file from google (MTC19T) , via the recovery > apply update from adb . But it fails. The error from the phone is:
Code:
E: failed to verify whole file signature
E: signature verification failed
And on the pc side I believe that the failure comes from the fact that my pc has never been connected to the phone via ADB, so it’s unrecognized.
- I have also tried to bypass the adb pc signature issue by connecting a usb flashdrive to my phone via a usb-c adapter but the mount /sdcard command doesn’t work.
I’ve tried a few more esoteric solutions, like booting into Emergency Download (EDL) but my phone just boots into the google logo and stays there.
A few informations on my device (according to the fastboot/recovery screen)
Code:
BL: angler-03.51
Baseband: angler-03.61
Product/Variant: ANGLER-ROW-WN1
6.0.1/MTC19T/2741993
Current Build Number: MTC19T
So, to summarize: Fastboot is locked and won’t work, ADB is unrecognized and using a usb drive pretending to be an sdcard doesn’t work and I’m working with a stock recovery.
I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Thank you!

Hipstronaute said:
Hello, I have a Nexus 6P stuck during boot on the white google logo. Apparently it happened during an update to N.....I'm looking for a way to bypass the fastbook lock or the adb verification. Or (even better) for anyone here to tell me that I've been going the wrong way all this time and that the solutions involves three easy steps...
Click to expand...
Click to collapse
Try again but you have to use an OTA that is newer than MTC19T. You still may be able to sideload when recovery is in ADB Sideload mode. There is no way to unlock your bootloader. Make sure you are using a recent, known working copy of ADB/Fastboot. The problem many people can't overcome is that they never set up ADB before or used it on a few occasions, so now the phone is dead they can't get it set up correctly. When the phone is connected in recovery>>ADB sideload update, what returns when you run "adb devices"? Do you have another phone you can use to confirm your ADB/fastboot setup is installed correctly?

Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Sent from my Nexus 6P using Tapatalk

Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.

Hipstronaute said:
Hi,
Thank you for your answers.
@v12xke For the OTA after trying MTC19T I downloaded and tried half a dozen images from Google. Previous versions, next version of marshmallow, a few of the nougat versions. The results were exactly the same.
As for adb I just updated my Android studio, and it's not the first time I've used these tools. The process of sideloading the zip always stops at 47% but I can see that adb and the recovery are communicating.
Fastboot devices also detects my device, but I don't have my computer on me right now.
@DavidSantos I already tried the toolkit but it just launched my phone on the Google logo and got stuck there.
Click to expand...
Click to collapse
You have turn off your phone , press volume up and power key , then a menu will pop up , then plug in your phone with your PC
Sent from my Nexus 6P using Tapatalk

DavidSantos said:
Download the Nexus toolkit and then boot into recovery and select on the toolkit "softbrick" , good luck. Private message if you need any help
Click to expand...
Click to collapse
Best way to brick your phone if you don't know what kind of softbrick this tool has been made for... :good:

You have turn off your phone , press volume up and power key
Click to expand...
Click to collapse
Yes, I did that. The soft just makes my nexus reboot to the Google logo.

@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...

Might be a special edition Nexus 6P , oh well. Mine had the same problem and it worked just fine
Sent from my Nexus 6P using Tapatalk

5.1 said:
@v12xke: Looks like there are also more and more of those bootloader + recovery access bootloop. With sideload OTA fails...
@Hipstronaute: I have already seen one or two users with the same kind of problem and if I remember, nothing fixed the problem.
Good luck...
Click to expand...
Click to collapse
That's too bad. Sounds like the storage memory going bad and the write process is interrupted when it hits that area. Thing is, I've heard the same OTA write failure occurring several times at 47%. Wonder what that means? Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.

@v12xke
Anyway sounds like @Hipstronaute is looking at a replacement phone, under warranty or otherwise.
Click to expand...
Click to collapse
Gosh do I hope that won't be the last post on this topic.