Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Error: Device Unauthorized. Please Check The Confirmation Dialog On Your Device.


  • Please log in to reply
12 replies to this topic

#1 matti

matti
  • Members
  • 13 posts
  • Twitter:MattiLinnanvuor
  • Country:
    fi - Finland
  • Location:
    Helsinki
  • Device Model:
    GT-S5570
  • CM Version:
    7.2
  • Recovery Image:
    ClockworkMod

Posted 03 August 2013 - 06:59 AM

When I tried to push the ZIP file to International version, I got the following error:
error: device unauthorized. Please check the confirmation dialog on your device.
However, there was no confirmation dialog on my device.
I have inadvertently booted to Samsung's software first, so maybe the Samsung software overwrote ClockworkMod Recovery.
I also tried adb sideload but got a check error.
http://wiki.cyanogen...d_from_recovery

When I tried to enter PIN to log in to the Samsung software after installing ClockworkMod Recovery, I got rejection. Maybe it is not possible to log in to the Samsung software anymore because PIN handling is broken now.

Edited by matti, 03 August 2013 - 07:00 AM.


#2 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 03 August 2013 - 03:04 PM

So you don't provide much information about what was your initial setup, which method you used to flash the cwm, which version of cwm? Was this a new cm install or a nightly update? Please, clarify.

Are you using windows or Linux? Odin or Heimdall? Version? Self-compiled or binary?

Is your device GT-I9505?

Are you using windows or Linux? Odin or Heimdall? Version? Self-compiled or binary?

Is your device GT-I9505?

#3 matti

matti
  • Members
  • 13 posts
  • Twitter:MattiLinnanvuor
  • Country:
    fi - Finland
  • Location:
    Helsinki
  • Device Model:
    GT-S5570
  • CM Version:
    7.2
  • Recovery Image:
    ClockworkMod

Posted 03 August 2013 - 06:41 PM

I used the method described on the Wiki page http://wiki.cyanogen..._from_recovery.
I used Heimdall Suite 1.4RC2 binary on Windows Vista and recovery-clockwork-6.0.3.3-jfltexx.img. My device is GT-I9505. The problem seems to be that the device does not allow me to go to recovery mode. It flashes a message that it is going to recovery mode but then the screen goes all black and it reverts back to power-off/battery charging mode. My device could have such a hardware defect I guess. I have not been able to install CyanogenMod yet.

Edited by matti, 03 August 2013 - 06:46 PM.


#4 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 03 August 2013 - 08:45 PM

Hi,

Ok, thanks for the details. I had pretty much same starting point as you. I did the same things and noticed that the only way I could make Heimdall work properly was to compile it from source on Ubuntu 12.04 x64 Linux. No binary version, on Win or on Linux, worked ok for me. And as the poor Heimdall f*ed up the recovery flash, my recovery would not work.

First step would be to get a working flashing software. If you can't use Linux, maybe you could use Odin on Win and find a ClockWorkMod 6.0.3.3 as a tar.md5?
Another option is to make a virtual machine on your Vista and install Ubuntu there. Third would be to make Win Heimdall work ... careful with that, I could not do that. But then again my Win was a netbook XP :)

#5 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 03 August 2013 - 09:11 PM

Shift, just remembered one thing: in my I9505, the recovery partition is called RECOVERY. You should use print-pit command in Heimdall to get your partition table and check the recovery partition name for your device.

This affects the Heimdall flash command, you should use --RECOVERY.

Could you first try with your Win Heimdall do

heimdall print-pit --file partitions.txt --verbose --no-reboot

And post the console output here along with file partitions.txt.

#6 matti

matti
  • Members
  • 13 posts
  • Twitter:MattiLinnanvuor
  • Country:
    fi - Finland
  • Location:
    Helsinki
  • Device Model:
    GT-S5570
  • CM Version:
    7.2
  • Recovery Image:
    ClockworkMod

Posted 04 August 2013 - 10:49 AM

$ ./heimdall print-pit --verbose --no-reboot
Heimdall v1.4 RC2

Copyright © 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
  Manufacturer: "Sasmsung"
   Product: "MSM8960"

    length: 18
  device class: 2
   S/N: 0
   VID:PID: 04E8:685D
bcdDevice: 0100
   iMan:iProd:iSer: 1:2:0
  nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
   endpoint[0].address: 82
   max packet size: 0010
  polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
   endpoint[0].address: 81
   max packet size: 0200
  polling interval: 00
   endpoint[1].address: 01
   max packet size: 0200
  polling interval: 00
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
ERROR: libusb error -7 whilst receiving packet.
Protocol is not initialised.

Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.

Beginning session...

This device may take up to 2 minutes to respond.
Please be patient!

Session begun.

Downloading device's PIT file...
PIT file download successful.

Entry Count: 33
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 13881
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 25544
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
FOTA Filename:


--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 33736
Partition Block Count: 105528
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MDM
Flash Filename: modem.bin
FOTA Filename:


--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139264
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: sbl1.mbn
FOTA Filename:


--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139520
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl2.mbn
FOTA Filename:


--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 140032
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL3
Flash Filename: sbl3.mbn
FOTA Filename:


--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 141056
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:


--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 145152
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash Filename: rpm.mbn
FOTA Filename:


--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash Filename: tz.mbn
FOTA Filename:


--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 147200
Partition Block Count: 33792
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash Filename:
FOTA Filename:


--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180992
Partition Block Count: 27904
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
FOTA Filename:


--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 208896
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
FOTA Filename:


--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 215040
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
FOTA Filename:


--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 221184
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS1
Flash Filename: m9kefs1.bin
FOTA Filename:


--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 222744
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS2
Flash Filename: m9kefs2.bin
FOTA Filename:


--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 224304
Partition Block Count: 1560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: M9KEFS3
Flash Filename: m9kefs3.bin
FOTA Filename:


--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 225864
Partition Block Count: 5652480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename:


--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5878344
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename:
FOTA Filename:


--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5894728
Partition Block Count: 4239360
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename:


--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10134088
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:


--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:


--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10166856
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:


--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10187336
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename:
FOTA Filename:


--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10207816
Partition Block Count: 12288
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename:
FOTA Filename:


--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10220104
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename:
FOTA Filename:


--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10226248
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename:
FOTA Filename:


--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 26
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10226264
Partition Block Count: 18432
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
FOTA Filename:


--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 27
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 10244696
Partition Block Count: 1024000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img.ext4
FOTA Filename:


--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 28
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 11268696
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img.ext4
FOTA Filename:


--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 29
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 11309656
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename: remained


--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:


--- Entry #30 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: MSM8960.pit
FOTA Filename:


--- Entry #31 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:


--- Entry #32 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 30777311
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:

Ending session...
Releasing device interface...

#7 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 04 August 2013 - 11:04 AM

Ok, now we can determine that your Heimdall is working, at least the print-pit worked. Did you get a file named partitions.txt into Win?

Next, you could re-try the flashing the recovery using the same setup as above and in the install guide (your link).

The flashing command should be

heimdall flash --RECOVERY recovery-clockwork-6.0.3.3-jfltexx.img --no-reboot

and it must be run as the admin user, at least on Linux.

Again, try that (per instructions in the install guide) and the above cmd (as admin) for the flash command. Then send the console log again for Heimdall.

Make sure that you enter the download mode properly, pass the disclaimer. Wait until the flash finishes, should not be too long.

Make sure you have enough battery remaining, that will be the limiting factor. Can you still get to a state where the battery is charging? If so, maybe stop for a while to let it charge full.

Reboot after the flash is done.

#8 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 04 August 2013 - 11:24 AM

One more, if you get into trouble with the battery running out or flashing not working, I live in the city next to yours. So, charging service and flashing available, if needed. Naturally, no guarantees for bricking etc.

#9 matti

matti
  • Members
  • 13 posts
  • Twitter:MattiLinnanvuor
  • Country:
    fi - Finland
  • Location:
    Helsinki
  • Device Model:
    GT-S5570
  • CM Version:
    7.2
  • Recovery Image:
    ClockworkMod

Posted 04 August 2013 - 11:53 AM

$ ./heimdall print-pit --file partitions.txt --verbose --no-reboot
ERROR: Failed to open file "partitions.txt"

#10 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 04 August 2013 - 12:08 PM

What was that? Oh, the earlier command without the file name worked ok but --file version fails? Ok, we got the RECOVERY name confirmed already.

So what's the console output when you do the flash command from my post? Including, of course all the steps from install guide.

Shift, looks like I printed my PIT also not using the --file :

heimdall print-pit --verbose --no-reboot | tee partitions.txt

Nevermind, I don't think that has any weight on the issue. Just go ahead with flashing with --RECOVERY

#11 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 04 August 2013 - 12:21 PM

I just tweeted you.

#12 matti

matti
  • Members
  • 13 posts
  • Twitter:MattiLinnanvuor
  • Country:
    fi - Finland
  • Location:
    Helsinki
  • Device Model:
    GT-S5570
  • CM Version:
    7.2
  • Recovery Image:
    ClockworkMod

Posted 05 August 2013 - 07:20 AM

The Recovery application that I have is not able to mount /sdcard and therefore it is not possible to flash CyanogenMod. I am not sure which Recovery application I have: ClockworkMod or Samsung's. I have tried to flash ClockworkMod but I have accidentally booted to Samsung's ROM and it may have overwritten ClockworkMod Recovery according to the Wiki page. I seems too difficult to boot into Recovery.

#13 tapiov

tapiov
  • Donators
  • 211 posts
  • Twitter:tapiov
  • Country:
    fi - Finland
  • Location:
    Espoo, Finland
  • Device Model:
    GT-I9505
  • CM Version:
    none
  • Recovery Image:
    Stock

Posted 05 August 2013 - 08:24 AM

Well, you should test which recovery you have by booting to it. If it says ClockWorkMod or CWM, it is CWM http://cdn.theunlock...overy-touch.jpg as example.

If it says anything like <3e> on the top like http://realitypod.co...sung-galaxy.jpg it is Samsung and it is not suitable for flashing cm.