Database Info

Samsung Media Hub back?

if i am rooted with superrooter, how do i get the Media Hub back when they start renting movies and shows?

clueless captivate said:
if i am rooted with superrooter, how do i get the Media Hub back when they start renting movies and shows?
Click to expand...
Click to collapse
Install this....

ok total noob, how do i do that......
tried to open it on my phone, with the xda app, can't see it, do i manually put in on using USB?

can anyone else help me out with this?

clueless captivate said:
can anyone else help me out with this?
Click to expand...
Click to collapse
Why not use the andriodcentral wonder machine? This will load the apk for you....

thanks i will try that tonight and let you know how it goes

i downloaded the .apk and tried to install it.
I get to summary and click "install".
Next it says
"Replace application
The application you are installing will replace another application.
All previous user data will be saved"
Kinda weird because i'm using super rooter and though that stuff was removed...but figured i screwed something up on the tibu restore of my apps and maybe restored it somehow (even though its no where in my phone).
I click okay. I see the regular install screen you'd see from a .apk if you are installing it that tells you what it has access to. I click install. it acts like it instals for a split second then says:
"aplication not installed". all i can click is done.
any ideas?

If you use the Android Central sideloader you will see this error.
Installing application
467 KB/s (199818 bytes in 0.416s)
pkg: /data/local/tmp/to_install.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
I am trying to install it again too and I have not got it to work yet.

If it already sees a version there, you may have to manually install it using adb install with the -r switch.

the loader exe is giving me some error about payload???? i see no files in this folder...? help!

pinoymutt said:
If it already sees a version there, you may have to manually install it using adb install with the -r switch.
Click to expand...
Click to collapse
Any other ideas?
\captivate\Droid Explorer\SDK\tools>adb install -r MediaHub.apk
262 KB/s (199818 bytes in 0.744s)
pkg: /data/local/tmp/MediaHub.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
By the way thank you for your help. I have asked twice on the SRE thread and have got no help there. Seeing as who it is the SRE that removed the file and the files he has posted to install the removed apps is what I am using I find that a little troublesum

i also have had no luck putting this back on.....

One last try. Anyone have any more ideas?

Over on the SRE thread I got a answer from DG.
--------cut-------
copy xxxx.apk to your sdcard
adb shell
su
adb mv xxxx.apk /system/app
or use root explorer or similar to copy it to the system app folder
reboot and it will be installed

Does it say "Not yet available. Check again later." for everyone else? I'm trying to use this on my Droid Eris.

Can't get to ClockworkMod

I installed Flashback 10.1 a while back. Today I wanted to install 10.3 and found out that I couldn't get into ClockworkMod at all. It would do a normal reboot instead of going to the recovery mode.
Any help is appreciated.

Just to be sure, you *are* holding the volume + button when you press the power button and keeping it held down until you see "recovery key detected" in the upper left corner?

Yes, I see
recovery key detected
Booting recovery kernel image
But it would stay there with the birds and "View Sonic - See the difference" forever, never go further than that.

Use nvflash and reload only ClockworkMod. Use the commands in this thread.

rajeevvp said:
Use nvflash and reload only ClockworkMod. Use the commands in this thread.
Click to expand...
Click to collapse
Hello rajeevvp,
I tried this method but I get the following error message...
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
When I run download.bat by itself, I get a message, "USB device not found".
Can you offer any suggestions?
Thanks,
ssummerlin

ssummerlin said:
I tried this method but I get the following error message...
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
When I run download.bat by itself, I get a message, "USB device not found".
Can you offer any suggestions?
Click to expand...
Click to collapse
That's a very strange error. What led to it?
Try these suggestions one by one.
1. Use a different USB cable and port on the PC. Bad cables and USB ports have been known to cause problems.
2. Open the gTab up and use the reset button, then disconnect and reconnect the battery.
3. Do the nvflash on Linux.

Did you ever find a fix for this, cub2000?
I ran into the same thing, when I attempted to update to CWM 5.5.04 (via flashable zip) using the procedures outlined in the [RECOVERY - 1.2] ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH thread.
After doing so, I figured my best bet was to roll back to bekit's original image, so I followed the procedures outlined in the [STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions) thread to roll back to TnT 1.0-2638.
I can't remember the specific ROM I was on before -- it's been ages since I last powered up my gTab. It may have been TnT Lite. Whatever it was, I'm fairly certain I was running Bootloader v1.1.
After nvflashing back to 1.0-2638, TnT offers an update as soon as I connect to wifi, but the update fails in the same way that CWM fails. It hangs here:
recovery key detected
Booting recovery kernel image​
The awful, original TnT still runs on my tab, so it's not a true bricking (or even a soft-brick), but now I'm stuck with... well, I'm stuck with the awful, original TnT.
If I find a way around this, I'll let you know. If you've already found one, please let me know!
Thanks.

See this thread.

Thanks, rajeevvp. I actually found a different solution before I got your recommendation; just hadn't had a chance to update this thread yet.
Solution: I didn't have any important data on my device, so I did a Full Stock NVFlash with CWM v5.5.0.4 (Touch), then flashed AOKP (and cleared my cache) from CWM before I ever booted into the stock ROM.
I'm up and running now! I may have chosen a different path, but I appreciate the help.

colbymulkey said:
Solution: I didn't have any important data on my device, so I did a Full Stock NVFlash with CWM v5.5.0.4 (Touch), then flashed AOKP (and cleared my cache) from CWM before I ever booted into the stock ROM.
Click to expand...
Click to collapse
You mean you flashed AOKP and then booted into AOKP?
BTW, did you expand "system" to more that 250MB for AOKP?

rajeevvp said:
You mean you flashed AOKP and then booted into AOKP?
Click to expand...
Click to collapse
No. I couldn't get into CWM to flash AOKP directly. Instead, I used NVFlash to flash a package that was titled Full Stock NVFlash with CWM v5.5.0.4 (Touch). (I found it in a thread on these forums, but I can't seem to find that thread now.) I'm pretty sure this is what got my bootloader and CWM back in sync...
I never actually booted into the stock ROM that I NVFlashed though. Instead, I immediately:
went into recovery mode
USB-mounted the gTablet's internal SD card
dropped the AOKP ZIP onto my device's filesystem
flashed AOKP
cleared the devices cache using CMW
booted into AOKP
rajeevvp said:
BTW, did you expand "system" to more that 250MB for AOKP?
Click to expand...
Click to collapse
I did not expand my system partition, and I may be paying the price now. I've reflashed the gapps, and I can install APK's directly, but the Play Store won't update apps. I can browse the store; just can't update anything. (The app updates never time out or give me any errors, they just perpetually show as Update Available and/or Update in Progress.

colbymulkey said:
No. I couldn't get into CWM to flash AOKP directly. Instead, I used NVFlash to flash a package that was titled Full Stock NVFlash with CWM v5.5.0.4 (Touch).
Click to expand...
Click to collapse
That package would've made your system partition 256 MB in size.
I never actually booted into the stock ROM that I NVFlashed though. Instead, I immediately:
went into recovery mode
USB-mounted the gTablet's internal SD card
dropped the AOKP ZIP onto my device's filesystem
flashed AOKP
cleared the devices cache using CMW
booted into AOKP
Click to expand...
Click to collapse
That's what I thought: You booted directly into AOKP after flashing it.
I did not expand my system partition, and I may be paying the price now. I've reflashed the gapps, and I can install APK's directly, but the Play Store won't update apps. I can browse the store; just can't update anything. (The app updates never time out or give me any errors, they just perpetually show as Update Available and/or Update in Progress.
Click to expand...
Click to collapse
Since you've used the TeamDRH nvflash package, you should have a 256 MB system partition now, but, that will not be enough for AOKP which needs ~262 MB for everything. Most likely the Gapps would've all been copied, but, the face-detection bits would not all be there. This isn't an issue now because the camera isn't working.
Go back into CWM and do a "wipe data/factory reset". See if that clears your market problems.

rajeevvp said:
That package would've made your system partition 256 MB in size.
That's what I thought: You booted directly into AOKP after flashing it.Since you've used the TeamDRH nvflash package, you should have a 256 MB system partition now
Click to expand...
Click to collapse
There's probably a way to confirm this within CMW (or by utilizing APX+NVFlash), but I haven't verified it yet. Still, I suspect there would be major stability issues if my system partition were too undersized -- and while there's lag at times, I haven't experienced many system app crashes.
rajeevvp said:
That will not be enough for AOKP which needs ~262 MB for everything. Most likely the Gapps would've all been copied, but, the face-detection bits would not all be there. This isn't an issue now because the camera isn't working.
Click to expand...
Click to collapse
Face detection is of little interest to me on this device; not too worried about that. Still, I don't really see a problem with upping my system partition a few MB -- especially if it'll help future-proof the system. I'll check the other threads to see if there's a recommended size; not sure if I should set it at 262MB, or err on the side of caution and aim a little higher.
rajeevvp said:
Go back into CWM and do a "wipe data/factory reset". See if that clears your market problems.
Click to expand...
Click to collapse
I'll give the factory reset a shot and let you know if it works; may even attempt to repartition the system partition, just to make sure everything's kosher.
Thanks for recommendations!

colbymulkey said:
I'll give the factory reset a shot and let you know if it works...
Click to expand...
Click to collapse
The factory reset didn't fix my Play Store issues. I was going to settle on the Amazon AppStore as a work around, except I can't even seem to install the APK for the Amazon AppStore. It downloads, but I can't launch it directly from my notification tray, and it's not listed in the "Downloads" app.
I love AOKP on my SII, but I may flash another ROM to see if I find something that works a little better (for me) on my gTablet.
Thanks, again, for your help rajeevvp!

colbymulkey said:
There's probably a way to confirm this within CMW (or by utilizing APX+NVFlash), but I haven't verified it yet.
Click to expand...
Click to collapse
In CWM or in the ROM, run this dmesg command right after the system boots:
Code:
$ [B]dmesg | fgrep -i 'Kernel command line'[/B]
<5>[ 0.000000] Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 bspversion=0202100908 btmac=6037cf131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[B][email protected](system)[/B],[email protected](cache),[email protected](bootbmp),[email protected](logodata)
In APX mode, use the ``--getpartitiontable'' flag and look through it for the APP partition:
Code:
C:\> .[B]\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
Multiply the NumSectors and BytesPerSector parameters.
Still, I suspect there would be major stability issues if my system partition were too undersized -- and while there's lag at times, I haven't experienced many system app crashes.
Click to expand...
Click to collapse
Well, that depends. If critical bits have not been written then you will have immediate crashes or bootloops. OTOH, if unused files have not been written then you won't notice any problems until something attempts to use them. Going by what the AOKP ROM installation script does, the last thing to be written is the face-detection stuff as I said. This would account for your not noticing any major problems.
If you look at the /tmp/recovery.log file right after you install AOKP you'll be able to see precisely which files have not been copied owing to lack of space.
I'll check the other threads to see if there's a recommended size; not sure if I should set it at 262MB, or err on the side of caution and aim a little higher.
Click to expand...
Click to collapse
Go for 270 MB.

[Q] Need some help installing CMW

Heya. Trying to install CMW and it just isn't happening. First I tried the Rom Manager method, which failed. On reboot, I'd get the default menu, and if I try to use reinstall, it aborts installation. Upon reading more threads, everyone says to stay away from RM and just do it manually. So I go over to the CMW thread, and follow the instructions completely. And I just can't overwrite the "recovery" file no matter what I try.
First I tried the file manager in Super Manager, since I already had it and it was mentioned in another tutorial. It didn't give me any errors, but apparently it failed. File date didn't change and still can't boot CWM. Next, I tried Android Commander, via CMW thread's recommendation. It too, is unable to overwrite it. The programs console readout says it failed to copy the file, then the program spits out a memory access violation. I tried running AC as administrator and without. I tried click n drag or using the buttons to initiate the push. I tried enabling writing on the recovery file. No dice.
Yes, my phone is rooted. I even rooted it again just to make sure via SuperOneClick. AC says it has root access too. Sidekick 4g with everything stock. Android Commander was ran on a Win7 Ultimate 64 bit machine.
What should I try next?
Edit: In the meantime, downloading http://forum.xda-developers.com/showthread.php?t=1593065 , gonna see if it helps.
Edit2: Nvm, figured it out. Had to use Super Manager and turn on Root mode, and had to reboot several times to get Root mode to turn on *facepalm*. Running GenericGinger now and all is well.

tr0ubl3mak3r said:
Heya. Trying to install CMW and it just isn't happening. First I tried the Rom Manager method, which failed. On reboot, I'd get the default menu, and if I try to use reinstall, it aborts installation. Upon reading more threads, everyone says to stay away from RM and just do it manually. So I go over to the CMW thread, and follow the instructions completely. And I just can't overwrite the "recovery" file no matter what I try.
First I tried the file manager in Super Manager, since I already had it and it was mentioned in another tutorial. It didn't give me any errors, but apparently it failed. File date didn't change and still can't boot CWM. Next, I tried Android Commander, via CMW thread's recommendation. It too, is unable to overwrite it. The programs console readout says it failed to copy the file, then the program spits out a memory access violation. I tried running AC as administrator and without. I tried click n drag or using the buttons to initiate the push. I tried enabling writing on the recovery file. No dice.
Yes, my phone is rooted. I even rooted it again just to make sure via SuperOneClick. AC says it has root access too. Sidekick 4g with everything stock. Android Commander was ran on a Win7 Ultimate 64 bit machine.
What should I try next?
Edit: In the meantime, downloading http://forum.xda-developers.com/showthread.php?t=1593065 , gonna see if it helps.
Edit2: Nvm, figured it out. Had to use Super Manager and turn on Root mode, and had to reboot several times to get Root mode to turn on *facepalm*. Running GenericGinger now and all is well.
Click to expand...
Click to collapse
Supermanager? Anyways, glad to see you are enjoying GG 3.7.

JiN1337 said:
Supermanager? Anyways, glad to see you are enjoying GG 3.7.
Click to expand...
Click to collapse
Yep. Super Manager has a whole bunch of useful tools, including a file manager with root access. And it's free.
And GG 3.7 is awesome.

Odin stuck at "recovery.img" on Tab 2 10.1

Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan

SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.

If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.

Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:

SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan

SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.

Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.

SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan

SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!

I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx

MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc

Problem trying to root with CASUAL

Alright other people have been saying it is working on windows so I decided to try it out. I installed the Samsung drivers and installed the java jdk. When I run it and click "Do it" for the Root GS3 with DebugFSRoot option my phone reboots and all I get is this and it just sits there....
Step 1 - Setup...
Copying files:
Copying su:3020 KB/s (380532 bytes in 0.123s)
Copying debugfs:3455 KB/s (1862336 bytes in 0.526s)
Copying debugfsinput:47 KB/s (144 bytes in 0.002s)
...done copying files.
Linking /system to tmp...
...done linking /system
Rebooting...
Step 2 - Rooting...* server not running ** daemon not running. starting it now on port 5037 *
* daemon started successfully *
Any help?

I had the same issue so I went with this method
http://forum.xda-developers.com/showthread.php?t=1792342

slick_shoes said:
I had the same issue so I went with this method
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
Went through the whole process for the other one too and the cmd window even showed that I had root but my phone still wont let me use rooted apps even after a reboot.

*facepalm* Had to restart my computer. 2nd method worked like a charm!

Just downlod ez unlocker in the app store it a app to unlock one touch and it was updated today to have a relock feature!
Sent from my SCH-I535 using Tapatalk 2

tonytownsend said:
Just downlod ez unlocker in the app store it a app to unlock one touch and it was updated today to have a relock feature!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
That doesn't root which is what the op was trying to do.

slick_shoes said:
I had the same issue so I went with this method
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
Ditto here.

+1 on the EZ unlocked. Couldn't be any easier than that.

RE: Casual R131. "You just download it, connect your Galaxy S III, launch the tool". Ok, I'm a NOOB to android. What tool?
In windows or linux, once you download, I take it you decompress.
Then what exactly do we do? Open a command prompt in Win? Then run what?
Same for Linux, run what from what. Just launch the tool is too vague for us newbees.
Understand the setup of this just fine. Not the execution.
Your help is appreciated.

I ran into the same issue. I clicked Do It again after waiting there for a few minutes. It restarted the process. When you get to step 2, wait for the device to be Connected before clicking okay. Worked like a charm.

meekell said:
I ran into the same issue. I clicked Do It again after waiting there for a few minutes. It restarted the process. When you get to step 2, wait for the device to be Connected before clicking okay. Worked like a charm.
Click to expand...
Click to collapse
This is what I had to do. I just repeated this a couple times until su worked.
Sent from my Nexus 7 using Tapatalk 2