[Q] Updating Galaxy Tab to Gingerbread 2.3.3 using Heimdall - Galaxy Tab Q&A, Help & Troubleshooting

Hi,
With the release of Galaxy Tab Gingerbread 2.3.3 by Chainfire
( http://forum.xda-developers.com/showthread.php?t=1073854 ), I intend to update my Galaxy Tab (running Froyo 2.2) to Gingerbread. Since I use only Linux in my computer, the only option to flash my Tab is to use Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ).
What I wish to know is:
1. The procedure using Odin calls for repartitioning. Is it okay to repartition using Heimdall?
2. There is a file called hidden.rfs in the official stock rom provided by Chanifire. How do I flash this hidden.rfs using Heimdall? Heimdall accepts only the following arguments as per it's man page:
action: flash
[--pit <filename>] [--factoryfs <filename>] [--cache <filename>]
[--dbdata <filename>] [--primary-boot <filename>]
[--secondary-boot <filename>] [--secondary-boot-backup <filename>]
[--param <filename>] [--kernel <filename>] [--recovery <filename>]
[--efs <filename>] [--modem <filename>]
(Nowhere is any mention of hidden.rfs. I am confused as how to include it while flashing my Galaxy Tab).
If someone can help me, I would very much appreciate it.
Thanks in advance.

Related

[Q] [i9000T] [Heimdall] Loop between Downloading & Black Screen of Death

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.

Tab Wont Boot

Hi Guys,
Was going to try a custom rom from here (Cyanogen Mod), and followed the link in the post to here....
I cant post URLS so *Cyanogen wiki galaxy tab GSM instructions *
I uploaded the kernel without issue. until it rebooted..... Then all i get is the Samsung galaxy tab screen... and it sticks there (the one you see when you turn your tab on).
I can get into DL mode... (power/volumedown). So I tried to load the [ROM][4.1.1] CyanogenMod 10 Preview [Build 3] via clock work... it faield... (Buildprop GT-1000 error?).
So I went to samfirmwares, got my O2 stock rom and DLed it... which comes (as you know) in a uselss... .md5 file. After much searching I found out about splitfus2... installed it and though good.. easy street.... Not it would seem....
Code:
$ ./splitfus2.exe P1000XWJQ8_P1000O2UJQ3_P1000XXJPZ_HOME.tar.md5
SplitFUS2 by Doky v2.11.120625GA
Checking prerequisites...
...tar, md5sum, zip found, ready to go!
Processing file: P1000XWJQ8_P1000O2UJQ3_P1000XXJPZ_HOME.tar.md5
MODEL: P1000
PDA: XWJQ8
CSC: O2UJQ3
MODEM: XXJPZ
mkdir: cannot create directory `P1000_XWJQ8_O2UJQ3': File exists
Temporary workfolder: P1000_XWJQ8_O2UJQ3\
[ P1_add_hidden.pit ] --- Size: 2008 bytes
Checking wipe data file: _base\P1000_userdata.img [NOT FOUND]
Wipe data file not found: _base\P1000_userdata.img
Your device not supported for wipe package
Now creating nonwipe package
tar: boot.img: Cannot stat: No such file or directory
tar: param.lfs: Cannot stat: No such file or directory
tar: system.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: csc.*: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
tar: BcmCP.img: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
adding: CSC_P1000_O2UJQ3.tar.md5 (deflated 99%)
adding: MODEM_P1000_XXJPZ.tar.md5 (deflated 99%)
adding: PDA_P1000_XWJQ8.tar.md5 (deflated 99%)
adding: readme.txt (deflated 34%)
Output file: P1000_XWJQ8_O2UJQ3_XXJPZ_by_SplitFUS2.zip
Removing work folder
SplitFUS2 finished
It wont extract....
So can you guys please assist me in recovering my tab with any suggestions other than 'send it to samsung'!.. ive been at this for hours, I don't care what ROM is on it as long as it works now... !
Its a GT-p1000 7 Inch GSM UK tab bough on the O2 network.
It was rooted and unlocked via a tutorial I found on here .
Thanks in advance.
Corpse.
Why you called a tar.md5 useless?
It is still a tar file and works right with Odin.
Follow my post here and you will be fine.
http://forum.xda-developers.com/showthread.php?p=30422534
Sent from my GT-I9300 using xda app-developers app
.tar.md5's are useless on their own... they require splitting for odin to use....
However thanks to your post/link I have managed to ressurect my tablet so thank you
C.
corpseslayer said:
.tar.md5's are useless on their own... they require splitting for odin to use....
However thanks to your post/link I have managed to ressurect my tablet so thank you
C.
Click to expand...
Click to collapse
Err...not true.. you can use the tar.md5 directly in Odin.
Anyway....
glad you resurrected your tab after all!

Repacking firmware to flash in Odin but Without increasing binary? [done dumping]

Well i dumped my own rom and did this:
Code:
tar -H ustar -c zImage boot.bin modem.bin Sbl.bin cache.img data.img factoryfs.img hidden.img param.lfs > odin.tar
md5sum -t odin.tar >> odin.tar
mv odin.tar odin.tar.md5
It does create a valid flashable image for Odin... but the problem is that it increases the binary counter!
Anyone know how can i create a tar image without increasing it?
Since no one replied and in case anyone is wondering: to make a repack just use the stock kernel because a custom recovery increases the binary.. As simples as that
Sent from my GT-N7000 using Tapatalk 2

I can't install kernel with heimdall before Cyanogenmod 10.1...

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

Restoring from Soft-brick via 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

Categories

Resources