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] Help i Have tried everything!!! Need a genius!

im hoping someone can help i really want to get my tablet working again! so its stuck on google logo screen i can get it into fastboot but nothings working to bring it back to life i have tried the kits i have tried it manually both get stuck at sending system. i have tried to push the factory zip by using adb sideload but it says waiting for usb debugging to be enabled which i cant do obviously since it doesnt turn on. any help would be awesome!!!

You can't use adb in the bootloader(fastboot mode). Use fastboot commands to flash a custom recovery and then use adb while in custom recovery (TWRP, CWM)
Sent from my Nexus 7 using xda app-developers app

veeman said:
You can't use adb in the bootloader(fastboot mode). Use fastboot commands to flash a custom recovery and then use adb while in custom recovery (TWRP, CWM)
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
tried it didnt work

Erica24 said:
tried it didnt work
Click to expand...
Click to collapse
That's a little lacking on info. What didn't work? Flashing the custom recovery? The adb transfer? The .zip flash? You need to provide the pertinent info if you want the correct help.
As far as the part of being stuck at sending system, this is something I have noticed when using older fast boot binaries or having a driver issue on your PC. Try downloading the sdk and updating to the newest fast boot and adb binaries. Fastboot refuses to work on my wife's laptop, and gets stuck in the exact same place. But, it works fine from mine.
Sent from my Nexus 7 using xda premium

rebel1699 said:
That's a little lacking on info. What didn't work? Flashing the custom recovery? The adb transfer? The .zip flash? You need to provide the pertinent info if you want the correct help.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
i can flash custom recovery no problem but the adb transfer does not work theres no zip. on the sd card so i have to try and get it on the card to flash it because sending system through fastboot hasnt worked i tried to push it to the sd card but it says waiting for usb debugging.

Erica24 said:
i can flash custom recovery no problem but the adb transfer does not work theres no zip. on the sd card so i have to try and get it on the card to flash it because sending system through fastboot hasnt worked i tried to push it to the sd card but it says waiting for usb debugging.
Click to expand...
Click to collapse
Which custom recovery are you using? I would suggest TWRP 2.6.0.0. I always have great luck getting adb to initialize with it. Just go into the advanced menu and hit adb sideload. As a secondary measure, if you have an otg cable, you can put the zip on a flash drive and load that way too. Advanced-mount-click otg
Sent from my Nexus 7 using xda premium

Erica24 said:
im hoping someone can help i really want to get my tablet working again! so its stuck on google logo screen i can get it into fastboot but nothings working to bring it back to life i have tried the kits i have tried it manually both get stuck at sending system. i have tried to push the factory zip by using adb sideload but it says waiting for usb debugging to be enabled which i cant do obviously since it doesnt turn on. any help would be awesome!!!
Click to expand...
Click to collapse
Hi, Erica24....
I've also had issues with 'sending system' myself... many times. Indeed, when fastboot flashing 4.3 a couple of weeks ago, I had endless problems with it. I'm not sure why, but it could be because of its size.
'sending system' should take no more than a minute or so; two minutes tops.
Anyway, if you think it's taking too long, open up another command prompt window (in whatever folder you have the fastboot.exe stored in) and type...
Code:
fastboot devices
If you DON'T see a SERIAL NUMBER, it means the FASTBOOT connection has died... and you'll be sitting there for evermore waiting for system to go across.
If that is the case, disconnect from the PC, reboot the bootloader, and reconnect to a different USB port on your PC. Also, ensure you're using the original USB cable that shipped with your Nexus 7.
As I've said, for me, 'sending system', is often problematic...but changing USB ports, and trying again, has fixed it for me in the past. It's often just a case of perserverance, unfortunately.
Rgrds,
Ged.

rebel1699 said:
Which custom recovery are you using? I would suggest TWRP 2.6.0.0. I always have great luck getting adb to initialize with it. Just go into the advanced menu and hit adb sideload. As a secondary measure, if you have an otg cable, you can put the zip on a flash drive and load that way too. Advanced-mount-click otg
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have tried doing it through adb sideload but in red letters it states failed and I am to using twrp 2.6.0.0

Erica24 said:
I have tried doing it through adb sideload but in red letters it states failed and I am to using twrp 2.6.0.0
Click to expand...
Click to collapse
That's because the factory images are NOT flashable zips. You have to use fastboot on bootloader screen for factory images.
Sent from my Galaxy Nexus

I'm a geenyous!
But I'm stumped anyway.
Sent from my cell phone telephone using some sort of app...

GedBlake said:
'sending system' should take no more than a minute or so; two minutes tops.
Click to expand...
Click to collapse
Just flashed my grouper and flo back to factory last night. Both on the same computer running Ubuntu12.04. Grouper took about 15 minutes to send system, flo took less than 2 min.
Sent from my Nexus 7 using XDA Premium HD app

mr1ncred1ble said:
Just flashed my grouper and flo back to factory last night. Both on the same computer running Ubuntu12.04. Grouper took about 15 minutes to send system, flo took less than 2 min.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
15 minutes sounds a bit long... when it works on my grouper, it usually goes across in about 90 seconds. But the trick is getting it to work at all. Which usually involves lot's of plugging and unplugging into different USB ports, and repeatedly rebooting the bootloader. Eventually, it acquiesces... and bends to my will... 'cos I'm stubborn like that.
It's an either-or situation for me... it either goes across quickly, or it doesn't goes across at all. But eventually, it does goes across.
Rgrds,
Ged.

GedBlake said:
15 minutes sounds a bit long... when it works on my grouper, it usually goes across in about 90 seconds. But the trick is getting it to work at all. Which usually involves lot's of plugging and unplugging into different USB ports, and repeatedly rebooting the bootloader. Eventually, it acquiesces... and bends to my will... 'cos I'm stubborn like that.
It's an either-or situation for me... it either goes across quickly, or it doesn't goes across at all. But eventually, it does goes across.
Click to expand...
Click to collapse
Fastboot always works perfectly on the first try and system takes 1 minute. You might have a short in your USB cord, or faulty USB ports.

cmason37 said:
Fastboot always works perfectly on the first try and system takes 1 minute. You might have a short in your USB cord, or faulty USB ports.
Click to expand...
Click to collapse
Hi, cmason37...
Well, anythings possible, I suppose... but your explanation doesn't really hold much weight, as I never have other USB connectivity problems. And I've flashed ROMs on other devices before, without problems. Besides, the whole 'sending system' issue isn't unique to me... it's been referred to before, by others.
I have no idea why it happens, but for some reason the fastboot connection is lost when sending system (and it doesn't happen every time)... it never happens with sending boot, or recovery. I'm used to it; I know that it's not really a problem; just a temporary irritation that is eventually resolved by some USB plugging and unplugging, rebooting the bootboader a couple of times... and some very colourful expletives.
It eventually all gets resolved. And I have JellyBean 4.3, rooted, running on my N7.
But, hey... great you don't have similar inconveniences - glad that it all works for you.
Rgrds,
Ged.

[Q] Update to 4.4 brick

Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!

Same problem here. I'm running a pure stock. In rooted device and it bricked on me.
Sent from my SGH-M919 using XDA Premium 4 mobile app

theblackout said:
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Click to expand...
Click to collapse
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.

noradoor said:
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
Click to expand...
Click to collapse
Same thing using that thread, I.
fastboot erase system
fastboot flash system system.img (old 4.3 img)
stuck on sending system <529061 KB>
getting nervous here, any other ideas?

OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it

theblackout said:
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
Click to expand...
Click to collapse
I will try this when i get home from work and see how it goes.

Ksealy03 said:
I will try this when i get home from work and see how it goes.
Click to expand...
Click to collapse
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.

GedBlake said:
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ok im actually trying it now. i have a different USB cable that I will use.

teraonic 318
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.

Ksealy03 said:
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Click to expand...
Click to collapse
I had a similar issue that I was able to fix. Hopefully this will help you too.
I have a Nexus 7 that is rooted, stock ROM, unlocked bootloader. I have gotten many OTA updates since buying the device, and all previous OTA updates have completed without a hitch.
On the most recent OTA Kit Kat update, the device froze when trying to apply the update. It just displayed the boot animation in perpetuity.
I was able to use the Nexus Toolkit here on XDA (LINK) to load the stock Kit Kat ROM. Hope that helps.

[Q] [HELP] Hard Brick Nexus 7

Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<

EverAngelOn said:
Hi, this is my firt post, i'm going to quote this problem that's the same problem that I have...
"Device : Nexus 7
Problem : I was trying to unroot it and flash a 4.4.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean"
I did exactly the same thing that this guy did... ----> http://forum.xda-developers.com/showthread.php?t=2345874
The difference is that I don't live in USA and my Nexus doesn't have warranty... What can I do T.T my pc shows the tablet as Unknown Device and makes a sound when I puggle it, there has to be something that I can do >.<
Click to expand...
Click to collapse
Can you get into the bootloader still?

I can't
b3ltazar said:
Can you get into the bootloader still?
Click to expand...
Click to collapse
No, I can't. The screen is completely black.

Have you tried any of the suggestions in the thread you linked in the OP?

EverAngelOn said:
No, I can't. The screen is completely black.
Click to expand...
Click to collapse
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
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

Wugs tool kit
First when you plug it in hold all three power buttons
Second
I also have used the tool kit it gets stuck all the time on the flashing system. I think its a time out error because of the complexity of extracting the image and flahing the image with out a retry or check command. Here is a fix that i have figured out. When in Wugs tool kit download the Os Version you want on your device locate the folder with the downloaded image and extract it using 7 zip. once extracted flash the remaing .img files seperatly under andvance setting menu select flash system then user data it should boot right up. if you forgot what version you flashed previously flash all img files boot bootloader system user etc. if you still have problems let me know. i can give you my email.
Click thanks if i helped

b3ltazar said:
Do you get a charging icon when you plug in the n7? did you try a diffrent cable?What exactly does ur computer do when you plug in the dead n7 (does it thy try to install a apx driver) Does toolkit see tablet like its in the bootloader? If so try to flash a new bootloader!
try this found in another thread
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
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.

EverAngelOn said:
My tablet doesn't show the charging icon, I've tried with different cables, when I plug it to the laptop it makes a sound and shows an APX driver... I'm stressed and that instructions didn't work for me.
Click to expand...
Click to collapse
Unfortunately it sounds like you erased your bootloader and nvflash can do nothing for you unless you used the unbrickable mod before u f'ed up your tablet. Try sending it to asus for Warranty tell em you installed the ota update and it wouldn't boot up afterwards. I have read many threads about this issue with nobody being able to recover there tablet. Asus does have global warranty

[Q] Bricked Tegra note 7 after flash android 4.4.2

hey guys, i've just got my Homecare tegra note 7, i had upgrade it to android 4.4.2. but when i tried to flash CWM with Super Tool (1.1, 2.1 and 2.4)
none of them had recognized my device in fastboot mode, so i tried to flash the rom mannualy
(i follow this instructions http://forum.xda-developers.com/showthread.php?t=2645890&page=3)
everything worked but when i try to turn it on it get a endless boot loop.
i had used the android 4.4.2 and 4.3 and nothing, how can i fix it?
Thank you guys.

OK did you have from the start 4.2.2 ?
Did you at least update to 4.3 via OTA.
The reason i ask is simple that partition layout was changed with the 4.3 OTA from nvidia and the bootloader was updated too.
The next question would be do you get a blank screen when you try to go into fast boot or do you get a menu?
Have you tried another cable ?
What version of WIndows are you using?
What USB Port you using is it USB2.0 or USB 3.0 etc we need a little more info before we can help further.
Have you checked that the driver is loading when in fastboot mode correctly etc.
If your using USB3.0 try a USB2.0 port USB2 seems to be more reliable on Windows 8.x
If you could post more info i can gladly help you recover your tablet hopefully without using APX as APX is the last resort trick due to it can lead to completely bricked tablets.