Database Develop

[Q] Can't root Bell i9000M

Hey,
First of all, I tried to find the answer tot he problem in the forums before posting but I was unsuccessful.
I am having some trouble rooting my Bell i9000M. It came with Froyo when I recieved it. I tried androot, z4root, and SuperOneClick but they all failed. In my forum research I came across some comment that said z4root does notwork with the UGJK4 version.
I am restricted to 2 computers, a Mac and a laptop running Ubuntu Linux, so it'd be difficult for me to use Kies for anything.
What is my next step in rooting the phone?
I also tried to flash a kernel, which I read I can do without root access usining heimdall but this error occured: unknown required load command 0x80000022.
My phone is able to do into 3-button recovery and download modes.
Thanks in advance for your help.
Alex.
edit: spelling

Upgrade to Jl2 use superoneclick it works.
Sent from my GT-I9000 using XDA App

have done a lot of reading over the last week trying to work out how to root my SGS i9000M, checking both these forums as well as android & phandroid, as well as googling the issue and trying the Market. I've also checked out many youtube videos on this topic but they seem out of date now. I note the most recent thread on here by liv4air (march 2011) but it doesn't really help with my query.
I am a total noob with regard to this - only heard about rooting a couple of weeks ago but I definitely like the idea. My 1st handset had to be replaced due to a sound issue (it had 2.2 Froyo) - was replaced with a handset sourced for Canadian market (linked to Bell - has lots of stock apps from them that are useless to me). I'd like to get rid of them to start with, but this handset is running Eclair 2.1 - didn't realise this for awhile after it was replaced and didn't actually understand the differences between the builds and firmware.
So now i've got GT-i9000M, Eclair.UGJH2
kernel [email protected] #2, firmware version 2.1-update1 (updated via Kies).
I have tried the one click root download which put the 'update.zip' file on my SD but when I tried to install this in the recovery mode (have discovered that I have the download and recovery mode buttons - also totally new to me!) there was a red error message:
E:Error in /sdcard/update.zip
(status 7)
Installation aborted.
Have seen the Ryan ZA OCLF in Market too, but understand that the 'rooting' ability has been removed from that app.
Have downloaded the Odin3 program to maybe try to root it via this method but am confused about how to get kernels/which ones to get...or even if that's what I have to do! can find various kernels etc at SamFirmware but not really sure how to use them.
Am I even close to working out how to root this phone!?
Please help!

Flash EZbase : http://forum.xda-developers.com/showthread.php?t=991792 with odin. All the instructions you need are over there.
It's a complete, stock rom except for a few modifications (such as root and cwm recovery), you can choose to download froyo or gingerbread depending on what you want to flash next, if you do.
(Froyo is the 2.2 android OS that has more stable custom roms/kernels while Gingerbread is the new 2.3.3)
Also since you're on a i9000m, you may want to flash a "i9000m" modem (with the 850mhz band) found here: http://forum.xda-developers.com/showthread.php?t=876391 after flashing, but it's not necessary.

Thanks for that link - it looks promising so i'll read through it properly and give it a go soon. I can't query to that forum as it's a development thread but a couple more queries...just want to make sure i don't do anything stupid!
The instructions state: Download all the EZOdin, EZbase CSC, PDA, PHONE and PIT if you do not have Samsung Kies installed, The Samsung USB Drivers will be required to.
Do you know if this means to download ALL those things if I don't have Kies installed, or just PIT if I don't have Kies installed? I do have Kies installed so not sure which of the above I require.
And on the Kies topic, it also states: If Samsung Kies is used please make sure you kill all Samsung Kies related services that are running (kies, tray agent, etc.)
sorry if i'm making you smack your head in disbelief at my ignorance, but does this mean I can use Kies to flash a kernel to my phone (and hence not need the above)...or that when using EZOdin to flash my phone, I need to make sure I have Kies completely shut down during the process?
And I assume by having Kies on my PC, I do not need to download the samsung USB drivers.
Thanks!

What the first sentence means is that you will need the usb drivers if Kies is not installed. There's a period missing I guess.
For the second one, it means you need to close Kies completely before flashing.

Thanks!
Got EZOdin, and the PDA/PHONE/CSC files, but when I click on the EZBase pit file this is all that's written on the page it opens:
v˜4
Edit: don't know why the rest of my post wouldn't complete above, but no luck in downloading the EZOdin.pit file, either at home (or now here at work).
Any thoughts? Reiterating my noob knowledge (or lack thereof) - I assume the .pit file is crucial to the process? Is there anywhere else I get this file, or another .pit file that will suffice?
Maybe i'll do some reading on PIT....

Rooted successfully!
been a bit of a task over the last fortnight trying to work out the ins & outs of rooting, the ways to go about it and to find a method that worked, which i've finally done.
this is really just a post in case anyone in a similar position and feeling as lost as i was along the road to discovery might benefit from how i managed it.
(and this assumes you've already read the many disclaimers out there about bricking your phone, & making sure you do a lot of reading of the threads on this topic)
i ended up using shortfuse superoneclick. got the program from shortfuse.org - v1.9. i downloaded it and ran it with my anitvirus turned off. It worked fine as per the instructions on the website (shortfuse.org) or in the thread here.
Bell Galaxy Vibrant i9000M
recently upgraded from 2.1 to 2.2 via Kies
UGKC1
kernel 2.6.32.9 [email protected] #4
...now to do some proper exploring and fun!

Well done, take your time and,welcome to the world of fast galaxy s!!
Sent from gt i9000 insanity 8.5/fugumod

see these instructions: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
good kernel, root, cwm and excellent, clear instructions

lgsshedden said:
see these instructions: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html
good kernel, root, cwm and excellent, clear instructions
Click to expand...
Click to collapse
Now rooted and have gone and obtained TiB, Terminal Emulator, Wireless Tether and Root Explorer.
Had the speedmod kernel downloaded and was going to try to flash it to my phone via Odin as per the link you provided but wasn't sure if the kernel itself would root my phone and didn't get replies for my query about that.
So...now that i'm rooted you would still recommend flashing the speedmod kernel? I would assume mainly for the benefits of the kernel itself? Any likelihood of problems arising, having already rooted with SuperOneClick?
Thanks for your advice - the speedmod does sound good and have heard many happy reports from users.

yes it would have rooted you hence my suggestions for using it: sorry to have not been more clear
yes the speedmod kernel would be an upgrade over the stock one but my signature indicates what I use now: very fast and outstanding, not available on xda
I was never able to get oneclick to work as it was blocked on my pc, so my solution stemmed from having to find an alternate answer to a problem like yours
its fun once you get started: lots of help, even more opinion!

URGENT ATT Captivate Rogers Help ROM

I posted in another section but there were no replies. Here's another one: (Sorry)
Hi, I bought my Samsung Captivate in December from Rogers Canada and I decided to flash to Att Froyo 2.2 since I wanted the latest version.
Unfortunately, because I'm a dumb noob, I can't seem to root, uninstall any Att crap, or do anything. I've tried doing the root applications, but it doesnt work (gives error message on Download mode).
I really want to take advantage of my phone (hoping not to make stupid mistakes again) so it would be awesome if someone could show me how to downgrade back to Rogers 2.1, remove the ATT startup screen and upgrade to Gingerbread 2.3, step by step. This would be very appreciated.
I've left my number 7789987933 just in case if this is too complex. Thanks

kooldc20 said:
I posted in another section but there were no replies. Here's another one: (Sorry)
Hi, I bought my Samsung Captivate in December from Rogers Canada and I decided to flash to Att Froyo 2.2 since I wanted the latest version.
Unfortunately, because I'm a dumb noob, I can't seem to root, uninstall any Att crap, or do anything. I've tried doing the root applications, but it doesnt work (gives error message on Download mode).
I really want to take advantage of my phone (hoping not to make stupid mistakes again) so it would be awesome if someone could show me how to downgrade back to Rogers 2.1, remove the ATT startup screen and upgrade to Gingerbread 2.3, step by step. This would be very appreciated.
I've left my number 7789987933 just in case if this is too complex. Thanks
Click to expand...
Click to collapse
based on your post you dont want gingerbread yet, trust me on that. you should probably use kies to upgrade to the rogers froyo. or flash a custom rom that already has root and busybox and various tweeks. im using andromeda from the armani captivate rom, it's a bit of a memory hog but has all the touchwiz features working like the music player in the notification bar and lock screen and the battery life is amazing.
im not totally familiar with rooting the rogers version or flashing it to stock roger but im pretty sure root doesn't involve download mode. if you do get it rooted you can flash a kernel with cwm recovery and flash a custom rom.

No, download mode should only be used if you're flashing back to a stock rom (such as the I897UCJF6).
The best idea for you to do right now is to run the 'One click root' application that TGA_Gunnman has made.
I'll give you the steps here:
1. Download this.
2. Also install this.
3. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
4. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed....
If you use a 64-bit Windows, install this.
If you use a 32-bit Windows, install this instead.
5. Extract the contents of GalaxyS_One-Click_Root_All_Models.rar to a folder.
6. Connect your phone to your PC via the USB cable and launch the file "Galaxy_One-Click_Root.exe" file.
7. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window, and MAKE SURE YOU FOLLOW THESE STEPS CAREFULLY.
If you really do need any further help, just send me a PM... Or alternatively follow the main topic here.

first off, ATT 2.2 hasnt been released yet for captivate (supposedly later today) dont know how you flased it (supposedly). Rogers in canada released it Jan 6. you should have flashed that (rogers boy) if you were going to do stock roms. but you are flasing anyway.. there are plenty of custom roms that are stripped down stock (no bloat just like you were trying to do), or tweaked up. shoulda flashed one of them.
and the only gingerbread roms for captivate are "look a-like" not real 2.3 dont bother.
so, you obviously didnt read enough first but here.....
heres some stuff to get you back
EASIEST: Captivate AIO toolbox (rogers edition)
http://forum.xda-developers.com/showthread.php?t=944418
some info so you know what youre doing:
http://forum.xda-developers.com/wiki...96#Custom_ROMs
Rogers 2.1 stock rom
http://www.megaupload.com/?d=TT4RYLDZ
Rogers 2.2 stock roms
http://forum.xda-developers.com/showthread.php?t=905042
alternate download
http://forum.xda-developers.com/show...&postcount=673
some info if you have installed 2.2 and now have e3 recovery and are having trouble installing clockwork recovery mod, where it fails verification check
http://forum.xda-developers.com/showthread.php?t=909213
and remove your phone # dumby,

[Q] How to root Tab running vanilla Gingerbread?

Ok, so this really seems to be a school-boy question, but I'm stuck.
I've flashed vanilla Gingerbread (http://forum.xda-developers.com/showthread.php?t=1073854) onto my Tab (P1000 UK model) using the non-bootloader version, all working fine. Now I want to root it so that I can grab a copy of the kernel and crack on with some Meego development.
I've tried two methods: SuperOneClick (http://forum.xda-developers.com/showthread.php?t=803682) with the Gingerbreak method selected, it all runs (after messing about to get rid of the 7 cdcs driver using the *#7284# pda selection screen) and sits there saying "Gingerbreak running" (or words to that effect) but never stops or reboots.
I've also tried running Gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) directly from the "Start menu" after moving it across to and installing on the device with ADBD and again it just sits there and doesn't seem to do anything (after 30min or more).
I've tried this both with an SD card mounted and with it un-mounted (running Gingerbreak on the device asks for it to be mounted, running SuperOneClick asks for it to be un-mounted.) In both cases I have usb debugging turned on (presumably that is required so that ADBD is running in the background - this is obviously working ok as otherwise SuperOneClick wouldn't get as far as running Gingerbreak.
So I'm just about out of ideas as to what is wrong. Has anyone else successfully used either SuperOneClick 1.9.1 or Gingerbreak?
Next step is to grab all the necessary files (Superuser, su, etc) and try running the original Gingerbreak exploit over the ADBD shell to see if the exploit is at fault and then just install them manually.
Any other ideas?

Hmm, more reading and apparently this loophole has been closed.
Perhaps time to flash a pre-rooted kernel then, drat, was hoping to avoid messing about with Odin any more.

if you just read what the Dev said in the 1st link you pointed probably you are rooted now , and i'm not replying you with 1 eye open ...
for the holy moly , read Chainfire steps ...
one of chainfire steps ( EDIT#2: CF-Root v3.2 for JQ1 / Gingerbread has arrived: http://forum.xda-developers.com/show...&postcount=176 )after u open this link hit the 1st post with red color ,
download this CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip ..
put your tab into download mode , put the zip in odin PDA . without pressing anything or adding anything , just hit the start button on odin , 2seconds your tab will reboot , with CWM & ROOT ... good nigt

lardman said:
Hmm, more reading and apparently this loophole has been closed.
Perhaps time to flash a pre-rooted kernel then, drat, was hoping to avoid messing about with Odin any more.
Click to expand...
Click to collapse
i think you read on wrong forum or what ? ? patience is the key

For now only CF root of chainfire can root GB
Sent from my GT-P1000 using Tapatalk

The tail end of the Gingerbreak threads on this forum say that the loophole has been closed afaict.
As I couldn't get it to work after a fair bit of trying, I assumed that was indeed the case and flashed Chainfire's pre-rooted kernel (CF-root).
Does anyone have a vanilla zImage backup they could post a link to for me, I don't want the CWM stuff in the CF-root kernel anyway and am also having troubles extracting the initramfs from it.
I'm going to alter the init binary and get back to Meego porting with the new kernel (which should now be easier to use with Meego's multitouch).
Thanks.

could you stop name it VANILLA GINGERBREAD . it sounds like sh*t when i spell it ..

k0sh said:
could you stop name it VANILLA GINGERBREAD . it sounds like sh*t when i spell it ..
Click to expand...
Click to collapse
Well that is what its called, are you not familiar with the term

natious said:
Well that is what its called, are you not familiar with the term
Click to expand...
Click to collapse
i'm talking about the way he wrote it .. i can feel it ...

k0sh said:
if you just read what the Dev said in the 1st link you pointed probably you are rooted now , and i'm not replying you with 1 eye open ...
for the holy moly , read Chainfire steps ...
one of chainfire steps ( EDIT#2: CF-Root v3.2 for JQ1 / Gingerbread has arrived: http://forum.xda-developers.com/show...&postcount=176 )after u open this link hit the 1st post with red color ,
download this CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip ..
put your tab into download mode , put the zip in odin PDA . without pressing anything or adding anything , just hit the start button on odin , 2seconds your tab will reboot , with CWM & ROOT ... good nigt
Click to expand...
Click to collapse
Your link seems broken.
Is this it? http://forum.xda-developers.com/showthread.php?t=885734
I did try this, but it seems that, I think it turned on, but immediately turned off

lardman said:
The tail end of the Gingerbreak threads on this forum say that the loophole has been closed afaict.
As I couldn't get it to work after a fair bit of trying, I assumed that was indeed the case and flashed Chainfire's pre-rooted kernel (CF-root).
Does anyone have a vanilla zImage backup they could post a link to for me, I don't want the CWM stuff in the CF-root kernel anyway and am also having troubles extracting the initramfs from it.
I'm going to alter the init binary and get back to Meego porting with the new kernel (which should now be easier to use with Meego's multitouch).
Thanks.
Click to expand...
Click to collapse
I asked a similar question to chainfire here and he said not possible here

I did find a way to root it here http://www.addictivetips.com/mobile/how-to-root-samsung-galaxy-tab-on-android-2-3-3-gingerbread/
I thanked you in your previous post for your help

[Q] Downgrade 2.3.3 to 2.2.1?

Hi,
I have two issues - firstly, three button recovery didn't work on my phone from new. The latest Android upgrade(2.3.3) has enabled it on 3e, but I think that's due to an error in the firmware(Three branded) - it says "can't access to '/system/csc/H3G/system'.'
I'm not getting on at all with Gingerbread(battery sucks, ogg files not playing properly, browser doesn't scroll nicely), and would like to downgrade back to an unbranded 2.2.1. I've been looking around and have grabbed some ROMs, odin, the "Aries_P-SBL" file needed to enable 2e recovery - but I'm also seeing things about updated bootloaders after the Gingerbread update, and I'm not totally confident in what I'm doing.
I'd like to downgrade to "I9000XWJSD", 2.2.1 released May 2011. The handset is Three(UK) branded, but has been SIM-unlocked(using the code provided by Three, and an alternative SIM does work). *#1234# gives PDA as I9000NEJVD, PHONE as I9000NEJV5, and CSC as I9000H£GJV6, with a build date of May 4th 2011. "About phone" gives a Build number of GINGERBREAD.NEJVD, Baseband version I9000NEJV5.
Will I be okay to do the 2e recovery, then the downgrade to the stock Samsung 2.2.1 flash? I have made the USB 3-resistor jig, and that puts me into download mode without a problem.
Sorry it was long-winded! Thanks!

The first thing you have to do is installing a 2.2.1 stock rom with froyo bootloaders(search for it in the forum, you'll find a couple of threads about it.
Very easy very simpel. Hope this will help you out.

Thanks for the reply. So I just drop down to 2.2.1 before thinking about installing the 2e recovery thing? Most things I've read indicate I need to have 2e recovery before flashing...
http://forum.xda-developers.com/showthread.php?t=1102881
On that page, "JSD" comes with bootloaders. Would that be safe to use on my handset?
Also, what is the "PIT" file for, and do I need to mess around with that?

EzBase is a good way of downgrading easily

http://forum.xda-developers.com/showthread.php?t=991792
^That? I shall bookmark it and have a look tonight.

Right, I've read through. The PDF guide for EZbase suggests 2e recovery is needed - how important is this? The guide for installing it suggests I need to root my device and check a string somewhere - but I can't root it using superoneclick, it just hangs.
How do I approach this? I have a working jig here, will that be sufficient to risk the flash without 2e installed? Should I just bite the bullet and go for EZbase 2.2.1, in the hope that I can then root the phone and check for that string?

Anyone, please? I'm technically minded and fairly competent, but as I get my internet through my handset(tethering) I'll be up the creek without a paddle if the phone ends up bricked... I need to be sure I'm not likely to mess things up!

I did it a couple of weeks ago, using this guide:-
http://forum.xda-developers.com/showthread.php?t=1100906
Went down to JPU, then straight to JSD. After gaining confidence by not c*cking it up, I chopped and changed modems a few times. ZSJPG had nice battery life but relatively sluggish/poor data connection and signal strength, so I used the Gingerbread 3UK modem from my last firmware - it works well for me.

[Q] Bell Samsung Galaxy Tab GT-P1000M firmware upgrade question

Greetings from a droid noob,
I have been trying to update my Galaxy Tab GT-P1000M using KIES, but KIES keeps telling me that I cannot update using KIES. I am very frustrated by this. It might be because the Tab I have used to be a display model used in stores. There is a continual demo screensaver that I can't disable either. It might be that there is something custom about it from Samsung/Bell for this functionality. I have never rooted the tab.
I then downloaded P1000MUGKF6_P1000MBMCKF6_BMC.ZIP from Bell to try to update to Gingerbread using Odin. This is where I get confused.
I have made many searches and there appear to be just a many versions of Odin as there are guides for the various phones out there. The instructions do not seem to follow the same pattern. Some say uncheck partition, some say leave it checked. Some use a PIT file, some don't. I really don't want to brick it.
I would really appreciate any help I can get on this. Step by step instructions would be especially helpful.
Model number: GT-P1000M
Firmware version: 2.2
Baseband version: P1000MUGJJ6
Kernel Version: 2.6.32.9 [email protected] #3
Build number: FROYO.UGJJ6

Go to overcome site
Http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
You can continue with the rest, and you will get Overcome 4.1 and you won't regret.
From there you can then try AOKP or CM9, all requires you to have Overcome Kernel with its CWM recovery to flash.

Thanks, priyana. I have actually seen that guide before. However, I am not trying to root. I am just trying to either go back to the "stock" FROYO and get rid of the KIES trouble or update to Gingerbread using ODIN.

"Stop there and you will have Gingerbread JQ1"
Not trying to root.
Read the guide images, it is exactly doing what you want. : flashing GB using ODIN.
BTW, no harm using the guide to apply your version of fimmware too.
Just use it as a guide for ODIN, what to put in what fields, what to tick, etc..
Also, it is good to hop on to GB stock safe first because that will get rid of bad bootloader, since some Froyo has locked bootloader.

Here is a step directly from the Guide section titled Preppin’ The System…
[REQUIRED FOR FROYO-BASED TABS ONLY:] Your Tab must be rooted.
Or am I understanding something wrong in those steps

Followed the pictures but I think I now have a brick.
My tab did not reboot itself as in the instructions. Instead it stayed in download mode. I rebooted manually...got the new start up sound and then got to the Samsung screen. It has been stuck on that for 10 minutes now.

Not sure if this is a good thing but I just saw the Samsung logo flicker.

Hmm.. did you get all steps passed in ODIN?
No harm redoing it again, but make sure you follow every steps (i.e. parts that let it reboot itself, etc)
Edit: I missed that bit that you said it did not boot itself.
I think it is essential, could it be that you didn't wait long enough?
The good thing is I think you can reach download mode, meaning you have not screwed up the bootloader, likely the bootloader were flashed correctly.
Power down the tab, and re-enter download mode and re-flash but make sure it completes itself.

Here, a very easy to follow going back to Gingerbread stock, follow carefully:
You can download any official firmware at http://fus.nanzen.se/
1a. Download Fus Check Downloader 2.1 from the above site. Using the Fus Check downloader, download a Firmware for your region. It will automatically decode the .enc2 file to.zip file
(For your case choose GT-P1000M)
1b. Download Odin3-v1.85
2. Extract the .zip file generated from decoding file to a folder and you will get
tar.md 5 file.
3. Start Odin - put the .md5 to PDA
3a. If your last firmware was gingerbread, leave everything else as is (No .pit file, leave repartition unchecked).
3b. If your last firmware was NOT gingerbread (get pitfile, and check the repartition) Note -- open up the.md5 package to check if there is a pitfile included,
as well as dbdata included. If they are included, you don't need to find pit file again, you can use it for your flash.
4. Go to download mode on the G-tab, connect it to your computer,
and click start on Odin. It takes about 6 to 7 minutes to do the flashing.

Good to know this! thanks.
I guess @ThiesWindu can try this way too, provided ODIN can see the tab.

Thanks, yappoe.
I am on step 3b. There was a tar file but no MD5. The tar file included a pit file but no dbdata.
I am going to try this. Fingers crossed.

Looks like I need that dbdata file as there was an error to that effect on the tab. However I did get further than last time. The tab is still stuck at the Samsung screen.
Where can I find that dbdata file?
Thanks

The issue was the dbdata.rfs file missing.
I found it here under misc notes.
http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1
It finally rebooted but what I got was the following message:
Sorry!
The application com.sec.android.app.samsungapps.una (process com.sec.android.app.samsungapps.una) has stopped unexpectedly. Please try again.
Is this something major or is it normal?
Thanks for the help so far.

that is why I recommend Overcome GB Stock safe in the first place.
Too many people asking where is dbdata.rfs, factoryfs.rfs, pit files etc when using other method.
Could your problem stem from using dbdata.rfs from different ROM?

priyana said:
that is why I recommend Overcome GB Stock safe in the first place.
Too many people asking where is dbdata.rfs, factoryfs.rfs, pit files etc when using other method.
Could your problem stem from using dbdata.rfs from different ROM?
Click to expand...
Click to collapse
Yes, of course, but he specifically wanted a non-rooted stock, and most likely from his region (and probably is ready to sell the tab for the newer tablet )
@ThiesWindu: one more step, and you should be done! (Hopefully -- Unless Priyana's fear is true... then the dbdata might not be for your Tab
go to Recovery Mode, and do a Factory Wipe and a Data Cache wipe.

The tab is working. The dbdata file seems to have done the trick. The tab works fine just takes longer to boot than before. Had to re-install a ton of apps though. I guess there are different versions for the different droid versions.
Is the slow down on boot up of concern? This is the first time I have done this.
Why would the stock not include it?

First boot after flash always takes longer time. What happen is android is installing and configuring your device for the first time.
Dbdata, pit and bootloader are not always included in a packaged stock because some Releases are meant for 'upgrade'. Since these files rarely changed from version to version, it wouldn't be included.
That is also why Priyana directed you to Team Overcome's GB-Stock-safe, because they include everything in the package. But because they have complete package, sometimes it's overwhelming for some people to follow the instruction.
Perhaps now that you completed flashing your g-tab, if you go back to team overcome website, you will have less difficulties following their instruction.

It seems to take longer all the time. Once booted it seems smoother and faster than before.
I have a 2nd Galaxy Tab that I can compare the times to and then report back when I get home tonight.
Thanks again

Compared it to the other tab and the boot time actually improved a little. Guess nothing to worry about then.
Thanks for the help guys.

updating your Canadian P1000M tab to android 4.4.4. or whatever other ROM you wish
I didn't want android 5 or up but the most stable Custom rom on my tab which only had the 2.3.3 update on it.
The problem with all the custom ROMs was they wouldn't work on the P1000M sim card model as only made for a P1000 .
There were a few threads about converting my current model to a P1000 but somewhat confusing about exactly what to do and where to get the downloads needed .After two days of playing around I found the guide and links in this thread as the most helpful they worked :http://forum.xda-developers.com/showthread.php?t=1881981
Once you install the GB Stock safe 5 tar file as per PDF instructions(which you need to read a few times ) use the JPZ Modem folder as per instructions on PDF –this is an Italian modem bin file but it will convert the P1000M to a P1000 which then allows you to complete the rest of the installs with the overcome wipe files and at the end of all the installs ,put your chosen recovery rom on tablet internal memory and flash using whatever custom Rom for a P1000 you wish (as there isn’t any links or availability for a P1000M except for gingerbread).Its a long process to get to using the custom rom but it works and seems to be the only way to go. I used omni nightly4.4.4 plus the gapps files and and updated SU zipfile.
Unfortunately once the omni ROMwas installed I kept getting the android process media has stopped message constantly so used the following to fix that issue :
Go to your app settings page (Settings > Applications > Manage Applications) and open Media Storage. Hit clear data.
If you have a custom recovery installed (most custom ROMs and kernels do have it), boot into it and fix permissions. In Clockworkmod Recovery, you can find it under “Advanced”. TWRP recover also has a similar option. Being a Linux-based OS, permissions are of paramount importance to smooth functioning of Android components.
In Manage Applications, open Google Services Framework. Clear data.
Open Google Play Store. Hit clear data. Note that this will clear all play store data, including your Google sign in. You will have to login with your Google / GMail account again the next time you open Play Store.
Open Download Manager, and clear its data too.
Backup your data and format SD card. Make sure to backup all data on your SD card, including media, apps and other files, before formatting it. Use FAT32 formatting, which is preferred for Android. This is because android.process.media is related to camera, gallery and other multimedia components, and SD card errors may cause this force close error.
Try a different SD card. Many SD cards, particularly those of class 6, 8 and 10, have been reported to not work reliably with Android devices. Class 4 seems to be the safest option .
Now running 4.4.4 on my tab P1000. thank goodness.