I got a i9000m from a friend of mine to try an fix. It boots to Logo and reboots over and over
I am able to get it to download mode with 3 button and Jig
I Odin flashed it to:
Stock 2.3.3 with stock kernal as well as 2.3 and 2.3.6 stocks
darky recovery 10.2 with pit
With and without repartition used.
I can always get into Download mode but there is no recovery despite kernal used - whether stock or CWM -
Bootloader is a question mark since i havent played with it yet...
Im just looking for some solution here...
I hope I dont have a busted internal SD card - that would suck...
Anyone with other solutions?
Thanks
Rico
iamrico00 said:
Anyone with other solutions? Thanks
Rico
Click to expand...
Click to collapse
Try flashing a semaphore.tar kernel, http://forum.xda-developers.com/showthread.php?t=1112908
Just tried It - No dice - it stool loops at After logo pops up - Any other ideas?
Rico
iamrico00 said:
Just tried It - No dice - it stool loops at After logo pops up - Any other ideas?
Rico
Click to expand...
Click to collapse
Try and get a hold of Stock Gingerbread JVZ firmware with individual files (including bootloaders)
1. Select PIT (usually 512) ( Check Partition)
2. Select BOOTLOADER (APBOOT)
3. Select PDA (CODE)
4. Select PHONE (MODEM)
5. Select CSC (CSC)
also If you can get a hold of param.lfs , dbdata.rfs and cache.rfs, that would make it a complete fresh setup
Thanks - I got ahold the JVZ stock rom with boot loader and updated as you said but it still shows the logo and loops - no CWM or recovery.
Im not sure what param.lfs , dbdata.rfs and cache.rfs are .. or how they are used ... ?
I appreciate your help guys ... any other ideas?
Rico
iamrico00 said:
Thanks - I got ahold the JVZ stock rom with boot loader and updated as you said but it still shows the logo and loops - no CWM or recovery.
Im not sure what param.lfs , dbdata.rfs and cache.rfs are .. or how they are used ... ? I appreciate your help guys ... any other ideas? Rico
Click to expand...
Click to collapse
number of other options , like Ezbase and rescue kit, links on my signature "Collections"
The latest version of Ezbase I could find is 2.0 - the 4.0 on the page is outdated and down - the 2.0 still doesnt work - it just continues the logo loop
I just tried the rescue kit for i9000 from your collections link and it uploaded everything just fine - image - kernal - data - the ifs stuff from the previous post but still - it just continues in the logo loop...
I tried the Dark rom rescue and it changes the boot logo to say darky rescue but then it reboots afterward... Im stuck
Rico
Anyone with good ideas?
-Rico
iamrico00 said:
Anyone with good ideas?
-Rico
Click to expand...
Click to collapse
You can't get into CWM,? so you must be able to get into 3e or 2e recovery,
1) try getting into it and doing a complete wipe before Flashing, also remove sim card as well as ext SD card before flashing
The issue must be bootloader or boot order... I dont think it gets to firmware processessing ... This is what I have done for i9000m:
flashed:
Stock KC1 - phone, cdc, pda - WITH BOOTLOADER on and repartition checked . this is the latest STOCK firmware for this device
rebooted directly into download mode (as letting it reboot normally is just the same boot loop)
Then flashed speedmod-kernel-k13e-500hz - which is the latest speedmod kernel with CWM
Rebooted into Logo loop again - i9000m then changes to i9000 and reboots
Then I tried
Stock JW4 with CF-root 4.4 JW4 and still boot loop i9000
I cant seem to get to just pats the boot logo to initiate kernel - hence it wont allow to enter CWM
I just tried:
Stock KC1 and Voodoo kernel Froyo (froyo stock) and same as before
Im stumped here guys...
Rico
went back to stock on everything - stock kc1 froyo with stock kernel and tried Darky's Recovery 10.2 -
Still a boot loop ... although it states i9000 with samsung at bottom then changes to i9000 Darky's recovery... if that helps anyone...
sim and sd removed
Rico
iamrico00 said:
The issue must be bootloader or boot order... I dont think it gets to firmware processessing ... This is what I have done for i9000m:
flashed:
Stock KC1 - phone, cdc, pda - WITH BOOTLOADER on and repartition checked . this is the latest STOCK firmware for this device
rebooted directly into download mode (as letting it reboot normally is just the same boot loop)
Click to expand...
Click to collapse
Repartitioned should only be checked If you are using a PIT file, Suggest you use a stock ROM and Stock kernel meant for i900M with PIT, Bootloader, and get it booting up once its OK, than you can try using a kernel with CWM
suggest you also remove sim and ext Sd card before flashing
Ive done repartition with PIT only and on stock rom - the kg1 i9000m - with stock kernal. It comes with stock bootloader as well.
It still gives me the boot loop, so i try installing over it a CWM kernel to see if I can get into recovery and no go.
I never had a sim or sd card in the phone ...
I use PIT 512 ... is there a different one I should be using? I didnt think so...
Rico
iamrico00 said:
Ive done repartition with PIT only and on stock rom - the kg1 i9000m - with stock kernal. It comes with stock bootloader as well.
It still gives me the boot loop, so i try installing over it a CWM kernel to see if I can get into recovery and no go.
I never had a sim or sd card in the phone ...
I use PIT 512 ... is there a different one I should be using? I didnt think so...
Rico
Click to expand...
Click to collapse
there is an 803 Pit for Galaxy S, not sure which models use this
done it - tried it and still its just in a boot loop....
Im usually pretty decent with this techie stuff but this time ... i think im gonna have to admit defeat ...
Thanks Guys for all your help,
Rico
Related
I have been trying to flash my GT-I9000M using the JL2 ROM and .512 PIT file, but after Odin runs "param.lfs", the phone disconnects and it says "Removed!!". At that point, the phone tries to boot up and is in an endless loop with the "GALAXY S Samsung" screen flashing. Anyone have any suggestions? I'm dead in the water.
During this last attempt, the device was "Removed!!", but then "Completed" and "All threads completed (succeed 1 / failed 0)" appeared, but the phone is still doing the endless loop and not booting up. Ugh.
Not sure, but I don't think you need to use the pit file. If still not working try a different ROM.
I'm using ODIN. Doesn't ODIN require a .PIT file?
I've tried 3 different ROMS with the same result, with and without the .PIT file.
My Galaxy S has the same problem, but i wasn't flashing anything. I will just get a new one next week. I bought it just 6 days ago
craichead said:
I've tried 3 different ROMS with the same result, with and without the .PIT file.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=818556
Block 2 method via Odin flash back to Eclair then upgrade .
jje
JJEgan said:
http://forum.xda-developers.com/showthread.php?t=818556
Block 2 method via Odin flash back to Eclair then upgrade .
jje
Click to expand...
Click to collapse
Just tried this...same result.
I should mention that this phone is a Bell Vibrant from Canada.
I had this issue with my phone as well.
I was able to get it working again by flashing XXJPY via odin with repartition checked. Then immediately going back into download mode and flashing UGJL2 without repartition checked.
Edit: I used Odin v1.3 and 512.pit
Try this and let me know how it works.
MiKE431 said:
I had this issue with my phone as well.
I was able to get it working again by flashing XXJPY via odin with repartition checked. Then immediately going back into download mode and flashing UGJL2 without repartition checked.
Edit: I used Odin v1.3 and 512.pit
Try this and let me know how it works.
Click to expand...
Click to collapse
What happened after you flashed XXJPY? Did it still endlessly cycle on the Galaxy screen? Mine does that as soon as the flash supposedly completes.
JPY on its own would not boot (w/ repartition)
JL2 on its own would not boot (w/ repartition)
The only way I got my phone to work was to flash JPY (w/ repartition) and then JL2 (w/o repartition).
MiKE431 said:
JPY on its own would not boot (w/ repartition)
JL2 on its own would not boot (w/ repartition)
The only way I got my phone to work was to flash JPY (w/ repartition) and then JL2 (w/o repartition).
Click to expand...
Click to collapse
Is your phone a Bell Vibrant (GT-I9000M) from Canada?
Yes. Approx a week old (a replacement for dead internal sd issue)
I don't know what I'm doing wrong. I tried your suggestion but got the same result. I don't know if this makes a difference, but the ROMs I got are USA ROMs from samfirmware.com. They didn't have any listing for Canada.
download UGJH2 and flash it without "phone bootloader update", without pit and no partition.
then flash UGJL2 with "phone bootloader update", without pit, and no partition.
Congrats, your phone works again.
People need to stop using Pit files/partition. It doesn't do anything other than wipe everything from the nand and cause weird issues like this.
Electroz said:
download UGJH2 and flash it without "phone bootloader update", without pit and no partition.
then flash UGLJ2 with "phone bootloader update", without pit, and no partition.
Congrats, your phone works again.
People need to stop using Pit files/partition. It doesn't do anything other than wipe everything from the nand and cause weird issues like this.
Click to expand...
Click to collapse
just tried your method and I'm saddened to say it didn't work... at least no for me ): can i be doing something wrong? perhaps i flashed them in the wrong section? *sigh* im running out of hope for this phone...
Electroz said:
download UGJH2 and flash it without "phone bootloader update", without pit and no partition.
then flash UGLJ2 with "phone bootloader update", without pit, and no partition.
Click to expand...
Click to collapse
For the second ROM, do you mean UGJL2? There is no UGLJ2 ROM that I can find.
Electroz said:
download UGJH2 and flash it without "phone bootloader update", without pit and no partition.
then flash UGLJ2 with "phone bootloader update", without pit, and no partition.
Congrats, your phone works again.
People need to stop using Pit files/partition. It doesn't do anything other than wipe everything from the nand and cause weird issues like this.
Click to expand...
Click to collapse
I just tried your method and it did not work. I have the same issue.
I had the same problem on 4 of these handsets (GT i9000m, aka Bell's "Vibrant") and none of those 4 were ever flashed or modded. The problem apparantly lies in a bunch of corrupt internal SD cards that got shipped to Canada. In any event, if you're still within your DOA period, you should probably just get a replacement.
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Best option for bell users is darkys rom. For further info check darky's rom info
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the <3e> recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Lyon huntington said:
I messed up my Bell SGS playing with odin.
Lost the 3 button options and ended up hacking a jig to get it into DL mode. done
Goal - a Functioning phone. Now what?
Thinking I should odin the I9000M_JL2_JL2_JL2_JL2_UG_BMC.tar.
But with or without repartition?
Can I use any 512pit?
I think repartitioning is where i messed it up.
Now all of this happened because I wanted seeARMS.JL2.v0.4 but couldn't update with the recovery mode.
Knowing that seeArms is my second (first?) goal, is there a different firmware I should flash something other than BMC to give me back update functions, but stable to resuscitate my phone?
There's ages of material here and I don't want brick my phone or waste time, I've done enough of that by myself.. now I'm looking for some expert opinion.
thanks
Click to expand...
Click to collapse
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
repartition yes? .pit universal?
Jason123420 said:
Flash the stock JL2 firmware with Odin the use super one click to root your phone then flash a new kernel with SGS Kernal flasher from the market... then u will have clockwork recovery then wipe and flash seeArms! Its a great rom but not as fast as darkys
Get the stock firmware from samfirmware.com u can get the .pit file from there to
Sent from my bell GT-I9000m using XDA App
Click to expand...
Click to collapse
So the stock JL2 that I have is a .tar and .dll
I have a 512.pit from a beta 2.2 , are they different?
Did I mention boot problems too? Hanging @ Samsung, no splash ani.
I guess the .pit means yes on repartition?
Thanks
Just use the stock firmware and .pit from samfirmware.com and when Odin is open do not tick off repartirion... just put the .pit in it's spot and the tar in th's PDA part and flash
Sent from my GT-I9000 using XDA App
Now I'm no pro... I just flashed a rom once and got stuck in a boot loop and this is what worked for me
Sent from my GT-I9000 using XDA App
Recovery back but can't mount /dev/block/stl10
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Sorry man like I said I'm no pro... ide flash stock jl2 back and send it back to Samsung for repair maybe they will do something for your warranty
Sent from my GT-I9000 using XDA App
Lyon huntington said:
Decided to try Darkys v9.2 Resurrection.. no go.
Flashed JL2 and got recovery back but crash after animation.
3e recovery shows me Can't mount /dev/block/stl10.
some threads say dead, others make ref. to old builds.
any current ideas?
thanks
Click to expand...
Click to collapse
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
It's Alive! - Can't mount /dev/block/stl10 fixed.
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
tsinc said:
Download a full firmware for your model and locale (with dbdata in it) and flash it with repartition with the pit proposed (samfirmware.com) then, I believe, you will have a full functioning phone. If everything is ok, then flash ... whatever.
Click to expand...
Click to collapse
Yes, do this. For repartition to work the .tar has to have dbdata.rfs, otherwise it won't work.
Then flash a speedmod kernel with odin for root/cwm and flash you're favourite custom rom
unlock&root owngrade or speedmod kernel? suggestions?
Forgot to mention that all this started after I got the phone back from Bell service after SD card failure.
I know mod methods changed with the latest firmware, as I had used the update.zip method that is now unavailable.
My phone went in unlocked and rooted
the phone came back re-locked (old code doesn't work? wtf?),
and it was unrooted w/3e recovery
Can the phone unlock code change?
Will downgrading to 2.1 make unlocking easier?
or is unlocking just as simple after a speedmod kernel with odin for root/cwm
Which is better?
downgrade the firmware to 2.1 and root using the old update.zip method or speedmod kernel?
Which kernel? (link please )
cheers
Lyon huntington said:
Hey All,
Got it all working again.
Repaired: Can't mount /dev/block/stl10
the fix: A full firmware (pda/csc/phone/pit) flash w/repartition.
Flashed w/repartition - I9000XXJP2.7p. (the only FULL firmware I had on-hand)
on reboot the system does a media check and was successful in reformatting and mounting the internal SD.
Phone didn't like the ROM and still logo of death, but..
A quick Jig into Download Mode..
Flashed I9000UGJL2_homebinary_add_param.tar with no repartition
(can't remember if I used .pit).
And Success!! my phone is alive and running 2.2
Thanks for the help, and hopefully this thread can help others.
Everyone should build/get a jig
There is nothing more awesome than being able to force download your non-booting phone.
I could not have done this repair without one.
http://forum.xda-developers.com/showthread.php?t=819551.
The only problem now is it's back to stock...
oh phone, how can I crash you next?
thanks again everybody!
Click to expand...
Click to collapse
All you did was flash UGJL2 with no repartition and it brought your phone back?
Kops said:
All you did was flash UGJL2 with no repartition and it brought your phone back?
Click to expand...
Click to collapse
You know what....I've been trying various combinations of CSC/MODEM/PIT and everything to get this phone running again.
All I did was select a FULL UGJL2, and thats IT. NO pit, NO repartition, and it worked
The best way to revive your I9000m is to first flash JPC (a three file ROM) with 512 PIT and repartition ticked. The phone will still be in a boot loop. Then flash the JL2 PDA without repartition or PIT. The best way to go back to stock! Has always worked for me. I9000m's are not the same as other I9000's and do not flash repartition and the PDA in the same flash! Good luck!
My Tab is stuck at GalaxyTab Samsung" boot screen after i try to flash Roto-JMI-v2, before i was running Overcome v1.1.2 rom and [Kernel] [EURO] [1.4ghz OC/UV] MCR EXT4 v12 and it work like a charm. But becurse i deside to sell my TAB i flash back to Roto JMI.
I flash with Odin 1.7 with success, but now it stuck at boot logo.
After that I try many other ROM and flash with Heimdal but no lock.
I have no problem to get download mode, and flash with odin and Heimdal. But I can't get into recovery mode (power+vol up)
I have try almost every solution in the Forum...
What to do next...??
Have you tried flashing kernel only? like the overcome kernel v1.0?
Perhaps that will get you ClockWorkMod Recovery back...and you can go from there.
I try it now, shall i use odin or Helmdall to flash kernel only
With overcome kernel v1.0 it fail in Odin
That's odd. Odin should flash the kernel fine.
Does it give an error? or it just says successful, but you still cannot get into CWM?
It give a error, and I still cannot get into CWM, shall i use a pit to flash
And I have try this....
1.Get a stock rom package (any of Rotohammer's firmwares will work)
2.Get P1_add_hidden.zip attached to this post and extract the P1_add_hidden.pit file
3.Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
4.Put P1_add_hidden.pit in Pit slot
5.Check repartition box
6.Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
7.After this, the Tab will reboot normally. Shut it down and return to download mode.
8.Open Odin 1.7 and reconnect the Tab.
9.In the PDA slot, choose the Overcome Kernel v2.0 tar file for use with Odin. Press start
10.It will flash the kernel then reboot. Upon reboot, you should hear the sexy robot voices informing you of the status of the EXT4 conversion.
11.Once done, the Tab will boot normally. At this point you can load Overcome v1.2.2 rom (or any other Rom of your choosing)
12.NOTE - Overcome 1.2.2 includes v2.0 of the kernel, so no reflashing is required after install.
Hi,
I try this from Samsung stock ROM P1000JK5 and i stuck on the Samsung boot imge. Can i only upgrade to kernel 2 when i have a JM* (Rotohammer rom?)
This is very weerd, other with some god solution
NN1123 said:
This is very weerd, other with some god solution
Click to expand...
Click to collapse
You are correct - he needs to repartition the sd card, using the .pit file because it was formatted to ext4.
Your steps are great! I do them one at a time with a reboot between each one.
sreins said:
Hi,
I try this from Samsung stock ROM P1000JK5 and i stuck on the Samsung boot imge.
Click to expand...
Click to collapse
Oops - if you got your rom from samsung you have a locked bootloader. You can continue to flash those updates, or you can use a patch to remove the lock, then you can continue on.
Can someone please paste the link to the patch?
how about the Verizon gtab...
same thing is happening to me on the galaxy tab from verizon... samsung says to send it.. but i dont want to wait two weeks without my tab... thanks..
Stuck in Bootup Screen
I also have same problem,
I flashed a Rom from "samfirmware" and after it finished it stuck on bootup screen, unable to do recovery mode.
only goes to bootup screen or Dawnload .
can you guys help ?
You gentlemen have a locked bootloader. If you search the tab development forum you will find the solution. A member named Chainfire developed an app you download to your sd card, then install it, then run it, and it will move the offending bootloader. I can't get the link here - google "locked bootloader patch" or posts by Chainfire.
When it is removed, don't flash roms with the samsung kies - all those roms have the locked bootloader.
Stuck in Bootup Screen
thanks
but I can not get the tab to load in order to run any app. it is stuck in boot screen. any suggestion ?
You cannot get into download mode? That is power + volume down.
Do you know of the adb program?
stuck on bootup screen
I havent used ADB before.
any other solution?
rangercaptain said:
You gentlemen have a locked bootloader. If you search the tab development forum you will find the solution. A member named Chainfire developed an app you download to your sd card, then install it, then run it, and it will move the offending bootloader. I can't get the link here - google "locked bootloader patch" or posts by Chainfire.
When it is removed, don't flash roms with the samsung kies - all those roms have the locked bootloader.
Click to expand...
Click to collapse
how install apk boot pacth phone only samsung logo or only enter download mode how install boot patch ?
newbie comes here to learn how to flash kernel.
I have been through a mess of attempts to root my phone and put it into 2e recovery so I could install custom mods, and ended up with nothing but an old version because I had to flash it on to be able to use it.
I'll try to explain the process.. first I had 2.2 firmware with JPC, was rooted already with superuser and then I tried to flash it into 2e recovery but when it finished the phone booted up, got in the main screen where you swipe the screen to unlock but got stuck there after a couple seconds, started vibrating randomly and shut down.
After that happened I flashed an original i9000 tar on it and it came back to life, unrooted and in JP6.
The first time I tried to flash it into 2e I forgot to run odin as an admin, so I thought that was my mistake so I went ahead and tried it again with a JP6 version and ran odin as admin, but the same exact thing happened... gets stuck in the same place so I flashed the original again.
I'm on a EU Galaxy S I9000 JP6 Froyo.
Anyone have an idea what I'm doing wrong?
SmokeyFish said:
I have been through a mess of attempts to root my phone and put it into 2e recovery so I could install custom mods, and ended up with nothing but an old version because I had to flash it on to be able to use it.
I'll try to explain the process.. first I had 2.2 firmware with JPC, was rooted already with superuser and then I tried to flash it into 2e recovery but when it finished the phone booted up, got in the main screen where you swipe the screen to unlock but got stuck there after a couple seconds, started vibrating randomly and shut down.
After that happened I flashed an original i9000 tar on it and it came back to life, unrooted and in JP6.
The first time I tried to flash it into 2e I forgot to run odin as an admin, so I thought that was my mistake so I went ahead and tried it again with a JP6 version and ran odin as admin, but the same exact thing happened... gets stuck in the same place so I flashed the original again.
I'm on a EU Galaxy S I9000 JP6 Froyo.
Anyone have an idea what I'm doing wrong?
Click to expand...
Click to collapse
do you want to stay on 2.2.1 or want to switch to GB...
if you can still get into dowloadmode (vol down / home / power)
froyo XXJPU : http://dl.dropbox.com/u/19506141/Stock - stock modems/I9000XXJPU (2.2.1).exe
GB XWJVH : http://dl.dropbox.com/u/19506141/Stock - stock modems/GT_I9000_XWJVH_XXJVO_NEEJV3_Sbl.exe
flas with odin : http://dl.dropbox.com/u/19506141/flash en drivers/Odin_+_pit.exe
PIT512 file is included, both firmwares come with safe bootloaders.
flash files with repatition checked.
and if you need them samsung drivers for PC :
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
for rooting your phone you can use
froyo : http://dl.dropbox.com/u/19506141/speedmod-kernel-k13e-500hz.tar
GB JVH :http://dl.dropbox.com/u/19506141/Gingerbread-GT-I9000-XWJVH-stock-kernel+hacks.tar
flash in PDA using odin.Do NOT check repartition....
Thanks for the reply..
I don't want to make any mistakes, as im quite new to this phone and hacking/updating/putting new **** on it, so can you be a little more clear on the steps to take? I'm obviously going to upgrade to GB...
I can get into download mode fine, do I flash the 512 PIT file and the PDA_XWJVH_Sbl.tar.md5 file together? also just to make absolutely sure because I heard the partition thing can brick my phone, should it be checked for this particular flash?
SmokeyFish said:
Thanks for the reply..
I don't want to make any mistakes, as im quite new to this phone and hacking/updating/putting new **** on it, so can you be a little more clear on the steps to take? I'm obviously going to upgrade to GB...
I can get into download mode fine, do I flash the 512 PIT file and the PDA_XWJVH_Sbl.tar.md5 file together? also just to make absolutely sure because I heard the partition thing can brick my phone, should it be checked for this particular flash?
Click to expand...
Click to collapse
You should only use the repartition option when flashing a 3 file firmware. You can get them from samfirmware.com. The JVB firmware has all 3 files so I would download it.
Once downloaded open Odin and stick the files in the required fields. Insert your .pit file and select repart.
Once you have booted in to JVB you can then flash JVH using Odin in the PDA field with NO repartition.
Once booted into JVH I would use CF Root kernal to get root access
Go to insanity thread and check out the link to Ezbase rom, its a cinge! Noob too!
Sent from my GT-I9000 using XDA App
slaphead20 said:
Go to insanity thread and check out the link to Ezbase rom, its a cinge! Noob too!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yes i second that,,got me ouy of trouble a few times
Hello and sorry bad english!
I have a problem that I can't flash back a stock Gingerbread rom with Heimdall. I'm now using CM7 and I would like to test new Overcome.
I followed closely Overcomes's guide when trying to install GB_Stock_safe_v3. I put mr.pit (with 'repartition device'), factoryfs, zimage, modem etc. to the right place and started installation. Everything went well and without any errors. Tab starts booting well, goes over the Samsung logo, but stops when the "android" logo appears on the screen. I waited for half an hour but it didn't make progress any further.
I tried also Chainfire stock 2.3.3 rom as the same results, it won't boot.
I flashed CM7 back with Heimdall and all went well and Tab booted OK. CM7 is now the only rom that boots on my Tab. Before installing CM7 I had stock 2.3.3 in, but after CM7 they have not worked anymore.
Is there problem with CM7 ext4 conversion or what?
Thanks.
Edit: pretty interesting that after CM7 flashing all my settings, themes, programs, etc. returning back to the same state as before. So flashing the stock 2.3.3 did not delete/wipe any data even though I put mark and correct filepath to repartion device/ mr.pit, pda, zimage, param, boot, sbl, cache, dbd and modem boxes.
try it using odin 1.7 it should have also came in the stock safe.
After Chainfire's stock 2.3.3 you should flash dbdata.tar. That solves the stock on samsung logo problem,usually I should add.....
bongski55 said:
After Chainfire's stock 2.3.3 you should flash dbdata.tar. That solves the stock on samsung logo problem,usually I should add.....
Click to expand...
Click to collapse
When flashing Heimdall there must be all the files in use if "repatition device" is enabled. Chainfire does not have a dbdata file in his .tar package. What dbdata I should use?
Tabulous said:
try it using odin 1.7 it should have also came in the stock safe.
Click to expand...
Click to collapse
Ok, I think that this is the only way. Too bad I do not have Windows on my computer Maybe I need to borrow Win laptop.
With Froyo Heimdall worked always fine.
jykke78 said:
When flashing Heimdall there must be all the files in use if "repatition device" is enabled. Chainfire does not have a dbdata file in his .tar package. What dbdata I should use?
Click to expand...
Click to collapse
Here look on the post no.1: http://forum.xda-developers.com/showthread.php?t=1073854
bongski55 said:
Here look on the post no.1: http://forum.xda-developers.com/showthread.php?t=1073854
Click to expand...
Click to collapse
So I flashed that "attached dbdata file" on the 1. post as dbdata (repartion enabled) and after successful flashing I flashed that same dbdata file as PDA (no repartition). That's how I understand these instructions:
- "- Flash dbdata.tar as PDA (NO repartition)"
Well, no booting after that. Boot stops when the first "galaxyTab" logo appears. Earlier the boot went further.
I give up now. I think I have to use Odin. Luckily the CM7 still works fine . I stick to it.
thanks anyway