I am updating the OS of my Samsung Galaxy tab p1000 (i.e. 2.2) to 2.3.6 using adb.

I am using the steps below:

  1. Check whether device is connected or not using ADB.

    C:\Users\PC>adb devices 
    List of devices attached S6802084d305f device
  2. Push 2.3.6 OS (i.e. update.zip) OS to SD card.

    C:\Users\PC>adb push C:\Android\update.zip /sdcard/update.zip   
    2765 KB/s (2260360 bytes in 0.798s)
  3. Go to recovery mode

    C:\Users\PC>adb reboot recovery

enter image description here

After selecting Apply sdcard: update.zip, I'm getting the screen below. But it shows it for long time. There is no response from device. We waited for 5 hours. No response.

enter image description here

How can I flash my Samsung Galaxy tab? Let me know if I am missing a step.


2 Answers 2


These are the steps to install/update a custom ROM from stock:

  1. Install a custom recovery (Clockworkmod for example).
  2. Copy the ROM zip to the phone sdcard (you can do this via adb).
  3. Reboot in recovery (it will load the custom recovery).
  4. Use the option to install zip from sdcard to install/update the ROM.
  • Isn't that exactly what the OP did? If not, what part did he do wrong? I'm in the same situation and I haven't understood how your instructions differ from what I already did. Aug 15, 2013 at 21:37
  • Ah! Perhaps he didn't do step 1! :-) I did do step 1, but perhaps I didn't do it right. Aug 15, 2013 at 21:38

There is a log of "apply update.zip" function on cache partition. You can check what went wrong there.

But it would come down to three possibilities:
the update.zip is broken,
not compatible,
or signature failure

Looks like you have custom recovery, so the signature failure shouldn't be your case.
It would happen if you'll try to do "apply update.zip" of custom update.zip using official recovery.

Unless you really need to use update.zip for updating, I would strongly advise against this method.
The recommended way is to flash full firmware with Odin. guide1, guide2

Officially the update.zip method is used by OTA updates. While the device is actively supported, it will download update.zip files in background.
These official update.zip files are signed and applicable only on version of FW, which they are meant for.
The update.zip file which you have is probably made by a MODder.
Although the update.zip file could contain all files and partitions of the target firmware version, this is seldom the case in custom update.zip files. Because of this, you might get different results applying custom update.zip on a devices with different firmware version.
It might work as intended, or might start freezing, or even fail to complete the update in case there is a command referring files or folders which don't exist or are different on your original firmware.
In many cases, not all partitions get updated and the part of firmware in SYSTEM partition is not compatible with bootloader present in another partition.
This might result in boot loops, very long boots, freezing, or random reboots.

If you don't specifically require version 2.3.6, you should consider using alternative builds, as the cyanogenmod for p1000 which is currently in its KitKat version v4.4.

KitKat plays very nice with devices with smaller memory, and you'll also be able to use Chrome and other Apps, which are not backward compatible. Overall, it's like having a new device.
Bear in mind, that the cyanogenmod is also distributed using update.zip files, the name of zip is different but it's still "update.zip type" file, so it's also important to apply the update from supported firmware version. I did the update from P1000XWJU6

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .