Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,733,899 Members 49,432 Now Online
XDA Developers Android and Mobile Development Forum

[Q] My tablet is completely f***ed

Tip us?
 
Gloftking
Old
#1  
Member - OP
Thanks Meter 0
Posts: 41
Join Date: Jun 2014
Exclamation [Q] My tablet is completely f***ed

I already had a problem where I was stuck in a bootloop and was told to flash the stock image (see here for previous issue : http://forum.xda-developers.com/show....php?t=2783631 ). I did this and tried it with the Nexus root toolkit with no wipe mode enabled and when I tried turning on the nexus I get this very annoying looping screen which shows the word google in the middle and the green start button at the top pointing towards the power button. every time I press the power button the green sign reapears and nothing happens. when I do this from the fastboot screen (using cmd on PC) I see a little message in the upper left corner saying "booting failed". I cannot seem to get the adb working at all which is a real problem and I am not sure if this tablet is reparable but I need someones help urgently http://forum.xda-developers.com/images/smilies/mad.gif

 
deltatux
Old
#2  
Senior Member
Thanks Meter 128
Posts: 572
Join Date: Apr 2011
Location: Toronto
Quote:
Originally Posted by Gloftking View Post
I already had a problem where I was stuck in a bootloop and was told to flash the stock image (see here for previous issue : http://forum.xda-developers.com/show....php?t=2783631 ). I did this and tried it with the Nexus root toolkit with no wipe mode enabled and when I tried turning on the nexus I get this very annoying looping screen which shows the word google in the middle and the green start button at the top pointing towards the power button. every time I press the power button the green sign reapears and nothing happens. when I do this from the fastboot screen (using cmd on PC) I see a little message in the upper left corner saying "booting failed". I cannot seem to get the adb working at all which is a real problem and I am not sure if this tablet is reparable but I need someones help urgently http://forum.xda-developers.com/images/smilies/mad.gif

Have you tried to flash the stock Android images using fastboot?

Note: Following command WILL WIPE your device.

Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/androi...s#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/androi...#nakasigktu84p

deltatux
Google Nexus 4 16 GB (E960 R11 304K)
Slim ROM 4.4.4 5.10 (KTU84P)
Slim Kernel 3.6 (3.4.92)

ASUS Nexus 7 16 GB 1st Gen
Slim ROM 4.4.4 5.10 (KTU84P)
M-Kernel a69 F2FS (3.1.10)
 
Gloftking
Old
#3  
Member - OP
Thanks Meter 0
Posts: 41
Join Date: Jun 2014
Question I just tried that

Quote:
Originally Posted by deltatux View Post
Have you tried to flash the stock Android images using fastboot?

Note: Following command WILL WIPE your device.

Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/androi...s#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/androi...#nakasigktu84p

deltatux
I tried what you said and when I entered the code in the cmd I got the following

"archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >" (without quotes)

and it just hangs here. Any idea what the problem is?
 
Gloftking
Old
#4  
Member - OP
Thanks Meter 0
Posts: 41
Join Date: Jun 2014
Quote:
Originally Posted by deltatux View Post
Have you tried to flash the stock Android images using fastboot?

Note: Following command WILL WIPE your device.

Code:
fastboot -w update image-nakasi-ktu84p.zip
For Nexus 7 (2012 WiFi): https://developers.google.com/androi...s#nakasiktu84p
For Nexus 7 (2012 3G): https://developers.google.com/androi...#nakasigktu84p

deltatux
for some reason whenever I try to execute your code I get

"archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >" (without quotes)
and it just hangs there

I appear to have bricked my nexus 7 as the tablet is not starting at all and I can recall that at some stage I accidentally used the fastboot command "fastboot erase bootloader" (not sure if it actually did that)
any ideas how to reverse this?

BTW in device manager the tablet shows up as UNKNOWN Device
 
deltatux
Old
#5  
Senior Member
Thanks Meter 128
Posts: 572
Join Date: Apr 2011
Location: Toronto
Quote:
Originally Posted by Gloftking View Post
for some reason whenever I try to execute your code I get

"archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >" (without quotes)
and it just hangs there

I appear to have bricked my nexus 7 as the tablet is not starting at all and I can recall that at some stage I accidentally used the fastboot command "fastboot erase bootloader" (not sure if it actually did that)
any ideas how to reverse this?

BTW in device manager the tablet shows up as UNKNOWN Device
If you erased the bootloader without flashing another one back in, you just bricked your device. The only course of action to save it is to do an nvflash but that would have required you to back up the nvflash blob before this incident. If all else fails, your tablet's a dud.

I would recommend either replacing your entire tablet or buy a replacement board on eBay and replace the motherboard yourself and then it will run like new.

deltatux
Google Nexus 4 16 GB (E960 R11 304K)
Slim ROM 4.4.4 5.10 (KTU84P)
Slim Kernel 3.6 (3.4.92)

ASUS Nexus 7 16 GB 1st Gen
Slim ROM 4.4.4 5.10 (KTU84P)
M-Kernel a69 F2FS (3.1.10)
 
Erovia
Old
#6  
Erovia's Avatar
Senior Member
Thanks Meter 233
Posts: 762
Join Date: Sep 2012
If you entered that command, your device is hardbricked and the only thing you can do about is to send it to Asus/Google for RMA.
Phone: Nexus 4
ROM: ParanoidAndroid 4+
Kernel: hells-Core
Recovery: MultiROM
--------------------------------------------------------------------------------------------------------------------------
Tablet: Nexus 7
ROM: SlimKat 5+
Kernel: LeanKernel
Recovery: MultiROM
--------------------------------------------------------------------------------------------------------------------------
Phone: Motorola Milestone A853 ROM: CyanogenMod 9.1.0d Recovery: Open Recovery MiniMod by -FuFu-
 
deltatux
Old
(Last edited by deltatux; 29th June 2014 at 11:05 PM.)
#7  
Senior Member
Thanks Meter 128
Posts: 572
Join Date: Apr 2011
Location: Toronto
Quote:
Originally Posted by Erovia View Post
If you entered that command, your device is hardbricked and the only thing you can do about is to send it to Asus/Google for RMA.
I doubt Google/ASUS will repair it and if they do, it'll likely cost you as much as a new tablet. I still stick to what I said and either get a new tablet or replace the motherboard yourself.

deltatux
Google Nexus 4 16 GB (E960 R11 304K)
Slim ROM 4.4.4 5.10 (KTU84P)
Slim Kernel 3.6 (3.4.92)

ASUS Nexus 7 16 GB 1st Gen
Slim ROM 4.4.4 5.10 (KTU84P)
M-Kernel a69 F2FS (3.1.10)
 
Gloftking
Old
#8  
Member - OP
Thanks Meter 0
Posts: 41
Join Date: Jun 2014
Default That is so annoying

I was trying to flash another bootloader called ("bootloader-grouper-4.23.img") but I think some error occurred in the command prompt and I am very surprised it actually let me do that unknowingly.

Is there another boot loader inside the nexus 7 that allows this procedure of swapping bootloaders to take place or is there any kind of hard reset button inside the nexus (I don't care what happens to my data on it)
 
Gloftking
Old
#9  
Member - OP
Thanks Meter 0
Posts: 41
Join Date: Jun 2014
Quote:
Originally Posted by deltatux View Post
If you erased the bootloader without flashing another one back in, you just bricked your device. The only course of action to save it is to do an nvflash but that would have required you to back up the nvflash blob before this incident. If all else fails, your tablet's a dud.

I would recommend either replacing your entire tablet or buy a replacement board on eBay and replace the motherboard yourself and then it will run like new.

deltatux
how on earth are you meant to use the nvflash software and does it definitely require a blob file.
BTW I do seem to recall that I saw a "writing to bootloader message" in cmd before it became inoprable. does that mean there is any better chance of this thing being revived?
 
deltatux
Old
#10  
Senior Member
Thanks Meter 128
Posts: 572
Join Date: Apr 2011
Location: Toronto
Quote:
Originally Posted by Gloftking View Post
how on earth are you meant to use the nvflash software and does it definitely require a blob file.
BTW I do seem to recall that I saw a "writing to bootloader message" in cmd before it became inoprable. does that mean there is any better chance of this thing being revived?
nvflash is meant to be a debugging software as an absolute last resort to restore a Tegra based device. More on nvflash here:
http://forum.xda-developers.com/wiki/Nvflash

The blobs are tied to your device because nvflash works pretty much at hardware level, so without your own blobs, it's nearly impossible to recover. Here's the procedure to extract the blob before brick: http://www.xda-developers.com/androi...with-flatline/

As for "writing to bootloader", if you can't access the bootloader now, it may be because you flashed the wrong bootloader (likely from the 3G variant of the Nexus 7 instead of WiFi-only or vice versa). Unless you can somehow gain access to fastboot, you'll need to recover via nvflash.

Without the blobs backed up, you'll probably be better off replacing the Nexus 7 motherboard with a working OS and all.

deltatux
Google Nexus 4 16 GB (E960 R11 304K)
Slim ROM 4.4.4 5.10 (KTU84P)
Slim Kernel 3.6 (3.4.92)

ASUS Nexus 7 16 GB 1st Gen
Slim ROM 4.4.4 5.10 (KTU84P)
M-Kernel a69 F2FS (3.1.10)

Thread Tools
Display Modes