Database Users

Heimdall and Litening rom 1.4

Hi,
I flashed Litenin (and other custom roms) with Heimdal on Linux flawlessy up to version 1.4 which hangs at boot.
I had to replace factoryfs.img with previous version's one (kernel and modem are from 1.4 still and it works....).
Is it a bug in heimdall or something wrong with Litenin rom 1.4 ?
A factory reset didn't help either, 1.4 can't be installed on my phone, at least not with heimdall.
Ciao
Max

bump !
Nobody using heimdall and litening rom here ?

I have exact the same problem....

tschakk said:
I had exact the same problem....
Click to expand...
Click to collapse
Did you solve it ? Flashing with Odin does the trick ?

No.. I dont have access to a win box...
but i think odin should work - another user reported after switching to odin everything was ok....

weird.
I'll try later on unpacking and repacking the factoryfs.img, maybe there's something on it which makes heimdall behava wrong.
Thank you for feedback

Could u resolve the problem?
Sent from my GT-I9100 using XDA App

Nope, unpacking and repacking didn't work either.
It seems that heimdall don't like 1.4 version

OK. thanks for the try...
I could access a windows computer this weekend. Odin worked fine...

I never got Heimdall working. It cant find my phone.

hmmm I did nothing special. What OS u use?
(Ubuntu)
1. I Install libusb-1.0 like described on the official heimdall homepage.
2. Install the heimdall .deb package.
3. put your phone to download mode
4. Start heimdall like: sudo heimdall print-pit
I only used the console edition (1.2.0) - not the gui edition...
For flashing type:
sudo heimdall flash --<partition identifier> <filename>

Lite'ning Rom v1.5 XXKF2
Lite'ning Rom v1.5 XXKF2 has just been released. Has anybody tried flashing the new version via Heimdall?

The link has been removed before I could try it

Yes, I saw that people were having problems with it. When the new version is up we can try it again.

Ok, just flashed Litening v1.5 with heimdall.
Everything worked as expected...

Nice, I'll try it tonight.

I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!

TheBishopOfSoho said:
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
Click to expand...
Click to collapse
I've used the same configuration to flash my SG2. But you do realize that VirtualBox is using the same ubuntu (linux) drivers for usb?
And why do you find windows to be more reliable?

TheBishopOfSoho said:
I run Ubuntu, but use VirtualBox and USB filtering on a Windows 7 Guest to run things like Odin, I just dont trust the Ubuntu tools for drivers, I find Windows to be more reliable and less likely to brick the phone when flashing.
It works fantastic for me!
Click to expand...
Click to collapse
I cant share your opinion. Im working now for more than a year with Android. We have our own android build. And i had much less problems working with Linux (Ubuntu) than with Windows...

Flashed Litening rom 1.5 just fine with Heimdall in Ubuntu 11.04.

Are there ways to flash a new modem besides ODIN?

I currently have the EC05 modem with SRF1.2 and Genocide 2.0 kernel. I'm getting some dropped calls, and my bluetooth isn't consistently connecting in my car, so I want to try a different modem. The problem is that I have a Mac. The only Windows machine I have access to is my computer at work, and it for some reason fails everytime I try to install the Epic drivers. I'm aware of using ODIN to flash new modems, but this isn't an option for me. I tried getting Heimdall to work on my Mac, but for some reason it wasn't allowing me to do anything (almost like view only). Are there any update.zip files or some way to flash a new modem using my Mac?

pharmer81 said:
I currently have the EC05 modem with SRF1.2 and Genocide 2.0 kernel. I'm getting some dropped calls, and my bluetooth isn't consistently connecting in my car, so I want to try a different modem. The problem is that I have a Mac. The only Windows machine I have access to is my computer at work, and it for some reason fails everytime I try to install the Epic drivers. I'm aware of using ODIN to flash new modems, but this isn't an option for me. I tried getting Heimdall to work on my Mac, but for some reason it wasn't allowing me to do anything (almost like view only). Are there any update.zip files or some way to flash a new modem using my Mac?
Click to expand...
Click to collapse
I don't believe so. Did you try running Heimdall on linux on the Mac? Heimdall also has Windows drivers if Odin doesn't work on that PC then maybe Heimdall will. You need to use modem.bin in Heimdall....extract it from the .tar file with 7zip.

I couldn't get heimdall to recognize my epic either. I don't believe our secondary bootloader has been fixed with the bug that was preventing Macs from working. I have odined to eb13 and even dg27 and gotten ota updates to ec05 but never get recognized on the mac. Heimdall works fine on my work PC though. You might try Linux on your mac that or bootcamp to XP or 7

stilesja said:
I couldn't get heimdall to recognize my epic either. I don't believe our secondary bootloader has been fixed with the bug that was preventing Macs from working. I have odined to eb13 and even dg27 and gotten ota updates to ec05 but never get recognized on the mac. Heimdall works fine on my work PC though. You might try Linux on your mac that or bootcamp to XP or 7
Click to expand...
Click to collapse
According to the Heimdall website, the second bootloader problem for Mac was fixed with Froyo 2.2. Of course Heimdall doesn't officially support Epic and I don't have a Mac (just Linux and Windows) so I haven't tried it.
To the OP:
What version of Heimdall are you using? Are you using the GUI or the command line?
There may be a problem with the GUI not acting the way it's expected. If nothing else works, I would recommend:
1. install Heimdall 1.2.0 (command line).
2. boot phone into download mode (power + 1 key)
3. attach phone to computer
4. see if heimdall recognizes the phone by using the command
heimdall print-pit
Click to expand...
Click to collapse
. That should give you a listing of the partitions on your phone. It will reboot your phone.
If that works, then repeat steps 1-3. Then to upload a different modem just use
heimdall flash --modem <file name>
Click to expand...
Click to collapse
where <file name> is the file name for the modem. I don't know how you specify the directory for files in Mac, but in linux I just navigate to the file and open the terminal window to save on the cd commands.

I was trying to use the GUI interface. I'll mess with it some more tonight if I get time and see if I can get it to work using command line. I also may try to bootcamp Linux if that works. Just curious, what are most people using for Linux...Ubuntu, Mint, or something else?

Yes it's will do it with ec05
Sent from my SPH-D700 using XDA Premium App

pharmer81 said:
I was trying to use the GUI interface. I'll mess with it some more tonight if I get time and see if I can get it to work using command line. I also may try to bootcamp Linux if that works. Just curious, what are most people using for Linux...Ubuntu, Mint, or something else?
Click to expand...
Click to collapse
I just started to use Mint 11. It's been almost 15 years since the last time I used linux shell.

UCKH3 Heimdall-One-Click [beta]

This is UCKH3 packaged in Heimdall One-Click Format. Run it at your own risk. I am placing it here because I need a place to store the link on mediafire
http://files.teamkomin.com/Captivate/SGH-i897-UCKH3-One-Click.jar
As of today, this is the latest, greatest semi-official, leaked firmware for the Captivate--3SEP11
If anyone wants to try it out, go ahead, please leave feedback.
No time to do a full release thread about this right now... Working on the UnBrickable Mod platform and this file is required to finish the job.

Could you do a UCKH3 instead?

whyareyou said:
Could you do a UCKH3 instead?
Click to expand...
Click to collapse
DIdn't realize there was a newer one. Yes. I'll get right on that.

Hi thanks for this, im just about to try it now. Hows KH3 going?

Summary: It kinda worked. I get garbled video with the camera and on bootup after the Samsung Galaxy animation.
Process:
I started on a semi-recent CM7.1 Nightly (90-ish).
I flashed to stock using AIO Captivate Toolkit. That got me to JF6. Note all download modes are initiated using USB jig.
As soon as I verified a good boot into stock, I fired up Heimdall One-Click, put the phone into Download mode and clicked the magic button...
It flashes, reboots, but then gets stuck at the white AT&T boot screen. No progress for many, many minutes. I get desperate and tried to shut it off. In the process, the phone reboots and begins what appears to be a normal boot process. This boot completes, but I'm left with the aforementioned artifacts - the camera doesn't work and I get garbled graphics on boot. Also, the phone feels laggy as heck.
I'm guessing I may have prematurely interrupted the initial boot process. To be honest, I wasn't tracking time, so I don't know if it was only 5 minutes or 15. I just know it didn't seem right and much, much slower than flashing to stock JF6 was.
I'm going to try a more conventional Odin flash to see if I get better results.

Moxie3000 said:
I'm going to try a more conventional Odin flash to see if I get better results.
Click to expand...
Click to collapse
This did not include the params.lfs. I did not realize it at the time I released it. I will include a better version soon. I just needed something quick to support this: http://forum.xda-developers.com/showthread.php?t=1242466

Sorry, I can't release UCKH3, it's missing files. I'll see about other versions...

AdamOutler said:
Sorry, I can't release UCKH3, it's missing files. I'll see about other versions...
Click to expand...
Click to collapse
You can pull the missing files from KF1. That's what I did when I flashed KH3 when I managed to messup my phone playing around with Heimdall 1.3.0...
Guessing the missing files weren't updated so they weren't included with the exception of the primary bootloader.

Updated to UCHK3 with missing files from UCKF1. This is the latest, greatest Samsung firmware as of today.

Whats wrong
This might be a noob question but what am I doing wrong? I make it executable but it does nothing. I am running Ubuntu 10.10

vdubguy said:
This might be a noob question but what am I doing wrong? I make it executable but it does nothing. I am running Ubuntu 10.10
Click to expand...
Click to collapse
Odin is for windows. Heimdall is the linux equivalent. So the file in the op probably won't help you on ubuntu.

vdubguy said:
This might be a noob question but what am I doing wrong? I make it executable but it does nothing. I am running Ubuntu 10.10
Click to expand...
Click to collapse
Right click and open with java... or run from command line java -jar mydownloadedfile.jar

Is anyone else having problems with running the KH3 version on Windows? When I try and run it I get -- "Invalid or Corrupt jarfile" and it closes.
I tried downloading 3 times to rule out corrupt download, and the previous KF1 version ran fine so I don't think it's my Java implementation.

pinoymutt said:
Is anyone else having problems with running the KH3 version on Windows? When I try and run it I get -- "Invalid or Corrupt jarfile" and it closes.
I tried downloading 3 times to rule out corrupt download, and the previous KF1 version ran fine so I don't think it's my Java implementation.
Click to expand...
Click to collapse
Verified... There must have been a problem with the secure file transfer (i was not watching it). It is an invalid java file when downloaded from the server.
Code:
[email protected]:~/Downloads$ chmod +x SGH-i897-UCKH3-One-Click.jar
[email protected]:~/Downloads$ ./SGH-i897-UCKH3-One-Click.jar
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:131)
at java.util.zip.ZipFile.<init>(ZipFile.java:92)
at sun.tools.jar.Main.list(Main.java:997)
at sun.tools.jar.Main.run(Main.java:242)
at sun.tools.jar.Main.main(Main.java:1167)
invalid file (bad magic number): Exec format error
I'm uploading a new one now, ETA 25 minutes.

The one from this morning was about 150 some odd megs, and the re-up over 200. This one seems to load up fine!

Does this include bootloaders?
Thanks!

There is a option to flash bootloaders. If you want them you will have to flash twice.as far as i know
jgaviota said:
Does this include bootloaders?
Thanks!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App

AdamOutler said:
Right click and open with java... or run from command line java -jar mydownloadedfile.jar
Click to expand...
Click to collapse
OK. Comes up now. My first Heimdall flash coming soon!

I'm on stock froyo, kb1, flashed to it using this: heimdall at&t stock firmware package. Can i flash UCKH3 that Adam linked in the OP over this? Is it enough to click on bottom left button (details), then write true in the Flash column to the IBL+PBL, SBL, PARAM rows to flash bootloaders too? Thanks for the answers!

bazarimajom said:
I'm on stock froyo, kb1, flashed to it using this: heimdall at&t stock firmware package. Can i flash UCKH3 that Adam linked in the OP over this? Is it enough to click on bottom left button (details), then write true in the Flash column to the IBL+PBL, SBL, PARAM rows to flash bootloaders too? Thanks for the answers!
Click to expand...
Click to collapse
yes. You should not have any problems.

[TOOL] Samsung Galaxy Rescue Kit

After running into a bit of trouble myself and seeing how many people ran into the same thing, namely bricking, i decided to create a quick and easy toolkit for unbricking which did the trick for me. The one i'm posting is for SGS I9000 Intl Version, using latest european firmware from this thread: http://forum.xda-developers.com/showthread.php?t=846913.
However you can create your own custom kit by replacing the files in the kit and modifying the batchfile i've included. Just make sure to read the readme file included for details.
What it does:
- unbricks
- flashes
- flashes with format
- does not use ****ty Odin.
This kit uses the 1click unbrick solution & Heimdall. For those, credit goes to Adam Outler for making the 1click unbrick and to Benjamin Dobell for making Heimdall. It's nothing out of the ordinary. It's just ingeniously flexible. That's all. Anyone with a bit of brain and 5 minutes of spare time can make himself one for his phone and it will get him out of the sticky situation of reverting from ics to gingerbread.
Basically this is all you need to get from broken to working. All of this took me roughly ~10 hours or more of grueling testing and experimenting on my own till 5 in the morn. If you use this or make your own, just credit me & gimme a thanks.
Download the kit from here (240 Mbs):
http://hotfile.com/dl/146355868/42dfea1/SGS_Rescue_kit-13-1-2012.rar.html

Hi. Does that mean I just need my USB cable and your soft to unbrick any SGS without download mode ?
Downloading, and gonna try it.

Sanael said:
Hi. Does that mean I just need my USB cable and your soft to unbrick any SGS without download mode ?
Downloading, and gonna try it.
Click to expand...
Click to collapse
I doubt. You will need usb jig for that. I think this is for softbrick and not for totally bricked SGS.
Sent from my GT-I9000 using xda premium

Hi guys, this is only for the case in which your phone is still able to enter download mode.

ldq said:
Hi guys, this is only for the case in which your phone is still able to enter download mode.
Click to expand...
Click to collapse
So not for bricked, just for softbricked phones.
Sent from my GT-I9000 using xda premium

Seems like a good idea I'll check it out later.

I've updated the download link with a new, working one.

ldq said:
Hi guys, this is only for the case in which your phone is still able to enter download mode.
Click to expand...
Click to collapse
Thanks for this post! I will be studying this closely in the coming days.
A quick question: when people cannot enter download mode, is that the situation when the button sequence doesn't work? in that scenario, i used "adb reboot download" -- worked well. after flashing via odin, it seems my button sequence works again.

It worked even on Linux!
Thanks alot for your link.
Unfortunately I use Linux as main OS. Your approach is more MS based but it saved my day anyway.
Had just to paste this shell command after compyling Heimdall for my ubuntu x64 distribution.
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
Hope my donation may pay you a beer

Thanks a lot dude ! and hey, glad i could help !
PS: Feel free to create a linux based version as well , if the same batchfile principle applies... why not ?

tanclo said:
Thanks for this post! I will be studying this closely in the coming days.
A quick question: when people cannot enter download mode, is that the situation when the button sequence doesn't work? in that scenario, i used "adb reboot download" -- worked well. after flashing via odin, it seems my button sequence works again.
Click to expand...
Click to collapse
In short yes, but it may also be because you're nervous and/or for some reason cannot press to button combo correctly, or if they are broken by hardware.
hmm... Its also possible to include a batch command to adb into download mode for extra comfort at the push of 2 buttons. I'll have to update the kit asap.

ldq said:
In short yes, but it may also be because you're nervous and/or for some reason cannot press to button combo correctly, or if they are broken by hardware.
hmm... Its also possible to include a batch command to adb into download mode for extra comfort at the push of 2 buttons. I'll have to update the kit asap.
Click to expand...
Click to collapse
Thanks for working so tirelessly on this script. I might give it a go on a windows box or look into your bash to use it on ubuntu. I'm afraid that Heimdall doesn't work on my device yet, though.
And yes, there is a big chance that it was me doing it wrong. on my device, the sequence seems to change with new Kies update too. Entering recovery is just crazy take a look here for further amusement
way simpler to just "adb reboot recovery" and keep the button pressing party for that inevitable rainy day

Hey my cell has been USB Bricked. That means the computer and Odin doesn't detect the cell even when it is in download mode. And not charges either. Will this still work? Can you please give me step-by-step instructions?

Can somebody please explain me the simple point of this software.
As far as I understood this can only be used, if you failed to enter download mode using your phone and you would like to re-instal a rom .. Or is this just a rom install manager?
Sorry confused

1337SereniTyx3 said:
Hey my cell has been USB Bricked. That means the computer and Odin doesn't detect the cell even when it is in download mode. And not charges either. Will this still work? Can you please give me step-by-step instructions?
Click to expand...
Click to collapse
Well, for starters you could try to bring it into download mode, use batchfile included and select the option of unbricking it. If that does not work, you may want to try and install the included drivers then attempt to unbrick again.
Can somebody please explain me the simple point of this software.
As far as I understood this can only be used, if you failed to enter download mode using your phone and you would like to re-instal a rom .. Or is this just a rom install manager?
Sorry confused
Click to expand...
Click to collapse
the point of this kit is to bring your phone from softbrick status into working condition (bootable). So no matter how bad you screw up with the rom installations, you can revert to this, re-root, and you're back on your feet.
Which reminds me: i gotta include a already rooted SGS EU rom. )
tanclo said:
Thanks for working so tirelessly on this script. I might give it a go on a windows box or look into your bash to use it on ubuntu. I'm afraid that Heimdall doesn't work on my device yet, though.
And yes, there is a big chance that it was me doing it wrong. on my device, the sequence seems to change with new Kies update too. Entering recovery is just crazy take a look here for further amusement
way simpler to just "adb reboot recovery" and keep the button pressing party for that inevitable rainy day
Click to expand...
Click to collapse
) Saw that. Ticks me off every time I gotta do the button juggle thinggie. I also tend to use adb console, because its far simpler ! )
Do you happen to know of any good batch scripting guides ? I've been looking for some indepth guide but can't find any. What I'd like to do is use a command which takes some parameters (like where you got your android sdk) and turn it into the path for the adb console (since you need to start it up with parameters like adb reboot recovery, that means that i have to actually tell the script to go into that folder via cd and run the app.). But if you know of alternative ways of starting it up, I'm all ears

Need help
i need some help here
i'm stuck, my phone was working well but i wanted to revert it to stock rom and followed instructions, but something goes bad
now i'm able just to enter in download mode, i can't enter recovery mode or even turn on my phone

jaskoooo said:
i need some help here
i'm stuck, my phone was working well but i wanted to revert it to stock rom and followed instructions, but something goes bad
now i'm able just to enter in download mode, i can't enter recovery mode or even turn on my phone
Click to expand...
Click to collapse
Just flash the stock rom again with odin, and cf-root if you want recovery. Good luck!

Nicely packaged up. However, after I ran:
Code:
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
The reboot presents me with "Confirm password". Got a bit confused, but it appears the trick is to just enter any password about 5 times until prompted that this will wipe the card. Then you're back in.
Just in case someone runs into the same situation and was as confused as I was.

ldq said:
After running into a bit of trouble myself and seeing how many people ran into the same thing, namely bricking, i decided to create a quick and easy toolkit for unbricking which did the trick for me. The one i'm posting is for SGS I9000 Intl Version, using latest european firmware from this thread: http://forum.xda-developers.com/showthread.php?t=846913.
However you can create your own custom kit by replacing the files in the kit and modifying the batchfile i've included. Just make sure to read the readme file included for details.
What it does:
- unbricks
- flashes
- flashes with format
- does not use ****ty Odin.
This kit uses the 1click unbrick solution & Heimdall. For those, credit goes to Adam Outler for making the 1click unbrick and to Benjamin Dobell for making Heimdall. It's nothing out of the ordinary. It's just ingeniously flexible. That's all. Anyone with a bit of brain and 5 minutes of spare time can make himself one for his phone and it will get him out of the sticky situation of reverting from ics to gingerbread.
Basically this is all you need to get from broken to working. All of this took me roughly ~10 hours or more of grueling testing and experimenting on my own till 5 in the morn. If you use this or make your own, just credit me & gimme a thanks.
Download the kit from here (240 Mbs):
http://hotfile.com/dl/146355868/42dfea1/SGS_Rescue_kit-13-1-2012.rar.html
Click to expand...
Click to collapse
Just used this, I was able to flash my Rom (Replacing with my files) all went well, I did a cache wipe partition and factory data reset in the 3e recovery, just before rebooting it said "unable to mount /data REBOOTING..." and rebooted, and then it rebooted and hangs at the I9000 Logo and waits for ever keeps cycling..
Any idea?
Edit : Before touching the 3e recovery this error shows up : (straight after flashing)
ASSERT FAILED : getprop("ro.product.device") == " GT-P1000" ||.... etc
E: Error in /cache/recovery/sec_csc.zip (STATUS7) Installation aborted

MaTSuNg said:
Just used this, I was able to flash my Rom (Replacing with my files) all went well, I did a cache wipe partition and factory data reset in the 3e recovery, just before rebooting it said "unable to mount /data REBOOTING..." and rebooted, and then it rebooted and hangs at the I9000 Logo and waits for ever keeps cycling..
Any idea?
Edit : Before touching the 3e recovery this error shows up : (straight after flashing)
ASSERT FAILED : getprop("ro.product.device") == " GT-P1000" ||.... etc
E: Error in /cache/recovery/sec_csc.zip (STATUS7) Installation aborted
Click to expand...
Click to collapse
Honestly I have no ideea mate. I can only guarantee for the files I supplied in my zip file. If you changed them with yours, it might indicate some of them might be corrupted or not working. I've only used the recovery kit to pull myself out of bricking and revert to stock rom. I didn't try installing a custom rom. Not sure what you were trying to do.
I advise you to try and debrick (should work), and do a format and then install.
If that doesn't work, dunno what to say. As I said above, for me it worked each time.

[GUIDE] Upgrading and modding NTT DoCoMo SC-01C (Japanese P1000)

Kind of a niche guide, but at least non-Japanese people owning an SC-01C have some sort of guidelines.
Before we begin
The SC-01C is the rebranded Japanese version of the P1000, locked exclusively to NTT DoCoMo. If you have this model and want to upgrade and/or flash custom ROMs with it, this guide may be able to help you.
Before beginning, you have to check your firmware version. What you'll have to download will depend on it. If you have Android 2.2 Froyo, read on, otherwise, if you're already running Android 2.3 Gingerbread skip to the Gingerbread Users section.
Also, based on experience, if you want to upgrade to other ROMs in the future you will have to keep your stock GB ROM file, your gt-p1000_mr.pit, the dbdata.tar and the entire Overcome kit (kernel and ROM). You will need all of them in the future because I've found that to install a new ROM you have to repeat the entire process of restocking to GB, then installing Overcome Kernel and ROM, then installing whatever ROM you want. It sucks, but it's the only way I've seen so far.
Froyo Users
If you're planning to install a custom ROM, you can't do it on Froyo straight away, at least not on a stock ROM with a protected bootloader. If you don't know if your bootloader is protected or not, the safest thing to do is to first upgrade your firmware to the stock Japanese Android 2.3 Gingerbread. Then you can follow the Gingerbread guide afterwards.
Froyo Users Will Need
Stock Japanese GB ROM (you can get it from here or from SamFirmware.com). The ROM is a .tar archive file, so you will also need 7-Zip or another file extracting utility to extract files from the tar file.
Odin 1.7 (higher versions will likely not hurt either)
Heimdall (in case Odin doesn't work or you aren't running Windows)
Upgrading to Gingerbread
Make sure your PC has the drivers for your Tab. If you've already connected your PC to the Tab before, you already have them. Otherwise, plug your Tab into your PC and let the drivers install automatically. This works even if you're in Download Mode. If they don't install automatically, you might need to download Samsung Kies or just the Samsung USB Driver for Mobile Phones to get the driver to install.
[FOR HEIMDALL USERS]
You will need to plug in your Tab and run zadig.exe for your drivers, which is found either in the same folder as your Heimdall.exe or in the Drivers folder in that same folder, depending on which version you have. From there, select Options -> List All Devices, then select Gadget Serial or Android USB Composite Interface, then click Install Driver.
After getting the drivers, unplug your Tab (you can keep the PC end plugged in). Turn off your Tab and plug your USB Interface cord into your PC (not the Tab just yet), then put your Tab into Download Mode. You can do this by either holding down the Power and Volume Down keys while the Tab is off, or simply holding down the Volume Down key while plugging in the cord to your Tab. If done correctly, you should see a screen with a yellow Android with a shovel, together with the words "DOWNLOAD MODE, DO NOT TURN OFF TARGET!"
If you're running Windows and using Odin, extract the gt-p1000_mr.pit from the .tar archive into the same folder as the archive. Otherwise, if you're running Heimdall, extract the entire archive into the same folder as your Heimdall.exe.
Plug your Tab back in if you haven't already. The next step will vary for Odin and Heimdall users.
[FOR ODIN USERS]
Open Odin and check if there is a yellow box amongst all the white ones which says [COM4] or something like that, it doesn't matter as long as the box is yellow.
Click PIT and select the gt-p1000_mr.pit you extracted from the stock Japanese GB .tar file, then click Start. This will re-partition the device, and it is absolutely critical that this is done first, as missing this step can cause a brick.
After the PIT flashing is successful, click Reset, then click PDA and select the stock Japanese GB .tar file, and click Start. You will have to wait for a few minutes while the ROM flashes. Progress bars will appear both on the Tab screen and Odin.
NOTE: If after flashing you boot into Recovery Mode and you get the following error:
Code:
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
Then you will have to download and flash dbdata.tar as PDA (Google "P1000 dbdata.tar"; it's about 1.25MB or so). That should solve it.
[FOR HEIMDALL USERS]
Since you already extracted the contents of the stock Japanese GB .tar file into the same folder as your Heimdall.exe, all you have to do is run the following command from a Terminal window (or Command Prompt if you're running Windows):
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Wait a few minutes while Heimdall flashes the ROM. It should inform you when the flashing is successful.
After the flashing is successful, you should now be running stock Android 2.3 Gingerbread. You can stop here or continue on to the Gingerbread Users section for flashing a custom ROM.
Gingerbread Users
Since you're already on Gingerbread, which is the latest stock Android version you have, you're probably reading this guide to find out how to install custom ROMs. Personally I've found, after bricking my Tab a couple of times, that trying to flash custom ROMs from the stock Japanese GB ROM doesn't work unless you flash the Overcome kernel and ROM first.
Hence, the first step to getting a custom ROM running on an SC-01C is to flash the Overcome kernel. For instructions on how to do this, go to the guide thread at the end of the paragraph. You can skip the restocking part, as you're already running stock GB. Instead, follow the instructions from Step 7 of the guide, found on Page 10. After following the instructions there and flashing the Overcome kernel and ROM, you should now be able to flash any other custom ROM you want, following the instructions for the regular P1000.
Getting the Overcome kernel and ROM: http://forum.xda-developers.com/showthread.php?t=1881981
Questions, Answers and Possible Issues
My SC-01C is stuck at boot logo after trying (and failing) to flash custom ROM.
Solving this issue depends on your firmware version and whether or not you can still get into Download Mode. If you can, just follow the instructions in this guide exactly and the problem should be solved.
My SC-01C is stuck at phone-exclamation mark!-computer screen.
This is also likely because of a failed ROM flashing or firmware upgrade. In that case, you can use Heimdall OneClickUnbrick to fix it. A guide to do so can be found here.
My SC-01C isn't detected by Odin, and/or Heimdall produces a "Claiming interface failed" error.
Your drivers aren't being detected and either need to be installed or reinstalled. To force a driver reinstall on Windows, plug in your Tab, go to the System Tray, right-click Safely Remove Hardware and Eject Media, then select Open Devices and Printers. Find your Tab's device name from there, then right-click it and select Remove Device, then unplug your Tab and plug it in again. The drivers should reinstall automatically. If they still don't reinstall, download Samsung Kies or the Samsung USB Driver for Mobile Phones and try again.
For other possible questions or concerns, please reply to this thread.

After successful repair, No Network/ No service
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?

dannyogolo said:
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
Click to expand...
Click to collapse
You'll need to modify it further to get it to work with other providers. I'm personally not sure if it's a hardware or a software hack, because I paid someone to unlock my Tab back when I didn't know jack **** about modding. If it was already unlocked prior to being bricked, try to flash a new ROM over it. Either way, please hit back if you find the answer so I can add it to the FAQ section.

Hi! I just got the SC-01C & it was already loaded with a custom ICS firmware. Would it be ok to flash another custom firmware DIRECTLY? or Do I still need to flash the GB first?

only root
how to root without change stock rom?
It is possible ?
Thank you

zmeus said:
how to root without change stock rom?
It is possible ?
Thank you
Click to expand...
Click to collapse
Yes it's possible, just Google "how to root galaxy tab". There's a few methods, so just pick one.
Sent from my GT-P1000 using xda app-developers app

Thank you
This it will help me for sure.
Sent from my GT-I9100 using Tapatalk 4

"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?

joevinz said:
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
Click to expand...
Click to collapse
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.

geno93n0 said:
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
Click to expand...
Click to collapse
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:

joevinz said:
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
Click to expand...
Click to collapse
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.

Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help

Help I think I am bricked
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....

WILLIEFRANCE said:
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
Click to expand...
Click to collapse
What are you Trying to do? and what errors?

SC-01C
rence.slvdr said:
What are you Trying to do? and what errors?
Click to expand...
Click to collapse
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...

WILLIEFRANCE said:
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
Click to expand...
Click to collapse
This happened to me as well, it's why I wrote this guide. Try the Overcome method that I posted in the guide, or search for it in this forum. Also, are you using the stock Japanese GB ROM or just a normal stock ROM? You need to use the stock Japanese Gingerbread ROM. I provided links in the guide.

rence.slvdr said:
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Click to expand...
Click to collapse
Don't flash them all at once. Look at the Overcome guide carefully.

pls help
hi.. im new here and i have a problem with modding my sc01c tab. im already running on official gingerbread SC01COMKE2 firmware and im also rooted. i followed all the steps but always ended up with a soft brick. heres what i did.. i downloaded overcome files from http://forum.xda-developers.com/showthread.php?t=1881981 and followed step by step guide. i flashed Overcome_Kernel_v4.0.0.tar and boot into recovery mode.. then flashed Overcome_7_Series_v4.1.0_Wipe.. but it says cannot open BAD FILE. i redownload even the no wipe version but same happens. i tried to restock using GB-Stock-Safe-v5 but it failed in odin.. whats weird is that when i flashed my tab with official firmware it succeeded without a problem.. can you guys help me here? what did i miss or do wrong? pls dont hate me much im just a noob.

geno93n0 said:
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Click to expand...
Click to collapse
ah finally had the time to modd my docomo tab, heres what happened, fashing the pit file went ok, but flashing the rom went haywire ended up brick. i did everything to the letter but to no success. i manage to unbrick the tab and redo the whole thing but i always end up bricking it. rom fails to flash. any ideas? should i be rooted in froyo before doing this?

ah finally after countless trial and error finally updated my tab to gingerbread, now next step is to root and install clockwork recovery mod. i will not rst until my tab gets the lates jellybean rom hahahah,