Database Develop

UK Galaxy S Help please?

Basically, in all of my wonderful wisdom, decided to try and root my Galaxy S thinking it would be a similar process as to that of the HTC Desire on the ground that I was sick of the way Orange have changed the phone.
Several methods here didn't work so I decided to play about with Odin. I ended up in a boot loop and have now managed to install a US T-moblie OS for a Vibrant handset. Does anyone have any idea how to rectify this horrific balls up? Or where I can get a UK OS from to put back on it? Also I have failed to root the phone.

now seems to be good time to install gb with cfroot kenrel

I know I'm a complete novice and I'm sorry for that, but could you/show or link me to a tutorial of that at all please?

Dave Dave Dave Dave Dave. What have you done?
Don't worry mate, check out the ezbase thread in development section. Full instructions and downloads included. Should sort you right out.
Happy flashing.
Sent from my GT-I9000 using XDA Premium App

So far so good, just lacking the room as I have no idea what I should download.
Any idea?

Dave759 said:
So far so good, just lacking the room as I have no idea what I should download.
Any idea?
Click to expand...
Click to collapse
Probably best to go for rom kitchen jvh - stable, customisable and great help from the users in the thread. Once you've a bit more experience with sgs flashing, then insanity all the way.
Hope it all goes well mate.
Edit: dave, have you flashed the gingerbread base rom from the ezbase thread yet?
Sent from my GT-I9000 using XDA Premium App

I couldn't tell you where I'm at. All I've done is follow the steps, downloaded EZOdin V1.70 and this;
Repartition is not mandatory, but it does not hurt to repartition the phone.
Start Phone in Download Mode (No Cable Attached)
Open EZOdin.
- Check Re-Partition
- Select EZbase.pit as PIT
- Select EZbase-PDA-XWJS3.tar.md5 as PDA
- Select EZbase-PHONE-XXJVE.tar.md5 as PHONE
- Select EZbase-CSC-XXJV1.tar.md5 as CSC
checked everything it says and pressed start. The message box is up to;
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
and has been that way for a good 10 minutes.

this is very strange,anyway
1- did u install kies as its important for the sake of the drivers
2- did u check/tick the 3 boxes in odin
3- if the 2 above are checked try changing the usb port or the computer
keep me informed m8

I think that's the froyo 2.2.1 ezbase base. On the first page, there should be a jvb (I think) ezbase download.
10 minutes is too long, pull battery, disconnect usb, close ezodin, reopen, re-add files, go to dl mode on phone, connect usb, wait for yellow light in ezodin, press start.
Sent from my GT-I9000 using XDA Premium App

Dave, if you want to pm me your home number, i can call you to talk you through it.
Worst case scenario is a flash of eclair jm9 - will sort 99% of snags.
Sent from my GT-I9000 using XDA Premium App

Do you have 3 button combo?
If so...
Download STOCK JVH gingerbread with bootloaders.
Follow instructions on JVH thread in the first post.
I would go into recovery, factory reset and format internal sd card before flashing.
Use 512.pit and repartition and use odin.

http://forum.xda-developers.com/showthread.php?t=1011901
Download this...
http://www.multiupload.com/INQRN37ODA
You can get odin and 512 pit from samfirmware.com
Then when you have a working phone you can root with cf-root.
http://forum.xda-developers.com/showthread.php?t=788108
And maybe install the screen off animation with battery percentage...
http://forum.xda-developers.com/showthread.php?t=1055979
This is the link to $omator's file for JVH...
http://forum.xda-developers.com/attachment.php?attachmentid=591847&d=1305015870

In my opinion, just get a stock JVH ROM from Ramad
Get it here
Run the .exe and the 3 files will be unpacked.
Try using Odin 1.3 to flash. I had problems with the phone not booting when I used 1.7
I'm using a 513 Pit so that's what I recommend. 513 was made a day after 512 so it makes me think it may correct some problems as no one knows the full theory behind Partition Information Tables (PIT) files.
When the phone boots for the first time, go into the phone dialler and put in the code below to factory reset the phone. This seems to cure issues that may occur if you just start using the phone as normal.
*2767*3855#
Good luck and post back if you have problems.

goodluck dave

Flashing in Odin always fail - no recovery

So I know I am not perfect at this, but I also am not new at it. I have reached an impass and am reaching out to the vast experience that is XDA. I was running on GB just fine and decided to flash a new kernel through SGS kernel flasher, bootloop, couldn't for the life of me get into recovery. So when I got home I tried to flash a new kernel through Odin, fail. Anything else I try to flash now fails. I don't know what to do or try, I can still get into dl mode, but definetly not recovery or even boot up now.
Please help as I don't think samsung will fix it as it is.

Try flashing with EZbase. Its a preconfigured set of files for flashing in EZodin. Meant specifically for recovery
http://forum.xda-developers.com/showthread.php?t=991792&highlight=ezbase

Kops said:
Try flashing with EZbase. Its a preconfigured set of files for flashing in EZodin. Meant specifically for recovery
http://forum.xda-developers.com/showthread.php?t=991792&highlight=ezbase
Click to expand...
Click to collapse
It is still failing to flash even through EZBase. Usually as soon as Firmware update starts it says Complete(write) operation fail.

Have you tried flashing with sd and sim removed?
GTi9000 insanity cm012/glitch

slaphead20 said:
Have you tried flashing with sd and sim removed?
GTi9000 insanity cm012/glitch
Click to expand...
Click to collapse
Still nothing but fail

Maybe try an older or newer version of Odin depending on what version your using, or try Heimdall. And try re-downloading all the files including odin, they maybe corrupt?And lastly try reinstalling the USB drivers. Hope something there works

Shrapnel2 said:
Maybe try an older or newer version of Odin depending on what version your using, or try Heimdall. And try re-downloading all the files including odin, they maybe corrupt?And lastly try reinstalling the USB drivers. Hope something there works
Click to expand...
Click to collapse
+1
agreed! best advice.
Leave battery out for 5-10 mins, redownload files as suggested, install on pc, odin 3.1 shouldn't present you with any problems so try that.
If you're getting into dl mode you WILL be able to flash.

J 3 M said:
+1
agreed! best advice.
Leave battery out for 5-10 mins, redownload files as suggested, install on pc, odin 3.1 shouldn't present you with any problems so try that.
If you're getting into dl mode you WILL be able to flash.
Click to expand...
Click to collapse
Ok i have been trying odin 1.7 and ezbase maybe i will get odin 3.1
Edit: whoa where can i find odin3.1

Odin failure may suggest a faulty USB port or USB cable,try using a different port to flash n if that does not work a different cable.. and it's also a possibility that the downloaded rom may be corrupted so download a new clean stock rom from SamFirmware.com ..hope this solves your issue!!
Sent from my GT-I9000 using XDA Premium App

doomsdaycs said:
Odin failure may suggest a faulty USB port or USB cable,try using a different port to flash n if that does not work a different cable.. and it's also a possibility that the downloaded rom may be corrupted so download a new clean stock rom from SamFirmware.com ..hope this solves your issue!!
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Well i did try to just flash a pit file and it worked. Also i tried different files and none worked.

So i think its toast. It wont charge and its deadnso no more dl mode. Thanks you all for your attempt at help for my sirry ass.
Edit: got it going by leaving the battery out for a while. Still no charging available though.

joelhon said:
Ok i have been trying odin 1.7 and ezbase maybe i will get odin 3.1
Edit: whoa where can i find odin3.1
Click to expand...
Click to collapse
use ezodin, which comes with the ezbase rom, read the instruction thoroughly, it is wonderfully simple....another classic from Nitr8.....and let me know how you get on......ezbase has full graphic walkthrough instructions too atb

slaphead20 said:
use ezodin, which comes with the ezbase rom, read the instruction thoroughly, it is wonderfully simple....another classic from Nitr8.....and let me know how you get on......ezbase has full graphic walkthrough instructions too atb
Click to expand...
Click to collapse
Sorry i meant that i tried ezodin and still it failed to flash.

So update time. I tried to flash jg8 jpu and jh2 all no luck. I even tried to flash just a bootloader and it failed as well. I really dont know anymore.

did you check the green confirmation screen in Odin and/or ezflash? if there is not confirmation that the application has found your device at the appropriate com port the flash won't work

klinggalaxy said:
did you check the green confirmation screen in Odin and/or ezflash? if there is not confirmation that the application has found your device at the appropriate com port the flash won't work
Click to expand...
Click to collapse
I think you meant yellow?
GTi9000 insanity cm012/glitch

I would ignore ezbase and flash jm9. If you have tried to change kernel with lagfix on, then you will need jm9. I recommend odin 1.7.
I have been in some sorry states with my phone, jm9 has always resolved any problem, even when ezbase has failed.
Sent from my GT-I9000 using XDA Premium App

klinggalaxy said:
did you check the green confirmation screen in Odin and/or ezflash? if there is not confirmation that the application has found your device at the appropriate com port the flash won't work
Click to expand...
Click to collapse
Really, are you kidding me? Do you not see my signature? Don't you think maybe I have done this a FEW times? I don't mean to be harsh, but seriously! That would be like saying make sure your computer is on before you try and flash. Make sure you take you pants down to have a sh*t. WOW! I am just a little tense and on edge right now so stupid comments are really not too appreciated. Plus it wouldn't even run if Odin didn't see your device. OMG!
UPDATE: Nothing was working so it is back to the store to have a look, fingers crossed they don't claim water damage or voided warranty for other reasons and want to charge me out the ass to fix it. Gotta love loaner phones, it's like being in the stone age.

[Q] Rooting KK4 stock not going well

I have been desperately trying to root my son's Captivate after installing KK4 using Heimdall one click. No matter what method I try, either using Odin to flash Corn Kernel 6.03 or Autoroot-Design Gears/stock KK4, I get the same message on Odin:
Added
Odin v.3 engine
File Analysis
Setup Connection
Initialization
Get PIT for mapping
Firmware update start
zimage
Complete (write) operation failed
After the failure I have to flash Heimdall again to unbrick it. I did not have this kind of problem when I rooted my cappy, but it was done with KI3 I believe, before KK4 was officially released. How can I go about correcting this, it's getting quite frustrating. I have 2 more to go after this one.
Thanks for any assistance!

I'm sure you've done this, but try using a different USB port/cable.
also you could try re downloading ODIN
If that doesn't help there's a long method to get to stock 2.3.5 with the right bootloaders which might help. If it doesn't then someone else might be better at helping you.
I've used this method when i screw things up bad many times, but it takes a lonnggg time, but it definitely works.
Try doing a one click to stock, 2.1
Then use Kies Mini, which is samsung's windows desktop application to update your software. Once you have kies mini then upgrade to 2.2, then 2.3 after. Once there you've for sure got the stock gingerbread bootloaders you should re try flashing kernels and what not. there's probably a quicker way to do it, but it's worked for me sure fire many times.
You mention that you have two more to go after your son's. I'd just use the kies mini and update them to ATT's 2.3.5 then go from there...
let me know if it works, i hope this helps.

There a way to do it need to put you phone in download mode then
http://forum.xda-developers.com/showthread.php?t=1386924 hope this helps it has bootloaders with or without it works anytime i need to go back stock already rooted and debloated
Sent from SAMSUNG-SGH-I897 using XDA

Maxmusic said:
I have been desperately trying to root my son's Captivate after installing KK4 using Heimdall one click. No matter what method I try, either using Odin to flash Corn Kernel 6.03 or Autoroot-Design Gears/stock KK4, I get the same message on Odin:
Added
Odin v.3 engine
File Analysis
Setup Connection
Initialization
Get PIT for mapping
Firmware update start
zimage
Complete (write) operation failed
After the failure I have to flash Heimdall again to unbrick it. I did not have this kind of problem when I rooted my cappy, but it was done with KI3 I believe, before KK4 was officially released. How can I go about correcting this, it's getting quite frustrating. I have 2 more to go after this one.
Thanks for any assistance!
Click to expand...
Click to collapse
Try a different micro usb/ usb cable and then flash the corn kernel...u will be surprised at how that can solve the prob.
Sent from my SAMSUNG-SGH-I897 using xda premium

Just flash Heimdall one-click Apex ROM with bootloaders. Man.

bravomail said:
Just flash Heimdall one-click Apex ROM with bootloaders. Man.
Click to expand...
Click to collapse
Tried several different cables to no avail. Researched Heimdall one-click Apex. After a little reading and You Tube video, I jumped in and kept my fingers crossed. It worked. Was then able to go to the ROM that I wanted. I am surprised that there are not more Heimdall One-Clicks out there ready to be flashed. I've had much more success with Heimdall that Odin. Thanks a bunch!

Same luck with Heimdall. Odin sux on some phones. AdamOutler rulez!

[SOLVED] Repairing bad flash i9000

[SOLVED] Read on to find out how.
For this to work you must be able to access "Download mode" and make sure that your phone is recognized by the computer.
Here's what happened:
Phone was running CM7.2 and Glitch 13.1 and I wanted Slim ICS 4.2 so what I did was: wipe user data, cache and devik cache then installed Slim ICS 4.2 through CWM and it worked.
But when the phone was trying to do the initial install after it had rebooted from flashing Slim in recovery it just restarts and loops, always about to do the initial install.
Got fed up with this and sort of rage flashed back to stock loosely following THESE instructions, but I didn't follow the instructions like I should have. What I did instead was flash my stock JVC gingerbread firmware (Orange of the UK branded) TAR file as PDA with the 20100512 PIT file in Odin3 1.87. And yes I did check "Repartition" in Odin, because the instructions I had for Hemidall said to have repartition "CHECKED".
This is the result, from 3e recovery.
--Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: getprop("ro.product.device") == "GT-P1000" ||
getprop("re.build.product") == "GT-P1000" ||
getprop("ro.product.device") == "GT-i9000" ||
getprop("re.build.product") == "GT-i9000"
E:Error in /cache/recovery/sec_csc.zip (Status 7)
Installation aborted.
So then some poo came out... but I thought if I followed the instructions EXACTLY as they were writtin these problems would all go away and I can go back to not crapping myself
I followed the instructions perfectly and I still get the same screen as written above, in 3e recovery.
So now too scared to touch the phone without some brief guidance, can someone please please help as I'd really like to be able to start testing and benchmarking ICS roms.
Thank you again XDA

You can try flashing with my recovery kit, worth trying, just download it, unzip and read the .txt first, pictorial instructions included
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium

Thank you slaphead20
My only question is: What have I done, and why will ezbase recovery kit for gb fix it?
Before trying ezbase (which is downloading now and will take 22 minutes) should I try flashing to stock like I normally would with Odin where by I just flash the one TAR file in PDA? But if you don't think it will help then I wont touch it until recovery kit gets here :/

Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone

mod2max said:
Odin can't see the phone, but Hemidall works perfectly... do I have to somehow revert the drivers in Device Manager for Odin to see my phone again?
As you know Hemidall comes with that "Zadig" drivers thing and it was after using this that Odin stopped seeing my phone
Click to expand...
Click to collapse
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Sent from my GT-I9300 using xda premium

slaphead20 said:
You may need to reinstall driver s,, not sure as I don't use heimdall, the kit I sent you is an Odin based kit, will give you a stripped down gb Rom called ezbase, there is a pit file included, and also a cf root kernel, so you should be able to use heimdall
Click to expand...
Click to collapse
Well it's 2:00AM Sunday morning here in the UK, got home a few moments ago and had a brainwave "Why not use a virtual machine to install the phone's drivers and test Odin" so I did and it works fine I will flash the recovery kit in the morning (even though it is morning... ) and let you know how it goes.

Thought I'd reinstall the drviers on my PC since it worked on the virtual machine, got Odin back
However, I set up the flash as described in EZOdin and it got to HERE and then it got stuck... been stuck for about 20 minutes now.
In the white "Connection" status box in Odin it says "Set Partition"
Phone is still plugged in, haven't seen any progress bars on the phone or any change in Odin, is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
UPDATE
Ok so got the phone removed, safely I think...
It's gone a bit funny like it did when Hemidall crashed... so no boot logo or kernel splash etc, just a white picture of a phone and dotted line connection to a pc. But I fixed that by flashing again with exact set up from the instructions for Hemidall, it got logos back and recovery etc.
But can still access download mode and and Odin sees the phone, hope is not lost
Is it worth trying to flash the files in normal Odin3? I have version 1.87. It might be a one off crash (like Hemidall's was) but I crap my self when stuff like this happens and would rather it didn't do it again

mod2max said:
is it safe to remove the phone (Hemidall would say "Hemidall crashed" but is safe to remove the phone)?
Click to expand...
Click to collapse
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again

xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Ahhh that must be what it is, upgrade mode :/
Well I got the phone out and download mode still works and Odin can still see the phone, so I'm pretty safe atm (I think.....) battery has already been removed etc.
But while download mode and Odin work I'm not doing more to the phone now, if I carry on I will actually have heart failure. So I will pick this up again later on this afternoon.

xsenman said:
Its stalled, Its Failed, but you have no option but to disconnect, which means you will be in upgrade mode or BSOD mode after you pull the plug. meaning you have to Flash again using Pit first but before that you need to remove battery, reinsert, best to remove external SD card and Sim card too.
restart odin and plug in usb cable, it might detect straight away for you to flash again
Click to expand...
Click to collapse
Could you please explain what you mean by "using Pit first"? I thought pit files go in it's space in Odin at the same time as flashing everything else (when you use Pits of course).
My current plan is, install the usb drivers on a machine that has never been touched by me, Odin or anything else. So maybe this will determine whether it is EZOdin playing up on the latest version of Windows 7... if it's not either of those then I guess that means I am no longer able to flash PIT files and am screwed.
But I will find out, fingered crossed!
Slaphead20, I've taken the PDA, PHONE and CSC files you gave me and would like to flash them in Odin3. I've stripped the files of their ".md5" extensions and now they are just ".tar" but I was wondering if this would have any bad effects while flashing? Does Odin3 take ".md5" files like EZOdin does? Is it safer to leave the files in their ".md5" format?

How it was solved:
I took the "ezbase recovery kit" that was kindly made available to me from Slaphead20 and unpacked the "PDA", "PHONE" and "CSC" .md5 files, I first removed the ".md5" extensions from the end of each file name and then used WinRAR to unload the contents of each ".tar" folder into a normal uncompressed folder for use with Hemidall.
**I did find that while unpacking these files there was two "cache.rfs" files, they are both the same but we just use one when using Hemidall.**
The reason I used Hemidall instead of EZOdin (which is supplied with the recovery kit) or Odin3 is because firstly when I tried to use the recovery kit in EZOdin, it crashed and I had to unplug the phone unwillingly (that caused "Upgrade mode"). And the reason for not using Odin3 was fear of the same.
The process:
**Make sure your handset has plenty of juice cause the last thing you want is a bad flash and then not being able to charge the batter without an external charger.**
Firstly, get your phone into "Download Mode" with the USB cable unplugged from the computer
Set up Hemidall like so...
**Make sure "Repartition" is checked and "No Reboot" is unchecked for this bit!**
Partition ID______Partitions (Files)
____0___________IBL+PBL = boot.bin
____3___________SBL = Sbl.bin
____6___________KERNEL = zImage
____11__________MODEM = modem.bin
____21__________PARAM = param.lfs
____22__________FACTORYFS = factoryfs.rfs
____23__________DBDATAFS = dbdata.rfs
____24__________CACHE = cache.rfs
After the flash is complete the phone will reboot, the first ever boot of the OS is a long one so just be patent and it will eventually (fingers crossed) load.
Q: What is it doesn't load?
A: Flash the above again until it does, or your doing something wrong -_-"
Once the phone has loaded, shut it down and then go back into "Download Mode" with the USB cable unplugged. Now, with Hemidall select the same pit file as before but make sure that "Repartition" and "No Reboot" are both unchecked, then click "Add" and select "Kernel" for the "Partition Name", browse to the "zImage" file in the "CF -Root for EZbase" folder (or similar). Plug the USB cable into the phone, click "Start" and wait for the phone to reboot, then you will have Root (+ SU) and CWM.
**If any flash you make with Hemidall stalls (fails) after you click "Start" and you have to unplug the phone it will now be stuck in "Upgrade Mode" but get into "Download Mode" and follow this guide from the start.**
Thank you Slaphead20 for this one

hi, thx for such an informative insight here...
there should be a sticky thread for such kind of issues and which would get everyone going in quick !
not sure if mods are listening to this
anyways thanks again
Sent from my GT-I9000 using xda app-developers app

Just as a heads up, all credits to
Nitr8 for the ez components
Chainfire for cf kernel
Samsung for pit file
Link to recovery kit, unzip and read.txt
http://db.tt/MOGZx01S
Sent from my GT-I9300 using xda premium

dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?

banana_plug said:
dude, ive had similar problems, due to this thread i was able to fix, and get my phone running. now ive got one small problem left. cwm wont flash. im stuck on 3e recovery, when i try to flash update.zip, it fails, and obviously i cant update to different rom with that. any hints on how to get cwm on it? and how do u generally get cwm when using that recovery pack?
Click to expand...
Click to collapse
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium

slaphead20 said:
flash the cf kernel as pda in Odin, no repartition....for crying out loud there's a pictorial guide with screen shots of Odin loaded up....:banghead::banghead::banghead::banghead:
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?

banana_plug said:
now guess what? i did flashed CF kernel. guess does it load CWM afterwards? no. 3e recovery loads up instead. it actually failed for the first time (when flashing in ezodin as pda) the second time it was flashed right. but no CWM. was following tutorial step by step. im sure i was doing exactly whats stated in it. any ideas my dear ?
Click to expand...
Click to collapse
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium

slaphead20 said:
did you flash as a separate step from the ez base flash?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.

banana_plug said:
dude, youre absolutely right. as a separate step. been through google for hours, untill now its unsolved for me. 3e recovery stays in.
Click to expand...
Click to collapse
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium

slaphead20 said:
try a new download of the kit, no one, and I mean no one, has ever had that before
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
yes. you probably understand why im actually posting here. i nearly never post, not because im a techie, im a total noob, its just that im good at research, and i dont like to bother others. but at this point im pretty tired. will go thru the procedure again (third time) and see what happens. ****ing 3e recovery!
p.s correct me, replacing the kernel with CFROOT one from the pack, should automatically flash CWM? if thats the case, i might go and find another kernel with such capabilities, am i on a right path? p.s when i get rich, ill donate to you a beer ;D

[Q] Need help with un-rooting & going back to Stock ROM

I have been trying to un-root my tab 8.9 since Monday without any success, have tried quite a few things, also downloaded stock ROM from here http://forum.xda-developers.com/showthread.php?t=1582943 & tried flashing with Odin but could not as once i put my tab in download mode Odin keeps saying Added!! & Removed!! the next instant; i am not sure what to do & how, can anyone help please!

Download the stock rom from sammobile.com for your device. It'll be a zip file. You'll need to extract the .tar.md5 file from it. Use 7-zip to do that. The .tar.md5 file can then be used in Odin. Browes to it from PDA in Odin. This should return you to stock.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
Download the stock rom from sammobile.com for your device. It'll be a zip file. You'll need to extract the .tar.md5 file from it. Use 7-zip to do that. The .tar.md5 file can then be used in Odin. Browes to it from PDA in Odin. This should return you to stock.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i am unable to connect/detect my device with Odin!!! it keeps saying added!! removed!! irritated!!

That's not good. Did you get the right rom for your specific tab? If you used the wrong one you've probably bricked it.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
That's not good. Did you get the right rom for your specific tab? If you used the wrong one you've probably bricked it.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i did i did! the device is working fine, all i want is to take it back to the condition it was when it came in a box!!

If the device is still working then it's probably the usb port. I can get one of my computers to recognize my device with Odin but not the other. Try different usb ports and if that doesn't work try another computer if you can. Also make sure you have the usb drivers installed. You can do that by installing kies on your computer.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
If the device is still working then it's probably the usb port. I can get one of my computers to recognize my device with Odin but not the other. Try different usb ports and if that doesn't work try another computer if you can. Also make sure you have the usb drivers installed. You can do that by installing kies on your computer.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i did buddy, i tried it on all 4 USB ports, have kies installed, installed drivers again!! will see on the other laptop too!