Develop Bugs

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

Softbricked(?) GNex, cwm restarts etc.

My phone stuck while using so as usual I pulled out the battery and it was his end. From then on bootanimation glitched and the phone restarted all over again. Sth like a bootloop but with complete phone restart. Then I tried to full wipe but with no luck, recovery hung and rebooted the phone. Even now restoring/zip installing etc suddenly restarts the phone. I also tried to flash new recovery/rom via fastboot as well as via Nexus Root Toolkit but everytime I got 'too many links error'
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2308 KB)...
OKAY [ 0.227s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.404s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.005s
sending 'radio' (12288 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.005s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.004s
archive does not contain 'boot.sig'
error: out of memory
Click to expand...
Click to collapse
I used two different cables that I use for every flashing so far, and different usb slots... I have no idea what else I can do.

Sth has changed, I tried to flash TWRP instead of CWM via fastboot and again, got 'too many links' error BUT it flashed the new recovery anyway . So now I have TWRP, managed to flash cm 10.2.1+gapps. I have a recovery log for sb to analyze. Could you check if my emmc is corrupted telling ftom this log?
i9250 recovery log http://pastebin.com/4Yx0ZwJK
Thanks
EDIT/
A second ago it booted to system in a normal way, then a sudden restart and the phone is stuck while boot animation, like a catch 22...

[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

[Q] Nexus 7 stuck on Google Logo! Confused

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?

How to unlock bootloader when OEM unlocking option is disabled

Hello,
I am asking here is there a way to unlock bootloader?
The situation is:
- the phone is in boot loop.
- the phone boots to download mode every time.
- cannot access to recovery mode from fastmode.
- cannot apply LG tot to refurbish in download mode. It now deads at 4% of the process.
- and the last, I didn't enable OEM unlocking when the phone was still functioning.
Adb, fastboot, I tried all the commands that I know so far, but no help.
I know that I have to enable OEM unlocking to be able to unlock bootloader. But again, I cannot boot in to do it.
So just hope that some experts might know a way.

You don't have a possibility to unlock it!
The only way is by settings from working phone.
S C:\Android\platform-tools> .\fastboot.exe devices
0171046759b8474f fastboot
PS C:\Android\platform-tools> fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.020s]
finished. total time: 0.021s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
OKAY [ 9.244s]
finished. total time: 9.247s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.008s
PS C:\Android\platform-tools> fastboot flash boot boot-fixed.img
target reported max download size of 536870912 bytes
sending 'boot' (11797 KB)...
OKAY [ 0.321s]
writing 'boot'...
OKAY [ 0.137s]
finished. total time: 0.461s
PS C:\Android\platform-tools> fastboot flash recovery recovery-fixed.img
target reported max download size of 536870912 bytes
sending 'recovery' (17437 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.209s]
finished. total time: 0.671s
PS C:\Android\platform-tools>

Sigh,
So no more hope.
Thank you ^_^

Try the battery discharge trick described by sd_cb on the page Fix-a-Brick: Fighting the Nexus 5X Bootloop:
"One trick I learned for my bootlooped 5X is that first you let the phone completely drain of battery (boot into recovery and let it sit). Then, plug in the phone and boot up. I would get ~1 minute in the phone before it would reset. What did this do for me? It allowed me to recover my 2 factor codes that I was stupid enough not to print or save to begin with. Lesson learned"