1. Are you ready for the Galaxy S20? Here is everything we know so far!

Recovery Flashing Issues

Discussion in 'Android Devices' started by Yathushan, Jul 11, 2013.

  1. Yathushan

    Yathushan Well-Known Member
    Thread Starter




    1. Download the Forums for Android™ app!


      Download

       
  2. El Presidente

    El Presidente Beware The Milky Pirate!
    VIP Member

    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 :)
     
  3. Yathushan

    Yathushan Well-Known Member
    Thread Starter

    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.
     
  4. jhawkkw

    jhawkkw Chinchillin'

    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?
     
    El Presidente likes this.
  5. Yathushan

    Yathushan Well-Known Member
    Thread Starter

    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?
     
  6. jhawkkw

    jhawkkw Chinchillin'

    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.
     
  7. Yathushan

    Yathushan Well-Known Member
    Thread Starter

    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?
     
  8. jhawkkw

    jhawkkw Chinchillin'

    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.
     
  9. Yathushan

    Yathushan Well-Known Member
    Thread Starter

    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.
     
  10. jhawkkw

    jhawkkw Chinchillin'

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

    Yathushan Well-Known Member
    Thread Starter

    I am still getting the same messages.
     
  12. jhawkkw

    jhawkkw Chinchillin'

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

    Yathushan Well-Known Member
    Thread Starter

    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.
     
  14. jhawkkw

    jhawkkw Chinchillin'

    Indeed, by any chance is the usb port you're using an old usb 1.0 or newer 3.0 port?
     
    El Presidente likes this.
  15. Yathushan

    Yathushan Well-Known Member
    Thread Starter

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

    jhawkkw Chinchillin'

    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 likes this.
  17. Yathushan

    Yathushan Well-Known Member
    Thread Starter

    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?
     
  18. jhawkkw

    jhawkkw Chinchillin'

    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.
     
Loading...

Share This Page

Loading...