Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,769,453 Members 42,041 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Nexus 7 Booting Failed & No ADB Connection

Tip us?
 
greyphox
Old
#1  
greyphox's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 5
Join Date: Nov 2012
Location: Preston
Unhappy [Q] Nexus 7 Booting Failed & No ADB Connection

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
 
Wilks3y
Old
#2  
Senior Member
Thanks Meter 638
Posts: 1,703
Join Date: Aug 2012
Location: Leek

 
DONATE TO ME
Quote:
Originally Posted by greyphox View Post
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
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?
If I Helped feel free to Thank me

My Websites:

 
greyphox
Old
#3  
greyphox's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 5
Join Date: Nov 2012
Location: Preston
Quote:
Originally Posted by Wilks3y View Post
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?
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
 
Wilks3y
Old
#4  
Senior Member
Thanks Meter 638
Posts: 1,703
Join Date: Aug 2012
Location: Leek

 
DONATE TO ME
Quote:
Originally Posted by greyphox View Post
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
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 .
If I Helped feel free to Thank me

My Websites:

 
ngoralph
Old
#5  
ngoralph's Avatar
Recognized Contributor
Thanks Meter 1266
Posts: 1,538
Join Date: Apr 2012
nexus toolkit from dev section
 
Wilks3y
Old
#6  
Senior Member
Thanks Meter 638
Posts: 1,703
Join Date: Aug 2012
Location: Leek

 
DONATE TO ME
Quote:
Originally Posted by ngoralph View Post
nexus toolkit from dev section
Have you even read what hes said?
He's already tried the toolkit...
If I Helped feel free to Thank me

My Websites:

 
greyphox
Old
#7  
greyphox's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 5
Join Date: Nov 2012
Location: Preston
Quote:
Originally Posted by Wilks3y View Post
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 .
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
 
greyphox
Old
#8  
greyphox's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 5
Join Date: Nov 2012
Location: Preston
Quote:
Originally Posted by Wilks3y View Post
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 .
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...
 
Wilks3y
Old
#9  
Senior Member
Thanks Meter 638
Posts: 1,703
Join Date: Aug 2012
Location: Leek

 
DONATE TO ME
Quote:
Originally Posted by greyphox View Post
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...
Sounds good mate !

Need any extra help drop us a PM I'd be happy to lend a hand.
If I Helped feel free to Thank me

My Websites:

 
greyphox
Old
#10  
greyphox's Avatar
Junior Member - OP
Thanks Meter 0
Posts: 5
Join Date: Nov 2012
Location: Preston
Quote:
Originally Posted by Wilks3y View Post
Sounds good mate !

Need any extra help drop us a PM I'd be happy to lend a hand.
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

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Google Glass XE20.1 Update Brings Improved Contacts, Head Nudge, New Cards and Commands

Ever since Google unveiled Android Wear earlier this … more

Remote Control Your Android Device with Monitordroid

The Android OS showsgreat potential in many areas. One of most interesting things that … more

Intel Partners with Unity to Support Android on Intel-Based Devices

Intel, largely known for their long-standing reputation as the king of … more

Device Review: Samsung Gear Live

Recently, Google announced Android Wear to the world. Android Wear is the Android-based initiative from … more