• Announcements

    • PsychoI3oy

      Unsupported devices & future versions   09/03/16

      Unsupported devices posts outside the Device requests forum will be deleted without comment. Posts asking about/for future versions of CM will be locked and/or deleted.   We don't have a crystal ball; we don't know if someone will make CM $version for your deivce or if CM $version+1 will be made for your supported device.
Sign in to follow this  
Followers 0
matti

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

13 posts in this topic

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

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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 :)

Share this post


Link to post
Share on other sites

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[/CODE]

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

Share this post


Link to post
Share on other sites

$ ./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...

Share this post


Link to post
Share on other sites

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[/CODE]

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

ERROR: Failed to open file "partitions.txt"

Share this post


Link to post
Share on other sites

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[/CODE]

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Well, you should test which recovery you have by booting to it. If it says ClockWorkMod or CWM, it is CWM http://cdn.theunlockr.com/wp-content/uploads/2012/09/clockworkmod-recovery-touch.jpg as example.

If it says anything like <3e> on the top like http://realitypod.com/wp-content/uploads/2011/03/recovery-mode-samsung-galaxy.jpg it is Samsung and it is not suitable for flashing cm.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0