yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] nzaw4:
Not sure, since im still too noob to mess with this and to top it off, just went full time with ubuntu and got rid of win7, and need to figure out all this driver stuff :p,

soo i think the manual method its listed in this thread via ADB , but please dont flame if im wrong, still new to this tab stuff :o

http://xdaforums.com/showthread.php?t=870690&highlight=recovery+BETA

Flash the kernel using flash_image: http://koush.tandtgaming.com//test/flash_image (This will flash both boot and recovery)

adb push flash_image /data/local/bin/flash_image

adb push verizon_zImage /sdcard/

adb shell

su

chmod 755 /data/local/bin/flash_image

/data/local/bin/flash_image boot /sdcard/verizon_zImage

sync

exit # This should take you back to your computer's console

adb reboot recovery # Boot into recovery
[Galaxy Tab  Android Development] tedum88:
yes i do have SU. it was pre-installed with the Stock Flash from Odin...
[Galaxy Tab  Android Development] gordesky1:
Hmm just checked my camera and it works perfect weird why other people is having camera problems, Im sprint also.

For the ones that has the cam problem did you guys update to the ea24 sprint update before flashing this kernel? Because i didn't so maybe that's why its not working for you?

Everything is working except the cdrom showing up for sdcard when mounting but that's a known problem for sprint tabs that uses the Verizon kernel.
[Galaxy Tab  Android Development] Boushh:
You can always flash back to the stock kernel, install the update, and flash the new kernel. You shouldn't have any issues with that. However, sometimes the OTA's won't work if your even just rooted, much less a completely custom kernel (from a different device).

Try booting into recovery after flashing the kernel and disabling/re-enabling it like other users have already posted with success. :)

Okay guys, I'm updating my threads now and just a small update. I have just received news that a really good dev has a VZW Tab on order, so I'll have some help with everything next week and we should be able to get things out much faster. (It will also allow me more time to look into you sprint users.)

I'm guessing everyone with camera issues is a Sprint user?

\o/ for us.
[Galaxy Tab  Android Development] Coolsaber57:
But would the stock kernel work with ext4? Wouldn't it not recognize his system?

Or am I way off lol?
[Galaxy Tab  Android Development] tedum88:
so Boushh.. i don't have to be rooted. all i have to do is flash your new v3 kernal and boot into recovery? how do i boot into recovery? don't i have to install a recovery? and how do i disable/ re-enable? im so sorry im such a noob.
[Galaxy Tab  Android Development] prohibit:
Thats awesome news boushh. maybe you guys can get some honeycomb going haha.

via GalaxyTAB
[Galaxy Tab  Android Development] beestee:
Camera working here on VZW.
[Galaxy Tab  Android Development] gordesky1:
I wonder if the ones that has camera issues updated to the ea24 sprint update before flashing too this kernel?

I have sprint and my camera is working but i also didn't update to the new sprint update.
[Galaxy Tab  Android Development] futuregerald:
stupid question but how does one get in to voodoo recovery once it's installed?
[Galaxy Tab  Android Development] gordesky1:
Hold both volume up and power button than when you see the samsung screen leave go of both or at least power button.

I just keep holding the volume up button till the recovery shows up, But if you keep holding the power it will shut off again.
[Galaxy Tab  Android Development] Boushh:
Correct, you will need to boot into recovery and disable the voodoo lagfix and system lagfix, then you can flash stock kernel. :)

Correct, check out the first post. I've just updated all the install instructions. Let me know what you guys think.

Also guys/gals -- Would you please take a look at the "known issues" list. The first item is something I want you people with wifi/3G issues to check out/test. Also, if you can think of anything that should be added let me know. I have read about a lot of random problems that aren't on the list, but most are due to not following my directions and not actually an issue with the kernel.
[Galaxy Tab  Android Development] futuregerald:
Thanks, i just read the updated OP and saw you were interested in setting up a Sprint branch, just curious if this will be something available soon(days) or more of a longterm plan? only asking so I can decide if I should flash the kernel + recovery on my new tab(just got here!), or if I should wait for the Sprint specific branch.
[Galaxy Tab  Android Development] beestee:
In terminal emulator, type in 'su', enter, and then 'reboot recovery', enter...or power down, then hold vol + & power until samsung logo pops up.

EDIT: sorry, didn't see gordesky already had it covered :)
[Galaxy Tab  Android Development] oxeneers:
Yeah, I'm on the latest maintenance release. Any way just to get back to stock?
[Galaxy Tab  Android Development] Boushh:
At this point I'd say weeks. This works on the Sprint tab, just not 100%. It might be sooner, but I wouldn't count on it.

If you do the terminal emulator method it is fine, if you have flashed both partitions before.

Technically

bml7 == Kernel

bml8 == Recovery.

Heimdall flash --kernel and SGS Kernel Flasher only flash bml7.

Heimdall flash --kernel --recovery and my zip's flash blm7 and bml8.

(still with me?)

When you hold volume up + power when booting, you boot into the recovery on bml7.

When you type reboot recovery from terminal emulator,adb reboot recovery from your computer or reboot into recovery from Rom Manager you boot into the recovery on bml8. This is your "backup recovery".

The reason for this is in case you really mess something up, you'll always have a backup recovery to go to. Much like the PC -!- Phone screen, which is the backup download mode.

Now, you don't normally want to flash everything onto the backup partition, because, well, what use is it if you don't use it as a backup. This is why SGS kernel flasher doesn't touch that partition. However, we need to get Voodoo CwM on there to start with, so we have a good, flashable recovery for backup use (when we need to do an adb reboot recovery for example).
[Galaxy Tab  Android Development] tedum88:
so.. no factory reset or wipe required?

also... don't you have to put your phone in download mode (volume down + power) instead of recovery mode in order to flash using heimdell or odin?

please let me know! thank you so much!
[Galaxy Tab  Android Development] futuregerald:
To those Sprint users that had the camera issues, were you running the latest update from Sprint? or no? that seems to be the main thing stopping me at this point and just trying to figure out what the problem is.
[Galaxy Tab  Android Development] oxeneers:
Yeah, I was. And now my camera(s) are both ****ed and I'm just trying to get back to stock. Anyone know the route to take?
[Galaxy Tab  Android Development] Boushh:
Yes, sorry about the type, volume DOWN + power. Thanks for pointing that out. Fixing now.

Also, you shouldn't *need* to factory reset or anything, but if it doesn't work, that's always something to try.

Odin back to stock.
[Galaxy Tab  Android Development] futuregerald:
so I just used Heimdall to flash the kernel + recovery, it finished and rebooted and now it's just on the initial samsung logo. I didn't hear a voice say anything and it hasn't moved on to that flashing logo yet. How long is it supposed to sit on the first boot screen?
[Galaxy Tab  Android Development] oxeneers:
If you're on Sprint, you'll have to boot into recovery (try adb reboot recovery) then go to voodoo, then disable both lagfixes - then reboot into Android, then reboot back into recovery and re-enable them. Then it'll boot. It didn't boot the first time for me, either.
[Galaxy Tab  Android Development] futuregerald:
I can get in to download mode with down and power but up and power doesn't get me anywhere. I also don't seem to have a way to get in to adb cause it just says "error: device not found" when I try to run an adb command. this sucks. only good thing is that I can at least get in to download mode...

followed the instructions @http://xdaforums.com/showthread.php?t=969892 and went back to full stock. not sure what went wrong, i followed the instructions and used the heimdall gui and it flash 100%. oh well, at least my tab is working, looks like i'll have to wait for that Sprint branch after all.
[Galaxy Tab  Android Development] Coolsaber57:
Just took a look at the instructions, I'm assuming that you don't still need CWM installed before installing your kernel, correct?

Also, grammar nazi thing: "ensure" vs "insure" :p
[Galaxy Tab  Android Development] ekoandrew:
Just completed flashing it, working like charm!! another awesome great job Boushh
[Galaxy Tab  Android Development] Boushh:
heheh, I spent too much time making ascii art before I rewrote this. In my mind I put "do not need CWM" :P
[Galaxy Tab  Android Development] blkblt412:
My tablet won't go past the initial Samsung screen on version 3 of the non OC kernel. I have a Verizon tablet and was running version 2 of the kernel with no problems. I can't get in to recovery either to clear the cache or do anything else. I went back to version 2 of the kernel for now in its late and I'm just missing something.
[Galaxy Tab  Android Development] futuregerald:
same issue i had.
[Galaxy Tab  Android Development] cruiserbax:
New version works great on my sprint tab!! amazing work! If you have the old kernel you probably had some version of the bootstrap before that in order to convert to ext4. If that is the case just download the cwm zip package of the new kernel then open terminal emulator on the tab (download from market for free) and do "reboot recovery" this will bring up a half working cwm, from there flash OPs new v3 and once it has completed go back one menu and go to advanced then choose "reboot recovery" now you will boot into the new kernel recovery. after this I verified that under the voodoo menu it listed as voodoo enabled then I went back a menu and did "reboot system" and it booted back into Android with all apps and the like intact.

---

At first I tried flashing with sgs kernel flasher but had the same problems as the few above me explained (not booting and not going back into recovery). I know my way around android flashing so I did try all the normal things but ended up flashing back to my starting state which was bootstrap zImage in recovery and OPs v2 in Kernel then just did the above method and all is well and good in the world, didn't have to do a data wipe or anything.
[Galaxy Tab  Android Development] gordesky1:
Also for sprint users before you update too this kernel make sure you dont have the sprint update installed it seems like the ones that had it installed there camera dont work anymore, I didint install the update and my camera doesint have any problems and I will not either which I was going too till I herd the problems.

So just going too keep saying no when it asks me too update too it lol
[Galaxy Tab  Android Development] tedum88:
flashed with sucess! many thansk again to everyone who posted instructions to help noobs like me! you guys are my ninjas!! but I still do have a problem same with other sprint users.. storage mode as cd rom drive.. and no camara.. it won't bother me too much. but just in case can i flash the stock rom from Sprint using odin if i want to go back?

edit: my tab won't go into landscape mode either. that's harsh.. any help on that!?

thank you!!!!!!
[Galaxy Tab  Android Development] futuregerald:
brand new Sprint tab, this happened to me on the first try(with this tab). After trying to flash v3 and having to flash back to stock multiple times last night i simply gave up then installed the update. however if someone finds a fix or at least a reason that this is happening then I'll try again.
[Galaxy Tab  Android Development] cruiserbax:
I have the sprint tab without the new update and using the method on the previous page all is well and I have auto-rotation and camera works fine. I will do a nandroid then go back to stock kernel and install the update then flash to see if I can logcat or something to see what's going on for OP.
[Galaxy Tab  Android Development] jschmid698:
Thank You!

Awesome i just finished loading everything on here! Thanks!
[Galaxy Tab  Android Development] tedum88:
Hey. By any chance.. did u update to new firmware after flashing this kernal? Mine keep poping up for an update. Its annoying!
[Galaxy Tab  Android Development] cruiserbax:
No I did not.
[Galaxy Tab  Android Development] cruiserbax:
@OP,

I noticed that with thos kernel on sprint tab gps will not lock, i can flash back to stock kernel after disabling lagfix and gps is fine bit sucky as usual. Anyway I was wondering if you might look at the differance in gps between your kernel source and stock sph-p100? I will bw glad to take a look of you dont have time, just point me to your repo for syncing.
[Galaxy Tab  Android Development] beeroatsnp90x:
I'm having trouble when flashing this. I am using Khasek's rom then with heimdall I flash the kernel and recovery. When I boot, it stays stuck at the samsung screen so I try to go to recovery and it never goes to recovery. I'm using a verizon tab
[Galaxy Tab  Android Development] futuregerald:
Several of us have had this problem, I haven't found a fix yet and I don't think anyone has. Its strange cause its happening to both verizon and sprint ta s and it started with version 3.
[Galaxy Tab  Android Development] cdred:
Flashed great but camera and landscape don't work anymore. I did this before getting to last post about the new sprint update which I did do. Do you think there will be a fix for this issue? Also, how do I flash back stock kernel until problem is fixed and will it erase the recovery menu
[Galaxy Tab  Android Development] jinsoku3g:
same problem.. is this bricked? it will still go to download mode just nothing else, turned off will show battery but never loads any stats..its there a way to go with a older version? I'd rather mess around with SOMETHING than just have a paperweight lol
[Galaxy Tab  Android Development] cruiserbax:
Just flash the other kernel back to kernel and recovery. Or you can use the near stock odin image to get back to stock just make sure you use the odin package WITHOUT! Modem included that way you keep your stock modem.
[Galaxy Tab  Android Development] jinsoku3g:
I was ignorant, did it at 4 am and didnt backup my old kernal.. so its just sittin on samsung, i did download the sprint No Modem Odin package from the zypher page, but when i click start it instantly says finished and doesnt do anything lol
[Galaxy Tab  Android Development] Boushh:
Once again.

Nothing I post will brick your phone. If you've followed my directions, you have not bricked your phone. Most likely if you have not followed my directions, you have not bricked your phone.

The last time I asked this, I did not see any response to my question so I'll try again. You guys that are having this problem, what method are you flashing via? I would really like to try it to see if I can get it to break too. I need a little more information to recreate it properly though. So can you take some time to get me some info (I know a few have already given it, so thank you). Also, would you let me know if you're running any custom ROMs, if you've flashed koush's recovery at all or anything else you think might be relevant. I haven't had my morning coffee yet so all the things aren't coming to my little brain. :P
[Galaxy Tab  Android Development] jinsoku3g:
i have CWM from the bootstrapper on the market

used heimdall to flash the K-Leen Rom

then used heimdall again to flash the kernal, and then ..nada..

with the stock/no modem in odin trying to just go back when i click start its saying suceeded0/failed 0.. so it seems like odin just isnt working with my tab in DL mode
[Galaxy Tab  Android Development] jinsoku3g:
interesting enough, each time i use heimdall to try reflashing the rom or a kernal.. the status on the TAB's DL mode screen does complete and then restarts.. just never gets to the lock screen.. crazy.. i actually WANT to see a verizon logo lol

have the rom in the Factory FS spot and the kernal in the zimage spot

EDIT: tomorrow's coffee on me, just trying to do the same setup as you, K-Leen with Voodoo.. probably overclocked, but with black transparent bar, when I did get the rom to load i didnt like that i couldnt read the time if a page was white
[Galaxy Tab  Android Development] blkblt412:
I used heimdall, though admittedly that is the only method I've tried. No luck using the gui front end or command line, same results either way. I even flashed back to factory and still have the same issue with the v3 kernel.
[Galaxy Tab  Android Development] futuregerald:
When I tried i was running a stock, factory new(just replaced) Sprint tab that did not have the new update, however it was definitely rooted since I rooted to backup my kernel using SGS kernel flasher. I flashed using the heimdall GUI and heimdall went to 100%, rebooted the device then it just sat at the first samsung logo. I did not hear the voice telling me it was converting or anything and no matter how many times I tried I could not boot in to recovery, the only thing I could do was go in to download mode and from there I flashed a stock rom using heimdall, got in to recovery and factory reset the device. I hope this information helps, also I used your previous v2 kernel which converted so this problem only happened when I tried to flash v3 kernel.
[Galaxy Tab  Android Development] jinsoku3g:
ughhh finally got it back to life, funny part is now I feel like I have a sprint tab, i flashed the firmware with no modem as directed, signal shows a R, which is .. i don't know? good thing i only use wifi right? i dont think im going to touch it for a while
[Galaxy Tab  Android Development] beeroatsnp90x:
Weird thing is, when you flash the voodoo kernel, you are supposed to hear converting data partition etc from the woman. I did not hear that in v2 either and I'm using a verizon tab. So im not even sure about what could be going on. I tried the kernel flasher app and also heimdall front end. So i'm clueless.

-Verizon Galaxy Tab

-Khasmek rom
[Galaxy Tab  Android Development] Boushh:
You didn't hear her voice because you were already converted to ext4.

I haven't been able do look into much today because I was busy with some other things, but I'll check it out more soon.
[Galaxy Tab  Android Development] cdred:
I installed kernel and it works great but phone no longer charges. Its recoginized thru usb but won't charge when hooked up to charger
[Galaxy Tab  Android Development] djf8:
I'm on a VZW tab and I am also getting stuck at the Samsung screen after flashing V3. I have flashed using SGS Kernel flasher, odin, and heimdall to attempt to flash this thing. Every method results in getting stuck at the Samsung screen at boot and recovery mode is no longer able to be opened. I can boot into download mode and flash back to v2 and I boot back up just fine.

On a side note can someone post a link to the OC v2 version the only copy of v2 I have atm is the standard version. Thanks

*Edit*

Not sure if it matters but I am on the stock rom.
[Galaxy Tab  Android Development] lhttan:
Can you upload kernel V2 . I am on a VZW tab and get stuck on kernel V3 too :(
[Galaxy Tab  Android Development] djf8:
Here is a copy of the non OC v2 kernel.

I'll leave this up for an hour or so I guess.

http://dl.dropbox.com/u/15498370/KhasMek.Voodoo.plus.CDMA.Tab.v2.zImage
[Galaxy Tab  Android Development] Boushh:
Okay. For the third time. I really want to fix this.

It hangs on the samsung screen

Is not nearly enough information for me to figure out what's going wrong. If you flashed via heimdall, did you use command line? gui? did it error, were you running stock kernel/rom before?

I'm getting just about half the information from some of you, and the other half from the other half of you, but I don't know if the missing parts are the same either.

Also, old versions of my kernels will always be indexed HERE but I really don't mind if you put them on your own servers/dropbox/whatever, lets just get v3 working for everyone. :)
[Galaxy Tab  Android Development] blkblt412:
Used Heimdall. Tried command line and gui. Kernel flashes just fine and tablet reboots, no errors. On initial reboot after flashing v3 kernel reboot tablet won't go past the Samsung screen. At no point are any errors displayed.
[Galaxy Tab  Android Development] futuregerald:
Also want to point out that it doesn't go past the first samsung screen, the static one, it doesn't get to the one with the glowing samsung logo and more importantly it does not let you boot in to recovery at all. only option is to go in to download mode.
[Galaxy Tab  Android Development] djf8:
Ok so I just used heimdall to completely restore my Verizon Tab back to a "out of the box" stock state. Let it boot up and everything worked fine. Booted into download mode and used the gui for heimdall to select the v3 zimage and set it in kernel and recovery. Pressed start and hiemdall completed 100% with no errors shown. At this point the tab reboots and brings up the Samsung boot screen, but doesn't load past that point. Using heimdall I was able to reflash v2 to kernal and recovery and now it boots up completly fine.

Please let me know if you have any questions.
[Galaxy Tab  Android Development] ap77:
This happened to me at first as well. I just re-flashed via heimdall again and it worked the second or third time.
[Galaxy Tab  Android Development] jinsoku3g:
Was having this issue as well. Im using K-Leanmod rom.

Here's how I fixed it :)

Flash Stock firmware using ODIN in download mode.

If you get this far, well good .. Until you restarted and got stuck at samsung again.

Instead of doing a circle, enter recovery mode using the Verizon Bootstrapper. ...then take a breath, recovery mode is a sight for sore eyes after this mess.

Wipe your caches, disable lagfix (this may not be necessary but I was tired of running in circles, anybody care to try w/o?)

Reboot into download mode and install the kernal through heimdall

At this point I assumed I was in the clear when I heard that sexy voice talking partitions, but it failed.. Said not enough room on card.. Bingo.. This very well may have BEEN the problem, it will allow you into the voodoo recovery now though, through cwm I wiped, reformatted, and repartitioned my sd, I changed my ram to 441 too. Again probably not necessary, but I take weird ways. From here, I rebooted into recovery and installed kleanmod rom.

On the restart, she speaks, then loads..fast.

Haven't had a problem since other than the FCs in my contacts (normal for this rom)

Im not responsible for what you do, this is just what I did, and kernal with rom is running very smooth

EDIT:should let you giys know im using v3 with overclock
[Galaxy Tab  Android Development] Boushh:
Heimdall command line or GUI guys? Also, maybe try flashing it via heimdall with the --kernel and not recovery. Just a thought.
[Galaxy Tab  Android Development] steveo11284:
Here's what I've tried, but have been stuck at the boot screen and I'm not able to get into recovery after flashing V3. I've tried both command line and GUI Heimdall. I've also tried doing just the kernel and both kernel and recovery. Also, I tried SGS Kernel Flasher and have had the same results. I have done all this on a fresh rom with no cwm installed and with it installed.