Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Bootlooping, adb not recognized, softbricked.

OP rohanjoshi

17th February 2014, 05:02 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
9 posts
Join Date:Joined: Feb 2014
Bootlooping, adb not recognized, softbricked.

So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".

I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like

Flash Stock + Unroot...
------------------------------------------------------------------


sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s

archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s



Booting up your freshly flashed stock device...
------------------------------------------------------------------

Wait for your device to finish booting up...

- It may appear to be boot looping; just wait...

- It could take 5-10 minutes; please be patient...

When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.

NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.



Press any key to exit...


- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
- My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.

I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Last edited by rohanjoshi; 17th February 2014 at 07:50 PM.
17th February 2014, 05:13 PM   |  #2  
mdamaged's Avatar
Senior Member
Flag South of Heaven
Thanks Meter: 1,075
 
1,676 posts
Join Date:Joined: Oct 2013
More
Not sure what happened with regards to the update freeze, but we're past that point now. Your next attempt failed because the bootloader is locked, and since you now have no way to enable debugging, you may have no choice other than to try to revert to factory.

Before trying it, issue a: 'fastboot devices' command and make sure your device appears if not you may have to fix your drivers, make sure you get the right image for your device.

https://developers.google.com/android/nexus/images

EDIT: Oh crap, you don't have USB debugging enabled. Try the link anyway, fastboot should still work.
Last edited by mdamaged; 17th February 2014 at 05:58 PM.
17th February 2014, 07:31 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
9 posts
Join Date:Joined: Feb 2014
I will give it a go
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
17th February 2014, 07:34 PM   |  #4  
mdamaged's Avatar
Senior Member
Flag South of Heaven
Thanks Meter: 1,075
 
1,676 posts
Join Date:Joined: Oct 2013
More
Quote:
Originally Posted by rohanjoshi

I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?

Do you have a camera on the front and back? And is WiFi only? If yes, it is a FLO and you want this one.

Do you have a camera on the front and back? And has LTE and WiFi? If yes, it is a DEB and you want this one.

Based on your initial post, it looks like you have a FLO.
The Following User Says Thank You to mdamaged For This Useful Post: [ View ]
17th February 2014, 08:12 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
9 posts
Join Date:Joined: Feb 2014
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
17th February 2014, 08:19 PM   |  #6  
mdamaged's Avatar
Senior Member
Flag South of Heaven
Thanks Meter: 1,075
 
1,676 posts
Join Date:Joined: Oct 2013
More
Quote:
Originally Posted by rohanjoshi

I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.

If you wanted the latest you'll want the 4.4.2...aka KitKat, that is what it was trying to update you to before this all happened. If you just want to go back to where you were, use the 4.3, but you will get prompted to update again.

Just keep in mind, runing flash-all as-is wipes everything, BUT, you can open the flash-all script in a text editor and remove the -w and it won't wipe userdata.

...also, if I may suggest, strongly, is if/when this works, and your device is backup, I suggest you unlock the bootloader first (since this wipes all data you might as well do it before you put anything on there), then go in and enable debugging. Now you can root, use adb if something happens again, etc.
Last edited by mdamaged; 17th February 2014 at 08:28 PM.
17th February 2014, 09:19 PM   |  #7  
Senior Member
Flag New Delhi
Thanks Meter: 58
 
336 posts
Join Date:Joined: Apr 2013
More
Quote:
Originally Posted by rohanjoshi

I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.

hey did u tried doing a factory reset from the stock recovery?
17th February 2014, 09:27 PM   |  #8  
OP Junior Member
Thanks Meter: 0
 
9 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by varuntis1993

hey did u tried doing a factory reset from the stock recovery?

do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?

If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
17th February 2014, 09:27 PM   |  #9  
mdamaged's Avatar
Senior Member
Flag South of Heaven
Thanks Meter: 1,075
 
1,676 posts
Join Date:Joined: Oct 2013
More
Quote:
Originally Posted by rohanjoshi

do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?

If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.

From there, hold power and press the volume up key, you should get a menu.

http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
18th February 2014, 06:53 PM   |  #10  
OP Junior Member
Thanks Meter: 0
 
9 posts
Join Date:Joined: Feb 2014
SOLVED
Quote:
Originally Posted by mdamaged

From there, hold power and press the volume up key, you should get a menu.

http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s

I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.

I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.

Thank you for you help! I truly appreciate it.

I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes