yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] brewguytim:
abax - I was in the EXACT same situation as you. Couldn't get past the Samsung screen and couldn't get into recovery.

I had done the bootstrapper from the market and that went fine. Then went with the SGS Kernel Flasher (option B) and that went horribly wrong and put me at the Samsung screen.

I tried connecting with Heimdall (option A) but it wouldn't see my device connected. I then chose option C. Odin saw my device connected and I just went through the instructions as specified. All of the sudden my device would boot and I could also boot into recovery.

Give it a shot.
[Galaxy Tab  Android Development] abax44:
Worth a shot. Thanks, man.
[Galaxy Tab  Android Development] brewguytim:
Now, here's my question: How do I get rid of the woman's voice? She mentions the data and system partitions every time I plug it in or start it up.

A couple of other noticable "bugs"?:

1) With new resolution set by kernel, home screen (screen 3) icons cannot by aligned lower than about 2/3 of the way down the screen

2) Tapping home icon, takes you to screen 1 rather than screen 3.

These are all rather minor in the grand scheme of things, but thought I would mention them. Great work on this! It's appreciated!
[Galaxy Tab  Android Development] beestee:
Get into recovery, go to the voodoo lagfix options, turn off the lagfixes, reboot.
[Galaxy Tab  Android Development] brewguytim:
Bestee - that will kill the lady's voice?

I ask because I supposedly have the lagfixes disabled at this point.
[Galaxy Tab  Android Development] abax44:
Is there a proper .PIT file that I should be using?

I'm finally able to get to recovery but I'm unable to select any of the choices.

DBDATA: wipe failed

E: can't mount /dev/block/mmcblk0p2

(invalid argument)

etc....
[Galaxy Tab  Android Development] dB Zac:
I had the same problem but i just pluged into a different USB port, problem solved

abax44, you need to download the stock files and flash them to your tab using Heimdall and "download mode"
[Galaxy Tab  Android Development] abax44:
I have DJ30 working now, but I can't upgrade to 24. Do I still need to use the stock files, and can it be done in Odin (starting to get the hang of Odin now)?
[Galaxy Tab  Android Development] beestee:
Hmm...after reading through abax's previous posts it seems that you need to sort the SD problems first...

Are you using the stock SD that came with your device or have you replaced it?

Have you ever formatted it?

How much free space does it have?
[Galaxy Tab  Android Development] brewguytim:
It's the stock that came with it.

No

14.31GB available
[Galaxy Tab  Android Development] steveo11284:
I've was having a lot of issues installing v4, but I was finally able to get it to work on my vzw tab.

I was coming from v3, so I tried the recovery install method first. It installed, I rebooted, and I had nothing but non stop force closes once it was up. To be fair, I was having some system issues before hand, just not this bad.

So, I went through Heimdall, but that just got stock on the Samsung screen and I couldn't get it in recovery. I reverted back to v3 which flashed fine using Heimdall, installed a fresh rom, and tried to install it using SGS Kernel Flasher, but again, it got stuck on the boot screen and I had no recovery.

Finally I tried ODIN, and it worked like a charm. I'm not sure why that worked and the others didn't for me, but I digress. So far so good :)

Thanks Boushh for your Kernel. It's pure awesomeness!
[Galaxy Tab  Android Development] Imoseyon:
i've noticed something weird with v4. Occasionally kswapd will go crazy and consume all cpu cycles. It's even weirder since there's no swap enabled.
[Galaxy Tab  Android Development] hawkye:
Heimdall flashes just fine but I get stuck at the Samsung screen also. I tried Odin but it doesn't flash, it just comes back with All Threads Completed 0/0. Uggh! I will am back at v3 until I can find a way around it...
[Galaxy Tab  Android Development] beestee:
The voice should happen once each time you enable/disable the lagfixes. The first time you boot with the kernel, the voice alerts you to the conversion progress while you are sitting at the samsung screen. You are not 'stuck at the samsung screen' if you are also hearing this voice. Let it do it's thing this one time and it shouldn't bother you again until you disable/enable the lagfix again. This process takes 3-5 minutes typically.
[Galaxy Tab  Android Development] idumych:
Okay so I used the leaked Sprint flasher to restore the factory rom and ran the OTA update. Then, I flashed the v4 kernel with the SGS Kernel Flasher. Now, my tab is stuck at the Samsung logo. WTF?

EDIT: I just tried flashing with Odin instead, and now it seems to be working! My tab is talking to me in a female robot voice.

EDIT 2: Ugh, now I'm trying to follow step 2, and it's stuck at "Welcome to KasMek's Voodoo Plus Kernel Install", it's been sitting there with no progress bar.
[Galaxy Tab  Android Development] whats77inaname:
I'm looking forward to loading this, but in the first couple posts it says that the camera isn't working. Has this been resolved as of yet?
[Galaxy Tab  Android Development] hawkye:
Any ideas why I can't get Odin to flash but Heimdall works just fine? Only problem flashing via Heimdall is I always get stuck at the Samsung with v4. It flashes v3 just fine though... Ugggggh!
[Galaxy Tab  Android Development] idumych:
I've tried flashing this, on a clean, factory flashed tab, with all three methods. SGS Flasher and Heimdall cause my tab to get stuck at the Samsung logo with no voices or anything, just stuck. When I flashed with Odin, I did get the voice notifications and it did install CWM, however, when I tried to flash the update zip in step two, it got stuck at the welcome message and never went anywhere.

Has anyone been able to get this working on a Sprint tab? Because frankly, if it doesn't work when flashed with any of the three methods on a freshly flashed tab with the leaked Sprint flash, I think it's fair to say it just doesn't work.
[Galaxy Tab  Android Development] oldmacnut:
I tried all 3 methods for my 8 hour old vzw tab, hell I even grew balls and was mixing and matching vzw recovery files, and this kernal in heimdall, boot loops on all 3 ways.

Then I tried wiping, not wiping, repartitioning, not, man I tried all ways possible, vzw bootstrap, rommanager, older cwm versions, etc.

I really wanted to ditch this stock software and run your kernal, and rom, looks like its not going to happen. I spent all day and night on it, kinda wanting to use the tablet, not work on it.

Ill wait for a version that doesn't take more than an hour of my time, sounds like I'm not the only one with these problems.
[Galaxy Tab  Android Development] idumych:
Found a working method!

Hey guys, I finally figured out how to install this! I have a sprint tab but it ought to work on both. First thing you need to do is either follow the CWM for Sprint thread, or use the verizon bootstrap app from the market.

Here's the steps I took:

1. Install and run verizon bootstrap

2. CWM failed to convert. At menu after failure, did factory wipe

3. Power off

4. Boot into recovery

5. conversion completes successfully

6. flash update zip

7. Listen to voice notifications

8. Success!

Don't forget to click thanks if this helps :)
[Galaxy Tab  Android Development] abax44:
I always get the "can't set up partition, SD card too small" message. The SD card is 16 gb and empty. I had maybe a few gb worth of stuff on the Tab to begin with. Plus the fact the internal memory doesn't show anymore. :mad:
[Galaxy Tab  Android Development] beestee:
Have you tried mounting the SD? You can do this from settings or recovery.
[Galaxy Tab  Android Development] abax44:
Yup, SD is mounted. The internal memory isn't showing at all. It used to show 3 separate types of memory, now there are just the 2.
[Galaxy Tab  Android Development] abax44:
Ok, so this link just solved all of my troubles:

http://www.talkandroid.com/21900-samsung-galaxy-tab-on-att-rogers-bell-hacked-for-voice-calls/

Anyone else having any sort of weird issues like I was should give it a shot. My tablet is fast and all the memory is showing up again. I just did it exactly as it's posted there.
[Galaxy Tab  Android Development] beestee:
How about 'fix permissions' in the 'advanced' section of recovery?

Or how about 'wipe data cache' in recovery and 'wipe dalvik cache' in 'advanced' recovery?

Verizon tabs only have 2 types of storage. 2GB internal device storage and then the external SD. Boushh mentioned a Sprint branch of this kernel in the updated OP...with this many issues, perhaps you would be better served going back to stock until that is available?

EDIT:...nevermind :D

EDIT 2: Whoa...wait a sec. Are you on a GSM tab?
[Galaxy Tab  Android Development] abax44:
I tried all the wipes and whatnot. I'm on a Bell tablet.
[Galaxy Tab  Android Development] jdiem:
Testing V4 with no problem... and workaround for SD Card mounting issues

I'm running on a Sprint Tab with V4 of the Kernel... it's only been an hour or so, and my testing is just me using my tab for some web browsing- but so far it's working fine.

1. Started with "clean" tab, after several prior mods, using ROTO-JME4 to start with a clean build.

2. Wiped cache, went to factory default, then installed Verizon bootstrap kernel which reboots the tab (and then after rebooting one more time into recovery mode) begins changing my filesystems to EXT4. I notice this makes a huge performance difference in filesystem response for applications.

3. A few days ago, installed the OC v3 of this Kernel, got the complaint about insufficient space on the data partition. As the other posts state, rebooted into recovery mode and disabled lagfix and rebooted. Got the voice again saying that the Voodoo Lagfix changes are disabled. Rebooted one more time into recovery and re-enabled the lagfix, and on reboot the voice comes on saying the voodoo lagfix is enabled.

4. Just downloaded v4 kernel today, saved it to external SD card, and rebooted back into recovery and used the "Install from Zip" option. Kernel flashed no problem and is running fine right now.

Regarding the SD Card workaround:

I found that going into adb shell, I was able to remount the card with a basic mount command:

mount -rw -t vfat /dev/block/mmcblk1p1 /mnt/sdcard

and then if I went into Settings->SD Card, I could remount the card.

Since opening up ADB shell (or using a console app) is kind of a pain every time I restart the device and want to mount the card... I downloaded "Script Manager" from the market, and you can use that to create a script. The easiest directory (and most logical place to me to) store it in was /system/sbin. The Script Manager has a nice interface to create the script, and then run it manually as a "favorite". It also has a feature to run at boot time... but this doesn't seem to work so well...

Anyway, now after rebooting, I push a button to start the scripting tool, and a 2nd button to run the script. Then I use settings->SD card to mount the storage.

It's not perfect, but hopefully this gets a few more people up and running again until a clean fix is worked out.
[Galaxy Tab  Android Development] mario23:
hey just to clarify...are u saying the verizon bootstrapper will work on sprint on its own or are there additional downloads
[Galaxy Tab  Android Development] Boushh:
Resolution isn't set by the kernel, it's set by the build.prop in the ROM.

Just to clarify, the resolution doesn't ever change, it's the screen density that does.

Oh for the love of the gawds please don't flash GSM ROMS ON YOUR CDMA TAB. It is not what you want for dinner.
[Galaxy Tab  Android Development] idumych:
Yes, I'm saying it works on sprint. The only download you need besides that app is the kernel zip from step 2 on the OP.
[Galaxy Tab  Android Development] abax44:
Solved all my issues and Bell is CDMA. Unless it works because Bell also uses HSPA? *shrug*
[Galaxy Tab  Android Development] Metalsteel:
Does Flashing this kernel convert my sprint tab to ext-4 filesystem or Do I have to do that first?
[Galaxy Tab  Android Development] brewguytim:
Thanks for the response. I have actually fixed the problem by using ADW Launcher where you can set the number of rows and columns in portrait and landscape. :)
[Galaxy Tab  Android Development] idumych:
Okay, so here's a couple problems I'm having:

1. Flashing this kernel broke my screen rotation

2. The screen looks weird now, hard to describe. The picture just looks grainy.
[Galaxy Tab  Android Development] Metalsteel:
Dont know what to do about the grainy picture... maybe reflash?

for the screen rotation you need to find the default sprint sensor and move it into a certain location within your filesystem. I can't find the thread that had the fix.

But I know there is a thread on this forum that shows you how to fix your orientation/ sensor I used to have same problem just do some searching
[Galaxy Tab  Android Development] bigdaddynw:
Hangs on Samsung screen and can't flash Verizon_zimage via CWM 3.0.0.0

OK kids, head-palm!!! I can finally post on here YIPPEEEE!!!

Worked three days on this...

I have reverted my VGT back to factory just to make sure I'm back to point A - via Droid Forums "[How TO] Restore VZW Galaxy Tab to stock DJ11"(sorry can't post link, not enough posts yet!) everything went with no problems

Interesting, its still rooted which I Z4'd a few days ago.

Next I booted, went to market to grab Verizon Tab Recovery Bootstrap (love to have the APK so I can sideload and not have to sign in to Google)

Ran VTRB, set the Bootstrap Recovery, Booted into Recovery

CWM Recovery 3.0.0.0 opened and backed all the data did the conversion and wrote the files back to the device. At this point I am EXT4. Think there was an error about not finding a sd-ext, not sure on the exact wording.

Wiped both caches (Dalvik, cache partition) get error when wiping Dalvik "E:failed to mount /sd-ext (no such file or directory), not sure this means anything, best I can surmise it has to do with no App2SD

Wipe Data Factory Reset

Rebooted into Recovery with no errors

Install zip from SD card

Selected verizon_zImage.zip

When I tell it yes apply, I get " Finding Update Package...Opening update package...Installing update... Installation aborted"

OK fine, so I decided I will install from Heimdal.

Wiped both caches, wipe data factory reset, rebooted in Android

Shut off tab, rebooted into Download

Flashed verizon_zImage to both the Kernel and Recovery via Heimdal

Rebooted into android and it DID NOT bootloop, which I was a little concerned as I figure it would if the image flashed correctly (judging by other posts)

After my VGT booted I shut it down and booted into recovery with no errors

Cleared both caches, wipe data factory reset. Rebooted but didn't let it boot to Android (held power key down until it shut off) because I was worried it would write to the cache(s)

Booted to download

Flashed with Heimdal to both the Kernal and Recovery the KhasMek.Voodoo.plus.CDMA.Tab.v4.OC.zImage

Rebooted

Hangs on Samsung screen

Shut off, tried to boot to recovery (to wipe caches and factory reset) CAN'T GET THERE, always hangs on the Samsung screen.

Booted into Download

Flashed with Heimdal to both the Kernel and Recovery verizon_zImage

Rebooted into Android, everything runs fine

Apologize for any typo's :-)

What am I going wrong?
[Galaxy Tab  Android Development] webrover83:
My experience is similar to the above. If I flash the voodoo zImage, by Tab is worthless. Will not boot to anything other than download. I can restore original VZW image, but nothing else will recover me.

I've tried lot's of combinations of CWR clear caches and enable/disable lag fixes. v4 is total fail for my set up.

VZW i800 - crapware that won't do bluetooth or peer wifi without mod's. :confused:
[Galaxy Tab  Android Development] jorgepsantos:
Try to flash v3 first, then v4
[Galaxy Tab  Android Development] bigdaddynw:
Have a link to ver 3 or direct me to its location? - thanks
[Galaxy Tab  Android Development] jorgepsantos:
PM me I'll give you a link to my dropbox.
[Galaxy Tab  Android Development] bigdaddynw:
Spent 3 days and many different configurations. Finally got it to work, used SGS Flasher. Not sure why it works and nothing else would.

Now that I have the kernel installed, I would like to get klean ROM installed. Anyone have a link to instructions, love to have it.
[Galaxy Tab  Android Development] gonzo1082:
so i'm coming from a stock rom. did the vzw bootstrapper and conversion, etc, then used the kernel flasher app. i'm stuck with the black samsung screen. can't boot into recovery either. but i can boot into download mode (at least my tab isnt bricked).
[Galaxy Tab  Android Development] bigdaddynw:
Which flasher tool did you use? The only way I was able to flash was to use the SGS tool found in the market. Need to use the .tar file. The instructions for SGS on page 1 worked correctly for me. Don't forget after you flash, boot back into recovery and wipe Dalkvik cache and partition cache, then reset to factory defaults. Then boot. If not you will bootloop.
[Galaxy Tab  Android Development] gonzo1082:
yup, i used the sgs from the market. but i used the zImage file, not the tar one. so what happened after it flashed, it never rebooted on it's own. i did a manual reboot and tried to get into recovery, the power + volume up didnt do anything. it just went straight to the samsung screen and hung. i'll give the tar file a try next time (tomorrow). i'll report back with my fail/success. thanks for the help

PS:anybody know how i can get out of that samsung bootloop screen w/o having to reflash back to stock? can i just flash back the stock kernel using hemidal?
[Galaxy Tab  Android Development] gonzo1082:
so this finally worked for me.

1. I completely restored back to stock GT with hemidal

2. installed the market's sgs kernel flasher,

i DID NOT USE

the zImage file on option 2. i used .tar file on option 3 instead.

3. ran the program, flashed kernel from memory card, restarted on its own as it should.

4. followed the second steps and voila!

thanks yall.
[Galaxy Tab  Android Development] jarrettv:
yep, heimdall isn't working with latest v4.

I'm also stuck on samsung
[Galaxy Tab  Android Development] gonzo1082:
yeah i tried flashing with hemidall, did you try the sgs kernel flasher app from the market? that worked for me.
[Galaxy Tab  Android Development] bigdaddynw:
From my limited experience, there is no way to get past the Samsung screen. this usually means the flash was not successful (from what I have surmised) However if you don't use the correct procedure to reach the Recovery screen, then you can't reach the data wiping etc.. so you can't get past the Samsung screen on boot up - viscous circle!. Correct procedure is to hold the vol. up key then press the power and hold the power key, when the Samsung splash appears immediately release the power button, keep the vol. up depressed. Once the screen goes blank you can let go of the vol. up. Now with that said, I was never able to get into the recovery when I was trying to boot V4 which was flashed with Heimdal, others had success hence my steps above.

I did not try flashing with the Verizon_zimage with Heimdal, then use the SGS to flash the v4 kernel. However I was successful in flashing the Verizon_zimage with Heimdal and then the v4 with Heimdal but as stated above never got past the Samsung screen. My success came from flashing back to stock via the info I stated in a previous post, then used SGS to flash the kernel, I too experienced SGS not able to reboot the system on its own. I waited about 5 minutes then rebooted manually.

Sorry for typos I'm a terrible speller and typist!! :-)
[Galaxy Tab  Android Development] bigdaddynw:
Followed what "second steps"? Flashing the Over Clock update portion (which there is no need since v4 has this incorporated) or double checking the recovery?

Just wondering :-)
[Galaxy Tab  Android Development] bigdaddynw:
Just to reiterate, I would strongly recommend you pull it back to stock! This will save you lots of little headaches etc.. the best way to pull back to stock, for me, was to use Heimdal and the info I stated in a previous post (speaks of the files you need and a link to grab them), this will ensure you are not ext4 and ARE stock format. Here is the link, looks like the XDA Gods have deemed me worthy of posting links now ~happy dance~ [How TO] Restore VZW Galaxy Tab to stock DJ11 Link - http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
[Galaxy Tab  Android Development] gonzo1082:
thanks, that's what i did. went back to stock tab. and used sgs app to flash the voodoo kernel. that time i didnt get stuck in samsung screen. finally got the ext4 conversion going with the funky voices coming from the tab.

from your previous post. i did the "Part 2" section after, which was basically to check if everything went through correctly. so, everything is good to go now :)
[Galaxy Tab  Android Development] idumych:
Any news on the Sprint rotation fix guys? Kinda a show stopper here. I did a search and I'm only seeing threads for other devices.
[Galaxy Tab  Android Development] dragon1022:
What problems are you having.
[Galaxy Tab  Android Development] idumych:
Rotation doesn't work after I flash this. Supposedly there's a simple fix involving copying a config file somewhere?

Also, for any sprint peeps having trouble getting this to flash, here's some advice: NONE of the three options in the OP worked for me. If you want this to actually boot, I suggest doing the following, as it worked great for me:

1. Install the SGS bootstrap if you haven't already, and do the conversion

2. Use CWM 3.0 to flash the update zip from step 2. Do NOT flash the Voodoo kernel first. Every time I tried to flash the update with CWM 2.5, it got stuck.

3. Enable lagfix in recovery. For some reason it seems to be disabled by default.
[Galaxy Tab  Android Development] matthewflinchbaugh:
I encountered the rotation issue when flashing a backup after trying spacemonkey's honeycomb port, after much frustration I found that simply reflashing the kernel solved this issue.
[Galaxy Tab  Android Development] Benjamin Dobell:
Those of you that are having trouble flashing with Heimdall. Could you please run Heimdall from command line with the verbose parameter and e-mail the output to service (_at_] glassechidna.com.au. Depending on the problem I might be able to sort something out.
[Galaxy Tab  Android Development] webrover83:
The above steps worked for me... finally! Whew.

Tab is fast and kewl looking. No FC's running around.

Now if we could just get BT Keyboards and the video cam working...
[Galaxy Tab  Android Development] empiricalis:
This seems to be working swimmingly on my Sprint tab, other than the camera. Have any Sprint users managed to get the cameras working?
[Galaxy Tab  Android Development] john122675:
Ok tried reading through some post but i have tried flashing this kernel on my vzw tab. I have tried sgs kernel flasher 3 times and i have tried odin and heimdall as well all give me the same thing i only get to samsung boot screen and no further. even holding down power button shutting down and attempting to get into cwm doesnt work all i can get is to samsung boot screen. my phone is rooted and i have cwm installed using koush bootstrapper off the market. any advice would be appreciated i really want voodoo and overclock bad. and every attempt i have had to flash back to stock using heimdall..... thanks in advance and i am sure this problem is something i am doing just so noone thinks i am saying the devs work is wrong or that i am blaming someone else.