yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 8.9 Android Development] creamoncrop:
well im on the Official ICS Rom now. i really really want the looks, the features , everything else of CM9.

but im scared as you said,there's a lot of chance of bricking the device.

will it cause semi brick? recoverable Via Odin or CWM?

or a hard brick? thats fully unrecoverable ?
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
As far as I can tell it's a hard unrecoverable brick. I think the ROM should be ok to use but the kernel is dangerous when used in clockwork.

As I said before you can use the old 6.0.0.8 clockwork recovery with old kernel to flash the experimental CM9 as long as you can live with that the screen will not turn on on the first boot after running the recovery. Those who used the ports I made from the official 10.1 ics has seen this before.

Still, you are on your own but flashing the new Rom with the old recovery should be ok.
[Galaxy Tab 8.9 Android Development] fred_be9300:
Same for cwm 5.1.2.6 or 5.5.0.4 you think?
[Galaxy Tab 8.9 Android Development] pseudoheld:
Holy **** buddy I feel for you and all the others that bricked their tab.

What exactly triggers the brick? Is it formating sth?

Edit:

So i just flashed back to 6.0.0.1.0 and when I restarted my tab I got kernel panic upload mode... Restarted it again and now it's working. Damn I think I'm never gonna turn my tab off again. ;)

What the hell happened. What causes the kernel panic mode? Is it related to the brick?
[Galaxy Tab 8.9 Android Development] fred_be9300:
The only time I ever got "Kernel Panic upload mode" was when I used the option/feature in Titanium Backup to "force remove app (using recovery exploit)" (I wanted to uninstall system app Google+ from the ported stock-p7500 ICS rom I was on at the time). I was on CWM 5.1.2.6

TB forced a reboot, and it got stuck. I forced shutdown, and from then on, every reboot got to that screen, and I'd need to force a 2nd reboot to get to Android.

I got rid of it by flashing another CWM (5.5.0.4 - using the .zip)... After a while I went back to 5.1.2.6 because I like it better (more logical menu, and 5.5.0.4 doesn't have shutdown or reboot to recovery in the menu)

So, in summary, try to flash another CWM, maybe best via Odin.

PS: @kk : feel for you and all others that are bricked. Hope that's not the end of your journey with the gt89

---------- Post added at 01:28 AM ---------- Previous post was at 12:51 AM ----------

just FWIW. I was reading this http://xdaforums.com/showthread.php?p=26893617#post26893617

It's a summary of the EMMC brickbug on Samsung Epic 4G Touch (same issue seem to have started there much earlier, around May)

The worrying bit is where the author explains that the bad EMMC call can also be triggered by an update-binary that is built against buggy sources.

(because a format() in edify script is wholly executed by the update-binary, not passed on to the recovery's kernel for execution).

disclaimer: I'm not in my comfort zone discussing these low-level technical issues. Just passing on the info.
[Galaxy Tab 8.9 Android Development] creamoncrop:
oh i see, its not the ROM its the kernel,. hmm. im scared to do flash it. im using 6.0.0.8 CWM. and i want to flash the CM9 on the first page"mediafire link" im a safe to do with this version of CWM?
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
The only Clockwork that uses the 3.1.10 kernel was the 6.0.1.2 version that I've removed the links for. It's the only one that is dangerous asfaik.
[Galaxy Tab 8.9 Android Development] Jnn1:
Kallt_kaffe, I posted this on the general section too, but

Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?

So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data), since it'll run according to the bugless kernel (this is how we got the ics roms on our tabs in the first place, right)!

I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?

This should work, right? Or an I mistake somewhere?
[Galaxy Tab 8.9 Android Development] pseudoheld:
Was answered in the general thread. Won't work. :(
[Galaxy Tab 8.9 Android Development] Jnn1:
yeah, boscorama thankfully educated me on why ... but it sounds like all will be well as long as we stick to cwm 6.0.0.8 and lower ... for the moment, I'm just sticking to the cm10 preview I've had installed ...
[Galaxy Tab 8.9 Android Development] C-o-M:
Hi kallt_kaffe

What changes did you do exactly make to your sources for these experimental builds? i'd tried to integrate the 3.1 kernel, but it fails for two reasons:

Kernel 3.1 provides no bcmdhd.ko, so I must switch back to dhd.ko (and use wlan0 instead of eth0 again). I've reverted all changes for bcmdhd, but it still doesn't load the driver on boot (I can manually load it and it works)

The screen fails to resume from standby. It just flickers like an old tv. The tab is fully working though. You can even interact, you just don't see anything.

Would be great if you can give me a hint (or even send me your diff ;))
[Galaxy Tab 8.9 Android Development] pershoot:
Kaltkaffe, curious..

Using the official ICS libs from your own device do you get this behavior:

Screen off then on in landscape,

Rotate to portrait on lockscreen, do u get a flicker on top 25% of screen (near time)?

Rotate to portrait on market, and install an app. In the perm dialog, do you get a flicker around borders of dialog?

If you did and resolved it can u let me know what you have done to resolve it?

This also happens on 05-21 ventana libs (what the current libs for tab 10 are based off of (i gather)).

Thx.
[Galaxy Tab 8.9 Android Development] chriscsh:
try install the lastest build, full wipe & format system, after boot and can't connect to wifi

anyone?
[Galaxy Tab 8.9 Android Development] fred_be9300:
Last thing kallt_kaffe said, his device is still bricked. So perhaps someone else can test that... (I'm not running cm9 myself). Those who do test it, should mention exactly which snapshot of cm9 they run
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
There is a new build at devs page from 09.09.12. Is camera working now ? Changelogged is only 1 item :(
[Galaxy Tab 8.9 Android Development] C-o-M:
No. And it won't unless kallt_kaffe gets a new tab.
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
:( let's donate ..
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
It's the reverse for us. We get the flicker on landscape mode. Portrait mode is native on the 8.9 tabs so we are rotated in landscape mode while you are rotated in portrait mode on the 10.1 tabs.

Same here, but in landscape.

I have not been able to resolve it. Actually I wrote you a PM about this some time ago. Right now I'm still bricked so I cannot even try.

Sometimes the flickering is gone and then it comes back. Almost like it sometimes rotates and display the wrong buffer while double buffering, like it gets out of sync sometime and then once it snaps back it's totally gone and then suddenly after some use it comes back again. I've even tried the stock kernel from the official P7310 firmware and it behaves just the same.

Since we have it in landscape and you in portrait it has to have something to do with the rotating.
[Galaxy Tab 8.9 Android Development] sbE:
Why will Cyanogen Mod don't integrate a working camera without kallt_kaffe??
[Galaxy Tab 8.9 Android Development] C-o-M:
First of all, kallt_kaffe is the the only active developer of CyanogenMod for p5 (see https://github.com/CyanogenMod/android_device_samsung_p5wifi/commits/ics). Although he is just pulling the changes from p4 (Tab 10.1), he is still responsible for all development progress for p5.

Pershoot is currently building a 3.1 kernel for p4 and uses the new ICS blobs. With this kernel and the new camera drivers, the camera is working. Kallt_kaffe adapted that kernel and integrated it in his test builds. Unfortunately, they forgot to disable mmc_cap_erase (a damn bug that occur on all ICS kernels of many Samsung devices). This yields to the bricked tablets. It's a hard brick (damaged memory) and can only be repaired by replacing the main unit by Samsung.

I'm currently trying to reproduce kallt_kaffe's experimental changes. I have a working and safe kernel, but the system doesn't load the new wifi driver. When I get it working, I'll upload the patch. But I suppose, kallt_kaffe will be faster ;)
[Galaxy Tab 8.9 Android Development] pseudoheld:
great summary and explenation and good luck with building the kernel!!
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
I'll upload my CM9 repos in state they are now soon so that you can use them to compile a fresh CM9 with a safe kernel.
[Galaxy Tab 8.9 Android Development] sbE:
Thanks for your Cooperation!
[Galaxy Tab 8.9 Android Development] nexus_g:
Thanks! Finally we are rolling again.
[Galaxy Tab 8.9 Android Development] C-o-M:
Redone the changes from scratch and now wifi and both cameras are working. Unfortunately, it still cannot resume from standby :(
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
I've now uploaded my latest repos here: https://github.com/kalltkaffe/

The obly thing that I've changed since the 2012-09-03 version is that I've recompiled the kernel without mmc_cap_erase and also added the extra mmc_cap_erase block to BoardConfigCommon.mk (I hope this will enough)

Completely untested (I'm still bricked).

While it should be safe now I still recommend to not compile any new recoveries. Continue to use the old Clockwork for now, just in case.
[Galaxy Tab 8.9 Android Development] C-o-M:
Thanks. But I cannot see the great difference to my changes. I have to look deeper into it tonight. As said before, I have that strange issue that the graphics don't resume from standby. Looks a bit like an old misstuned tv. The tab is fully responsible, you can touch it, you see the differences in color on the screen, but it's just flickering. Maybe a sync issue? Hopefully, I'll find the bug tonight.
[Galaxy Tab 8.9 Android Development] jeffrey567:
Hey KK from what I know with Samsung is that a USB jig could get u into download mode I know the tab doesn't have a micro USB but if could find witch port goes witch then u could wire a resistor and just maybe...... to be continued
[Galaxy Tab 8.9 Android Development] C-o-M:
Hi kallt_kaffe

I've recompiled cm9 from scratch using that local_manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="kalltkaffe/galaxy-31" path="kernel/samsung/p5" />
<project name="kalltkaffe/android_device_samsung_p5-common" path="device/samsung/p5-common" />
<project name="kalltkaffe/android_device_samsung_p5wifi" path="device/samsung/p5wifi" />
<project name="kalltkaffe/proprietary_vendor_samsung" path="vendor/samsung" />
<remove-project name="CyanogenMod/android_hardware_broadcom_wlan" />
<project name="kalltkaffe/android_hardware_broadcom_wlan" path="hardware/broadcom/wlan" />
</manifest>

Unfortunately, it is still refusing to wake up from standby :(
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Did you ever try my 2012-09-03 version? If yes, did it not have that issue? If no, maybe it behaves just the same on your device.

On the 10.1 pershoot recommends flashing the bootloader from the official ICS to resolve some screen problems so it might depend on what bootloader it has.

I also do not remember if I had CONFIG_FB_TEGRA_CMC623_EXTEND on or off in the 2012-09-03 version. It was on, but I turned it off at some point to see if it would help with the occasional graphics glitches. The 10.1 kernel has it off but the 8.9 kernel usually has it on. Not sure what it does and I noticed no difference when I turned it off but perhaps your tablet needs it. Try turning it on and compile a new kernel.
[Galaxy Tab 8.9 Android Development] C-o-M:
Same issue there.

I just flashed P7310UELPB_P7310XARLPB. It didn't boot, no idea why. But at least the bootloader should be updated (according to ODIN log). Didn't solve the screen issue (I even see the strange flickering right after the reboot performed by odin, but it disappeared with the stock boot animation).

It's off on both of your kernels. I'll enable it and try again.
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Here's fresh builds with CMC623_EXTEND enabled in the kernel (and MMC_CAP_ERASE removed from kernel):

P7300: http://www.mediafire.com/?u5go1a0d55d6bcm

P7310: http://www.mediafire.com/?4eb6bbk3t5bn9d6

Should be safe but I cannot guarantee anything (cannot even test them).
[Galaxy Tab 8.9 Android Development] C-o-M:
Doesn't fix it :(
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Hmm... Are you one of those who need the alternate clockwork version? I suppose flashing stock ICS with Odin might help but that assumes you have a P7310 since there are no official P7300 version yet.
[Galaxy Tab 8.9 Android Development] pomah:
Im still using the new cwm version, should i still down to 6.0.8?
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Do NOT use version 6.0.1.2! Any other version should be fine.
[Galaxy Tab 8.9 Android Development] chriscsh:
the P7300 official ICS is out

maybe this can help on the new version ;)
[Galaxy Tab 8.9 Android Development] pomah:
Just installed your latest version, 20120918, flashed perfectly, but the graphic glitches in market are still there, and i used cwm 6.0.0.8 from this thread
[Galaxy Tab 8.9 Android Development] C-o-M:
The CWM version should not affect the installation at all.

I had a flash odyssey yesterday :cowboy: Since I don't know what my original ROM was (my P7310 with support for Switzerland, but none of the ROMs I've found seem to have support for it), I just flashed everything I could find :fingers-crossed:

Here are the results:

CM9 with 2.6 kernel -> working, but with known bugs (camera)

CM9 with 3.1 kernel -> no screen after resume :crying:

CM10 with 2.6 kernel -> working, but with known bugs (camera)

CM10 with 3.1 kernel -> no screen after resume :crying:

Your port of P7510 (3.1 kernel) -> no screen after resume :crying:

ICS P7310UELPB (via Odin) -> boot loop :crying:

ICS P7310UELPB (via CWM) -> no screen after resume :crying:

HC P7310XXKJ4 (via Odin) -> everything fine, but well, it's honeycomb ...

ICS P7310XXLPJ (OTA released yesterday!) -> everything fine :victory:

So at least I have a fully working ICS with 3.1 kernel now. I'll check for differences tonight. Maybe it's just a blob, maybe it's kernel configuration, maybe I just have a scary device ;)
[Galaxy Tab 8.9 Android Development] taiger78:
WHAT where :confused:

---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------

Ah okay found the leaked version.
[Galaxy Tab 8.9 Android Development] C-o-M:
Update:

...

ICS P7310XXLPJ (OTA released yesterday!) -> everything fine

flashed CWM -> screen scrolls, but usable

CM9 with 3.1 kernel -> everything fine :victory:

I guess the XXLPJ bootloader made it.

There are still some interesting facts:

There are some driver changes between GT-P7510_ICS_Opensource_Update2 (8-Aug) and GT-P7300_HK_ICS_Opensource_Update1 (27-Aug)

kalltkaffe_samsung_p5wifi-ics_defconfig is slightly different from XXLPJ's config (though I think that are only minor changes)

in XXLPJ only the camera and audio blobs are different than the UELPB ones

Does the current build has any issues? Maybe there is some fix in the new code.
[Galaxy Tab 8.9 Android Development] mali100:
The kernel from the GT-P7300_HK_ICS_Opensource_Update1 source still contains MMC_CAP_ERASE, so everyone who tries to compile the kernel should remove it first (https://github.com/kalltkaffe/galaxy-31/commit/b749e1f5f443bfd6867ea254e3bd25277954c247)
[Galaxy Tab 8.9 Android Development] SecretAgentKen:
Looks like there's a solution to the MMC bricking. http://xdaforums.com/showthread.php?t=1667886
[Galaxy Tab 8.9 Android Development] C-o-M:
The only solution is replacing the main unit. The PIT file method is just a workaround. The damaged mmc is gone forever.
[Galaxy Tab 8.9 Android Development] kosmepe:
There is a new (2012-09-23 20:13:18) nightly on CyanogenMod site http://get.cm/?device=p5. Does anybody know what was changed? Anybody tested it?
[Galaxy Tab 8.9 Android Development] earldroid:
Here is the changelog

http://changelog.bbqdroid.org/#p5/cm9/1348431198
[Galaxy Tab 8.9 Android Development] kosmepe:
Thanks!
[Galaxy Tab 8.9 Android Development] pomah:
It seems like the cameras are not working in this build...

But I'm not getting any graphic glitches and it seems faster than the 0903 build
[Galaxy Tab 8.9 Android Development] sbE:
it's very annoying that p7300 users still don't have a stable rom with working camera. :( what's up with samsung? what's up with the modding community?

is our p7300 so unimportant??

...i can't believe that because imho this tab is nearly perfect and i loooooooooove it so much. ;)
[Galaxy Tab 8.9 Android Development] chriscsh:
seem you haven't try this

http://xdaforums.com/showthread.php?t=1893456

this one have working camera, cause is base on the official ICS rom :D
[Galaxy Tab 8.9 Android Development] sbE:
i've seen it...it's based on an unreleased official (test)rom. it looks like that this rom is not very stable (users with battery & kernel problems). so i can't believe that this rom will be the official version which will samsung release someday. or i'm false!?

btw...it seems the rom has the whole samsung stuff installed... :(
[Galaxy Tab 8.9 Android Development] kosmepe:
This ROM is stable and does not have battery problems (it was the one of KK which had).

BUT of course this is stock and not CyanogenMod....

What is really a pity is that we do not have a CM9 ROM with all hardware working :p
[Galaxy Tab 8.9 Android Development] C-o-M:
Which hardware is not working in the latest CM9 build?
[Galaxy Tab 8.9 Android Development] pomah:
None of the cameras are working
[Galaxy Tab 8.9 Android Development] kosmepe:
No GPS either
[Galaxy Tab 8.9 Android Development] C-o-M:
Use this build, both cameras are working:
[Galaxy Tab 8.9 Android Development] pomah:
I ran that build before, it had problems with graphics glitches in market and so on.
[Galaxy Tab 8.9 Android Development] truden:
As usual, CM guys are showing magic :)

Thank you!

It would be comforting for all of us to know how long it will take to fix the camera, so we could adjust our mind for a wait ;)
[Galaxy Tab 8.9 Android Development] C-o-M:
The camera will probably never be fixed in CM9. Whilst it is working with 3.1 kernel, you get those ugly graphic glitches at the same time. No problem though in CM10. I'll post an experimental build in the CM10 thread in the next days.
[Galaxy Tab 8.9 Android Development] truden:
Thank you for the input :)
[Galaxy Tab 8.9 Android Development] Thenetstriker:
It seams as the Android USB Host Api is not working in CM 9 on my p5wifi. I've checked it using the app "USB Device Info". Under tab "Linux" I did see my usb device, but not under the "Android" tab. Is this part maybe still in development and will be working in a later release?
[Galaxy Tab 8.9 Android Development] aheeejd:
Delete

Sent from my GT-P7310 using Xparent Blue Tapatalk 2
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Where can I find the XXLPJ bootloader?

I got my 8.9 back from repair and it originally had 3.1 firmware but came back with 3.2 and the bootloader I have now get's the same problems as you described. The only P7310 ICS over at samfirmware doesn't contain any bootloader so flashing it doesn't help.
[Galaxy Tab 8.9 Android Development] pomah:
Great news! I hope we can soon see som new firmware now that you are back in the game Kallt! (fingers crossed)
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Got a new CM9 build ready but ran into problems when the new bootloader my repaired tab came back with.

Hopefully I got it working now.

I figured since the XAR 4.0.4 update does not contain a bootloader the XAR 3.2 bootloader should work so I flashed the XAR 3.2 firmware (which does contain a bootloader) and then the XAR 4.0.4 firmware. Now the garbled screen after sleep problem is gone so it looks like I'm back in business again. :)
[Galaxy Tab 8.9 Android Development] :
good thing you're back again!
[Galaxy Tab 8.9 Android Development] pseudoheld:
glad to see you back again kallt!
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Here's new CM9 builds.

p7300: http://www.mediafire.com/?y3o75y4mnfxyae6

p7310: http://www.mediafire.com/?jq0ikx96fdiv8cd

I got garbled screen after turning the screen off and on again until I flashed this 3.2 build with Odin: http://samsung-updates.com/get/652/Samsung_Firmware_GT-P7310_XAR_P7310UELA3_Android_3_2.html

I also flashed the 4.0.4 XAR firmware afterwards but since that one does not contain a bootloader I think flashing the 3.2 version should be enough. Also if you ran the old CM9 builds with the 3.1 kernel without problems then you likely already have a compatible bootloader.

Use the old Clockwork for now. I'm using a 3.1-kernel based clockwork that should be safe but I do not feel comfortable with releasing it yet.

Old issues are still there like the graphics glitches in landscape mode and the crashing Google Maps. For Google maps you can find a compatible version in pershoots blog: http://droidbasement.com/db-blog/

As for the graphics glitches (that exist in portrait mode for the 10.1 builds) they don't exist in CM10 according to pershoot so once we move to CM10 it should no longer be an issue.
[Galaxy Tab 8.9 Android Development] C-o-M:
Hi kallt_kaffe

Great to see you back. Hopefully you have some more experience than me with this device. I'm still trying to build a cm10 rom. After some try and error I figured out how to get camera and wifi working. But I still have the problem that the tab doesn't fully resume from deep sleep. The kernel resume function throws a 'Unable to handle kernel paging request' oops and reboots.

The weird thing is that its not the kernel: I tried yours, I tried mine, I even tried an official Samsung one, it's always the same. It's also independent whether wifi is on or off.

I've pushed all my changes to github; feel free to pull them. Maybe you'll see the problem.

PS: I'm sorry, I forgot to mention that: a day after my flashing odyssey I saw that the problem is already described in the FAQ. Including the solution to flash UELA :silly:
[Galaxy Tab 8.9 Android Development] legionz:
market issues

hey i have no android market is there anyway to install it on the new rom it keeps closing on its own when i dl from extnral sourse
[Galaxy Tab 8.9 Android Development] randomb:
Hello Hello,

i have great results on latest build from 01-23 with galaxiansouv2 apps

the stretch on roating is gone! which is really really nice.