Root Recovery Flashing Issues

[Yathushan]

Hi everyone,

I am currently having issues trying to flash cwm recovery to my nexus 7. I followed this guide http://androidforums.com/android-system-mods-scripts-hacks/706533-guide-how-flash-nexus-factory-image-manually.html I get up to step 9 and then I get:
[HIGH]FAILED (command write failed (Invalid Argument))[/HIGH]

I am unsure about how to proceed from here. Any advice would be much appreciated.

 

[El Presidente]

That's a factory image (it will reset the tablet back to as it was when it came from the factory). I take it that's not what you want to do?

Easiest way to get CWM or TWRP (a better recovery IMO) on there is to use Wugs Toolkit: http://forum.xda-developers.com/showthread.php?t=1766475

That should make things a lot simpler

 

[Yathushan]

I tried to use the Wugs toolkit initially and was able to unlock the device but it wasn't able to root it though. So I thought if I flashed the factory image to start again it would work. But I was unable to flash the factory image and now I am stuck at the bootloader.

 

[jhawkkw]

If you completed step 8, then your device has no kernel or os to boot into. So we will have to flash the factory image to get back up and running and then we can proceed to the rooting procedure. What is the exact command you are entering that is causing that error?

 

[Yathushan]

It was that I was unable to flash anything to device:
[HIGH]fastboot flash recovery
fastboot flash bootloader[/HIGH]
But now I am unable to detect my devices when I type:
[HIGH]fastboot devices[/HIGH]

Sorry to be a further pain. Does anyone have any ideas on how I could sort these problems out?

 

[jhawkkw]

after the fastboot flash recovery or bootloader commands, you need to type the name of the file that was extracted from that .tzg that you downloaded. For example:

fastboot flash recovery twrp.img

Out of curiosity, your device state list it as unlocked? If it says locked, then that's the other reason why it may not let you flash.

As for it not reading your device, try unplugging it from the computer and then replugging it back in and try the command again and see if it comes up.

 

[Yathushan]

Sorry about that I put the name of the file into the command and I executed it from the correct directory and the Lock state is currently noted as unlocked.

I have just to do that and when I type the command in, it just returns blank with no information. Do you have any other idea on how I could do it?

 

[jhawkkw]

Alright, though it's not optimal, step 10 & 11 isn't necessary to get this back up and running as long as your didn't erase your bootloader. try going right to step 11, the update command. that will flash the kernel, recovery, and os back to the device which should allow it to boot back up.

If fastboot devices is still blank, then try a different usb port on your computer and then check the device manager to see if it reads an android bootloader interface.

 

[Yathushan]

So I type:
[HIGH]
fastboot -w update image-nakasi-jdq39.zip
[/HIGH]
And it returns:
[HIGH]
archive does not contain 'boot.sig.'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
[/HIGH]

Then it returns back with no affect to the device.

 

[jhawkkw]

So I type:
[HIGH]
fastboot -w update image-nakasi-jdq39.zip
[/HIGH]
And it returns:
[HIGH]
archive does not contain 'boot.sig.'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
[/HIGH]

Then it returns back with no affect to the device.

You might have a bad download of the factory image, yet re-downloading it.

 

[Yathushan]

I am still getting the same messages.

 

[jhawkkw]

Alright, turn the device off and then reboot into the bootloader, just to make sure it didn't lock up.

 

[Yathushan]

This time it gets further and shows this:
[HIGH]
archive does not contain 'boot.sig.'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
-----------------------------------------------------
Bootloader Version...:4.18
Baseband Version....: N/A
Serial Number.........: 015d2994800c161e
-----------------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.019s]
sending 'boot' (4944 KB)...
FAILED (data transfer failure (Unknown error))
Finished. Total time: 0.173s
[/HIGH]

So it looks like a transfer error showing. Also I'm not sure if this is relevant but the signing state is not defined.

 

[jhawkkw]

Indeed, by any chance is the usb port you're using an old usb 1.0 or newer 3.0 port?

 

[Yathushan]

USB 3.0 port. Why? Does it make a huge difference?

 

[jhawkkw]

USB 3.0 port. Why? Does it make a huge difference?

Believe it or not it does. The fastboot drivers are not coded very well for non 2.0 ports. Do you have any 2.0 ports?

 

[Yathushan]

That helped so much. It must have been the non USB 2.0 port which caused an issue pushing any images across. BTW do you think usb 3.0 will get support?

 

[jhawkkw]

That helped so much. It must have been the non USB 2.0 port which caused an issue pushing any images across. BTW do you think usb 3.0 will get support?

I expect google top eventually update the drivers once 3.0 becomes more standard. Unfortunately I don't know when that will be. It's long overdue in my opinion though.