[Q] Nexus 7 stuck on Google Logo! Confused - Nexus 7 (2013) Q&A

I realize this has been discussed ad nauseam and after searching through all the posts on it I am a little confused about what my options are. My Nexus 7 2013 mobile is stuck on the Google logo. Here's what I have done..
First, I tried to simply wipe the cache partition to no avail.
Second, using the WugFresh Nexus toolkit I tried to unroot and flash stock to no avail. It would get to the point of flashing I would get remote failure error messages when trying to flash the radio etc,
Basically, all I have at this point, is the Google screen and access to fastboot and it's options and the Nexus is recognized by my computer through fastboot.
What are my options now?
Should I relock the bootloader and request Google repair it?
Or should I try to flash 4.4.4 manually through fastboot without a toolkit. If so, can you refresh my memory on how to do this?
I would appreciate any help you could provide. Thanks!

Try flashing 4.4.4 manually in fastboot. There are instructions on the page where you download the firmware. Did you flash 5.0 on a LTE model?

I did not flash 5.0. It froze during usage and I restarted it and then it suddenly would not boot past the Google logo. I did nothing to it.
I downloaded the factory image for 4.4.4 and followed instructions and ran the flash-all.bat and here is what the command prompt returns:
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.709s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 3.034s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 174.608s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
Is it time to relock the bootloader and hope Google will repair it?

Related

GNex factory reset apparently doesn't write anything and I'm not able to update.

Hello, my gnex (maguro) started rebooting frequently (like every 30 seconds). I hope is not an hardware fault and now I'm trying to restore a factory image so I can rule out any custom rom-derived problems.
I'm trying to flash yakju-jwr66y the problem is when I flash the bootloader and radio everyithing is ok but when it reboots to install the rest of the system the bootloader and radio are still not updated!
If I try to update manually the bootloader this is what I get:
Code:
[email protected]:~/Scaricati/yakju-jwr66y (2)$ fastboot flash bootloader bootloader-maguro-primemd04.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
OKAY [ 7.971s]
finished. total time: 8.279s
[email protected]:~/Scaricati/yakju-jwr66y (2)$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
But the bootloader version is still the primemd03! The same goes with the radio.
What is going on?
Probably fried EMMC. Try to lock the bootloader. If its still unlocked your EMMC is fried..
Sent from my Galaxy Nexus using xda app-developers app
Try to fastboot flash system and userdata separately

[Q] Is my tablet finally dead?

It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
What have you been trying to flash as "bootloader" ? If you want to flash a recovery you should do
fastboot flash recovery recovery-destination-here-or-name-if-you-are-aleady-in-the-same-file.img
But I'd suggest you downloading the factory image from Google's page and doing a fresh complete install
PS don't use toolkits they are much more complicated and can mess things up
billownz said:
It think my faithful friend died. Last night my n7 ran out of battery and after charging would only boot to the Google screen. It does work in fastboot but the custom recovery hangs at splash.
Ive had absolutely no luck flashing anything....
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.622s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
Rinse and repeat. I have even resorted to trying skip's toolkit (with similar results)
Is it done? Should I start with the funeral arrangements?
Click to expand...
Click to collapse
I had the very same issue occur to me 18 hours out of the box on a 2013 refurb. Had to RMA to Asus. It was a hardware issue. On the repair slip they said they had to replace the board.
You might talk to them and see what a repair out of warranty would cost. There is a member here who works for Asus Customer Service, who perhaps might be able to give you some guidance. I cannot find his name at the moment, but will update with it when I do.
Update:
His name is @[email protected] and he posted here with his info: http://forum.xda-developers.com/nexus-7/help/asus-answers-t2846136
Happened the same 2me with my first nexus... I was on cm, two random reboots and that's it, couldn't flash anything, luckily i managed to relock the bootloader and erase the recovery partition (twrp)... Another user couldn't relock the bootloader so he ended up buying a motherboard on ebay

Saving Data from locked, bricked device

Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...

Bricked -unable to use Wug tool kit to revive it

i can only get to fastboot mode. My nexus Bootloader version - FLO- 04.04, and it's unlocked. I've tried to use Wug tool kit but got stuck at "erasing cache". See log below. I've tried different cables and different USB ports. Any tips or guidance is greatly appreciate. Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.742s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
sending 'boot' (7448 KB)...
OKAY [ 0.245s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.166s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
erasing 'cache'...
i have the same problem
the nand flash is broken, change your mainboard and you will be happy again
i will never buy a asus device

[Bricked] Samsung Galaxy Nexus GT-I9250.

Hi XDA!
I'm trying to unbrick my old Galaxy Nexus GT-i9250 without success.
Already tried several ways, "ODIN, FastBoot/NexusToolKit", with multiple ROMs from 4.0.1 to 4.4.4. The device powers on and stays on Google screen for hours then it turn off automatically.
When I write a new ROM it goes into a boot-loop, then again freezes on Google screen.
Can anyone help me to unbrick this device? I'm losing hope..
Trying to use TWRP with no luck, still getting default "factory" Recovery Mode. It seems that my device is not getting writted by fastboot/ODIN? (tried several TWRP images, from twrp-2.1.0-maguro-signed.zip and up)
D:\temp\cell\platform-tools-v16>fastboot devices
<REDACTED> fastboot
D:\temp\cell\platform-tools-v16>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.017s
D:\temp\cell\platform-tools-v16>fastboot flash recovery twrp.img
sending 'recovery' (5670 KB)...
OKAY [ 0.634s]
writing 'recovery'...
OKAY [ 4.640s]
finished. total time: 5.284s
Please help?

Categories

Resources