Nexus 7 2013 Stuck at "Google" screen - I've fucked up edition
8 replies, posted
[t]http://puu.sh/5YoTt.jpg[/t]
So yaddahyaddah, unlocked the boot loader and directly after installed a custom recovery, which got me to continue through the Google screen, but got me to a black screen. Tried TeamWin recovery, stuck on Google screen. Tried Google provided stock images, no change.
Flash stock image two times, do a full wipe in twrp, give it at least twenty minutes to boot.
[QUOTE=mobrockers;43307185]Flash stock image two times, do a full wipe in twrp, give it at least twenty minutes to boot.[/QUOTE]
I cannot wipe in recovery, but I'll flash the stock images twice and do wipes inside fastboot.
[QUOTE=WhiteHusky;43307476]I cannot wipe in recovery, but I'll flash the stock images twice and do wipes inside fastboot.[/QUOTE]
Why can't you wipe in recovery? It's in advanced I think in twrp.
Fastboot is no longer functional. (Halts when plugged in and the computer disconnects and reconnects repeatedly. Last error was something of Too Many Links.)
Recovery is still unbootable. (No option starts it.)
System is unbootable. (Doesn't even get the boot animation. Just blackness.)
[editline]25th December 2013[/editline]
Fastboot is dysfunctional. (Only works at times before kicking out. Errors of Too Many Links are generated.)
[editline]25th December 2013[/editline]
Fastboot is functional.
Done a factory flash-all.
Still stuck on Google screen. Setting timer.
Don't have much experience with nexus bricks, but I assume they're about as difficult to brick as samsung devices. Looks like you might need one of those usb thingies that force a device into download mode (or however it's called on nexus devices).
[QUOTE=mobrockers;43307838]Don't have much experience with nexus bricks, but I assume they're about as difficult to brick as samsung devices. Looks like you might need one of those usb thingies that force a device into download mode (or however it's called on nexus devices).[/QUOTE]
I've gotten back to the more reassuring stuck on that Google screen. Right now I'm just waiting.
Here's the log output.
[code]
...
(bootloader) The bootloader is already unlocked!
OKAY [ 0.004s]
finished. total time: 0.004s
erasing 'boot'...
OKAY [ 0.121s]
finished. total time: 0.123s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.308s]
finished. total time: 0.310s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.448s]
finished. total time: 0.450s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 14.570s]
finished. total time: 14.572s
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
OKAY [ 1.282s]
finished. total time: 1.417s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
sending 'radio' (16384 KB)...
OKAY [ 0.521s]
writing 'radio'...
OKAY [ 0.727s]
finished. total time: 1.252s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
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........: 05e529d5
--------------------------------------------
checking product...
FAILED
Device product is 'flo'.
Update requires 'tilapia'.
finished. total time: 0.038s
Press any key to exit...
[/code]
I have no experience with fastboot, but it says it failed so are you sure your image is correct? Where did you get it from and did you md5 check it?
[editline]25th December 2013[/editline]
Looks like you downloaded the wrong device image.
You downloaded 'tilapia'.
Your product is 'flo'.
[editline]25th December 2013[/editline]
[url]https://dl.google.com/dl/android/aosp/razor-jss15q-factory-4f77b811.tgz[/url]
This is your latest device image.
[editline]25th December 2013[/editline]
Woops, I mean this one:
[url]https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz[/url]
Yeah, I just noticed too. When I clicked for my version, I mistakenly thought the page didn't properly scroll and I selected one for the mobile version.
Sorry, you need to Log In to post a reply to this thread.