[gs3 - I9300] pit partition error

gibus61 commented 10 years ago

Hi, I just would like to flash my galaxy S3 16GB with your awesome tool heimdall :)

I get an error while downloading .pit file from my device. My gs3 is well recognized by heimdall but verbose output give me this result :

Heimdall v1.4.0

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

length: 18 device class: 2 S/N: 0 VID:PID: 04E8:685D bcdDevice: 021B 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: 83 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: 02 max packet size: 0200 polling interval: 00 Claiming interface... Setting up interface... ERROR: Setting up interface failed! Releasing device interface...

What do you think about this error ? (No pit partition file is created by heimdall on my pc)

Thanks for your help.

Benjamin-Dobell commented 10 years ago

You didn't specify your operating system, but this looks like a driver issue.

On Linux, this would be caused by insufficient permissions. Heimdall comes with a udev rule which makes the USB device accessible by regular users. If you're getting this error then perhaps you need to reboot, alternatively you can run Heimdall with super-user permissions.

On OS X, Heimdall installs a codeless kext which makes the USB device accessible from user-land. However, if you've previously installed Kies on your Mac, the Kies driver interferes with Heimdall's. You can remove the Kies driver with:

sudo rm -rf /System/Library/Extensions/ssuddrv.kext/

and then reboot your system.

gibus61 commented 10 years ago

I currently run on ubuntu 12.04 LTS 64bits (live usb version) and I have launched heimdall after a "sudo su" command with : heimdall-frontend &

Am I forced to reboot my linux while installing heimdall ?

Benjamin-Dobell commented 10 years ago

Actually, I thought I included a post-install script in the Linux packages that automatically restarted the udev system, so super-user shouldn't be required. Perhaps I removed it...

Anyway, you can restart the udev system manually (without rebooting) by executing:

sudo service udev restart

gibus61 commented 10 years ago

root@ubuntu:/home/ubuntu/Desktop/gs3# service udev restart udev stop/waiting udev start/running, process 5228

so, now heimdall gives me something like that : Heimdall v1.4.0

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: "SAMSUNG" Product: "Gadget Serial"

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

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: 83 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: 02 max packet size: 0200 polling interval: 00 Claiming interface... Attempt failed. Detaching driver... Claiming interface again... Setting up interface...

Initialising protocol... Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond. Please be patient!

Session begun.

Downloading device's PIT file... ERROR: Failed to unpack received packet. ERROR: Failed to receive PIT file size! ERROR: Failed to download PIT file! Ending session... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. ERROR: Failed to send end session packet! Releasing device interface... Re-attaching kernel driver...

My phone is well detected.

Seems to be worse no ?

Benjamin-Dobell commented 10 years ago

Hmm, this is similar to another problem that started occurring recently when Samsung released updated secondary bootloaders for several newer Samsung devices. I've not heard about it occurring with an SGS3 though.

What model is your phone (GT-I9300 etc.)?

Did you update your firmware recently?

Firstly, I'd recommend just detaching the device, reattaching it, rebooting into download mode, and repeating the procedure in order to make sure the results are deterministic.

If you do get the same error then you could try compile the latest commit on the master branch and try again; as I've made a few changes recently in this area.

gibus61 commented 10 years ago

I did not update my phone since a long time ago. I tried to stop heimdall, disconnect my phone, start heimdall, connect my phone. Then phone is always detected by heimdall and the result is the same (report below while trying to download pit file from gs3).

Heimdall v1.4.0

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: "SAMSUNG" Product: "Gadget Serial"

        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

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: 83 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: 02 max packet size: 0200 polling interval: 00 Claiming interface... Attempt failed. Detaching driver... Claiming interface again... Setting up interface...

Initialising protocol... Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond. Please be patient!

Session begun.

Downloading device's PIT file... ERROR: Failed to unpack received packet. ERROR: Failed to receive PIT file size! ERROR: Failed to download PIT file! Ending session... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. Retrying... ERROR: libusb error -7 whilst sending packet. ERROR: Failed to send end session packet! Releasing device interface...

Re-attaching kernel driver...

This can give you more details on my phone : GALAXY S3 BLEU 16GO (SGH-GALAXY-S-III) Dimensions (h/l/e) : 136.6 x 70.6 x 8.6 mm Poids : 133 g Batterie : 2100 mAh Ecran : Ecran super Amoled HD 4.8 pouces 16 M° de couleurs (1280x720) Couleur : Bleu (Pebble Blue) Communication réseau Catégorie : Quadri -bande Gprs : Class 12 (4+1/3+2/2+3/1+4 slots), 32 - 48 kbps Connexion pc : USB & Bluetooth (Samsung Kies) Edge : Class 12 HSDPA (3G+) : Oui GPS intégré : Oui Connectivité Connexion Bluetooth : 4.0 NFC : Oui DLNA : Oui Wi-fi : Oui, Wifi direct Mémoire Mémoire interne : 16 Go Multimédia Lecteur mp3 : Oui Radio : Oui avec RDS Agenda : Oui Débit d'Absorption spécifique (DAS) : 0,342 W/kg Type de carte SIM : MicroSIM Fonction Photo : 8 Mégapixels, Autofocus, détection des visages Fonction Video : HD 1080 (30 images/s) Flash : Flash LED Camera frontale : 1.9 Mégapixels - 720p Bureau Processeur : Samsung Quadri-coeur Exynos 4412 à 1.4 Ghz

In december 2012, I have rooted my phone with : CF-Auto-Root-m0-m0xx-gti9300.tar.md5 (cache.img and recovery.img). --> My phone worked fine until now !

Benjamin-Dobell commented 10 years ago

Could you please boot the phone up and tell me the model:

Settings -> More -> Model Number

If your phone is stuck on a weird screen asking you to connect to your PC and won't boot, then boot into download mode and execute:

heimdall close-pc-screen

The same can be done from the Utilities tab in Heimdall Frontend.

gibus61 commented 10 years ago

My phone doesn't boot further than "Samsung GALAXY S III GT-I9300" step. It seems blocked at this screen

example : http://www.google.fr/imgres?imgurl=http://forums.androidcentral.com/attachments/android-4-1-4-2-4-3-jelly-bean/104426d1392223972t-galaxy-s3-frozen-samsung-start-screen-after-software-update-galaxy-siii-boot-640x480.jpg&imgrefurl=http://forums.androidcentral.com/android-4-1-4-2-4-3-jelly-bean/332286-galaxy-s3-frozen-samsung-start-screen-after-software-update.html&h=480&w=640&tbnid=LfqSaEgX2eYvYM:&zoom=1&tbnh=90&tbnw=120&usg=__d0ByhKzdx4LdVSk26J5Y_ggo7jI=&docid=zWjhGZyLiIg5cM&client=ubuntu&sa=X&ei=oAnBU_D_D-SO0AXH0oHIAQ&ved=0CD0Q9QEwAg&dur=2111

I don't know how to proceed ! Phone is no more under guarantee ! Hope something is still possible ?

Benjamin-Dobell commented 10 years ago

@gibus61 Was your phone already doing that?

Because as long as you were only trying to Print PIT, then Heimdall definitely didn't write any data to your phone.

I'd be inclined to think some data on the phone is corrupt. Try boot into recovery and wipe the cache partition. If that doesn't work, then you might need to factory reset instead (which means you'll lose your messages, apps etc.)

I don't know what recovery you've got installed on your phone, but if you're using a custom recovery like ClockworkMod, then as a last resort you can download any update recovery firmware (like Cyanogenmod - http://wiki.cyanogenmod.org/w/Install_CM_for_i9300#Installing_CyanogenMod_from_recovery) onto an SD card (or possibly over USB mass storage if your recovery supports it) and flash from recovery.

gibus61 commented 10 years ago

going to see cyanogen_from_recovery that tomorrow morning.

Erikmu commented 10 years ago

i've got same kind of errors on my s3, i have an L710 , T999 & i747 same errors. :c

gibus61 commented 10 years ago

Hi, For me Impossible to turn on my phone in recovery mode (only download mode functions). When i try to press "vol+ / home / sleep button", nothing happen and i see the GS3 screen as mentionned above.

I have put philz_recovery.zip on a sd card but nothing happened either.

gibus61 commented 10 years ago

Unfortunately, it seems to be an hardware problem and my 1-year warrantly (rue du commerce website) is now ended (unless samsung provides a 2-years warrantly).

http://www.galaxynote.fr/telephone-inutilisable-solutions-t11991.html

What do you think about that ?

gibus61 commented 10 years ago

Finally, I just called samsung a few minutes ago, and the advisor told that me my phone was always under warrantly (2 years warrantly). He gave me a partner adress near from my home who's going to send my phone to samsung factory (hardware replacement).

More information when I'll get my phone (so about 7-10 days) ....

gibus61 commented 10 years ago

So ... I have received my phone (returned from samsung factory). It runs well. Finally, it wasn't an hardware problem ! no hardware replacement (motherboard, etc). On the tasks sheet, they call that a software freeze. To my mind, they have specific factory tools allowing them to unblock this kind of situations.

I have paid nothing. All is supported by Samsung because phone was under warrantly (lucky for my root operation).

Kadz commented 9 years ago

Hey.. A little help please.

Using a galaxy s3 international version trying to repartition because my whole Pit got screwed up...when attempt to print Pit

Checking if protocol is initialised... Protocol is not initialised. Initialising protocol... Handshaking with Loke...

Beginning session... Session begun with device of type: 131072

Downloading device's PIT file... ERROR: Failed to receive PIT file size! ERROR: Failed to download PIT file!

thats the output. and when I attempt to repartition it says

Uploading PIT ERROR: Failed to confirm end of PIT file transfer! PIT upload failed! Ending session...

help please...using Windows 8 and the heimdall front end

Benjamin-Dobell / Heimdall

[gs3 - I9300] pit partition error #215

I get an error while downloading .pit file from my device. My gs3 is well recognized by heimdall but verbose output give me this result :

Re-attaching kernel driver...