It seems that my I9000T from Claro Guatemala has managed to brick itself. I had it in download mode, connected to my Ubuntu computer running Heimdall Frontend. I clicked the Print PIT button under Utilities and received an error saying that heimdall had crashed.
Now the phone is stuck between the infamous BSOD or, if I hold down the magic 3 key combo long enough, download mode.
I did not attempt to flash any files, the phone still has (had?) the stock 2.1 firmware.
It seems like my only option at this point is to go ahead and try to flash a different ROM. Is that correct?
Ok, I am up and running with an update from Claro CR.
I grabbed the file from here: http://forum.xda-developers.com/showpost.php?p=25480021&postcount=33
Unpacked everything into a single folder, put the brick into download mode, and ran the following command:
~/Descargas/Gt I9000t Galaxy 2.3$ sudo heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin --verbose
So now I am running an updated firmware, and the phone appears to fully functional. I say appears because i am in an area with limited cell coverage, it will have to wait for the morning to test everything fully.
apater said:
I clicked the Print PIT button under Utilities and received an error saying that heimdall had crashed.
Click to expand...
Click to collapse
What heimdall version You use? I use v1.3.1 and its work
-----------------------------------------------------------------------
Heimdall v1.3.1, Copyright (c) 2010-2011, 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/
.
.
.
--- Entry #12 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 11
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:
Ending session...
Rebooting device...
Re-attaching kernel driver...
The Heimdall-Frontend is version 1.3.2
It may be that my phone is from Claro/Telcel and they have some funky bootloaders that other I9000's don't have.
I was able to un-brick the phone by flashing (via the heimdall cli) firmware from Claro PR.
Related
I would like install Cyanogenmod 10.1 on my i9000. I installed on my Ubuntu 12.04 heimdall 1.4 deb (for Ubuntu 12.10).
The guide is tho official guide on wiki's Cyanogenmod: wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
1. Download Semaphore's ClockworkMod Recovery, and the Heimdall Suite:
2.Power off the Galaxy S and connect the USB adapter to the computer but not to the Galaxy S.
3.Now boot the Galaxy S into download mode by holding down Home & Volume Down. Accept the disclaimer. After this insert the USB cable into the device.
4.Place Semaphore's ClockworkMod Recovery file into the Heimdall directory.
5.On the computer, open a terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage --no-reboot
When I try to apply the kernel, this is the answer:
Code:
[email protected]:~$ sudo heimdall flash --kernel zImage --no-reboot
[sudo] password for domenico:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
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:
Initialising connection...
Detecting device...
Claiming interface...
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...
PIT file download successful.
ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Releasing device interface...
[email protected]:~$
What's up? Where I'm wrong?
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
whetu said:
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
Click to expand...
Click to collapse
THANKS!!!
How to open a terminal??
Hi
Please help! On the computer; How to open a terminal and run command...??
Thanks in advance
whetu said:
Try capitalising 'kernel', worked for me last night
Code:
heimdall flash --KERNEL zImage --no-reboot
Click to expand...
Click to collapse
Yes it worked
Thanks mutch
[Q] ERROR: Partition "factoryfs" does not exist in the specified PIT. [SOLVED]
Code:
K:\GT-19000\HEIMDALL\Heimdall Suite 1>heimdall flash --repartition --pit m110s.p
it --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boo
t boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem mo
dem.bin
Heimdall v1.4.0
Copyright (c) 2010-2013, 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...
libusbx: error [cache_config_descriptors] unexpected configuration descriptor si
ze (actual) for '\\.\USB#VID_0000&PID_0538#5&ED9EEE6&1&1'.
Claiming interface...
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.
ERROR: Partition "factoryfs" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
I tried this method to flash eclair back on my m110s. I am currently running cm7. But it gives above error. The flashing works fine using Odin but causing my baseband/imei missing. Any idea why?
EDIT: LOL, I guess Uppercase matters in windows compared to linux.
I bricked my phone by flashing the wrong zip in FlashFire. It hung at the ATT logo or powered off after the Samsung logo. The following method allowed me to restore it back to factory I537UCUCNE3 (4.4.2):
Boot into Odin Dowload Mode:
http://forum.xda-developers.com/wiki/Odin_mode#Entering_Odin_mode
Code:
$ unzip SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip
$ tar -xf AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ heimdall flash --pit JACTIVELTE_USA_ATT.pit --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --PERSDATA persdata.img.ext4 --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img
zip obtained here:
http://forum.xda-developers.com/showthread.php?t=2629093
heimdall obtained here:
http://ftp.us.debian.org/debian/pool/main/h/heimdall-flash/heimdall-flash_1.4.0-2_amd64.deb
I hope this is able to help others who have locked bootloaders but rooted ROMs on SGS4A and have corrupted their ROMs as a result of a bad flash or similar. ENjoy!
Thanks ... and small typo.
First of all, many thanks for the post. It saved me! Second, I think you have a typo -- I believe JACTIVELTE_USA_ATT_16G.pit should be JACTIVELTE_USA_ATT.pit. Or at least, that's what I had to change to get everything to work.
z_thompsonpa said:
I bricked my phone by flashing the wrong zip in Flash Gordon. It hung at the ATT logo or powered off after the Samsung logo. The following method allowed me to restore it back to factory I537UCUCNE3 (4.4.2):
Boot into Odin Dowload Mode:
http://forum.xda-developers.com/wiki/Odin_mode#Entering_Odin_mode
Code:
$ unzip SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip
$ tar -xf AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ tar -xf CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5
$ heimdall flash --pit JACTIVELTE_USA_ATT_16G.pit --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --PERSDATA persdata.img.ext4 --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img
zip obtained here:
http://forum.xda-developers.com/showthread.php?t=2629093
heimdall obtained here:
http://ftp.us.debian.org/debian/pool/main/h/heimdall-flash/heimdall-flash_1.4.0-2_amd64.deb
I hope this is able to help others who have locked bootloaders but rooted ROMs on SGS4A and have corrupted their ROMs as a result of a bad flash or similar. ENjoy!
Click to expand...
Click to collapse
fbshapiro said:
First of all, many thanks for the post. It saved me! Second, I think you have a typo -- I believe JACTIVELTE_USA_ATT_16G.pit should be JACTIVELTE_USA_ATT.pit. Or at least, that's what I had to change to get everything to work.
Click to expand...
Click to collapse
You are right. I had to revisit these steps recently when I upgraded to OC7.
If reflashing ML2, that rom uses pit file named, JACTIVELTE_USA_ATT_16G.pit
If reflashing NE3, that rom uses pit file named, JACTIVELTE_USA_ATT.pit
When following the Lollipop Root Method mentioned here:
Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
Click to expand...
Click to collapse
If you want to use Linux just substitute the following for the Odin step mentioned above:
Code:
tar -xf I537_OC7_Bootloader.tar.md5
heimdall flash --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn
Hi all, i'm a noob with all this.
I've a trouble with my Samsung GT-P1000N. I used a wrong firmware and now my tab is dead. (Blackscreen, nothing shows).
If i hold down POWER BUTTON + VOLUMEN (-), Odin and Hemidall detect my tab, but the screen still is in black. So i try to re-stock or fix my tab with the firmware download from "sammobile.com/firmwares/"
In heimadall i do:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
and the output is:
Detecting device...
Claiming interface...
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...
PIT file download successful.
ERROR: Partition "primary-boot" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
So i try to print the PIT with "heimdall print-pit", and this prints a big table with partitions. So i think i'm using wrong name "--primary-boot", i don't know if it need to be "IBL+PBL"... can you give me a tip how to solve the blackscreen trouble.
Entry Count: 15
Unknown 1: 1
Unknown 2: 0
Unknown 3: 7703
Unknown 4: 65
Unknown 5: 64224
Unknown 6: 18
Unknown 7: 55296
Unknown 8: 67
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: IBL+PBL
Flash Filename: boot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename:
FOTA Filename:
....
Thanks in advance.
First, if you have a problem, since you can enter download mode-like thing, try odin to restock first.(It's ease to use)
Also, you maybe need the pit file in the stock ROM to pass to heimdall.
[Q&A] [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Avai
Q&A for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite (1.4.0 Now Available). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Flashing ROM from Mac OS X
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.
jvigneshcs said:
Hi,
I tried to flash a ROM (recovery.img) using heimdall command line, I tried with the following command
Code:
sudo heimdall flash --recovery filename.img --no-reboot
The device in download mode got detected, then it says Initializing Protocal. after that I got "Error: failed to send data, releasing device interface"
Any solutions or help, regarding this.
Click to expand...
Click to collapse
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo
tetakpatak said:
You didn't mention the device details, i9000? Heimdall 1.4.0 worked with my newer Samsung devices, but there I had to type --RECOVERY instead of --recovery.
It hasn't worked for my i9000 (Ubuntu 12.04 32-bit)
For my old Samsung i9000 (S1) I had to uninstall Heimdall 1.4.0 and install Heimdall 1.3.1
Your typing style would perfectly fit there.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks for you response. I tried with my Samsung Galaxy Grand Duos GT-I9082 with suitable recovery.img.
Later I installed using Odin from Windows machine.
Successfully tested on Samsung Galaxy S4 Active (GT-I9295)
The frontend sucks But after some research I understood the logic and managed to (re-)flash my phone with I9295XXUCNH2 . I didn't need to repartition and had a valid .pit file on the phone, so it is pretty straightforward:
Code:
sudo heimdall flash --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img --HIDDEN hidden.img.ext4
Cannot load PIT from S3 Neo
Hi,
I want to root my i9301. This requires odin... Since I am on linux, I tried Heimdall. But I fail already downloading the PIT file.
Looks like usb problems, any idea?
Code:
Heimdall v1.4.1
...
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...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
tried i8730 using same cable at motherboard usb port.
worked fine with "WARNING: Empty bulk transfer after sending packet failed. Continuing anyway..."
Ubuntu 16.04 Kernel 4.4.0-34-generic
thanks
Edit: solved, used odin on windows instead.