yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] paulshields:
I flashed the Euro cmr which seemed to go fine. To test it I did a backup, then a factory reset via cmr (which then booted into the default tab setup), and then a restore of the backup I'd previously done. It all seemed to come back ok, but on testing found the camera stopped working and the buttons didn't light up when active. Not sure if that's just local to me or related to the new kernel, but posting for info anyway.

Restored via a heimdall reflash of JM6, re-root, app restore via titanium backup and everything's back as it was prior to cmr flash.

Snippet from logcat when firing up camera:

E/Camera ( 3676): initRemains()
E/TwIndicatorsRemainCount( 3676): setRemainCount1067
E/AbstractCameraActivity( 3676): bAutoBrightness = false, VALUES = 0.65
E/AbstractCameraActivity( 3676): onResume : intentExtras is null
E/SensorManager( 3676): ####### akmd2 started!!!
E/SecCamera-JNI-Cpp( 3676): JNI_OnLoad
E/SecCamera-JNI-Java( 3676): SecCamera.open()
E/CameraHardwareSec( 2425): Smartautoscene thread was already stop
E/SecCamera( 2425): Blur is not setting in Back camera.
E/MediaPlayerService( 2425): Client::notify In
E/MediaPlayer( 2425): message received msg=1, ext1=0, ext2=0
E/MediaPlayerService( 2425): Client::notify In
E/MediaPlayer( 2425): message received msg=1, ext1=0, ext2=0
E/CameraHardwareSec( 2425): Smartautoscene thread was already stop
E/SecCamera( 2425): Blur is not setting in Back camera.
E/CameraHardwareSec( 2425): Smartautoscene thread was already stop
E/SecCamera( 2425): Blur is not setting in Back camera.
E/CameraEngine( 3676): getGpsLocation : loc is null
E/SensorManager( 3676): registerListener 1:BMA150 delay:240
E/SensorManager( 3676): =======>>>Sensor Thread RUNNING <<<========
E/SecCamera( 2425): ERR(fimc_v4l2_s_ctrl):VIDIOC_S_CTRL failed, ret: -1
E/SecCamera( 2425): int android::SecCamera::startPreview()::1225 fail. errno: Invalid argument
E/CameraHardwareSec( 2425): ERR(startPreview):Fail on mSecCamera->startPreview()
E/SecCamera-JNI-Java( 3676): postEventFromNative
E/CameraEngine( 3676): CameraEngine-RuntimeException
E/WindowManager( 2518): Overwriting rotation value from 1
E/SecCamera-JNI-Java( 3676): Error -2
E/CameraEngine( 3676): ErrorCallback.onError (-2)
E/Camera ( 3676): Initialize Camera Sound
[Galaxy Tab  Android Development] cramjammer:
FYI- For noobs like me...this is still BETA. i know it was said already but i feel like the poster child for this one. i have the vzw tab, usa.

I learned the hard way, which i guess was good because i did learn some things on my own. I followed all the steps for loading CWM and Koush's Bootstrap. After two days (bug free) i ended up stuck at samsung boot image...not sure why really but i have to thank Jarrettv on page 15, post 143. his instrutions do work. it got me out of a jam.

however I'm only saying this because i wasnt patient and didnt wait. for more experienced people this might be OK, but this really gave me some grief. so again, if you're not comfortable with flashing, heimdall, etc....WAIT. Trust me on this one. without the forums i would have been screwed.

so, thank you!
[Galaxy Tab  Android Development] Blinkergffg:
After installing bootstrapper I lost the ability to connect to a Bluetooth device. I want to back to stock kernel. I want to go back to 100% stock and start over. Any help would be appreciated.
[Galaxy Tab  Android Development] shmigao:
use market access

google "android market access"
[Galaxy Tab  Android Development] rmanaudio:
Anyone know how to do this via Windows?

In what format do you save the zImage and flash_image files so it can be pushed?
[Galaxy Tab  Android Development] cultldr:
Unfortunately on mine everything looks like it is working, drivers are fine, heimdall says it flashed and still Samsung logo. So yes I should have waited but bricked and it's just not coming back.

Also while it says it's in beta here ( after being downloaded, purchased and bricked) it does not and did not say that in the market. It says if you're not comfortable with heimdall or odin and I had no problems with getting it flashed or getting the tab to that state in all those directions. Just for some reason it is not working on mine and I have a paperweight and needed it for a trip so going to end up having to get a new one.

So yes I agree with you, wait or just don't do it at all. I'm glad some of you got it back and are able to use it, I am not one of those people and a lot of people seem to just say noob and make you feel like you're an idiot. I guess I am, buying a 2.00 app and bricking my 600 tab, yep I definitely am an idiot. Lesson learned and won't happen again.
[Galaxy Tab  Android Development] Yaotl:
which zImage did you flash?
[Galaxy Tab  Android Development] dsb9938:
Guess I got lucky.

VZW Tab, Bootstrap from the market.

Not a single problem.

Flashed, reooted, backed up, converted, running fine.

Thanks k,

D
[Galaxy Tab  Android Development] Landroid:
i noticed that after flashing CWM my softkey lights arent workin! any solutions for that?
[Galaxy Tab  Android Development] papi92:
What's the point of the recovery right now? There are no custom roms. I'd just,wait till one comes out then worry about it.
[Galaxy Tab  Android Development] roan67:
Hi

has anyone successfully applied to the EUR version?

If not. Why let the link?

I'm 6th unsuccessful attempts, 3 in manual. Between each manipulation. 1 flash

I was happy...... for nothing: (
[Galaxy Tab  Android Development] shmigao:
Chicken and egg
[Galaxy Tab  Android Development] Yaotl:
for me, nandroid. I tend to mess with little things that work on other android phones to see if they work on the tab with no problem. since I'm not programming savvy, I tend to break things often :)
[Galaxy Tab  Android Development] paulshields:
Was this with the "International" kernel? I had the same problem (+ camera didn't work). Ended up restoring via Heimdall for now so can't help, but looks like it wasn't just an issue local to my setup.

I'd advise people to tread very carefully with this, even if it's labeled as "beta". I'm also surprised that there's a paid-for version in the Marketplace if it's possible to cause the issues being reported here (I flashed via adb as I'm a cheapskate :)).
[Galaxy Tab  Android Development] shmigao:
Same here

10char
[Galaxy Tab  Android Development] Landroid:
same **** as in the early alpha version.... but hey we got a working nandroid and we can.flash update.zips! :)
[Galaxy Tab  Android Development] shmigao:
Used bootstrap for Euro tab

Good

- backup ok

- convert to ext4 ok

- restore ok

- boot ok

- reboot into clockwork recovery ok

- 2nd backup ok

Bad

- no softkey back light

- in ROM Manager if I want to use the functions (such as Manage Backups) it tells me to install clockwork recovery (thought I had done that already...), and in the pop up window to choose the appropriate device, Galaxy Tab Euro Version is not listed

- fix_permissions doesn't do anything
[Galaxy Tab  Android Development] Technomancer:
I just tested Bluetooth pairing on mine (AT&T Tab, JK5 and international_zImage) and Bluetooth pairing is hosed as well. It pairs for a second and then changes state to "Pair with this device".

I tried pairing with a headset and BT keyboard that used to work before and it fails.

I can post adb logcat if necessary.
[Galaxy Tab  Android Development] shmigao:
Works, apart from the issues I reported in my post above
[Galaxy Tab  Android Development] Landroid:
just flashed back to JMA cause of the backlight and camera issues! I wait for a final version!
[Galaxy Tab  Android Development] shmigao:
Well I guess we need to wait for a fixed kernel from koush

I just wonder why when I successfully flashed clockwork recovery, rom manager still says «recovery unknown»???
[Galaxy Tab  Android Development] TheGrammarFreak:
I tested the interational version for Koush, everything works fine for me. Softkey backlights, backup and restore. The lot

Sent from my GT-P1000
[Galaxy Tab  Android Development] rmanaudio:
I tried the manual way with the 2 files and commands and it does not work. Just hangs at the TAB screen.
[Galaxy Tab  Android Development] shmigao:
Camera working?

Did you use bootstrap our manual adb commands?

What firmware are you on?
[Galaxy Tab  Android Development] TheGrammarFreak:
Camera works

I was made to use both (damn Koush), and I'm on the latest official firmware in the UK: JJ7

Sent from my GT-P1000
[Galaxy Tab  Android Development] Unimaginative:
The bootstrap app boned my Tab half-way to Mars. Wouldn't pass initial boot screen or boot recovery. Ah well; you win some and you lose some.
[Galaxy Tab  Android Development] shmigao:
Well that's great.I am on JM6 and have all the issues others also reported. No camera, no backlight, and i	would bet no bluetooth either (can't test it right now).

Why did koush «make» you do both methods? Please explain...
[Galaxy Tab  Android Development] TheGrammarFreak:
He asked for help on twitter, I responded.

Sent from my GT-P1000
[Galaxy Tab  Android Development] shmigao:
Ok.well glad for you

Sad for all that have the problems...

Wonder what causes the different behavior.

I did not anything special, or wong...

1. Install bootstrap

2. Run bootstrap

3. reboot recovery

4. Reboot

5. Install rom manager

Could it be the current firmware?
[Galaxy Tab  Android Development] TheGrammarFreak:
You don't need ROM Manager(get used to using recovery manually). Its possible that the new firmwares are expecting a different kernel version

Sent from my GT-P1000
[Galaxy Tab  Android Development] shmigao:
Yes I dont "need" rom manager, because I can do all in recovery itself, but rom manager provides a user interface ...it should work.

Well if it's a firmware issue, then first post should say a disclaimer that the method had been tested only with a particular firmware.

Okay.I will be patient.maybe we will get a international kernel update that fixes the problems
[Galaxy Tab  Android Development] TheGrammarFreak:
You could try downgrading your firmware to test that hypothesis. And I don't think ROM Manager even works with euro tabs yet.

Sent from my GT-P1000
[Galaxy Tab  Android Development] paulshields:
I suspect that's the case as well. It would be useful info for those with issues to state what firmware they're running prior to flashing this recovery kernel. I was on the Euro JM6 and had issues with soft key light and camera. I've no intention of reverting back to stock firmware myself, but if the International kernel is working perfectly with stock firmware then that's useful info.
[Galaxy Tab  Android Development] shmigao:
I could.

Like to think there might be a kernel update that can support newer firmwares.

If rom manager is not supported, why does instruction in first post under euro tab say:

"Use ROM Manager to create a Backup.

Download ROM Manager from the Market.

Flash Recovery.

Choose the appropriate Galaxy Tab version.

If you appreciate my work, please buy the Premium version of ROM Manager"

Copy paste?

Fix_permissions doesn't work because it looks in data/data instead of /dbdata

Half baked bread
[Galaxy Tab  Android Development] shmigao:
Do you still have the broken cam, backlight, etc., or how did you fix it?
[Galaxy Tab  Android Development] paulshields:
In the end I went back to a full flash of the JM6 firmware via heimdall (including selecting partitioning). Initially I restored the backup that cmr makes prior to the install of the recovery kernel, but that still had the same issues - which was a bit worrying as I'd expected the backup to be a complete recovery (I'm thinking that maybe it doesn't restore the kernel? Didn't check that closely at the time).

Anyway, heimdall came to the rescue as it often does... ;).
[Galaxy Tab  Android Development] TheGrammarFreak:
Copy paste.

These changes to the kernel require the source code. The source code released is for the latest official firmware, not the leaked builds.

Sent from my GT-P1000
[Galaxy Tab  Android Development] cultldr:
The one in the OP first page for Vzw
[Galaxy Tab  Android Development] Koush:
To revert to stock:

heimdall flash --factoryfs factoryfs.rfs --kernel zImage --recovery zImage

Then boot into stock recovery and wipe data.
[Galaxy Tab  Android Development] Koush:
I believe I may have found the cause of several bugs; I am using the busybox sh link rather than the normal Android sh. This may be causing a lot of problems with scripts executing, and thus possibly various initializations of the hardware. I'll put new releases out for Vzw and Euro tonight.
[Galaxy Tab  Android Development] Frustu:
Koush sorry for distub but on rommanager when i try to install recovery in the appropiate device euro tab missing , how device i have to select verizon att t mobile or you update the list soon?
[Galaxy Tab  Android Development] annafil:
Used the bootstrap for euro on my original Asian firmware, got stuck on booting into recovery so had to Odin a new firmware. Then I tried with xjm6 euro and I saw clockworkmod but then it died with the message can't find sd card giving me the same boot issue so had to flash again.

Not really complaining, xjm6 is way better than what I had before but warning for those unsure! Make a backup or wait for a while if you don't want to spend half the night restoring :-)

Im wondering if im missing a step? I ran the first step in the bootstrap then it said success, boot into recovery so I pressed the next button and then the above happened.

Anyone here with a working bootstrap?

Edit: Duh Koush just saw your post. Shall wait for tonight's update, and invest in Titanium backup pro to save myself some time if things go pear shaped again :D

Thanks for your hard work.
[Galaxy Tab  Android Development] naddie:
OP: You might want to add that you need to download the Android SDK and install it, as well as Kies for the drivers. Took me a while to figure it out.

Gotta help the noobs out. :)

http://developer.android.com/sdk/index.html

I don't know where to download Kies though. Samsung seems to be hiding it...
[Galaxy Tab  Android Development] shmigao:
great! as i said - i will be waiting patiently :-)

mh, one question... since the backlight, camera and bluetooth don't work now, would i have to revert first, and then apply your new release, will the new release fix over it?

also, as mentioned earlier, fix_permissions doesn't do anything, because it looks for the app files in data/data, rather than in /dbdata.

I am using a modified fix_permissions script i found by googleing it. would be nice if it could be integrated working in the recovery.
[Galaxy Tab  Android Development] shmigao:
right, i had the same experience. when i applied the nandroid of "before ext4 conversion" i already had "the feeling" that it wouldn't revert completely. it's probably the kernel...

I am now prepared to flash rotohammer's JMC update via Odin 1.7

should work shouldn't it????
[Galaxy Tab  Android Development] paulshields:
JMC runs great! I don't use Odin but heindall flashed it fine.
[Galaxy Tab  Android Development] :
I am running into an issue with my VZW Tab. I have rooted, installed CWM recovery, been through the bootstrap process, etc all without incidence. I am back up and running successfully on the ext4 filesystem (very noticeable speed improvement, btw!) and everything appeared to be working properly.

Here's the issue I am now having. I ran my Tab down to about 12% battery last night and powered it off before going to bed. I plugged it in to charge (wall charger) and noticed the on-screen battery show up as usual. However, it stayed on the screen way too long. I unplugged my charger and the on-screen battery stayed on the screen.

The battery never shows the charge amount. I only see the shape of the battery with the activity indicator (the 'rotating circle' activity indicator) stuck in the center of the battery. The Tab appears hung at this point. I plugged my Tab into my computer and attempted to 'adb shell' into it--device not found. I then tried to 'adb logcat' and I am left with '- waiting for device -' in my command prompt.

In my experience with other Android devices, the results of the commands I listed above generally mean the device is completely unresponsive. At this point, I am left to hold my Tab power button for ~7 seconds which actually powers it fully off. I can then power it on straight away and it runs as normal.

I can charge my Tab off the wall charger as long as it is powered up and in the OS. My concern, however, is that someone will run their Tab completely out--as in, the OS powers down the Tab on its own. They *might* not be able to charge it up enough to get it to power into the OS again. Read: completely dead device.

Has anyone else noticed the same behavior? If I need to re-flash anything - kernel or otherwise - I can certainly do that to troubleshoot. This is quite troubling to me, however. I do not want to end up in a scenario where I cannot even charge my Tab anymore.

Thanks!
[Galaxy Tab  Android Development] mosone23:
Same. just noticed it last night. Tab said low battery, and instantly went to the aforementioned screen. It was a little harder than just holding the power button to get it back on though....
[Galaxy Tab  Android Development] :
How did you manage to get it back on, though?
[Galaxy Tab  Android Development] mosone23:
At first I was mashing buttons like I was tryin to unlock a secret level on contra...(freakin out cause I couldn't get ANY programs to recognize it..tried kies,adb,even superoneclick) finally I just un plugged it,shut down the screen(so the null battery was no longer on the screen)and walked away for a few minutes...came back hit power and it booted up.keeping it charged now. Im at a loss.
[Galaxy Tab  Android Development] BuglessFan:
The only time this happened to me was after root but before CWM. It just "slept" in the middle of the day when it had around 30% battery. When leaving it plugged in for 30 minutes did nothing, I wound up holding the power button down for what seemed like 20 or 30 seconds to get it to reboot. It's kind of scary to not be able to do a battery pull.
[Galaxy Tab  Android Development] bert269:
Which CWM recovery ?

Hey

I am on T-mobile TAB hardware, with the t-mobile CWM recovery installed and working. If I want to install the EURO rom, which CWM recovery do I need to install? - T-mobile or EURO ?

(is this hardware related of rom related?)

Thanks for the great help
[Galaxy Tab  Android Development] Technomancer:
Euro rom uses euro kernel so use euro (international) recovery.
[Galaxy Tab  Android Development] cramjammer:
Bugless, monsone23, and Mr. Blippy....i have the same issue with charging while tab is off. (vzw tab) after a few days of no issues with Bootstrap and CWM it appeared that way as well. even after i flashed zimage to fix samasung-hang using heimdall, thats when i noticed it.

i pretty much uninstalled bootstrap and CWM and am just waiting till its out of BETA.

just wanted to share that i have had the same issue...but for the record, i can reboot with root tools and manual reboot without a problem, but try to turn off and charge does not work...not matter how long you leave it. at this point i'm too jaded to mess with it anymore. i barely got it back on...NOOB HERE!

just wanted to share.

thanks

cram-jam
[Galaxy Tab  Android Development] Koush:
I have updated the Euro/international and Verizon kernels. Let me know if the issue is fixed.
[Galaxy Tab  Android Development] Frustu:
The euro kernel works with all firmwares? In italy the last official update is the JK5 , or i have to update it with the last Samfirmaware ? Thank you
[Galaxy Tab  Android Development] Yaotl:
The VZW image in the OP now borked my Tab. Extracted the one from the bootstrap apk and it works like it did before.

I hadn't noticed the battery thing as I never charge with my tab off. When I was having all of the issues with my previous Tab though, it did still charge with the battery icon stuck like that. It still charges, just doesn't show anything.
[Galaxy Tab  Android Development] :
I just flashed the updated VZW kernel. After I power off my Tab and plug in the wall charger, I see a quick flash of some text (much like when booting into recovery) but I still experience the same issue as before. It still hangs on the charging screen.
[Galaxy Tab  Android Development] LuckOne79:
thanks, im will give it 2nd try today. :-)

Sent from my GT-P1000
[Galaxy Tab  Android Development] robonutz:
It still charges... the indicator is just mucked up.

I've run mine down to 0 two or three times already.
[Galaxy Tab  Android Development] :
That's good to know. I hesitated to leave mine plugged in too long in case any internal mechanisms to monitor temperature and charge rate/level were also hung. Secondly, I know LCD panels are less prone to image persistence than CRT, but it can still happen. I would hate to have a semi-permanent battery image persisting on my LCD display after several charging cycles. :p
[Galaxy Tab  Android Development] LuckOne79:
@koush:

Same problem, it hangs/stuck on boot screen. Tryed the bootstrapper tool from market v1.04. :(

I am on JMC ... Maybe i should try stock rom JK1. But not sure if i can reverse to JK1 from JMC by heimdal/Odin ...

Anyway, you will get this to work ... :-)

Will try a 3rd time today :D
[Galaxy Tab  Android Development] Landroid:
appearently it doesnt work on JJ4 cause i did the same as on JM6 and it stuck on samsung galaxy tab (boot splash) screen!
[Galaxy Tab  Android Development] Blinkergffg:
Update Verizon Bootstrap, rebooted, now I stuck on Samsung Screen. Try Home, up volume and power button. Goes to Samsung screen and freezes.

Can someone help me get stock Kernel back.
[Galaxy Tab  Android Development] LuckOne79:
You have to go in Download Mode (Power+ DownVol) and flash via Odin/Heimdal.
[Galaxy Tab  Android Development] Frustu:
For help the noobs ( like me ) somebody can post a little guide step by step for flashing the stock kernel whit heimdall please? I know a little odin but i dont know how to flash only a zimage file.

Thank you
[Galaxy Tab  Android Development] coldheater:
Great work! I need a little help. I purchased a used T-Mobile USA Tablet and it came with a custom rom on it. I just want to put it back to the stock. Can anyone help me do so? I read the info above and i'm lost.

Thank you in advance.
[Galaxy Tab  Android Development] paulshields:
Koush posted a couple of pages ago how to recover:

http://xdaforums.com/showpost.php?p=9998032&postcount=223

Good luck!
[Galaxy Tab  Android Development] Frustu:
I dont have to restore for now it s just for have a complete guide to use heimdall and to know what to do to make it work i always have the MSVCP100.dll error on win 7 64 bit
[Galaxy Tab  Android Development] cultldr:
I got this link from the Heimdall download site and once installed it takes care of that error:

http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en

I have Window 7 Pro 64 bit and this worked fine.
[Galaxy Tab  Android Development] Frustu:
Thank you friend now works fine!!!
[Galaxy Tab  Android Development] Technomancer:
I have tried flashing it with flash_image boot international_zImage but it didnt quite work out (stuck at samsung logo after boot). So I flashed it with heimdall flash --kernel international_zImage and it worked. Unfortunately bluetooth pairing is still broken. I even had force close once in Bluetooth Settings.

Is it possible it is some permissions problem (maybe due to EXT4?). When I try pairing with a headset, it looks like the headset accepts the pairing because the LED on it stops blinking but the Bluetooth Settings UI status does not change to paired or connected, so maybe the pairing/connection status is not updated on the Tab due to permission problems?
[Galaxy Tab  Android Development] Blinkergffg:
Where do I get the "factoryfs factoryfs.rfs" file and the recovery zImage.
[Galaxy Tab  Android Development] vanam:
hi there i have tmobile version mode sgh-t849 which unable to chmod boot: No such file or dirctory need help thank inadvan