Related
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
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
nexus toolkit from dev section
ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol
Issue Fixed I think, he PM'd me.
Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.
Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1
This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.
Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.
it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!
Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app
Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.
OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.
Use USB ports on the back of your computer, not the front.
Wanting to go back to a factory image on my Nexus 10 so that I can take the update for Android 4.4. Being the lazy guy that I am, I tried to take the easy way out and used the WugFresh tool to go back to the factory image and unroot. It didn't work. Now I have no recovery or system so I can only boot into the bootloader. When I try and flash a new bootloader the command prompt just sits on "sending boot" and never gets there. I am noticing that on the Nexus when I initiate the command a cyan colored box comes up that says "FASTBOOT STATUS - DATA00140000" Sometimes the numbers after the data part are different but that's it. I'm not sure how to fix it because I can't send files to it. Any help would be appreciated.
EDIT: completely uninstalled and reinstalled (for the second time) adb, fastboot, and universal drivers and then rebooted my machine Nexus started connecting just fine.
jcrss13 said:
Wanting to go back to a factory image on my Nexus 10 so that I can take the update for Android 4.4. Being the lazy guy that I am, I tried to take the easy way out and used the WugFresh tool to go back to the factory image and unroot. It didn't work. Now I have no recovery or system so I can only boot into the bootloader. When I try and flash a new bootloader the command prompt just sits on "sending boot" and never gets there. I am noticing that on the Nexus when I initiate the command a cyan colored box comes up that says "FASTBOOT STATUS - DATA00140000" Sometimes the numbers after the data part are different but that's it. I'm not sure how to fix it because I can't send files to it. Any help would be appreciated.
EDIT: completely uninstalled and reinstalled (for the second time) adb, fastboot, and universal drivers and then rebooted my machine Nexus started connecting just fine.
Click to expand...
Click to collapse
I the same happens but with Android L. and you say you fix reinstalling drivers?
I have a Nexus 7 2012 (KOT49H, nakasi) which will only boot into fastboot, but not to Android.
I don't know what caused this - when it happened first I rebooted, and it worked again for another couple of days, then I got a "Google Play Services has stopped" message, so I tried to power off and reboot the tablet.... and it won't reboot!
At that time I was unaware that such a thing as USB debugging existed, so it's not been set... Indeed all I know about these problems now is what I've found out here... so sorry if I test your patience!
What I have done:-
I have tried a factory reset, with no effect.
Tried Wug's toolkit, which was unable to do anything (as USB debugging not set?)
(Windows 7 appears to have the drivers for this - it appears in Device Manager as Google Nexus 7 Bootloader interface)
Tried Skipsoft's Toolkit, which succeeded in unlocking the bootloader, and I have flashed images (downloaded from google) for Boot and System to the appropriate partitions... still nothing! Flashing the bootloader image failed ("An error occurred")
Is this Nexus destined for the dustbin? It is, of course, out of warranty :crying:
Apologies if I've done something daft, but I'm getting desperate...
Can anybody help?
Many thanks
hEY,
i got the same. I tried to install cm11 and i format sd card and happens that i formated the system too.
Now i can only to restart in revory "cwm v6.0.5.0" but cant start in download modus with Power+down (see only GOOGLE LOGO with open lock sign).
With wugs fresh i got the same with the f**** usb debugging enable thing, i cant get into nothing only in cwm.
I would be sooo happy to find a tool like (adb-tool) how i can put files again on my nexus 7.
thank you guys in advance!
beaquoy said:
I have a Nexus 7 2012 (KOT49H, nakasi) which will only boot into fastboot, but not to Android.
I don't know what caused this - when it happened first I rebooted, and it worked again for another couple of days, then I got a "Google Play Services has stopped" message, so I tried to power off and reboot the tablet.... and it won't reboot!
At that time I was unaware that such a thing as USB debugging existed, so it's not been set... Indeed all I know about these problems now is what I've found out here... so sorry if I test your patience!
What I have done:-
I have tried a factory reset, with no effect.
Tried Wug's toolkit, which was unable to do anything (as USB debugging not set?)
(Windows 7 appears to have the drivers for this - it appears in Device Manager as Google Nexus 7 Bootloader interface)
Tried Skipsoft's Toolkit, which succeeded in unlocking the bootloader, and I have flashed images (downloaded from google) for Boot and System to the appropriate partitions... still nothing! Flashing the bootloader image failed ("An error occurred")
Is this Nexus destined for the dustbin? It is, of course, out of warranty :crying:
Apologies if I've done something daft, but I'm getting desperate...
Can anybody help?
Many thanks
Click to expand...
Click to collapse
smoschi said:
I would be sooo happy to find a tool like (adb-tool) how i can put files again on my nexus 7.
Click to expand...
Click to collapse
If you have wugs, you already have the adb tool on your computer. Look in the wugs directory. However it sounds like your drivers are messed up. If that is the case nothing is going to work until you get that corrected.